Narrative:

I came back from break and the operational supervisor (os) asked me to d-side at sector 84 as we were with no warning placed into the hold for ord. After the 3rd aircraft was issued and entered the holding stack; I called to G52 (bradford sector) and asked if they could advance a couple of our guys as we were holding 7 aircraft between 84 and 94 (high/super high). The bdf controller said he couldn't take any as weather was encroaching the holding pattern in his airspace. The weather he was talking about was in our airspace; but extended well into ours at the next sector west of ours (sector 32/92). The bdf controller asked us to hold aircraft on the backside of the front. A large majority of east-west traffic was deviating into our sectors to get around the weather. Plus the sector to the west is a completely different RNAV arrival into ord. We could clearly see that the G52 controller was holding 2 aircraft both at bdf VORTAC one at FL240 and the other at FL250. He ended the shoutline request with I'll ask my os and see what he can do. Within 2 mins we were allowed to advance aircraft with a 250kts assigned 20 miles-in-trail (mit) single stream. Not two hours after this event the G52 controller again with no warning or reason called the shoutline and said you're shut off for O'hare again he was holding none. I'm sure there is tension from C90 and ZAU; but the pushback to us is ridiculous. The controller has for some time been in many shouting matches with ZKC controllers of small arguments. I am personally tired of his antics as with his actions he is introducing more risk than needed into the NAS. We have tried back channel communications with ZAU and this gentleman continues his non-professional; non-conforming attitude to the shoutline between facilities. Lastly after a new arrival route/playbook was put into play there was one aircraft that informed us that he would not have enough fuel to accept the reroute with any additional delays. I called back up to the G52 controller to see if they could sneak that plane in as all aircraft that were coming from the southwest corner post were now going to the southeast post. To which a no came across the line. I get it ZKC is like a red headed stepchild. We have no major hubs we only feed centers that do. We have a ton of mit and sequencing that goes on and the men and women at this facility show the greatest amount of professionalism when having to deal with those requirements. However controllers are controllers. I understand that major facilities are set up for canned procedures; i.e. Arrival areas and departure areas. That is fine when operations are normal day to day ops; but when things go non-standard then it is as though those individuals are unable to say the opposite of what it is they normally do.the controllers of ZAU and specifically at G52 need a reality check and need to understand the impact on safety when they pose on us when they unable to assist.

Google
 

Original NASA ASRS Text

Title: ZKC controller reported continual conflicts with ZAU; and one specific controller; over coordination of holding enroute aircraft.

Narrative: I came back from break and the Operational Supervisor (OS) asked me to D-side at sector 84 as we were with no warning placed into the hold for ORD. After the 3rd Aircraft was issued and entered the holding stack; I called to G52 (Bradford Sector) and asked if they could advance a couple of our guys as we were holding 7 Aircraft between 84 and 94 (High/Super High). The BDF controller said he couldn't take any as weather was encroaching the holding pattern in his airspace. The weather he was talking about was in our airspace; but extended well into ours at the next sector west of ours (Sector 32/92). The BDF controller asked us to hold Aircraft on the backside of the front. A large majority of East-West traffic was deviating into our sectors to get around the weather. Plus the sector to the west is a completely different RNAV arrival into ORD. We could clearly see that the G52 controller was holding 2 Aircraft both at BDF VORTAC one at FL240 and the other at FL250. He ended the shoutline request with I'll ask my OS and see what he can do. Within 2 mins we were allowed to advance Aircraft with a 250kts assigned 20 Miles-in-Trail (MIT) single stream. Not two hours after this event the G52 controller again with no warning or reason called the shoutline and said you're shut off for O'Hare again he was holding none. I'm sure there is tension from C90 and ZAU; but the pushback to us is ridiculous. The controller has for some time been in many shouting matches with ZKC controllers of small arguments. I am personally tired of his antics as with his actions he is introducing more risk than needed into the NAS. We have tried back channel communications with ZAU and this gentleman continues his non-professional; non-conforming attitude to the shoutline between facilities. Lastly after a new arrival route/playbook was put into play there was one Aircraft that informed us that he would not have enough fuel to accept the reroute with any additional delays. I called back up to the G52 controller to see if they could sneak that plane in as all Aircraft that were coming from the SW corner post were now going to the Southeast post. To which a NO came across the line. I get it ZKC is like a red headed stepchild. We have no major hubs we only feed centers that do. We have a ton of MIT and sequencing that goes on and the men and women at this facility show the greatest amount of professionalism when having to deal with those requirements. However controllers are controllers. I understand that major facilities are set up for canned procedures; i.e. arrival areas and departure areas. That is fine when operations are normal day to day ops; but when things go non-standard then it is as though those individuals are unable to say the opposite of what it is they normally do.The controllers of ZAU and specifically at G52 need a reality check and need to understand the impact on Safety when they pose on us when they unable to assist.

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.