NTSB investigations: Cessna 172K
9 cases on aircraft the registry lists as Cessna 172K, where the first occurrence was “Overrun”. Aircraft are matched to the registry by N-number and event date, checked against the reported serial number, make and model, so older matches can be wrong.
Cases per year
| 1987 | 1 |
|---|---|
| 1994 | 2 |
| 1995 | 2 |
| 1996 | 1 |
| 2000 | 1 |
| 2001 | 1 |
| 2003 | 1 |
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 c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072430')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o.\"occurrenceNumber\" = 1 AND o.\"occurrenceCode\" = 340))
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 c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072430')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o."occurrenceNumber" = 1 AND o."occurrenceCode" = 340))
ORDER BY c."eventDate" DESC, c."ntsbNumber" DESCRun 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 NYC04CA028Accident · No injuriesData collectionFinal reportCessna 172K · Kilbourne, OHThe pilot's failure to obtain the proper touchdown point which resulted in an overrun and subsequent nose over.NTSB ANC01LA085Accident · No injuriesLimited investigationFinal reportCessna 172K · Wasilla, AKThe pilot's delay in aborting the takeoff roll.NTSB ATL01LA006Accident · No injuriesLimited investigationFinal reportCessna 172K · Indiantown, FLThe pilot had excessive airspeed, misjudged the landing distance, and did not perform a go-around, which resulted in a nose over. The ditch was a contributing factor.NTSB NYC96LA124Accident · No injuriesLimited investigationFinal reportCessna 172 · Gardner, MAthe pilot 's misjudgment of speed and distance during landing.NTSB BFO96LA030Accident · No injuriesLimited investigationFinal reportCessna 172K · Lovingston, VAthe pilot's improper planning/decision during the approach/landing phase of flight. Related factors were: the pilot's selection of the wrong runway, and the gusty tailwind conditions.NTSB CHI95LA070Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Cottage Grove, WIThe pilot's selection of unsuitable terrain/runway for landing. Factors related to the accident were: the unfavorable wind, icy runway condition, and snowbank at the end of the runway.NTSB CHI94LA326Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Brookfield, WIthe commercial pilot's poor planning/decision making. A related factor is the wet, grass runway selected for landing.NTSB NYC94LA060Accident · No injuriesLimited investigationFinal reportCessna 172K · Dayton, OHthe pilot's failure to maintain directional control which resulted in a runway overrun. Factors are the pilot's improper recovery from a bounced landing, and his lack of experience.NTSB ATL88LA033Accident · No injuriesLimited investigationFinal reportCessna 172K · Cumming, GAThe student plt rptd that the airplane contacted the rwy and bounced twice during the ldg flare. Once he got the airplane on the rwy, he realized that the airspeed was 'too high' for the rwy remaining and attempted to ground loop the airplane to stop it. The…