 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Albuquerque center controller reported a loss of separation in tucson approach airspace.
| Attributes | |
| ACN | 1415048 |
| Time | |
| Date | 201701 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | ZAB.ARTCC |
| State Reference | NM |
| Aircraft 1 | |
| Make Model Name | Fighter |
| Flight Phase | Cruise |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | Fighter |
| Person 1 | |
| Function | Enroute |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 13.5 |
| Events | |
| Anomaly | ATC Issue All Types Airspace Violation All Types Conflict Airborne Conflict Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy |
Narrative:
Flight of 3/fighter aircraft checked on to my frequency at level at 170. [The flight] was flying a [coded route] to sells MOA. I acknowledged the check in and switched the aircraft to tactical frequency. It is standard operation procedure to acknowledge the check in and immediately switch the aircraft to tracon.tus approach control attempted to point out [aircraft a]; C130; to sector 46 level at 170. I informed the tus controller that I was no longer talking to [the flight of 3] who was in conflict with [aircraft a].both aircraft were at 170 inside tus approach airspace. The error occurred between 2 aircraft that tus had the responsibility to separate. The [coded route the flight of 3] was flying does not enter ZAB airspace. It goes from tus to sells MOA. Does ZAB still need to be involved in the process?I would recommend ZAB not even talk to these aircraft. Tus approach should switch them to tactical frequency after they have separated from all of their known aircraft.
Original NASA ASRS Text
Title: Albuquerque Center Controller reported a loss of separation in Tucson Approach airspace.
Narrative: Flight of 3/Fighter aircraft checked on to my frequency at level at 170. [The flight] was flying a [coded route] to SELLS MOA. I acknowledged the check in and switched the aircraft to tactical frequency. It is standard operation procedure to acknowledge the check in and immediately switch the aircraft to Tracon.TUS Approach Control attempted to point out [Aircraft A]; C130; to Sector 46 level at 170. I informed the TUS controller that I was no longer talking to [the flight of 3] who was in conflict with [Aircraft A].Both aircraft were at 170 inside TUS approach airspace. The error occurred between 2 aircraft that TUS had the responsibility to separate. The [coded route the flight of 3] was flying does not enter ZAB airspace. It goes from TUS to SELLS MOA. Does ZAB still need to be involved in the process?I would recommend ZAB not even talk to these aircraft. TUS approach should switch them to tactical frequency after they have separated from all of their known aircraft.
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.