FLC CLRED FOR VISUAL APCH TO RWY 36L LINED UP APCH TO RWY 35L. MISTAKE WAS DISCOVERED; ACFT LINED UP AND LANDED ON CORRECT RWY.

1996-02 · NASA ASRS report 328784

Date: 1996-02 · Aircraft: SF 340A · Phase: approach

Anomalies: deviation-track-heading-all-types|deviation-discrepancy-procedural-clearance

Synopsis

FLC CLRED FOR VISUAL APCH TO RWY 36L LINED UP APCH TO RWY 35L. MISTAKE WAS DISCOVERED; ACFT LINED UP AND LANDED ON CORRECT RWY.

Narrative

OUR ACFT WAS CLRED FOR 'VISUAL APCH TO RWY 36L' AT DFW INTL ARPT WHEN THE FOLLOWING EVENT OCCURRED (SEE DIAGRAM ON REVERSE). WE WERE ON A L BASE FOR RWY 36L ABOUT 5 MI SW OF DFW DSNDING WHEN REGIONAL APCH CLRED US FOR A VISUAL APCH TO RWY 36L AND INSTRUCTED US TO FOLLOW COMPANY TFC ON FINAL TO RWY 36L. AT THIS POINT WE HAD TFC IN SIGHT. WE CHANGED TO TWR FREQ AND WERE CLRED TO LAND. I WAS THE PF; THE CAPT WAS PNF. AS WE CONTINUED ON BASE AND STARED THE FINAL TURN I THOUGHT IT WAS STRANGE THAT A JET WAS DEPARTING FROM OUR RWY. BOTH ME AND THE CAPT WERE SEARCHING FOR THE COMPANY TFC WHICH WE HAD NOW LOST SIGHT OF BUT WERE SURE WAS JUST AHEAD. THE DEPARTING JET SEEMED TOO CLOSE TO WHERE OUR TFC SHOULD BE. AS THE FINAL TURN WAS COMPLETED THE CAPT SAID 'THE TFC IS OVER THE VOR.' THIS ACFT TURNED OUT TO BE ANOTHER JET ON FINAL TO THE R PARALLEL; WHICH SEEMED VERY STRANGE TO ME. AT THIS MOMENT I REALIZED THE ARPT TERMINALS WERE TO OUR L AND WE WERE LINING UP ON RWY 35L! AN IMMEDIATE CORRECTION LINED US UP ON RWY 36L. THE LNDG WAS UNEVENTFUL AND NOTHING WAS SAID ON TWR OR GND FREQ ABOUT THE EVENT. THERE WAS NO CONFLICT WITH THE TFC THAT WAS LNDG ON RWY 35R. AFTER THE FLT THE CAPT AND I ATTEMPTED TO RECONSTRUCT WHAT HAD HAPPENED. IT WAS VERY STRANGE THAT WE BOTH MISSED THE ERROR. THE FOLLOWING ARE 'LINKS' IN THE CHAIN THAT SHOULD HAVE TIPPED US OFF. THE JET DEP IN FRONT OF US WAS TOO CLOSE TO HAVE ALLOWED THE COMPANY TFC TO LAND AND CLR THE RWY. ACFT NEVER LAND WITHIN 2 MI OF EACH OTHER ON PARALLEL RWYS (IE RWYS 35L AND 35R). THE VOR IS ON THE E SIDE OF THE OF THE ARPT. WE WERE BOTH SO BUSY LOOKING FOR THE TFC THAT WE DID NOT XCHK OUR NAV SYS WHICH WE BOTH SET TO THE RWY 36L LOC. I BELIEVE THERE WERE 2 IMPORTANT FACTORS THAT ALLOWED THIS SIT TO DEVELOP. THERE WAS A PARTIAL BROKEN CLOUD LAYER NEAR THE ARPT WHICH WAS CASTING A SHADOW ACROSS THE W COMPLEX (RWYS 36L/R). THERE IS A NEW PARALLEL RWY BEING BUILT ON THE E SIDE OF THE ARPT WITH A CTL TWR BTWN IT AND RWYS 35L/R. THESE 2 FACTORS I BELIEVE CONTRIBUTED TO AN ILLUSION IN THE PERIPHERAL VISION THAT WE WERE INDEED LINED UP ON THE CORRECT RWY. THE EASIEST WAY TO PREVENT THIS IS TO INSURE THAT BOTH CREW MEMBERS ARE NOT CONCENTRATING ON THE SAME TASK. I DO HOWEVER FIND IT VERY STRANGE THAT IT TOOK THE TWO OF US AS LONG AS IT DID TO DETECT THE ERROR.

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.