37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1258690 |
Time | |
Date | 201505 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ZAB.ARTCC |
State Reference | NM |
Environment | |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Small Transport Low Wing 2 Turboprop Eng |
Flight Phase | Climb |
Route In Use | None |
Flight Plan | VFR |
Aircraft 2 | |
Make Model Name | Fighter |
Operating Under FAR Part | Part 91 |
Flight Phase | Descent Cruise |
Route In Use | None |
Flight Plan | IFR |
Person 1 | |
Function | Enroute |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 11.25 |
Events | |
Anomaly | Conflict Airborne Conflict Deviation - Procedural Clearance |
Narrative:
I was working 90 combined with 47 (interestingly enough; not 46). Aircraft X called me for an IFR clearance from sad (safford az) to prc (prescott; az). The jackal MOA/atcaa was active FL290 and below (base of the MOA is 11;000 MSL or 3;000 AGL; whichever is higher) with aircraft Y; flight of 3 military fighters. I told aircraft X I couldn't give them the clearance due to jackal being active; radar identified them; and started telling them about the flight of three. Aircraft Y's datablock showed two aircraft (I left the datablock up instead of freezing it like most people in my area do) at FL240/250 (or thereabouts). There was a third north of the two ship at FL185 on a 4000 code. They looked like they were running intercepts. I told aircraft X about all three fighters and kept calling traffic. I called aircraft Y on 243.0 to have them come up on 281.5 (sector 90 UHF) for traffic information. Aircraft a called me. Since I wasn't sure which one aircraft a was; I asked the pilot if he was the single ship; but the pilot didn't respond; so I started telling the pilot about aircraft X reference the location of aircraft Y as the two fighters were closer to aircraft X than the single 4000 code. As I kept calling traffic between all three fighters and aircraft X; I saw aircraft Y descend out of FL240 for 15;800 and buzz aircraft X. They were head on at same altitude. I gave aircraft X a traffic alert and advise them to turn 40 degrees right immediately. Aircraft X said they had the traffic in sight. Aircraft a then told me they were going to stay above 170 and work to the east to stay away from aircraft X. I told the front line manger (flm) about the situation in no uncertain terms and expressed my dismay about the fighters doing something so blatantly unsafe. The flm called the squadron. Before I gave up the sector; the flm had me ask aircraft X how close they got. The pilot said about two miles. Given that they were head on at the same altitude; that is a bit too close. I also told the two operation managers (OM)s at the desk as I walking out of the control room and said they may want to touch base with the flm.I give permission to share this report.not sure what to say about this. Blatant disregard for safety is a problem for me.
Original NASA ASRS Text
Title: An Albuquerque Center (ZAB) Controller reports of working an aircraft IFR that makes a request he is unable to approve due to a restricted area being hot with aircraft operating in that area. He issues traffic to both the aircraft and the second aircraft group; and one of the aircraft attempts to buzz the single IFR aircraft. The Controller reports this to Front Line Manager (FLM) and Operations Manager (OM).
Narrative: I was working 90 combined with 47 (interestingly enough; not 46). Aircraft X called me for an IFR clearance from SAD (Safford AZ) to PRC (Prescott; AZ). The Jackal MOA/ATCAA was active FL290 and below (base of the MOA is 11;000 MSL or 3;000 AGL; whichever is higher) with Aircraft Y; flight of 3 military fighters. I told Aircraft X I couldn't give them the clearance due to Jackal being active; radar identified them; and started telling them about the flight of three. Aircraft Y's datablock showed two aircraft (I left the datablock up instead of freezing it like most people in my area do) at FL240/250 (or thereabouts). There was a third north of the two ship at FL185 on a 4000 code. They looked like they were running intercepts. I told Aircraft X about all three fighters and kept calling traffic. I called Aircraft Y on 243.0 to have them come up on 281.5 (sector 90 UHF) for traffic information. Aircraft A called me. Since I wasn't sure which one Aircraft A was; I asked the pilot if he was the single ship; but the pilot didn't respond; so I started telling the pilot about Aircraft X reference the location of Aircraft Y as the two fighters were closer to Aircraft X than the single 4000 code. As I kept calling traffic between all three fighters and Aircraft X; I saw Aircraft Y descend out of FL240 for 15;800 and buzz Aircraft X. They were head on at same altitude. I gave Aircraft X a traffic alert and advise them to turn 40 degrees right immediately. Aircraft X said they had the traffic in sight. Aircraft A then told me they were going to stay above 170 and work to the east to stay away from Aircraft X. I told the Front Line Manger (FLM) about the situation in no uncertain terms and expressed my dismay about the fighters doing something so blatantly unsafe. The FLM called the squadron. Before I gave up the sector; the FLM had me ask Aircraft X how close they got. The pilot said about two miles. Given that they were head on at the same altitude; that is a bit too close. I also told the two Operation Managers (OM)s at the desk as I walking out of the control room and said they may want to touch base with the FLM.I give permission to share this report.Not sure what to say about this. Blatant disregard for safety is a problem for me.
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.