NMAC.

1992-03 · NASA ASRS report 204036

Date: 1992-03 · Aircraft: Small Aircraft; Low Wing; 1 Eng; Retractable Gear

Anomalies: conflict-nmac|deviation-discrepancy-procedural-clearance|deviation-discrepancy-procedural-far|deviation-discrepancy-procedural-published-material-policy|other-unspecified|other-airspace-violation-entry-or-exit

Synopsis

NMAC.

Narrative

THIS IS WRITTEN AS A RESULT OF A SITUATION THAT TOOK PLACE ON MAR/XX/92 AS MY STUDENTS AND I WERE RETURNING TO GYR ON AN IFR TRAINING MISSION. WE CROSSED THE BXK VOR AT 6000 FT MSL IN AN SMA W; INBOUND TO GYR ON AN IFR FLT PLAN. ZAB HANDED US OFF TO LUKE APCH. LUKE GAVE US A HDG OF 110 DEGS AND A DSCNT TO 5000 FT. AT A POINT APPROX 5 NM S OF LUKE AUX 6 WE WERE GIVEN ANOTHER DSCNT TO 3000 FT MSL AND A HDG OF 100 DEGS AND TOLD 'CLRED VISUAL APCH; CONTACT GYR TWR 120.1.' AT THE TIME OF FREQ CHANGE WE HEARD GYR TWR CALL OUT TO A DEPARTING SMA ACFT X '1 SMA Y IN R DOWNWIND TFC AND A SECOND SMA INBOUND FROM THE W.' ASSUMING THAT LUKE HAD INFORMED GYR TWR WE WERE INBOUND; WE LOCATED THE SMA AT 12 O'CLOCK TO 11 O'CLOCK ON THE DOWNWIND. THE DEP SMA CALLED TFC IN SIGHT; SMA Y. AT THIS POINT; WE WERE ENTERING THE R DOWNWIND TFC WITHOUT THE SMA Y OR THE (UNKNOWN TO US) THIRD SMA Z IN SIGHT. AT THIS POINT AT OUR 3 O'CLOCK POS; WE SAW AN SMA Z AT LESS THAN 100 YARDS AWAY AND CLOSING. WE BANKED SHARPLY TO THE L AND CLBED APPROX 300 FT TO CLR PATTERN ALT. AT THIS POINT GYR TWR REQUESTED WE SQUAWK 1200 AND RETURN TO LUKE AUX 6 TO RE-ENTER THE PATTERN. AS REQUESTED; WE CONTINUED OUR L TURN THEN DSNDED TO 2000 FT MSL. AFTER RE-ENTERING; WE LANDED AND WERE THANKED BY GYR TWR FOR THE HELP. LUKE APCH HAD NEVER CONTACTED GYR TWR AND WE WERE STILL ON AN IFR FLT PLAN; UNDER IFR RADAR CTL. THIS SITUATION COULD CAUSE A MIDAIR COLLISION. ON MAR/XX/92 THIS WAS NARROWLY AVOIDED (WITH LESS THAN A 50 YARD SEPARATION) BUT WITH FASTER ACFT OR NON OBSERVANT CREWS A MIDAIR COLLISION WOULD HAVE HAPPENED. THE POTENTIAL FOR A MIDAIR WOULD BE GREATLY INCREASED IF THE ARRIVING ACFT WAS UNFAMILIAR WITH GYR AND NOT AWARE OF THE NUMBERS OF ACFT THAT MIGHT BE IN THE PATTERN. I RECOMMEND THE FOLLOWING BE DONE AS A RESULT OF THIS: 1) COMMUNICATE WITH LUKE APCH AND FIND OUT WHY THEY DID NOT NOTIFY GYR TWR BY LANDLINE BEFORE TURNING US OVER TO TWR. LUKE VIOLATED THE FAR FOR AIR TFC CTLRS AND AIM SECTION 4; PARAGRAPH 5-58 BY FAILING TO COORDINATE OUR HDOF TO GYR. 2) HAVE A WRITTEN POLICY IF WE ARE TO CANCEL IFR BEFORE ENTERING THE GYR ATA.

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.

Loading the flight search…

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.