NTSB investigations: Cessna 172M, 2025
12 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\") = 2025
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") = 2025
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 ANC26LA008Accident · No injuriesClass 4 · LimitedFinal reportCessna 172M · Palmer, AKThe student pilot’s failure to maintain directional control during the landing roll.NTSB ERA26LA062Accident · Minor injuriesClass 4 · LimitedFinal reportCessna 172 · Pensacola, FLThe pilot’s exceedance of the critical angle of attack during initial climb which resulted in an aerodynamic stall.NTSB WPR26FA043Accident · 2 fatalClass 3 · FieldPreliminary reportCessna 172M · Poleta, CAOn November 10, 2025, at about 1515 Pacific standard time, Cessna 172M, N13221, was substantially damaged when it was involved in an accident near Poleta, California. A pilot-rated passenger and a passenger were fatally injured, and the pilot was seriously…NTSB CEN26LA035Accident · No injuriesClass 4 · LimitedFinal reportCessna 172 · Grantsburg, WIThe collision with a white-tail deer during the landing in dark night visual conditions.NTSB ERA26LA007Accident · Minor injuriesClass 3 · LimitedPreliminary reportCessna 172 · Miami, FLOn October 07, 2025, at 1440 eastern daylight time, a Cessna 172M, N433PT, was substantially damaged when it was involved in an accident near Miami, Florida. The private pilot and the flight instructor were uninjured. The airplane was operated as a Title 14…NTSB ERA26LA016Accident · No injuriesClass 4 · LimitedFinal reportCessna 172 · Bluffton, OHThe pilot’s improper landing flare, which resulted in a hard, bounced landing.NTSB WPR25FA268Accident · 1 fatalClass 3 · FieldPreliminary reportCessna 172M · Fort Morgan, COOn August 31, 2025, about 1040 mountain daylight time, a Cessna 172M, N61657, and an Extra Flugzeugproduktions-UND EA 300/LC, N330AN, were both destroyed when they collided midair near Fort Morgan, Colorado. The pilot and safety pilot of the Cessna received…NTSB CEN25LA355Accident · Minor injuriesClass 4 · LimitedFinal reportCessna 172M · Lubbock, TXThe pilot’s mismanagement of available fuel, which resulted in a loss of engine power due to fuel starvation.NTSB WPR25LA296Accident · No injuriesClass 4 · LimitedFinal reportCessna 172M · Albany, ORThe pilot’s improper landing flare and subsequent improper recovery from a bounced landing.NTSB CEN25LA230Accident · No injuriesClass 4 · LimitedFinal reportCessna 172 · Wichita, KSThe student pilot’s failure to maintain directional control during the takeoff that resulted in a runway excursion.NTSB ANC25LA023Accident · No injuriesClass 4 · LimitedFinal reportCessna 172 · Cantwell, AKThe pilot’s failure to maintain altitude during a low-altitude maneuver which resulted in inadvertent ground contact and a nose over.NTSB ANC25LA020Accident · Minor injuriesClass 3 · LimitedFinal reportCessna 172M · Kapolei, HIThe flight instructor’s failure to avoid wake turbulence from a heavy airplane departing from a parallel runway, which resulted in a loss of airplane control during initial climb after a touch-and-go landing.