 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Reporter's company notified the flight crew that military F16's were filing a report faulting the flight crew for flying into an MOA and causing a conflict. Rptrs were navigating with vors on a VFR flight plan and flight followed by all en route ATC facilities. At no time were they advised of being in an MOA or the proximity of traffic.
| Attributes | |
| ACN | 333033 |
| Time | |
| Date | 199604 |
| Day | Mon |
| Local Time Of Day | 1801 To 2400 |
| Place | |
| Locale Reference | atc facility : zab |
| State Reference | NM |
| Altitude | msl bound lower : 17500 msl bound upper : 17500 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | artcc : zab |
| Operator | common carrier : air taxi |
| Make Model Name | Commercial Fixed Wing |
| Operating Under FAR Part | Part 135 |
| Flight Phase | cruise other |
| Flight Plan | VFR |
| Person 1 | |
| Affiliation | company : air taxi |
| Function | flight crew : first officer |
| Qualification | pilot : commercial pilot : atp pilot : instrument pilot : cfi |
| Experience | flight time last 90 days : 240 flight time total : 5250 flight time type : 1300 |
| ASRS Report | 333033 |
| Person 2 | |
| Affiliation | company : air taxi |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : commercial pilot : cfi pilot : atp pilot : instrument |
| Experience | flight time last 90 days : 275 flight time total : 7900 flight time type : 6000 |
| ASRS Report | 333023 |
| Events | |
| Anomaly | conflict : airborne less severe other anomaly other other anomaly other |
| Independent Detector | other other : unspecified |
| Resolutory Action | none taken : detected after the fact |
| Consequence | Other |
| Supplementary | |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | Pilot Deviation |
Narrative:
On apr/mon/96, flight ab from lake havasau city to phx was reported by luke approach as flying in the gladden/bagdad MOA without flight following. This report was supposedly handed on to FAA abq and to our airline's corp office. Our airline then informed the captain of that flight, of this conflict. However, the captain and myself (PNF) were navigating by vors and had no knowledge of or intentions of flying into the above mentioned MOA's at any time during the course of the flight. Throughout the flight we had VFR flight following with ZAB, luke approach, and phx approach. At no time to our knowledge was in traffic conflict brought to our attention or did we see or observe any traffic conflict. The flight was uneventful with nothing brought to our attention by any ATC controller to our knowledge.
Original NASA ASRS Text
Title: RPTR'S COMPANY NOTIFIED THE FLC THAT MIL F16'S WERE FILING A RPT FAULTING THE FLC FOR FLYING INTO AN MOA AND CAUSING A CONFLICT. RPTRS WERE NAVING WITH VORS ON A VFR FLT PLAN AND FLT FOLLOWED BY ALL ENRTE ATC FACILITIES. AT NO TIME WERE THEY ADVISED OF BEING IN AN MOA OR THE PROX OF TFC.
Narrative: ON APR/MON/96, FLT AB FROM LAKE HAVASAU CITY TO PHX WAS RPTED BY LUKE APCH AS FLYING IN THE GLADDEN/BAGDAD MOA WITHOUT FLT FOLLOWING. THIS RPT WAS SUPPOSEDLY HANDED ON TO FAA ABQ AND TO OUR AIRLINE'S CORP OFFICE. OUR AIRLINE THEN INFORMED THE CAPT OF THAT FLT, OF THIS CONFLICT. HOWEVER, THE CAPT AND MYSELF (PNF) WERE NAVING BY VORS AND HAD NO KNOWLEDGE OF OR INTENTIONS OF FLYING INTO THE ABOVE MENTIONED MOA'S AT ANY TIME DURING THE COURSE OF THE FLT. THROUGHOUT THE FLT WE HAD VFR FLT FOLLOWING WITH ZAB, LUKE APCH, AND PHX APCH. AT NO TIME TO OUR KNOWLEDGE WAS IN TFC CONFLICT BROUGHT TO OUR ATTN OR DID WE SEE OR OBSERVE ANY TFC CONFLICT. THE FLT WAS UNEVENTFUL WITH NOTHING BROUGHT TO OUR ATTN BY ANY ATC CTLR TO OUR KNOWLEDGE.
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.