 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZAB controller described a restricted area incursion by a phx air carrier departure indicating that the vector issued by the phx departure controller most likely caused the infraction.
| Attributes | |
| ACN | 989098 |
| Time | |
| Date | 201201 |
| Local Time Of Day | 0001-0600 |
| Place | |
| Locale Reference | ZAB.ARTCC |
| State Reference | NM |
| Aircraft 1 | |
| Make Model Name | B737-800 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Initial Climb |
| Route In Use | Vectors |
| Flight Plan | IFR |
| Person 1 | |
| Function | Enroute |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types Airspace Violation All Types |
Narrative:
I was working sector 90 and outlaw and jackal MOA/atcaa's had gone active about 5-10 minutes previous before the incident. Sector 46; the sector that works departures off of phx; to the southeast; yelled across the room and said watch that guy when the sent a pvd of a B737 to my scope. Phx approach had given the aircraft a vector out the departure gate; when they were supposed to have give the aircraft a full route clearance via tfd VOR because the gate was close due to the MOA/atcaa's being active. I immediately got on guard and called the aircraft that were working in outlaw and told them to maintain the altitudes of fl220b290 in outlaw; and to acknowledge with an identify. The aircraft working in the military airspace never idented but instead came up on my frequency and asked why and I told them the reason and to maintain the assigned altitudes. By this time the B737 had already deviated the MOA/atcaa airspace before being turned out by the sector 46 controller. I am not sure the procedures within phx approach airspace that notifies controllers that the departure gate is closed; but maybe something that makes the controllers more aware that the military airspace that is in their airspace is active would be more helpful.
Original NASA ASRS Text
Title: ZAB Controller described a restricted area incursion by a PHX Air Carrier departure indicating that the vector issued by the PHX Departure Controller most likely caused the infraction.
Narrative: I was working Sector 90 and Outlaw and Jackal MOA/ATCAA's had gone active about 5-10 minutes previous before the incident. Sector 46; the sector that works departures off of PHX; to the southeast; yelled across the room and said watch that guy when the sent a PVD of a B737 to my scope. PHX Approach had given the aircraft a vector out the departure gate; when they were supposed to have give the aircraft a full route clearance via TFD VOR because the gate was close due to the MOA/ATCAA's being active. I immediately got on Guard and called the aircraft that were working in OUTLAW and told them to maintain the altitudes of FL220B290 in OUTLAW; and to acknowledge with an IDENT. The aircraft working in the military airspace never IDENTED but instead came up on my frequency and asked why and I told them the reason and to maintain the assigned altitudes. By this time the B737 had already deviated the MOA/ATCAA airspace before being turned out by the Sector 46 Controller. I am not sure the procedures within PHX Approach airspace that notifies controllers that the departure gate is closed; but maybe something that makes the controllers more aware that the military airspace that is in their airspace is active would be more helpful.
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.