 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A P50 controller described a loss of separation event noting the facility pre-arranged coordination procedures are not being completed as required.
| Attributes | |
| ACN | 1014917 |
| Time | |
| Date | 201206 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | P50.TRACON |
| State Reference | AZ |
| Aircraft 1 | |
| Make Model Name | B737 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Descent |
| Route In Use | STAR EAGUL |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | B737 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Climb |
| Route In Use | Vectors SID CHILY1 |
| Flight Plan | IFR |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy |
Narrative:
Once again prearranged coordination procedures were not complied with and an operational error may have occurred. I had just walked into the TRACON after a break and was signing back on position when I heard apache yell at navajo 'way to go navajo; what the hell.' B737 was descending via the eagul RNAV STAR and another B737 was climbing to FL210; on vectors for the CHILY1 departure. When I heard him yell; I looked and the two aircraft were less than 1;000 ft and three miles apart. I assume that visual separation; if in use; was not coordinated with apache by navajo; which is a requirement by the .65 and P50 SOP. There was a relief briefing overlap in progress at navajo; and this still occurred. The facility needs to address the use of prearranged coordination procedures. These procedures are violated all the time; especially the use of visual separation. The departure controller is required to advise the arrival controller of its use; so the other aircraft can be advised; but it never occurs. Brief; retrain; redesign or abandon these procedures if they are not going to be used properly.
Original NASA ASRS Text
Title: A P50 Controller described a loss of separation event noting the facility pre-arranged coordination procedures are not being completed as required.
Narrative: Once again prearranged coordination procedures were not complied with and an operational error may have occurred. I had just walked into the TRACON after a break and was signing back on position when I heard Apache yell at Navajo 'way to go Navajo; what the hell.' B737 was descending via the EAGUL RNAV STAR and another B737 was climbing to FL210; on vectors for the CHILY1 departure. When I heard him yell; I looked and the two aircraft were less than 1;000 FT and three miles apart. I assume that visual separation; if in use; was not coordinated with Apache by Navajo; which is a requirement by the .65 and P50 SOP. There was a relief briefing overlap in progress at Navajo; and this still occurred. The facility needs to address the use of prearranged coordination procedures. These procedures are violated all the time; especially the use of visual separation. The Departure Controller is required to advise the Arrival Controller of its use; so the other aircraft can be advised; but it never occurs. Brief; retrain; redesign or abandon these procedures if they are not going to be used properly.
Data retrieved from NASA's ASRS site as of July 2013 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.