NTSB investigations: Cessna 172M, 2009
14 cases on aircraft the registry lists as Cessna 172M. 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
| 1972 | 3 |
|---|---|
| 1973 | 24 |
| 1974 | 59 |
| 1975 | 82 |
| 1976 | 104 |
| 1977 | 99 |
| 1978 | 92 |
| 1979 | 80 |
| 1980 | 59 |
| 1981 | 50 |
| 1982 | 53 |
| 1983 | 34 |
| 1984 | 35 |
| 1985 | 34 |
| 1986 | 38 |
| 1987 | 29 |
| 1988 | 28 |
| 1989 | 38 |
| 1990 | 37 |
| 1991 | 36 |
| 1992 | 31 |
| 1993 | 37 |
| 1994 | 24 |
| 1995 | 29 |
| 1996 | 23 |
| 1997 | 35 |
| 1998 | 30 |
| 1999 | 22 |
| 2000 | 22 |
| 2001 | 30 |
| 2002 | 26 |
| 2003 | 24 |
| 2004 | 18 |
| 2005 | 16 |
| 2006 | 18 |
| 2007 | 16 |
| 2008 | 24 |
| 2009 | 14 |
| 2010 | 15 |
| 2011 | 13 |
| 2012 | 18 |
| 2013 | 20 |
| 2014 | 20 |
| 2015 | 9 |
| 2016 | 10 |
| 2017 | 19 |
| 2018 | 14 |
| 2019 | 13 |
| 2020 | 16 |
| 2021 | 8 |
| 2022 | 24 |
| 2023 | 12 |
| 2024 | 14 |
| 2025 | 12 |
| 2026 | 8 |
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\") = 2009
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072418'))
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 x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072418'))
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 WPR10CA089Accident · No injuriesData collectionFinal reportCessna 172M · Albion, IDThe pilot's failure to maintain clearance from mountainous terrain while maneuvering in gusting winds.NTSB CEN10CA075Accident · No injuriesData collectionFinal reportCessna 172 · Pearland, TXThe student pilot's failure to control the airplane's descent rate during the short-field landing, resulting in a hard landing. Contributing to the accident was the flight examiner's delayed response.NTSB WPR10CA073Accident · No injuriesData collectionFinal reportCessna 172M · Diamond Point, WAThe pilot's inadequate compensation for the variable and unfavorable wind conditions.NTSB WPR10CA013Accident · No injuriesData collectionFinal reportCessna 172H · Tucson, AZThe pilot's failure to maintain directional control during the takeoff ground roll.NTSB WPR09CA348Accident · Serious injuriesData collectionFinal reportCessna 172M · Thermopolis, WYThe instructor pilot's failure to ensure that his dual student maintained clearance from the terrain during a dark night visual flight rules descent.NTSB ERA09LA379Accident · No injuriesLimited investigationFinal reportCessna 172M · Princeton, NJThe partial loss of engine power for undetermined reasons.NTSB WPR09FA316Accident · 2 fatalField investigationFinal reportCessna 172M · Rimrock, WAThe pilot's failure to maintain clearance from trees during a go-around. Contributing to the accident was the pilot's lack of flight experience, and his delayed initiation of a go-around.NTSB WPR09CA305Accident · Minor injuriesData collectionFinal reportCessna 172M · McCall, IDA total loss of engine power during descent due to fuel exhaustion as a result of the pilot's failure to determine the fuel quantity prior to departure.NTSB ERA09LA310Accident · No injuriesLimited investigationFinal reportCessna 172M · Sarasota, FLA loss of engine power for undetermined reasons.NTSB WPR09FA246Accident · Minor injuriesField investigationFinal reportCessna 172 · Burlington, WAThe failure of the pilot of another airplane to maintain adequate visual lookout during the approach.NTSB ERA09LA272Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Chesterfield, SCThe partial loss of engine power due to a broken exhaust valve. Contributing to the accident was the operator's exceedance of the engine manufacturer's recommended time before overhaul.NTSB WPR09CA206Accident · No injuriesData collectionFinal reportCessna 172M · Corona, CAThe pilot's improper landing flare.NTSB ERA09CA175Accident · No injuriesData collectionFinal reportCessna 172 · Reidsville, GAThe pilot's failure to maintain control of the airplane during an attempted recovery from a stall/spin.NTSB CEN09CA140Accident · No injuriesData collectionFinal reportCessna 172M · Little Rock, ARThe loss of engine power due to the missing nut on the bolt connecting the throttle cable and carburetor's lever arm.