37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1428064 |
Time | |
Date | 201703 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | ZAU.ARTCC |
State Reference | IL |
Environment | |
Light | Night |
Aircraft 1 | |
Make Model Name | Large Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 121 |
Flight Phase | Climb |
Route In Use | Vectors |
Flight Plan | IFR |
Person 1 | |
Function | Enroute |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 7 |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types Inflight Event / Encounter Weather / Turbulence |
Narrative:
Aircraft X was on a westbound heading at 110 parallel to the south of a thunderstorm affecting C90 and ord. Aircraft was traveling inbound to ord and was attempting to find a gap in the storm to proceed north to get to the field. The sector I was working (43/44) works C90 southbound departures; that are delivered climbing to 15000. C90 arrival controller called me regarding aircraft X who I had observed traveling just north of my boundary. They wanted to coordinate the aircraft on a 210 heading climbing to 10000 saying that he wasn't going to get through and would need to divert to an alternate airport. Also he said he needed to get him out of his airspace before he became a problem.I only own 11000 and above; so I agreed to coordinate with sector below me to try and help them out. I know there were a lot of diverts earlier in the evening; so I thought this was just another one of many. When the aircraft checked on I climbed him into my airspace and queried them as to what divert/alternate airport they selected. The flight crew advised they didn't want to divert; they had plenty of fuel and wanted to attempt to get in to ord. At this point the aircraft was well established on a 210 heading and pointed away from ord and the referenced weather. There was no longer any way for aircraft X to see the weather on their onboard radar since it was well outside of their line of sight; and there was no practical way to point the aircraft back in that direction.the C90 controller was at best not forthcoming with the entire story; and at worst; dishonest. From my perspective and the information I have available; they chose not to discuss any of these options; their plan; or the reason for the vector with the pilots of aircraft X. While the C90 controller made it sound like the aircraft was aware and working on a plan to divert; it was very clear when I asked the pilot that they hadn't yet thought about or been told about a plan to divert. Furthermore; I called back to C90 arrivals and advised them that aircraft X did not want to divert; to which he responded that I 'make bearz [sector 35] eat 'em'; who apparently was the controller that handed off aircraft X to C90. After heading southwest bound for 50-60 miles with no way to safely make it to the backside of the storm; aircraft X had to divert.given the weather; it is very likely that the aircraft wasn't going to be able to make it in to ord. However; it is unsafe and unprofessional for a controller to vector an aircraft out of their airspace while not advising the pilot of the intentions. They took away the aircrafts ability to safely observe and judge the weather to make an informed decision; and forced their hand the other way. The controller admitted on the line that they thought he was going to just be 'a problem'.as controllers; we should do all we can to help aircraft safely navigate convective activity. Sometimes; this may involve advising the pilot that we cannot safely let them continue further; and that we need to move them away from the weather; and possibly even clear them to an alternate airport. However; this all requires the controller to advise the aircraft of their intentions. Controllers should not arbitrarily divert an aircraft based on an unwillingness to be bothered. Additionally; communication needs to be clear an honest. I was told an aircraft was working on an alternate; when they were clearly not. Lying during controller to controller coordination is a major safety risk; but at least unprofessional. Both items should be briefed as to their severity in nature.
Original NASA ASRS Text
Title: ZAU Center Controller reported that a C90 TRACON Controller advised the Center Controller that an aircraft wanted to divert. The pilot never wanted to divert and the reporting Controller advised that the TRACON Controller was not helpful nor honest.
Narrative: Aircraft X was on a westbound heading at 110 parallel to the south of a thunderstorm affecting C90 and ORD. Aircraft was traveling inbound to ORD and was attempting to find a gap in the storm to proceed north to get to the field. The sector I was working (43/44) works C90 southbound departures; that are delivered climbing to 15000. C90 arrival controller called me regarding Aircraft X who I had observed traveling just north of my boundary. They wanted to coordinate the aircraft on a 210 heading climbing to 10000 saying that he wasn't going to get through and would need to divert to an alternate airport. Also he said he needed to get him out of his airspace before he became a problem.I only own 11000 and above; so I agreed to coordinate with sector below me to try and help them out. I know there were a lot of diverts earlier in the evening; so I thought this was just another one of many. When the aircraft checked on I climbed him into my airspace and queried them as to what divert/alternate airport they selected. The flight crew advised they didn't want to divert; they had plenty of fuel and wanted to attempt to get in to ORD. At this point the aircraft was well established on a 210 heading and pointed away from ORD and the referenced weather. There was no longer any way for Aircraft X to see the weather on their onboard radar since it was well outside of their line of sight; and there was no practical way to point the aircraft back in that direction.The C90 controller was at best not forthcoming with the entire story; and at worst; dishonest. From my perspective and the information I have available; they chose not to discuss any of these options; their plan; or the reason for the vector with the pilots of Aircraft X. While the C90 controller made it sound like the aircraft was aware and working on a plan to divert; it was very clear when I asked the pilot that they hadn't yet thought about or been told about a plan to divert. Furthermore; I called back to C90 arrivals and advised them that Aircraft X did not want to divert; to which he responded that I 'make Bearz [sector 35] eat 'em'; who apparently was the controller that handed off Aircraft X to C90. After heading southwest bound for 50-60 miles with no way to safely make it to the backside of the storm; Aircraft X had to divert.Given the weather; it is very likely that the aircraft wasn't going to be able to make it in to ORD. However; it is unsafe and unprofessional for a controller to vector an aircraft out of their airspace while not advising the pilot of the intentions. They took away the aircrafts ability to safely observe and judge the weather to make an informed decision; and forced their hand the other way. The controller admitted on the line that they thought he was going to just be 'a problem'.As controllers; we should do all we can to help aircraft safely navigate convective activity. Sometimes; this may involve advising the pilot that we cannot safely let them continue further; and that we need to move them away from the weather; and possibly even clear them to an alternate airport. However; this all requires the controller to advise the aircraft of their intentions. Controllers should not arbitrarily divert an aircraft based on an unwillingness to be bothered. Additionally; communication needs to be clear an honest. I was told an aircraft was working on an alternate; when they were clearly not. Lying during controller to controller coordination is a major safety risk; but at least unprofessional. Both items should be briefed as to their severity in nature.
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.