# NTSB investigations: Wrong surface or wrong airport NTSB aviation accident and incident investigations since 1962: the probable cause, findings, aircraft, crew, weather and docket of each, linked to the FAA registry and the FAA’s own reports. ## Latest cases - [NTSB ANC26LA087](https://openairdocs.org/ntsb/ANC26LA087.md): Cessna 172P · Inalåhan, GU · Accident · Minor injuries · Class 4 · Limited · Investigation open · Aug 5, 2026 · N62195 · Substantial damage - [NTSB DCA26WA283](https://openairdocs.org/ntsb/DCA26WA283.md): Boeing 737 · Tehran, Iran · Incident · Class 5 · Foreign · Jun 30, 2026 · EP-SII - [NTSB ERA26LA102](https://openairdocs.org/ntsb/ERA26LA102.md): Cessna 172 · New Castle, DE · Accident · No injuries · Class 4 · Limited · Final report · Jan 29, 2026 · N969FG · Substantial damage > The pilots’ failure to properly identify the assigned runway during the landing approach, which resulted in the airplane landing on a closed, snow-covered runway. Contributing was the illumination of the closed runway’s edge lighting. - [NTSB ANC26LA011](https://openairdocs.org/ntsb/ANC26LA011.md): Cessna 150K · Anchorage, AK · Accident · No injuries · Class 4 · Limited · Final report · Jan 25, 2026 · N6333G · Substantial damage > The flight instructor’s unintentional selection of the wrong, snow-covered landing surface, which resulted in a nose-over. - [NTSB OPS25LA054](https://openairdocs.org/ntsb/OPS25LA054.md): Bombardier CL-600-2D24 · Freeland, MI · Incident · No injuries · Class 3 · Limited · Preliminary report · Jul 16, 2025 · N833SK · No damage > On July 16, 2025, about 1542 eastern daylight time (EDT), SkyWest Airlines (SKW) flight 3751, a Bombardier CL-600-2D24, N833SK, departed from a closed runway at MBS International Airport (MBS), Freeland, Michigan. The flight continued without further incident… - [NTSB DCA25WA236](https://openairdocs.org/ntsb/DCA25WA236.md): Boeing 737 · Pusan City, South Korea · Incident · No injuries · Class 5 · Foreign · Jun 12, 2025 · Not reported · No damage - [NTSB DCA25WA221](https://openairdocs.org/ntsb/DCA25WA221.md): Boeing 767 · Xi An Shi, Comoros · Incident · Class 5 · Foreign · May 27, 2025 · 4L-GMC - [NTSB DCA25WA220](https://openairdocs.org/ntsb/DCA25WA220.md): Boeing 737 · Lima, Peru · Incident · Foreign investigation · May 23, 2025 · HP-1844CMP - [NTSB DCA25WA175](https://openairdocs.org/ntsb/DCA25WA175.md): Boeing 737 · Pusan, South Korea · Incident · No injuries · Class 5 · Foreign · Mar 25, 2025 · HL7561 · No damage - [NTSB DCA25LA163](https://openairdocs.org/ntsb/DCA25LA163.md): Boeing 737-8H4 · Orlando, FL · Incident · No injuries · Class 4 · Limited · Final report · Mar 20, 2025 · N8315C · No damage > The captain’s failure to recognize that the airplane’s location did not agree with the assigned departure runway as required per the Southwest Airlines Airplane Operating Manual, and the captain’s plan continuation error when he missed several cues that would… - [NTSB DCA25WA098](https://openairdocs.org/ntsb/DCA25WA098.md): Boeing 757 · Brussels, Belgium · Incident · Class 5 · Foreign · Jan 16, 2025 · D-ALER - [NTSB DCA25WA005](https://openairdocs.org/ntsb/DCA25WA005.md): Boeing 777 · Rawalpindi, Pakistan · Incident · Class 5 · Foreign · Oct 14, 2024 · HZAK21 · No damage - [NTSB OPS24LA045](https://openairdocs.org/ntsb/OPS24LA045.md): Cessna 525 · Brunswick, GA · Incident · No injuries · Class 4 · Limited · Final report · Sep 29, 2024 · N70FC · No damage > The flight crew’s failure to properly identify the airport and runway of intended landing, and the lack of verification of their airplane’s position using all available navigation information. - [NTSB DCA24LA318](https://openairdocs.org/ntsb/DCA24LA318.md): Embraer ERJ 170-100 LR · Chicago, IL · Incident · No injuries · Class 3 · Limited · Final report · Sep 25, 2024 · N772MR · No damage > The flight crew’s misidentification of the intended landing runway, which resulted in an approach to and landing on the wrong runway due to their planned continuation bias. Contributing to the incident was the flight crew’s decision to continue the approach… - [NTSB ERA24LA320](https://openairdocs.org/ntsb/ERA24LA320.md): Cirrus Design SR20 · Port St. Lucie, FL · Accident · No injuries · Class 4 · Limited · Final report · Jul 18, 2024 · N89LF · Substantial damage > The pilot’s failure to correctly identify the airport runway, which resulted in a landing on a road and contact with a power line. Contributing to the outcome was the sun glare. - [NTSB DCA24LA219](https://openairdocs.org/ntsb/DCA24LA219.md): Boeing 737-79P · Portland, ME · Incident · No injuries · Class 3 · Limited · Final report · Jun 25, 2024 · N7861J · No damage > The flight crew’s inadequate review of preflight information and the flight dispatcher’s noncompliance with company guidance requiring the placement of a flight lock, which resulted in the flight’s departure from a closed runway. Contributing to the incident… - [NTSB DCA24WA178](https://openairdocs.org/ntsb/DCA24WA178.md): Boeing 747 · Ryadh, Saudi Arabia · Incident · No injuries · Class 5 · Foreign · Apr 21, 2024 · 9H-AKF · No damage - [NTSB ERA24LA113](https://openairdocs.org/ntsb/ERA24LA113.md): Piper PA28 · Melbourne, FL · Accident · No injuries · Class 4 · Limited · Final report · Feb 13, 2024 · N650FT · Substantial damage > The pilot receiving instruction’s failure to correctly identify the runway centerline prior to initiating the nighttime takeoff, which resulted in a collision with a runway edge light and subsequent runway excursion. Contributing to the accident was the… - [NTSB ERA24LA085](https://openairdocs.org/ntsb/ERA24LA085.md): Beech 58 · Griffin, GA · Accident · No injuries · Class 4 · Limited · Final report · Dec 15, 2023 · N303RA · Substantial damage > The pilot’s misidentification of a taxiway as the intended runway, which resulted in a collision with a utility pole and trees. - [NTSB DCA22LA133](https://openairdocs.org/ntsb/DCA22LA133.md): Boeing 737-9 · Pittsburgh, PA · Incident · No injuries · Class 3 · Limited · Final report · Jun 21, 2022 · N37513 · No damage > The flightcrew’s misidentification of the intended landing runway, which resulted in approach to and landing on the wrong runway. Contributing to the incident was the distraction caused by the dual reset of the flight management computer displays. - [NTSB DCA22LA126](https://openairdocs.org/ntsb/DCA22LA126.md): Boeing 757-236 · Tulsa, OK · Incident · No injuries · Class 3 · Limited · Final report · Jun 8, 2022 · N949FD · No damage > The flight crew’s misidentification of the intended landing runway. Contributing to the incident were (1) the flight crew’s failure to perceive and correctly interpret visual and auditory indicators – including electronic guidance – that they were approaching… - [NTSB WPR22LA105](https://openairdocs.org/ntsb/WPR22LA105.md): Shelton Joseph G S-7 · Buckeye, AZ · Accident · No injuries · Class 4 · Limited · Final report · Feb 19, 2022 · N242K · Substantial damage > The pilot’s exceedance of the airplane’s critical angle of attack while on final approach to land which resulted in an aerodynamic stall and hard landing. - [NTSB DCA22WA008](https://openairdocs.org/ntsb/DCA22WA008.md): Boeing 737-800 · Hong Kong, Hong Kong SAR China · Incident · No injuries · Class 5 · Foreign · Oct 13, 2021 · VP-BEN · No damage - [NTSB CEN21LA182](https://openairdocs.org/ntsb/CEN21LA182.md): Cessna 180 · Denver, CO · Accident · No injuries · Class 4 · Limited · Final report · Apr 2, 2021 · N4802 · Substantial damage > The pilot’s loss of situational awareness, and his unintended landing on a soft unimproved dirt road, which resulted in a loss of directional control into soft ground and the airplane to subsequently nose over. - [NTSB CEN21LA136](https://openairdocs.org/ntsb/CEN21LA136.md): Learjet 55 · Jeffersonville, IN · Accident · No injuries · Class 3 · Limited · Final report · Feb 19, 2021 · N559RA · Substantial damage > The flight crew’s failure to verify the correct runway for landing, which resulted in a landing on a snow contaminated runway and resulting damage to the airplane. The illumination of the lights associated with the closed runway contributed to the accident. - [NTSB ERA21LA049](https://openairdocs.org/ntsb/ERA21LA049.md): Piper PA28 · Lititz, PA · Accident · Minor injuries · Class 4 · Limited · Final report · Nov 20, 2020 · N9086W · Substantial damage > The pilot’s inadvertent attempt to takeoff on a taxiway, rather than a runway, which resulted in a collision with a fence during takeoff. - [NTSB ERA20CA300](https://openairdocs.org/ntsb/ERA20CA300.md): Cessna 182 · Millington, MD · Accident · No injuries · Class 4 · Data collection · Final report · Aug 30, 2020 · N3707U · Substantial damage > The pilot’s misidentification of a corn field for the destination airport’s runway, and a subsequent aerodynamic stall at low altitude while attempting to land. - [NTSB CEN20CA119](https://openairdocs.org/ntsb/CEN20CA119.md): Cessna 208 · Rhinelander, WI · Accident · Serious injuries · Data collection · Final report · Mar 5, 2020 · N706FX · Substantial damage > The pilot's improper decision to continue an instrument approach to landing following a loss of visual reference with the runway, which resulted in the airplane touching down left of the runway in snow and flipping over. - [NTSB DCA19FA089](https://openairdocs.org/ntsb/DCA19FA089.md): Embraer EMB145 · Presque Isle, ME · Accident · Minor injuries · Class 3 · Field · Final report · Mar 4, 2019 · N14171 · Substantial damage > The flight crew’s decision, due to confirmation bias, to continue the descent below the decision altitude when the runway had not been positively identified. Contributing to the accident were (1) the first officer’s fatigue, which exacerbated his confirmation… - [NTSB DCA18IA081](https://openairdocs.org/ntsb/DCA18IA081.md): Bombardier DHC 8 402 · Pullman, WA · Incident · No injuries · Incident investigation · Final report · Dec 30, 2017 · N412QX · No damage > the flight crew's misidentification of the taxiway as the landing runway due to the failure of the runway lighting that caused only the taxiway lights to be illuminated. - [NTSB DCA17IA148](https://openairdocs.org/ntsb/DCA17IA148.md): Airbus A320-211 · San Francisco, CA · Incident · No injuries · Class 1 · Incident · Final report · Jul 8, 2017 · C-FKCK · No damage > The flight crew's misidentification of taxiway C as the intended landing runway, which resulted from the crewmembers' lack of awareness of the parallel runway closure due to their ineffective review of notice to airmen (NOTAM) information before the flight… - [NTSB DCA16IA200](https://openairdocs.org/ntsb/DCA16IA200.md): Airbus Industrie A320 211 · Rapid City, SD · Incident · No injuries · Incident investigation · Final report · Jul 8, 2016 · N333NW · No damage > The flight crew's misidentification of the desired landing runway due to excess altitude requiring an extended downwind, and failure to use all available navigation information. - [NTSB DCA16IA036](https://openairdocs.org/ntsb/DCA16IA036.md): Boeing 737 · Seattle, WA · Incident · No injuries · Incident investigation · Final report · Dec 19, 2015 · N477AS · No damage > the flight crew's misidentification of the taxiway as the landing runway. - [NTSB DCA14IA037](https://openairdocs.org/ntsb/DCA14IA037.md): Boeing 737 7H4 · Branson, MO · Incident · No injuries · Incident investigation · Final report · Jan 13, 2014 · N272WN · No damage > The Flight crew's failure to properly identify the airport and runway of intended landing. Contributing to the incident was the flight crew's failure to comply with procedures for use of navigation information and visual cues to verify the airport and runway… - [NTSB DCA14IA016](https://openairdocs.org/ntsb/DCA14IA016.md): Boeing 747 - 409LCF · Wichita, KS · Incident · No injuries · Incident investigation · Final report · Nov 22, 2013 · N780BA · No damage > the flight crew's failure to properly identify the airport and runway of intended landing. Contributing to the incident was the flight crew's failure to follow company procedures for crosschecking navigational information and visual cues to verify the airport… - [NTSB ANC11LA008](https://openairdocs.org/ntsb/ANC11LA008.md): Piper PA-32-300 · Platinum, AK · Accident · Minor injuries · Limited investigation · Final report · Jan 4, 2011 · N9304K · Substantial damage > The pilot's misidentification of the airport's active runway, resulting in an off-runway landing and collision with a ditch/berm. - [NTSB WPR10CA035](https://openairdocs.org/ntsb/WPR10CA035.md): Piper PA-28-140 · Angwin, CA · Accident · No injuries · Data collection · Final report · Oct 30, 2009 · N1721T · Substantial damage > The pilot's failure to properly identify the runway surface for takeoff and his subsequent failure to abort the takeoff when he realized he was not on the runway. Contributing to the accident was the pilot’s failure to select the appropriate radio frequency… - [NTSB OPS10IA001](https://openairdocs.org/ntsb/OPS10IA001.md): Boeing 767 · Atlanta Hartsfield Intl. Apt. (KATL), GA · Incident · No injuries · Incident investigation · Final report · Oct 19, 2009 · N185DN · No damage > The flight crew’s failure to identify the correct landing surface due to fatigue. Contributing to the cause of the incident were (1) the flight crew’s decision to accept a late runway change, (2) the unavailability of the approach light system and the… - [NTSB CEN09CA422](https://openairdocs.org/ntsb/CEN09CA422.md): Piper PA-28-140 · Hibbing, MN · Accident · No injuries · Data collection · Final report · Jul 2, 2009 · N88FN · Substantial damage > The pilot mistakenly using a closed taxiway for takeoff, which resulted in the airplane striking a construction barricade. - [NTSB WPR09CA274](https://openairdocs.org/ntsb/WPR09CA274.md): Piper PA-38-112 · Grangeville, ID · Accident · No injuries · Data collection · Final report · May 28, 2009 · N25353 · Substantial damage > The pilot's failure to maintain clearance from an obstacle during taxi. ## The whole list in SQL Runs in DuckDB 1.2 or later on the release's Parquet files over HTTPS: ```sql SELECT c."ntsbNumber", c."eventDate", c."eventType", c."eventCity", c."eventStateOrRegion", a.n_number, a."aircraftMake", a."aircraftModel", c."highestInjuryLevel", c."totalFatal", c."completionStatus", c.report_url FROM 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c LEFT JOIN 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' a ON a.case_mkey = c."mKey" AND a.position = 1 WHERE c."mKey" IN (SELECT e.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' e WHERE e."isDefiningEvent" AND e."tier2Number" = '284') ORDER BY c."eventDate" DESC, c."ntsbNumber" DESC ``` This list as a web page: https://openairdocs.org/ntsb-events/284/cases --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.