NTSB investigations, 2009
12 cases where the defining event was Landing area overshoot.
Cases per year
| 2008 | 18 |
|---|---|
| 2009 | 12 |
| 2010 | 24 |
| 2011 | 20 |
| 2012 | 18 |
| 2013 | 10 |
| 2014 | 13 |
| 2015 | 10 |
| 2016 | 10 |
| 2017 | 10 |
| 2018 | 7 |
| 2019 | 3 |
| 2020 | 8 |
| 2021 | 11 |
| 2022 | 13 |
| 2023 | 7 |
| 2024 | 15 |
| 2025 | 16 |
| 2026 | 9 |
Where
Latest 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\") = 2009
AND c.\"mKey\" IN (SELECT e.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' e WHERE e.\"isDefiningEvent\" AND e.\"tier2Number\" = '380')
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") = 2009 AND c."mKey" IN (SELECT e.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' e WHERE e."isDefiningEvent" AND e."tier2Number" = '380') 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 WPR10LA072Accident · No injuriesLimited investigationFinal reportStinson 108-3 · Clarksburg, CAThe pilot’s improper touchdown point and excessive airspeed during landing, which resulted in a runway overrun.NTSB ERA10CA030Accident · No injuriesData collectionFinal reportCessna 182 · White Plains, NYThe pilot's failure to attain the proper touchdown point, resulting in a landing overrun. Contributing to the accident was the pilot’s excessive airspeed in an attempt to comply with air traffic control’s request to expedite his landing.NTSB CEN10CA015Accident · Serious injuriesData collectionFinal reportAerostar International RX8 · Albuquerque, NMThe pilot’s failure to select an adequate landing area.NTSB WPR09CA466Accident · Minor injuriesData collectionFinal reportBeech A23-19 · Tehachapi, CAThe pilot's failure to attain an established approach path while on final approach resulting in an improper flare and bounced landing.NTSB ERA09CA533Accident · No injuriesData collectionFinal reportCessna 182 · Montauk, NYThe pilot’s failure to attain the proper touchdown point while landing.NTSB ERA09LA469Accident · 1 fatalLimited investigationFinal reportRaytheon 58 · Teterboro, NJThe complete loss of thrust due to the second-in-command’s (SIC) inadvertent feathering of both propellers during a high-speed, low-altitude approach. Contributing to the accident was the pilot-in-command’s inadequate monitoring of the SIC’s performance.…NTSB ANC09CA085Accident · No injuriesData collectionFinal reportCessna 140 · Fairbanks, AKThe pilot's failure to achieve a proper touchdown point, resulting in an overrun and a nose over.NTSB WPR09CA276Accident · No injuriesData collectionFinal reportCessna A185F · Wenatchee, WAThe pilot's misjudged approach and failure to attain the proper touchdown point.NTSB CEN09CA332Accident · No injuriesData collectionFinal reportHughes 369A · Baltimore, OHThe pilot's failure to attain a proper touchdown point, and his decision not to perform a go-around.NTSB CEN09CA317Accident · Serious injuriesData collectionFinal reportCessna 182E · Martinsville, INThe pilot's failure to attain the proper touchdown point during landing and his delay in initiating a successful go-around, which resulted in a loss of airspeed and an aerodynamic stall.NTSB ERA09CA252Accident · No injuriesData collectionFinal reportCessna/Air Repair 305F · Embden, METhe pilot's failure to obtain the proper touchdown point while landing.NTSB WPR09LA168Accident · No injuriesLimited investigationFinal reportCessna 182Q · Sedona, AZThe pilot's failure to achieve the proper touchdown point during a full-stop landing attempt. Contributing to the accident were the pilot's failure to ensure that the aircraft was properly configured for landing, his not initiating a go-around, and a…