NTSB investigations: Cessna 172K

11 cases on aircraft the registry lists as Cessna 172K, where the sequence of events included Loss of engine power (total). 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

20102026
NTSB investigations: Cessna 172K per year, 2010–2026: 11 cases
20101
20112
20122
20142
20192
20241
20261

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 ('2072430')
      AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' s WHERE s.case_mkey = x.case_mkey AND s.aircrafts_position = x.position AND s.\"tier2Number\" = '341' AND s.case_mkey IN (SELECT case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' WHERE \"isDefiningEvent\")))
  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 CEN26LA094Accident · No injuriesClass 3 · LimitedPreliminary reportCessna 172K · Amery, WIOn January 16, 2026, about 1130 central standard time, a Cessna 172 airplane, N79118, was substantially damaged when it was involved in an accident near Amery, Wisconsin. The pilot was not injured. The airplane was operated as a Title 14 Code of Federal…Jan 16, 2026 · N79118 · Substantial damageNTSB ERA24LA388Accident · Minor injuriesClass 3 · LimitedFinal reportCessna 172K · Spartanburg, SCMaintenance personnel’s failure to follow the engine manufacturer’s maintenance guidance, which resulted in the assembly of the engine with an obstructed oil passage, a subsequent lack of lubrication to the front main bearing, and a total loss of engine power.Sep 20, 2024 · N7037G · Substantial damageNTSB ERA19LA280Accident · No injuriesClass 3 · LimitedFinal reportCessna 172 · Manville, NJA total loss of engine power due to the ingestion of sealant material that had loosened inside the carburetor airbox.Sep 24, 2019 · N78192 · Substantial damageNTSB CEN19CA239Accident · No injuriesData collectionFinal reportCessna 172 · Oshkosh, WIThe pilot's improper fuel planning and decision to not divert to a closer airport when the planned flight profile changed, which resulted in a total loss of engine power due to fuel exhaustion.Jul 28, 2019 · N79575 · Substantial damageNTSB ERA14FA428Accident · 2 fatalField investigationFinal reportCessna 172 · Selkirk, NYA loss of engine power for reasons that could not be determined because postaccident examination of the airframe and engine did not reveal any anomalies that would have precluded normal operation.Sep 8, 2014 · N79438 · Substantial damageNTSB CEN14LA134Accident · No injuriesLimited investigationFinal reportCessna 172K · Milan, ILThe pilot’s delayed use of carburetor heat while operating the airplane in atmospheric conditions conducive to carburetor icing, which resulted in a total loss of engine power due to carburetor icing during a short final approach.Jan 26, 2014 · N4VN · Substantial damageNTSB ERA12LA241Accident · No injuriesLimited investigationFinal reportCessna 172K · Belfast, METhe flight instructor’s failure to ensure the radio was set correctly to activate the pilot-controlled lighting, which resulted in poor positioning for a proper landing and a subsequent off-runway forced landing during an attempted go-around. Contributing to…Mar 20, 2012 · N46492 · Substantial damageNTSB ERA12LA234Accident · No injuriesLimited investigationFinal reportCessna 172K · Pensacola, FLA total loss of engine power due to the improper installation of the crankshaft gear bolt or lockplate by maintenance personnel. Contributing to the accident was the lack of suitable terrain for a forced landing.Mar 16, 2012 · N79509 · Substantial damageNTSB ERA11CA441Accident · No injuriesData collectionFinal reportCessna 172K · Sylacauga, ALA stuck exhaust-valve on the number one cylinder which resulted in a loss of engine power.Aug 5, 2011 · N7214G · Substantial damageNTSB CEN11CA322Accident · No injuriesData collectionFinal reportCessna 172K · Farmersville, TXA loss of engine power due to fuel starvation as a result of the pilot's improper fuel management.May 5, 2011 · N46400 · Substantial damageNTSB 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…Sep 25, 2010 · N84249 · Substantial damage