37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1181357 |
Time | |
Date | 201406 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | P50.TRACON |
State Reference | AZ |
Environment | |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Medium Large Transport |
Operating Under FAR Part | Part 121 |
Flight Phase | Descent |
Route In Use | STAR Kooly4 |
Flight Plan | IFR |
Person 1 | |
Function | Approach |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 15 |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy Deviation - Speed All Types |
Narrative:
Once again ZAB has assigned airspeed to an aircraft and then transferred communications without advising the receiving controller. Aircraft X reported on my frequency and advised he was 290 KTS until squez; which is on the P50/ZAB boundary line. Aircraft X was descending via the KOOLY4 arrival (RNAV) and the published speed at squez is 250 KTS. The ZAB/P50 LOA states that ZAB must issue descend via (dv) clearance with runway transition (if applicable) on RNAV stars. In appendix east it states that ZAB must cross squez at 250 KTS. Faao 7110.65 5-4-5 states for the transferring controller must advise the receiving controller of pertinent information not contained in the data block or flight progress strip unless covered in a LOA or facility directive. Pertinent information includes: 1. Assigned heading. 2. Airspeed restrictions. 3. Altitude information issued. 4. Observed track or deviation from the last route clearance. 5. The beacon code if different from that normally used or previously coordinated. 6. Any other pertinent information.in this case ZAB did not comply with the LOA and faao 7110.65. Personally I have sent in reports on this before and there are numerous reports filed by pilots flying into phoenix that complain about ZAB and how they assign speeds contrary to what is published. In this case; it was the end of the push and ZAB46 had just two aircraft; aircraft X and an [another jet] following him by 10 miles. When I called; ZAB controller was not very courteous and I was just trying to discuss the speeds assigned and it appeared the pilot was confused as well how to meet what was issued. The ZAB controller offered to pull the tapes and mail them to me. ZAB routinely assigns faster than normal speed to a fix on the ZAB/P50 boundary and do not coordinate them in accordance with directives. This has been a problem for years; help us stop this problem between the facilities. Have ZAB coordinate the assigned speed; which is required by faao 7110.65 or comply with the LOA. This is not an isolated incident with this area either; all four sectors that feed P50 do this.
Original NASA ASRS Text
Title: P50 Controller describes situation where ZAB controllers do not advise him of a different speed that has been assigned.
Narrative: Once again ZAB has assigned airspeed to an aircraft and then transferred communications without advising the receiving Controller. Aircraft X reported on my frequency and advised he was 290 KTS until SQUEZ; which is on the P50/ZAB boundary line. Aircraft X was descending via the KOOLY4 Arrival (RNAV) and the published speed at SQUEZ is 250 KTS. The ZAB/P50 LOA states that ZAB must issue descend via (DV) clearance with runway transition (if applicable) on RNAV STARs. In Appendix E it states that ZAB must cross SQUEZ at 250 KTS. FAAO 7110.65 5-4-5 states for the transferring Controller must advise the receiving Controller of pertinent information not contained in the data block or flight progress strip unless covered in a LOA or facility directive. Pertinent information includes: 1. Assigned heading. 2. Airspeed restrictions. 3. Altitude information issued. 4. Observed track or deviation from the last route clearance. 5. The beacon code if different from that normally used or previously coordinated. 6. Any other pertinent information.In this case ZAB did not comply with the LOA and FAAO 7110.65. Personally I have sent in reports on this before and there are numerous reports filed by pilots flying into Phoenix that complain about ZAB and how they assign speeds contrary to what is published. In this case; it was the end of the push and ZAB46 had just two aircraft; Aircraft X and an [another jet] following him by 10 miles. When I called; ZAB Controller was not very courteous and I was just trying to discuss the speeds assigned and it appeared the pilot was confused as well how to meet what was issued. The ZAB Controller offered to pull the tapes and mail them to me. ZAB routinely assigns faster than normal speed to a fix on the ZAB/P50 boundary and do not coordinate them in accordance with directives. This has been a problem for years; help us stop this problem between the facilities. Have ZAB coordinate the assigned speed; which is required by FAAO 7110.65 or comply with the LOA. This is not an isolated incident with this area either; all four sectors that feed P50 do this.
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.