NTSB investigations, 2018
14 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\") = 2018
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") = 2018 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 GAA19CA084Accident · Serious injuriesData collectionFinal reportPiper PA28 · Casa Grande, AZThe student pilot's failure to maintain a proper glidepath during the approach, which resulted in impact with a fence and terrain.NTSB GAA19CA016Accident · No injuriesData collectionFinal reportPiper PA24 · Winder, GAThe pilot’s failure to maintain an adequate approach path at night after an electrical failure, which resulted in the airplane striking runway lights.NTSB GAA19CA001Accident · No injuriesData collectionFinal reportCessna 340 · Keokuk, IAThe pilot's failure to correctly identify the runway environment during an instrument approach at night in instrument meteorological conditions because he mistook building lights for runway lights, which resulted in landing short of the runway.NTSB GAA18CA551Accident · No injuriesData collectionFinal reportPiper PA28 · Cypress, TXThe student pilot’s improper approach path after the airplane encountered turbulence, which resulted in the airplane landing hard short of the runway.NTSB ERA18LA224Accident · No injuriesClass 3 · LimitedFinal reportGlasair SHA · Greenville, NCA total loss of engine power for reasons that could not be determined based on the available information. Contributing to the accident was the pilot’s misjudgment of the airplane’s glidepath during the forced landing, which resulted in the airplane touching…NTSB GAA18CA443Accident · No injuriesData collectionFinal reportJust JA30 Superstol · Chelan Falls, WAThe pilot's improper approach over a river, which resulted in a collision with a dock.NTSB GAA18CA406Accident · No injuriesData collectionFinal reportBeech 76 · Fort Lauderdale, FLThe pilot receiving instruction's failure to maintain a proper approach path and her delayed go-around during a simulated emergency landing, which resulted in landing short of the runway. Contributing to the accident was the flight instructor's failure to…NTSB GAA18CA395Accident · No injuriesData collectionFinal reportCostruzioni Aeronautiche Tecna P2002 Sierra · San Carlos, CAThe pilot’s failure to maintain a proper glidepath and crosswind correction during landing, which resulted in an aerodynamic stall.NTSB GAA18CA410Accident · No injuriesData collectionFinal reportAyres S2R · Pantego, NCThe pilot's failure to maintain the proper approach path during landing, which resulted in landing short of the runway.NTSB ANC18CA052Accident · No injuriesData collectionFinal reportCessna 182 · Chugiak, AKThe pilot's mismanagement of the engine controls due to distraction in the traffic pattern, which resulted in a hard landing short of the runway.NTSB GAA18CA375Accident · No injuriesData collectionFinal reportTaylorcraft F19 · Goose Bay, AKThe pilot’s failure to maintain a proper approach path during landing in dusky, flat light conditions, which resulted in a tree strike.NTSB GAA18CA254Accident · No injuriesData collectionFinal reportBeech 58 · Sisters, ORThe pilot’s failure to maintain sufficient altitude during approach in gusting crosswind conditions, which resulted in an attempted rejected landing and a runway undershoot.NTSB GAA18CA126Accident · No injuriesData collectionFinal reportCessna 180 · Nenana, AKThe pilot’s failure to maintain an adequate approach path to an unimproved airstrip, which resulted in a hard landing short of the airstrip.NTSB GAA18CA104Accident · Minor injuriesData collectionFinal reportGeldermann Bert E Lancair Legacy · Friday Harbor, WAThe pilot’s inability to maintain the landing flare, which resulted in the airplane landing hard short of the runway. Contributing to the accident was the cockpit canopy opening in flight.