37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 333040 |
Time | |
Date | 199604 |
Day | Tue |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | atc facility : phx |
State Reference | AZ |
Altitude | msl bound lower : 14500 msl bound upper : 14500 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | artcc : zab tower : pvd |
Operator | common carrier : air taxi |
Make Model Name | Beech 1900 |
Operating Under FAR Part | Part 135 |
Navigation In Use | Other |
Flight Phase | cruise other |
Flight Plan | VFR |
Person 1 | |
Affiliation | company : air taxi |
Function | flight crew : captain oversight : pic |
Qualification | pilot : instrument pilot : commercial pilot : cfi pilot : atp |
Experience | flight time last 90 days : 275 flight time total : 7900 flight time type : 6000 |
ASRS Report | 333040 |
Person 2 | |
Affiliation | company : air taxi |
Function | flight crew : first officer |
Qualification | pilot : cfi pilot : instrument pilot : atp pilot : commercial |
Experience | flight time last 90 days : 240 flight time total : 5250 flight time type : 1300 |
ASRS Report | 333034 |
Events | |
Anomaly | conflict : airborne less severe non adherence : far other anomaly other |
Independent Detector | other other : unspecified |
Resolutory Action | none taken : detected after the fact |
Consequence | faa : investigated faa : reviewed incident with flight crew |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | other |
Narrative:
On apr/xx/96 I was the captain on a flight from phx to hii. We were flying with VFR flight following from center at ZAB and then luke AFB. Luke reports we were in the MOA without flight following and had a near miss with one of their F16's. We had flight following but were never told about the incident and we were outside the MOA. I was informed about this instance on apr/xy/96. Callback conversation with reporter revealed the following information: aircraft verified as BE02. Reporter captain was notified by his company, for whom he no longer is employed, that twice in 2 days the same F16 pilot reported an near midair collision with the flight crew. Reporter states that at no time did any ATC facility warn them of being close to or entering an MOA. Once ZAB advised them of traffic, but they didn't acquire it. Also they had TCASII and never saw any traffic. However, reporter did say that when contacting the base commander at luke AFB to obtain more information regarding the alleged near midair collision, he was told that once the F16 joined on his wing. Also, the F16 contacted the center to identify the aircraft, because the military pilot thought they were in the MOA. Reporter contacted the FSDO at abq who investigated the incident and feedback determined that the F16 was probably outside his MOA at the time. Reporter requested that tapes be obtained to clarify the situation, but that was not done, presumably at the direction of the FSDO. When reporter asked the base commander for tapes, the commander allegedly said that it was out of his hands and reporter would have to work through his company.
Original NASA ASRS Text
Title: POSSIBLE INCURSION INTO MOA SECOND TIME IN 2 DAYS. RPTR FLC WAS IN COM FOR FLT FOLLOWING WITH ALL ATC FACILITIES ENRTE, LUKE APCH, PHX APCH AND ZAB. NONE OF THOSE CTLRS TOLD FLC THEY WERE ENTERING OR CLOSE TO AN MOA, BUT THE SAME MIL F16 PLT RPTED AN NMAC WITH THE RPTR ACFT TWICE. ONCE THE F16 JOINED UP ON THE RPTR. FSDO AT ABQ DETERMINED THE F16 WAS OUT OF THE MOA AT THE TIME OF THE CONFLICT.
Narrative: ON APR/XX/96 I WAS THE CAPT ON A FLT FROM PHX TO HII. WE WERE FLYING WITH VFR FLT FOLLOWING FROM CTR AT ZAB AND THEN LUKE AFB. LUKE RPTS WE WERE IN THE MOA WITHOUT FLT FOLLOWING AND HAD A NEAR MISS WITH ONE OF THEIR F16'S. WE HAD FLT FOLLOWING BUT WERE NEVER TOLD ABOUT THE INCIDENT AND WE WERE OUTSIDE THE MOA. I WAS INFORMED ABOUT THIS INSTANCE ON APR/XY/96. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: ACFT VERIFIED AS BE02. RPTR CAPT WAS NOTIFIED BY HIS COMPANY, FOR WHOM HE NO LONGER IS EMPLOYED, THAT TWICE IN 2 DAYS THE SAME F16 PLT RPTED AN NMAC WITH THE FLC. RPTR STATES THAT AT NO TIME DID ANY ATC FACILITY WARN THEM OF BEING CLOSE TO OR ENTERING AN MOA. ONCE ZAB ADVISED THEM OF TFC, BUT THEY DIDN'T ACQUIRE IT. ALSO THEY HAD TCASII AND NEVER SAW ANY TFC. HOWEVER, RPTR DID SAY THAT WHEN CONTACTING THE BASE COMMANDER AT LUKE AFB TO OBTAIN MORE INFO REGARDING THE ALLEGED NMAC, HE WAS TOLD THAT ONCE THE F16 JOINED ON HIS WING. ALSO, THE F16 CONTACTED THE CTR TO IDENT THE ACFT, BECAUSE THE MIL PLT THOUGHT THEY WERE IN THE MOA. RPTR CONTACTED THE FSDO AT ABQ WHO INVESTIGATED THE INCIDENT AND FEEDBACK DETERMINED THAT THE F16 WAS PROBABLY OUTSIDE HIS MOA AT THE TIME. RPTR REQUESTED THAT TAPES BE OBTAINED TO CLARIFY THE SIT, BUT THAT WAS NOT DONE, PRESUMABLY AT THE DIRECTION OF THE FSDO. WHEN RPTR ASKED THE BASE COMMANDER FOR TAPES, THE COMMANDER ALLEGEDLY SAID THAT IT WAS OUT OF HIS HANDS AND RPTR WOULD HAVE TO WORK THROUGH HIS COMPANY.
Data retrieved from NASA's ASRS site as of July 2007 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.