NTSB investigations, 2013
17 cases where the sequence of events included Landing area overshoot.
Cases per year
| 2008 | 35 |
|---|---|
| 2009 | 26 |
| 2010 | 38 |
| 2011 | 30 |
| 2012 | 24 |
| 2013 | 17 |
| 2014 | 19 |
| 2015 | 20 |
| 2016 | 28 |
| 2017 | 14 |
| 2018 | 14 |
| 2019 | 13 |
| 2020 | 11 |
| 2021 | 21 |
| 2022 | 16 |
| 2023 | 8 |
| 2024 | 25 |
| 2025 | 25 |
| 2026 | 17 |
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\") = 2013
AND c.\"mKey\" IN (SELECT s.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' s WHERE s.\"tier2Number\" = '380' 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") = 2013 AND c."mKey" IN (SELECT s.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' s WHERE s."tier2Number" = '380' 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 ERA14CA017Accident · Serious injuriesData collectionFinal reportBeech A36 · Burnsville, NCThe pilot's failure to achieve a proper touchdown point during landing, which resulted in a runway excursion.NTSB ERA14CA031Accident · Serious injuriesData collectionFinal reportSchweizer SGS 1 26E · Eighty Four, PAThe pilot's failure to maintain proper airspeed and glide path, which resulted in an overshoot, a hard landing, and a subsequent collision with terrain. Contributing to the accident was the pilot's lack of total experience in make and model.NTSB ERA14CA037Accident · No injuriesData collectionFinal reportPiper PA 28-150 · Newport, NHThe pilot's incorrect glide path, which resulted in a landing area overshoot and a runway excursion.NTSB WPR13LA419Accident · No injuriesLimited investigationFinal reportPiper PA60 602P · Sandpoint, IDThe pilot's failure to fly the approach at the appropriate landing speed and attain the correct touchdown point, which resulted in a runway overrun.NTSB CEN13CA489Accident · No injuriesData collectionFinal reportBeech 58P · Peoria, ILThe pilot did not attain the proper touchdown point during landing, which resulted in a runway excursion and impact with a perimeter fence.NTSB WPR13CA328Accident · No injuriesData collectionFinal reportCessna 172S · Redlands, CAThe student pilot's improper flare and unsuccessful attempt to correct a bounced landing, which resulted in the overrun landing.NTSB ERA13CA315Accident · Minor injuriesData collectionFinal reportBeech A23-19 · Easton, PAThe pilot's improper touchdown point during landing, which resulted in a runway overrun. Contributing to the accident was the pilot’s decision to land with a tailwind condition and his lack of recent experience.NTSB WPR13CA273Accident · No injuriesData collectionFinal reportPiper PA-28-140 · Coolin, IDThe pilot’s failure to maintain an adequate glide path, which led to a runway excursion and collision with objects.NTSB ERA13LA276Accident · No injuriesLimited investigationFinal reportCessna 170 · Plainville, CTThe pilot’s overflight of the landing runway during a forced landing after a loss of engine power. Contributing to the accident was the pilot’s inadequate preflight which resulted in his failure to detect water contamination of the fuel system.NTSB WPR13FA227Accident · No injuriesField investigationFinal reportGates Learjet 35A · McMinnville, ORFailure of maintenance personnel to reattach the landing gear squat switches following maintenance, which rendered the airplane's steering, braking, and thrust reverser systems inoperative during landing. Contributing to the accident were the failure of both…NTSB ERA13LA241Accident · No injuriesLimited investigationFinal reportCessna 182E · Southwick, MAThe partial loss of engine power for reasons that could not be determined because postaccident examination of the engine did not reveal any malfunctions or failures that would have precluded normal operation.NTSB ERA13CA231Accident · No injuriesData collectionFinal reportCessna 182G · Arcadia, NYThe pilot's improper decision to continue a high approach with a tailwind, rather than perform a go-around, which resulted in an overrun on a wet, down-sloping, grassy runway.NTSB ERA13CA218Accident · Serious injuriesData collectionFinal reportCessna 172P · Davis, WVThe pilot’s improper glidepath as he approached the runway and his subsequent delayed decision to abort the landing.NTSB ERA13CA222Accident · No injuriesData collectionFinal reportCirrus Design SR22T · Milledgeville, GAThe student pilot’s failure to maintain a proper approach path for landing and the flight instructor’s delayed remedial action, which resulted in a runway undershoot and collision with a taxiway sign.NTSB CEN13CA226Accident · No injuriesData collectionFinal reportEdward W Gray Lancair 360 · Alexandria, LAThe pilot's failure to attain the proper touchdown point, and his decision to continue the landing, which resulted in a runway excursion.NTSB ERA13CA164Accident · Minor injuriesData collectionFinal reportPiper PA-25-235 · Groveland, FLThe pilot's failure to maintain the proper airspeed during a tailwind approach, his improper decision to continue a fast approach with a tailwind rather than go around, and his improper use of the wheel brakes during the landing roll.NTSB DCA13WA054Incident · No injuriesForeign investigationBoeing 737 · Seoul, South KoreaThe Aviation and Railway Investigation Board of Korea has notified the NTSB of an accident involving a Boeing 737 airplane that occurred on February 03, 2013. The NTSB has appointed a U.S. Accredited Representative to assist the ARAIB investigation under the…