37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1704744 |
Time | |
Date | 201911 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | ZKC.ARTCC |
State Reference | KS |
Aircraft 1 | |
Make Model Name | B737-800 |
Operating Under FAR Part | Part 121 |
Flight Phase | Cruise |
Route In Use | Direct |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | B737 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | Cruise |
Route In Use | Direct |
Flight Plan | IFR |
Person 1 | |
Function | Enroute |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 3.5 |
Events | |
Anomaly | ATC Issue All Types Airspace Violation All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy |
Narrative:
Aircraft X was in my airspace and on my frequency eastbound at 35000 ft. He had just been transferred from ZDV sector 17 and was only about 15 miles into my airspace. ZDV sector 17 initiated an automated point out for aircraft Y at 35000 ft. And initiated a radar handoff with ZKC sector 24 eastbound in direct conflict with aircraft X. I used the landline and called ZDV 17 and requested aircraft Y turned 30 degrees to the right. He cheerfully said he would. ZKC sector 24 shortly thereafter took the handoff which did not have any fourth line data indicating the turn. I did not approve the point out for aircraft Y. Someone then entered runway 30R in the fourth line data. I used the quick look function and saw that ZDV had already transferred communications for aircraft Y to ZKC sector 24 even though no coordination had been accomplished with me for aircraft Y to transition my airspace without a transfer of communication. I called ZKC 24 and asked if he was talking with aircraft Y. He said that he was and I asked him if he would 'fix it because that's not going to work.' I knew the 30 degrees probably wasn't enough but I wanted to get his turn started before deciding how much further the aircraft needed turned. ZKC 24 ended up using another 20 degrees of turns for a total of 60 degrees to ensure the aircraft did not have a midair collision. ZDV handing off deals to ZKC is a daily occurrence. I tried to resolve the conflict but was not able to because I did not have communications with the aircraft entering my airspace without permission. When I called ZDV; I could have said radar contact which may have alleviated the situation. I never heard ZDV call ZKC sector 24 so I believe ZDV 17 violated ZKC 24 as well by turning an aircraft they had the handoff on without prior coordination. This was an extremely unsafe situation that was totally avoidable; which is what I attempted to do. At no point was ZDV given permission to enter my airspace without a transfer of radio communication for [company]. I recommend the controller be de-certified so that they can learn how air traffic functions and to prevent a collision in the NAS. Everything else we have tried to get through to them on not transferring communications/radar of an aircraft until known conflicts are resolved has not worked. I don't want it to take a mid-air collision before someone gets serious and makes that specific ZDV area understand the rules as stated in the faao but I feel like that's where we are at. I just hope it isn't under my watch because I have lost hope in the NAS identifying an extremely unsafe trend and mitigating the risk.
Original NASA ASRS Text
Title: A Center Controller reported the adjacent Center sector handed them off two aircraft on converging headings at the same altitude and stated this is a repeat problem between these two facilities.
Narrative: Aircraft X was in my airspace and on my frequency eastbound at 35000 ft. He had just been transferred from ZDV Sector 17 and was only about 15 miles into my airspace. ZDV Sector 17 initiated an automated point out for Aircraft Y at 35000 ft. and initiated a radar handoff with ZKC Sector 24 eastbound in direct conflict with Aircraft X. I used the landline and called ZDV 17 and requested Aircraft Y turned 30 degrees to the right. He cheerfully said he would. ZKC Sector 24 shortly thereafter took the handoff which did not have any fourth line data indicating the turn. I did not approve the point out for Aircraft Y. Someone then entered Runway 30R in the fourth line data. I used the quick look function and saw that ZDV had already transferred communications for Aircraft Y to ZKC Sector 24 even though no coordination had been accomplished with me for Aircraft Y to transition my airspace without a transfer of communication. I called ZKC 24 and asked if he was talking with Aircraft Y. He said that he was and I asked him if he would 'fix it because that's not going to work.' I knew the 30 degrees probably wasn't enough but I wanted to get his turn started before deciding how much further the aircraft needed turned. ZKC 24 ended up using another 20 degrees of turns for a total of 60 degrees to ensure the aircraft did not have a midair collision. ZDV handing off deals to ZKC is a DAILY occurrence. I tried to resolve the conflict but was not able to because I did not have communications with the aircraft entering my airspace without permission. When I called ZDV; I could have said Radar Contact which may have alleviated the situation. I never heard ZDV call ZKC Sector 24 so I believe ZDV 17 violated ZKC 24 as well by turning an aircraft they had the handoff on without prior coordination. This was an extremely unsafe situation that was totally avoidable; which is what I attempted to do. At no point was ZDV given permission to enter my airspace without a transfer of radio communication for [Company]. I recommend the Controller be de-certified so that they can learn how Air Traffic functions and to prevent a collision in the NAS. Everything else we have tried to get through to them on not transferring communications/radar of an aircraft until known conflicts are resolved has not worked. I don't want it to take a mid-air collision before someone gets serious and makes that specific ZDV area understand the rules as stated in the FAAO but I feel like that's where we are at. I just hope it isn't under my watch because I have lost hope in the NAS identifying an extremely unsafe trend and mitigating the risk.
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.