BE400 LANDED AT AN ARPT OTHER THAN THAT FILED AS THE DEST IN IFR FLT PLAN.

2007-10 · NASA ASRS report 758052

Date: 2007-10 · Aircraft: Beechjet 400

Anomalies: other-landed-at-wrong-arpt

Synopsis

BE400 LANDED AT AN ARPT OTHER THAN THAT FILED AS THE DEST IN IFR FLT PLAN.

Narrative

FLT PLANNED TO EFD. HOU WAS ALTERNATE. INTO EFD SEVERAL ROUTING CHANGES FOR A COUPLE OF LINES OF WX. HOUSTON APCH CTL WAS VERY BUSY. WHEN WE APCHED THE HOUSTON AREA THE CTLRS WOULD VECTOR US THEN STARTED TELLING US DIRECT HOBBY VOR THEN DIRECT EFD. AFTER SEVERAL TIMES OF THIS THE CTLR ASKED IF WE HAD CURRENT WX EFD. I SAID WHICH ATIS I HAD AND HE SAID NEW ATIS WAS NOW CURRENT SO I TOLD HIM I WOULD GET THE NEW WX. AFTER GETTING THE NEW WX AT EFD HE TOLD US TO EXPECT ILS RWY 22 EFD. I TOLD HIM OK AND HE PUT US ON ANOTHER VECTOR. WE WERE SET UP FOR THE APCH; TUNED AND IDENTED AT THAT POINT. AFTER ANOTHER HDG AND ALT CHANGE WE WERE CLRED FOR THE ILS RWY 22. NO FLAGS ON EITHER INST. AT THAT POINT WE WERE SHOWING R OF COURSE AND CORRECTING BECAUSE HE HAD FLOWN US THROUGH THE LOC. HE CAME BACK TO CORRECT THIS WHEN WE BROKE OUT AND THE RWY WAS IN FRONT OF US TO THE L 3-5 MI. AT THAT POINT WE WERE VISUAL AND COMING BACK TO THE L THINKING THIS WAS RWY 22 EFD. THE CTLR THEN SAID TO CONTACT TWR 118.7. I CALLED TWR ON 118.7 AND THEY CLRED US TO LAND ON RWY 22. AFTER LNDG I REALIZED WE HAD LANDED AT THE WRONG ARPT BUT WE HAD CLRNC FROM HOBBY TWR. TAXIED TO PARKING. BOTH ARPTS HAVE RWYS 17 AND 22. I GUESS WITH THE PROX OF BOTH ARPTS SO CLOSE TOGETHER THAT WOULD BE THE REASON THAT THE ILS DID NOT FLAG AS WE APCHED HOBBY INITIALLY IN IMC. AND AT THIS ALT I COULD NOT MAKE OUT THE DIFFERENCE OF THE ARPT DIAGRAMS. IF THE APCH WOULD HAVE CONTINUED WE WOULD HAVE TO HAD GONE MISSED DUE TO THE NEEDLE DEFLECTION. SEEING THE RWY PUT US INTO A VISUAL MODE AND NOT CHKING THE NEEDLE TO SEE IF IT CTRED UP AS WE APCHED THE RWY. THE CTLR AND MYSELF NEVER SAID THE TWR'S NAME; JUST THE FREQ. THIS WOULD HAVE AVERTED THE MISTAKE. SUPPLEMENTAL INFO FROM ACN 757850: CONTRIBUTING FACTORS WERE THE SEVERE WX IN THE AREA; HIGH WORKLOADS FOR BOTH ATC AND THE PLTS; MULTIPLE RE-RTES THAT COVERED LONG DISTANCES THAT HELPED US LOSE SITUATIONAL AWARENESS; 2 OF THE SAME RWYS IN CLOSE PROX TO EACH OTHER WITH THE SAME APCH; THE PNF AND THE CTLRS NEVER SAID 'HOUSTON OR ELLINGTON TWR' WHEN THEY COMMUNICATED WITH EACH OTHER; WE WERE HAVING PROBS WITH OUR HSI PRECESSING; WE ASSUMED THAT WE WERE VECTORED THROUGH THE FINAL COURSE; AND OUR ACFT DOES NOT HAVE A MOVING MAP ON BOARD IN THE AVIONICS PACKAGE WHICH WOULD HAVE MADE US MORE SITUATIONALLY AWARE.

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.