NTSB investigations: Cessna 172E

9 cases on aircraft the registry lists as Cessna 172E, 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

20092026
NTSB investigations: Cessna 172E per year, 2009–2026: 9 cases
20092
20102
20121
20151
20192
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 ('2072412')
      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 WPR26LA081Accident · No injuriesClass 4 · LimitedFinal reportCessna 172E · Kingman, AZThe pilot’s failure to use a pre-takeoff checklist, which resulted in the fuel selector being in the off position, and subsequent loss of engine power during takeoff.Jan 14, 2026 · N7783U · Substantial damageNTSB GAA19CA236Accident · No injuriesData collectionFinal reportCessna 172 · Wasilla, AKThe flight instructor's failure to verify the fuel level, which resulted in a total loss of engine power due to fuel exhaustion and a subsequent forced landing and collision with a power line pole. Contributing to the accident was the student pilot's…May 1, 2019 · N3031U · Substantial damageNTSB ERA19TA098Accident · Minor injuriesClass 3Final reportCessna 172 · Lignum, VAA total loss of engine power for undetermined reasons.Feb 10, 2019 · N7414N · Substantial damageNTSB ERA15LA363Accident · Serious injuriesLimited investigationFinal reportCessna 172E · Gettysburg, PAThe total loss of engine power due to carburetor icing. Contributing to the accident was the pilot's failure to maintain a proper approach speed during the forced landing, which resulted in impact with trees.Sep 19, 2015 · N3647S · Substantial damageNTSB ERA12LA545Accident · Minor injuriesLimited investigationFinal reportCessna 172E · East Bend, NCA total loss of engine power during the initial climb after takeoff for reasons that could not be determined because examination of the engine did not reveal any anomalies that would have precluded normal operation.Sep 1, 2012 · N377SP · Substantial damageNTSB WPR11LA062Accident · Minor injuriesLimited investigationFinal reportCessna 172E · Suisun City, CAA total loss of engine power for undetermined reasons.Nov 27, 2010 · N5582T · Substantial damageNTSB ERA10FA202Accident · 1 fatalField investigationFinal reportCessna 172E · West Milford, NJThe complete loss of engine power due to fuel starvation.Apr 3, 2010 · N5528T · Substantial damageNTSB ERA09CA297Accident · No injuriesData collectionFinal reportCessna 172 · Perryville, MDA total loss of engine power due to fuel exhaustion as a result of the pilot’s inadequate preflight planning.May 20, 2009 · N3063U · Substantial damageNTSB CEN09LA143Accident · No injuriesLimited investigationFinal reportCessna 172E · Plano, TXA loss of engine power in flight due to fuel exhaustion as a result of the pilot's inadequate fuel planning.Jan 23, 2009 · N5420T · Substantial damage