NTSB investigations, 2023
9 cases where the sequence of events included Landing area undershoot.
Cases per year
| 2008 | 16 |
|---|---|
| 2009 | 10 |
| 2010 | 17 |
| 2011 | 13 |
| 2012 | 11 |
| 2013 | 7 |
| 2014 | 4 |
| 2015 | 6 |
| 2016 | 17 |
| 2017 | 17 |
| 2018 | 14 |
| 2019 | 8 |
| 2020 | 11 |
| 2021 | 6 |
| 2022 | 12 |
| 2023 | 9 |
| 2024 | 9 |
| 2025 | 15 |
| 2026 | 2 |
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\") = 2023
AND c.\"mKey\" IN (SELECT s.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' s WHERE s.\"tier2Number\" = '370' 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") = 2023 AND c."mKey" IN (SELECT s.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' s WHERE s."tier2Number" = '370' 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 ANC24LA011Accident · No injuriesClass 3 · LimitedFinal reportCessna 172P · Kahului, HIA partial loss of engine power due to the formation of carburetor ice, which resulted in the inability to maintain altitude in the traffic pattern. Contributing to the outcome was the pilot’s delayed use of carburetor heat in conditions conducive to the…NTSB DCA23WA444Incident · No injuriesClass 5 · ForeignAirbus A319 · Samui, ThailandNTSB ERA23LA348Accident · Minor injuriesClass 4 · LimitedFinal reportCessna 150 · Pink Hill, NCThe pilot’s inadequate compensation for prevailing wind conditions during the landing approach, which resulted in the airplane contacting the ground short of the runway.NTSB ERA23LA300Accident · 1 fatalClass 3 · LimitedFinal reportPiper PA46 · Vineyard Haven, MAThe pilot’s incapacitation due to a sudden in-flight cardiac event, which resulted in a gear-up landing.NTSB CEN23LA266Accident · No injuriesClass 3 · LimitedFinal reportPiper PA-28-181 · Howell, MIA loss of engine power due to the formation of carburetor ice that resulted from the pilot’s delayed use of carburetor heat during the landing approach.NTSB ERA23LA291Accident · No injuriesClass 4 · LimitedFinal reportVolato 400 · Dublin, GAThe pilot’s improper landing flare which resulted in a runway undershoot and a hard landing, which substantially damaged the airplane’s firewall.NTSB ANC23LA027Accident · No injuriesClass 3 · LimitedFinal reportCessna 182R · Minto, AKA total loss of engine power for reasons that could not be determined.NTSB GAA23WA080Accident · No injuriesClass 5 · ForeignEmbraer EMB202 · Rincão de Santana, BrazilNTSB ANC23LA021Accident · No injuriesClass 4 · LimitedFinal reportPiper PA-32-260 · Tok, AKThe pilot's failure to maintain a proper approach glide path, which resulted in a hard landing, short of his anticipated touchdown point.