NTSB investigations: Cessna 172K, 2010
4 cases on aircraft the registry lists as Cessna 172K. 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
| 1967 | 1 |
|---|---|
| 1968 | 3 |
| 1969 | 29 |
| 1970 | 48 |
| 1971 | 66 |
| 1972 | 52 |
| 1973 | 43 |
| 1974 | 40 |
| 1975 | 21 |
| 1976 | 30 |
| 1977 | 29 |
| 1978 | 25 |
| 1979 | 15 |
| 1980 | 12 |
| 1981 | 13 |
| 1982 | 11 |
| 1983 | 6 |
| 1984 | 5 |
| 1985 | 7 |
| 1986 | 6 |
| 1987 | 12 |
| 1988 | 9 |
| 1989 | 5 |
| 1990 | 7 |
| 1991 | 11 |
| 1992 | 4 |
| 1993 | 7 |
| 1994 | 12 |
| 1995 | 6 |
| 1996 | 12 |
| 1997 | 5 |
| 1998 | 6 |
| 1999 | 6 |
| 2000 | 10 |
| 2001 | 5 |
| 2002 | 8 |
| 2003 | 10 |
| 2004 | 7 |
| 2005 | 4 |
| 2006 | 2 |
| 2007 | 8 |
| 2008 | 3 |
| 2009 | 1 |
| 2010 | 4 |
| 2011 | 6 |
| 2012 | 6 |
| 2013 | 5 |
| 2014 | 7 |
| 2015 | 2 |
| 2016 | 6 |
| 2017 | 1 |
| 2018 | 2 |
| 2019 | 8 |
| 2020 | 1 |
| 2021 | 3 |
| 2022 | 4 |
| 2023 | 4 |
| 2024 | 4 |
| 2025 | 4 |
| 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\") = 2010
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072430'))
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") = 2010
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072430'))
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 CEN11LA073Accident · Serious injuriesLimited investigationFinal reportCessna 172K · San Antonio, TXThe pilot's failure to maintain aircraft control, which resulted in an aerodynamic stall. Contributing to the accident was the pilot's decision to land with a tailwind.NTSB ERA10FA502Accident · 2 fatalField investigationFinal reportCessna 172 · Chatsworth, GAThe pilot's inadequate flight planning and in-flight fuel management resulting in a total loss of engine power due to fuel exhaustion. Contributing to the accident was the operator's failure to ensure aircraft records pertaining to engine modifications and…NTSB CEN10CA405Accident · No injuriesData collectionFinal reportCessna 172K · Boyne City, MIThe pilot's failure to attain the proper touchdown point and delayed go-around.NTSB ERA10CA212Accident · Minor injuriesData collectionFinal reportCessna 172K · Romney, WVThe pilot's improper decision to land with a 20-knot tailwind and his failure to initiate a go-around, which resulted in a runway overrun.