37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1592683 |
Time | |
Date | 201811 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | ZAB.ARTCC |
State Reference | NM |
Aircraft 1 | |
Make Model Name | Small Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 91 |
Flight Phase | Cruise |
Flight Plan | IFR |
Person 1 | |
Function | Enroute |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 19 |
Events | |
Anomaly | ATC Issue All Types Airspace Violation All Types Deviation - Procedural Published Material / Policy |
Narrative:
Per LOA with phx approach; aircraft on the jesse arrival can be blended/stacked with eagul arrivals. Controller in phx approach had already asked me to pull out 1 jesse arrival if the inbound stream which I complied with. His communication was rude and vague. The aircraft mentioned above were coordinated with the apache sector controller. I coordinated descending to 140 and 250 knots to protect for aircraft X. The rude controller responded 'what am I gonna do with that?' I told him I had no idea because I don't work in that facility but I was complying with the letter. He told me he wasn't going to accept the handoff and to spin him. I told him I wasn't going to spin him; that I had numerous eagul arrivals in the stream behind him and that he needed to take the handoff. He told me no; he wasn't going accept the aircraft and to spin him. I told him I absolutely was not going to spin the aircraft unnecessarily. I hung up [and] waited for him to accept the hand off which he didn't do. I called him back and told him he needed to take the hand off and comply with the letter and he refused. I decided instead of risking safety of flight for all aircraft on the eagul behind him due to this controller's lack of ability or understanding of facility agreement letters; I would let the aircraft continue. At no time was safety compromised. I shipped the aircraft to phoenix approach control without a handoff. I would address the issue at the TRACON level. It's been an ongoing issue with P50 and ZAB.
Original NASA ASRS Text
Title: Albuquerque Center Controller reported an airspace deviation due to unprofessional Phoenix TRACON Controller not accepting the aircraft.
Narrative: Per LOA with PHX Approach; aircraft on the Jesse Arrival can be blended/stacked with EAGUL Arrivals. Controller in PHX Approach had already asked me to pull out 1 Jesse arrival if the inbound stream which I complied with. His communication was rude and vague. The aircraft mentioned above were coordinated with the Apache Sector Controller. I coordinated descending to 140 and 250 knots to protect for Aircraft X. The rude controller responded 'What am I gonna do with that?' I told him I had no idea because I don't work in that facility but I was complying with the letter. He told me he wasn't going to accept the handoff and to spin him. I told him I wasn't going to spin him; that I had numerous EAGUL arrivals in the stream behind him and that he needed to take the handoff. He told me no; he wasn't going accept the aircraft and to spin him. I told him I absolutely was not going to spin the aircraft unnecessarily. I hung up [and] waited for him to accept the hand off which he didn't do. I called him back and told him he needed to take the hand off and comply with the letter and he refused. I decided instead of risking safety of flight for all aircraft on the EAGUL behind him due to this controller's lack of ability or understanding of facility agreement letters; I would let the aircraft continue. At no time was safety compromised. I shipped the aircraft to Phoenix Approach Control without a handoff. I would address the issue at the TRACON level. It's been an ongoing issue with P50 and ZAB.
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.