NTSB investigations: Cessna 172M

16 cases on aircraft the registry lists as Cessna 172M, where NTSB found Not determined, general. 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

20082026
NTSB investigations: Cessna 172M per year, 2008–2026: 16 cases
20082
20092
20122
20133
20143
20161
20191
20201
20221

Latest 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 ('2072418')
      AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_findings.parquet' f WHERE f.case_mkey = x.case_mkey AND f.aircrafts_position = x.position AND starts_with(f.\"findingCode\", '05000000')))
  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.

NTSB WPR22LA371Accident · 1 fatalClass 3 · LimitedFinal reportCessna 172M · Pacific Ocean, CAUndetermined because the airplane and pilot were not located.Aug 20, 2022 · N9670VNTSB WPR21LA032Accident · 1 fatalClass 3 · LimitedFinal reportCessna 172 · Billings, MTThe pilot’s failure to maintain the proper descent glide path while on final approach for reasons that could not be determined from available evidence.Oct 31, 2020 · N124TW · Substantial damageNTSB GAA19CA258Accident · Serious injuriesData collectionFinal reportCessna 172 · Dexter, MIThe airplane's failure to maintain a climb for reasons that could not be determined based on the available evidence.May 11, 2019 · N21794 · Substantial damageNTSB WPR17FAMS2Accident · 3 fatalMissing aircraftFinal reportCessna 172M · Open water, HIUndetermined because the airplane was not located.Dec 31, 2016 · N174LL · DestroyedNTSB ERA15LA091Accident · Minor injuriesLimited investigationFinal reportCessna 172M · South Bimini, BahamasThe total loss of engine power for reasons that could not be determined because examination of the engine did not reveal any anomalies that would have precluded normal operation, which resulted in a subsequent ditching in the ocean.Dec 22, 2014 · N12182 · Substantial damageNTSB ERA14LA448Accident · No injuriesLimited investigationFinal reportCessna 172M · Leesburg, FLThe flight instructor’s delayed remedial action and his subsequent loss of directional control during landing on a wet runway for reasons that could not be determined because postaccident examination of the airplane revealed no anomalies.Sep 19, 2014 · N13394 · Substantial damageNTSB CEN14CA155Accident · No injuriesData collectionFinal reportCessna 172M · South Bend, INThe pilot involved and the phase of flight when the damage was incurred were not determined.Feb 26, 2014 · N9801V · Substantial damageNTSB ERA13LA339Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Farmingdale, NJThe airplane’s loss of lift shortly after picking up a banner for reasons that could not be determined because postaccident examinations revealed no anomalies that would have precluded normal operation.Jul 26, 2013 · N61929 · Substantial damageNTSB WPR13LA224Accident · No injuriesLimited investigationFinal reportCessna 172M · Lakeport, CALoss of engine power during climb due to a failure of the No. 2 piston assembly; the reason for the failure could not be determined because of the extent of damage to the piston assembly.Apr 29, 2013 · N20800 · Substantial damageNTSB WPR13LA113Accident · No injuriesLimited investigationFinal reportCessna 172 · Wilcox, AZThe loss of engine power for reasons that could not be determined because postaccident examination did not reveal any abnormalities that would have precluded normal operation.Feb 2, 2013 · N1421V · Substantial damageNTSB CEN13LA104Accident · No injuriesLimited investigationFinal reportCessna 172M · Arcola, TXThe loss of engine power during initial climb for reasons that could not be determined because postaccident examination of the engine did not reveal any anomalies that would have precluded normal operation.Dec 7, 2012 · N172BJ · Substantial damageNTSB WPR12LA099Accident · No injuriesLimited investigationFinal reportCessna 172M · Cusick, WAA total loss of engine power during cruise flight for reasons that could not be determined because postaccident examination did not reveal any anomalies that would have precluded normal operation.Feb 9, 2012 · N5100R · Substantial damageNTSB ERA09LA379Accident · No injuriesLimited investigationFinal reportCessna 172M · Princeton, NJThe partial loss of engine power for undetermined reasons.Jul 4, 2009 · N64178 · Substantial damageNTSB ERA09LA310Accident · No injuriesLimited investigationFinal reportCessna 172M · Sarasota, FLA loss of engine power for undetermined reasons.May 30, 2009 · N12151 · Substantial damageNTSB NYC08CA269Accident · Minor injuriesData collectionFinal reportCessna 172M · Jefferson, NCA loss of directional control during the takeoff roll for undetermined reasons. Contributing to the severity of the event was the descending embankment adjacent to the runway.Aug 3, 2008 · N73594 · Substantial damageNTSB LAX08LA240Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Bountiful, UTA partial loss of engine power for undetermined reasons.Jul 22, 2008 · N7672 · Substantial damage