Narrative:

There is a procedure in place for gyy arrivals with a portion of it having too steep of a descent for aircraft to comply. The route is supposed to be poogy cooks with the rbs 45 sector crossing 10 NM south of poogy at FL240 then cooks at 17;000 ft. My airspace lies between FL230 and cooks at 17;000 ft; so I am dependent on the sector before [mine] to meet their restriction and transfer communication in time to issue the cooks at 17;000 ft crossing. There is approximately 25 miles for aircraft to descend 7;000 ft. A factor that makes this more challenging is aircraft usually have a tailwind on the heading to cooks. Today; aircraft X was cleared direct cooks by the previous sector; did not apreq [approval request] direct cooks and was too high to make the crossing at cooks. When I received communications with aircraft X; had less than 10 NM to make the crossing. I was forced coordinate aircraft X descending with the next sector beginning just after cooks. Coincidentally; upon communications transfer to sector newtt/eon 43/44; the aircraft did not respond and was NORDO[no radio]. Communication with aircraft X was reestablished well inside newtt/eon 43/44 airspace without incident.the rbs sector failed to coordinate the aircraft not meeting the SOP. The SOP route and altitude restriction is not feasible for aircraft to fly when the SOP restrictions are made. The procedure should be designed to go from rbs 45 to newtt/eon 43/44. A route of rbs lucit would move the gyy aircraft further south; which would aid 43/44 in missing their south departure traffic. It would be a more direct route and it would stay in one area rather than go from the south area; the southwest area; then back to the south area. The descent profile should be shallowed out with rbs 45 getting aircraft to FL240 earlier to account for any traffic situations between FL240 and 17;000 ft.

Google
 

Original NASA ASRS Text

Title: ZAU Controller reports of an aircraft coming in high from a previous sector during handoff which resulted in a missed crossing restriction and an increase in controller workload. The enroute Controller makes recommendations on how to remedy the situation.

Narrative: There is a procedure in place for GYY arrivals with a portion of it having too steep of a descent for aircraft to comply. The route is supposed to be POOGY COOKS with the RBS 45 sector crossing 10 NM S of POOGY at FL240 then COOKS at 17;000 FT. My airspace lies between FL230 and COOKS at 17;000 FT; so I am dependent on the sector before [mine] to meet their restriction and transfer communication in time to issue the COOKS at 17;000 FT crossing. There is approximately 25 miles for aircraft to descend 7;000 FT. A factor that makes this more challenging is aircraft usually have a tailwind on the heading to COOKS. Today; Aircraft X was cleared direct COOKS by the previous sector; did not APREQ [Approval Request] direct COOKS and was too high to make the crossing at COOKS. When I received communications with Aircraft X; had less than 10 NM to make the crossing. I was forced coordinate Aircraft X descending with the next sector beginning just after COOKS. Coincidentally; upon communications transfer to Sector NEWTT/EON 43/44; the aircraft did not respond and was NORDO[No Radio]. Communication with Aircraft X was reestablished well inside NEWTT/EON 43/44 airspace without incident.The RBS sector failed to coordinate the aircraft not meeting the SOP. The SOP route and altitude restriction is not feasible for aircraft to fly when the SOP restrictions are made. The procedure should be designed to go from RBS 45 to NEWTT/EON 43/44. A route of RBS LUCIT would move the GYY aircraft further South; which would aid 43/44 in missing their South departure traffic. It would be a more direct route and it would stay in one area rather than go from the South Area; the Southwest Area; then back to the South Area. The descent profile should be shallowed out with RBS 45 getting aircraft to FL240 earlier to account for any traffic situations between FL240 and 17;000 FT.

Data retrieved from NASA's ASRS site and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.