NTSB investigations, 2024
9 cases where the sequence of events included Wrong surface or wrong airport.
Cases per year
| 2008 | 1 |
|---|---|
| 2009 | 5 |
| 2011 | 1 |
| 2013 | 1 |
| 2014 | 1 |
| 2015 | 1 |
| 2016 | 1 |
| 2017 | 3 |
| 2018 | 2 |
| 2019 | 1 |
| 2020 | 7 |
| 2021 | 4 |
| 2022 | 5 |
| 2023 | 2 |
| 2024 | 9 |
| 2025 | 9 |
| 2026 | 5 |
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 year(c.\"eventDate\") = 2024
AND c.\"mKey\" IN (SELECT s.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' s WHERE s.\"tier2Number\" = '284' AND s.case_mkey IN (SELECT case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' WHERE \"isDefiningEvent\"))
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 year(c."eventDate") = 2024 AND c."mKey" IN (SELECT s.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' s WHERE s."tier2Number" = '284' AND s.case_mkey IN (SELECT case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' WHERE "isDefiningEvent")) 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 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 WPR24LA212Accident · Minor injuriesClass 4 · LimitedFinal reportPiper PA31 · Lemoore, CAThe pilot’s improper in-flight decision making which resulted in a total loss of engine power due to fuel exhaustion and a subsequent emergency landing.NTSB DCA24WA178Incident · No injuriesClass 5 · ForeignBoeing 747 · Ryadh, Saudi ArabiaNTSB ANC24LA026Accident · Serious injuriesClass 4 · LimitedFinal reportCirrus Design SR22T · Paso Robles, CAThe flight instructor’s failure to maintain adequate airspeed during landing which resulted in a loss of directional control and runway excursion. Contributing to the accident was the pilot receiving instructions failure to maintain runway alignment.NTSB 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…