Narrative:

Looth and bearz were on a west flow. C90 was taking handoffs inside of the prise way point; this does not allow the bearz controller sufficient time; or room; to turn and avoid an airspace deviation. With this in mind; we are hesitant to offload arrivals from royko to watsn; as C90 accused bearz of having 3 airspace deviations recently. Fewer planes over warsn means fewer opportunities for deviations. If the bearz controller is focused solely on making sure C90 takes handoffs in a timely manner; that controller's ability to accept any additional volume is compromised. Historically; C90 has routinely accepted handoffs on the watsn stream more than 10 miles outside of prise. I was working looth; rerouting few royko arrivals to the watsn stream. I had four arrivals; between 10 and 15 miles in trail. With absolutely no demand from the southwest or northwest fixes; C90 slowed me from 250 to 210 KTS; then my supervisor came and changed my in trail from 10 to 15 miles. I asked when that was to start; he said between planes 2 and 3. I hesitated; but commenced vectoring plane 3 after ensuring the appropriate point out was made. As plane 2 approached the ZAU; C90 boundary; I called C90 for the handoff and the response was 'I was waiting for my 15 miles.' more point outs ensued; I vectored plane 2 and 4 to provide the additional unneeded in trail; then called C90 again that plane 2 (who was approaching the boundary for a second time; C90 had the handoff) would turn direct looth shortly. The new controller said direct ord; and go to 250 KTS; very shortly thereafter; the supervisor at C90 called our area desk; offering that bearz sector assume control for additional airspace along the watsn arrival up to dweed. The idea the ZAU would take this airspace sets a new standard for idiocy. I cannot imagine anyone being comfortable accepting new airspace with no training; no map to display the new airspace; and no procedures. Recommendation; C90 has been jumping through hoops showing us they cannot see aircraft outside prise; and cannot thus accept handoffs in a timely fashion when on the watsn arrival. C90 also has a history of accepting handoffs well outside prise. They need to operate such that they can; and do; accept handoffs in sufficient time or abandon the watsn arrival. If C90 cannot accept handoffs more than 10 miles outside prise; all ord arrivals formerly routed via the WATSN1 should be cleared esspo direct ord; or a procedure should be developed that C90 will accept all watsn arrivals; with the appropriate in trail; inside the mkita way point. They assure us they'll accept these aircraft. They routinely say 'keep 'em coming; I can't see him yet.' if that's the case and they want to shirk their responsibility to accept handoffs in a timely fashion; absolve us of our responsibility to ensure the handoffs are completed.

Related reports:

Google
 

Original NASA ASRS Text

Title: ZAU Controller voiced concern regarding C90's failure to accept handoffs in a timely fashion on the WATSN arrival route. Controller suggested alternative procedures be developed.

Narrative: Looth and Bearz were on a west flow. C90 was taking handoffs inside of the PRISE way point; this does not allow the Bearz Controller sufficient time; or room; to turn and avoid an airspace deviation. With this in mind; we are hesitant to offload arrivals from ROYKO to WATSN; as C90 accused Bearz of having 3 airspace deviations recently. Fewer planes over WARSN means fewer opportunities for deviations. If the Bearz Controller is focused solely on making sure C90 takes handoffs in a timely manner; that Controller's ability to accept any additional volume is compromised. Historically; C90 has routinely accepted handoffs on the WATSN stream more than 10 miles outside of PRISE. I was working Looth; rerouting few ROYKO arrivals to the WATSN stream. I had four arrivals; between 10 and 15 miles in trail. With absolutely no demand from the southwest or northwest fixes; C90 slowed me from 250 to 210 KTS; then my Supervisor came and changed my in trail from 10 to 15 miles. I asked when that was to start; he said between planes 2 and 3. I hesitated; but commenced vectoring plane 3 after ensuring the appropriate point out was made. As plane 2 approached the ZAU; C90 boundary; I called C90 for the handoff and the response was 'I was waiting for my 15 miles.' More point outs ensued; I vectored plane 2 and 4 to provide the additional unneeded in trail; then called C90 again that plane 2 (who was approaching the boundary for a second time; C90 had the handoff) would turn direct Looth shortly. The new Controller said direct ORD; and go to 250 KTS; very shortly thereafter; the Supervisor at C90 called our area desk; offering that Bearz Sector assume control for additional airspace along the WATSN arrival up to DWEED. The idea the ZAU would take this airspace sets a new standard for idiocy. I cannot imagine anyone being comfortable accepting new airspace with no training; no map to display the new airspace; and no procedures. Recommendation; C90 has been jumping through hoops showing us they cannot see aircraft outside PRISE; and cannot thus accept handoffs in a timely fashion when on the WATSN arrival. C90 also has a history of accepting handoffs well outside PRISE. They need to operate such that they can; and do; accept handoffs in sufficient time or abandon the WATSN arrival. If C90 cannot accept handoffs more than 10 miles outside PRISE; all ORD arrivals formerly routed via the WATSN1 should be cleared ESSPO direct ORD; or a procedure should be developed that C90 will accept all WATSN arrivals; with the appropriate in trail; inside the MKITA way point. They assure us they'll accept these aircraft. They routinely say 'keep 'em coming; I can't see him yet.' If that's the case and they want to shirk their responsibility to accept handoffs in a timely fashion; absolve us of our responsibility to ensure the handoffs are completed.

Data retrieved from NASA's ASRS site as of April 2012 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.