NTSB investigations
40 cases where the defining event was Wrong surface or wrong airport.
Cases per year
| 2009 | 4 |
|---|---|
| 2011 | 1 |
| 2013 | 1 |
| 2014 | 1 |
| 2015 | 1 |
| 2016 | 1 |
| 2017 | 2 |
| 2019 | 1 |
| 2020 | 3 |
| 2021 | 3 |
| 2022 | 3 |
| 2023 | 1 |
| 2024 | 7 |
| 2025 | 7 |
| 2026 | 4 |
Where
Open the mapLatest cases
Query with SQL
duckdb -csv -c "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"
Prints the whole list as CSV. It reads the release’s Parquet files over HTTPS, so there’s nothing to download first. Install DuckDB to run it.
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
Run it at the DuckDB prompt, or in any tool that reads Parquet over HTTPS. More ways to query the release are on Use the data.
NTSB ANC26LA087Accident · Minor injuriesClass 4 · LimitedInvestigation openCessna 172P · Inalåhan, GUNTSB DCA26WA283IncidentClass 5 · ForeignBoeing 737 · Tehran, IranNTSB ERA26LA102Accident · No injuriesClass 4 · LimitedFinal reportCessna 172 · New Castle, DEThe 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 ANC26LA011Accident · No injuriesClass 4 · LimitedFinal reportCessna 150K · Anchorage, AKThe flight instructor’s unintentional selection of the wrong, snow-covered landing surface, which resulted in a nose-over.NTSB OPS25LA054Incident · No injuriesClass 3 · LimitedPreliminary reportBombardier CL-600-2D24 · Freeland, MIOn 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 DCA25WA236Incident · No injuriesClass 5 · ForeignBoeing 737 · Pusan City, South KoreaNTSB DCA25WA221IncidentClass 5 · ForeignBoeing 767 · Xi An Shi, ComorosNTSB DCA25WA220IncidentForeign investigationBoeing 737 · Lima, PeruNTSB DCA25WA175Incident · No injuriesClass 5 · ForeignBoeing 737 · Pusan, South KoreaNTSB DCA25LA163Incident · No injuriesClass 4 · LimitedFinal reportBoeing 737-8H4 · Orlando, FLThe 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 DCA25WA098IncidentClass 5 · ForeignBoeing 757 · Brussels, BelgiumNTSB DCA25WA005IncidentClass 5 · ForeignBoeing 777 · Rawalpindi, PakistanNTSB OPS24LA045Incident · No injuriesClass 4 · LimitedFinal reportCessna 525 · Brunswick, GAThe 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 DCA24LA318Incident · No injuriesClass 3 · LimitedFinal reportEmbraer ERJ 170-100 LR · Chicago, ILThe 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 ERA24LA320Accident · No injuriesClass 4 · LimitedFinal reportCirrus Design SR20 · Port St. Lucie, FLThe 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 DCA24LA219Incident · No injuriesClass 3 · LimitedFinal reportBoeing 737-79P · Portland, METhe 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 DCA24WA178Incident · No injuriesClass 5 · ForeignBoeing 747 · Ryadh, Saudi ArabiaNTSB ERA24LA113Accident · No injuriesClass 4 · LimitedFinal reportPiper PA28 · Melbourne, FLThe 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 ERA24LA085Accident · No injuriesClass 4 · LimitedFinal reportBeech 58 · Griffin, GAThe pilot’s misidentification of a taxiway as the intended runway, which resulted in a collision with a utility pole and trees.NTSB DCA22LA133Incident · No injuriesClass 3 · LimitedFinal reportBoeing 737-9 · Pittsburgh, PAThe 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 DCA22LA126Incident · No injuriesClass 3 · LimitedFinal reportBoeing 757-236 · Tulsa, OKThe 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 WPR22LA105Accident · No injuriesClass 4 · LimitedFinal reportShelton Joseph G S-7 · Buckeye, AZThe 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 DCA22WA008Incident · No injuriesClass 5 · ForeignBoeing 737-800 · Hong Kong, Hong Kong SAR ChinaNTSB CEN21LA182Accident · No injuriesClass 4 · LimitedFinal reportCessna 180 · Denver, COThe 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 CEN21LA136Accident · No injuriesClass 3 · LimitedFinal reportLearjet 55 · Jeffersonville, INThe 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 ERA21LA049Accident · Minor injuriesClass 4 · LimitedFinal reportPiper PA28 · Lititz, PAThe pilot’s inadvertent attempt to takeoff on a taxiway, rather than a runway, which resulted in a collision with a fence during takeoff.NTSB ERA20CA300Accident · No injuriesClass 4 · Data collectionFinal reportCessna 182 · Millington, MDThe 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 CEN20CA119Accident · Serious injuriesData collectionFinal reportCessna 208 · Rhinelander, WIThe 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 DCA19FA089Accident · Minor injuriesClass 3 · FieldFinal reportEmbraer EMB145 · Presque Isle, METhe 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 DCA18IA081Incident · No injuriesIncident investigationFinal reportBombardier DHC 8 402 · Pullman, WAthe 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 DCA17IA148Incident · No injuriesClass 1 · IncidentFinal reportAirbus A320-211 · San Francisco, CAThe 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 DCA16IA200Incident · No injuriesIncident investigationFinal reportAirbus Industrie A320 211 · Rapid City, SDThe 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 DCA16IA036Incident · No injuriesIncident investigationFinal reportBoeing 737 · Seattle, WAthe flight crew's misidentification of the taxiway as the landing runway.NTSB DCA14IA037Incident · No injuriesIncident investigationFinal reportBoeing 737 7H4 · Branson, MOThe 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 DCA14IA016Incident · No injuriesIncident investigationFinal reportBoeing 747 - 409LCF · Wichita, KSthe 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 ANC11LA008Accident · Minor injuriesLimited investigationFinal reportPiper PA-32-300 · Platinum, AKThe pilot's misidentification of the airport's active runway, resulting in an off-runway landing and collision with a ditch/berm.NTSB WPR10CA035Accident · No injuriesData collectionFinal reportPiper PA-28-140 · Angwin, CAThe 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 OPS10IA001Incident · No injuriesIncident investigationFinal reportBoeing 767 · Atlanta Hartsfield Intl. Apt. (KATL), GAThe 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 CEN09CA422Accident · No injuriesData collectionFinal reportPiper PA-28-140 · Hibbing, MNThe pilot mistakenly using a closed taxiway for takeoff, which resulted in the airplane striking a construction barricade.NTSB WPR09CA274Accident · No injuriesData collectionFinal reportPiper PA-38-112 · Grangeville, IDThe pilot's failure to maintain clearance from an obstacle during taxi.