NTSB investigations: Cessna 172S

15 cases on aircraft the registry lists as Cessna 172S, where the sequence of events included Off-field or emergency landing. 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 172S per year, 2009–2026: 15 cases
20091
20101
20112
20122
20131
20151
20171
20191
20213
20231
20251

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 ('2072439', '2072442')
      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\" = '440' 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 ERA26LA014Accident · No injuriesClass 4 · LimitedFinal reportCessna 172 · North Lauderdale, FLA total loss of engine power due to a fuel delivery system leak, which allowed air to enter the fuel system. The source of the leak could not be determined based on the available evidence.Oct 13, 2025 · N1206U · Substantial damageNTSB ERA24LA033Accident · Minor injuriesClass 3 · LimitedFinal reportCessna 172S · Orlando, FLA partial loss of engine power during initial climb after takeoff for undetermined reasons.Nov 10, 2023 · N91PF · Substantial damageNTSB ERA21LA388Accident · No injuriesClass 3 · LimitedFinal reportCessna 172 · Port Orange, FLThe separation of the nut from the stud and the fracture of the bolt that secured the crankshaft idler gear to the engine crankcase, which resulted in a total loss of engine power due to the inability of the left crankshaft idler gear assembly to drive of the…Sep 29, 2021 · N116SV · Substantial damageNTSB CEN21LA414Accident · Minor injuriesClass 3 · LimitedFinal reportCessna 172S · LaSalle, COA loss of engine power for undetermined reasons.Sep 10, 2021 · N2099J · Substantial damageNTSB CEN21LA268Accident · No injuriesClass 4 · LimitedFinal reportCessna 172S · Saint James, LAThe in-flight fatigue failure of an air-conditioning system hose which resulted in a precautionary landing and impact with a road sign.Jun 10, 2021 · N365CP · Substantial damageNTSB GAA19CA401Accident · No injuriesData collectionFinal reportCessna 172 · Vineyard Haven, MAThe pilot's failure to maintain lateral position in relation to the instrument approach course at night in instrument meteorological conditions, which resulted in collision with a tree.Jul 11, 2019 · N677DM · Substantial damageNTSB WPR18LA002Accident · No injuriesLimited investigationFinal reportCessna 172S · Tonopah, NVThe pilot's failure to enrich the mixture during the descent, as required by the Pilot's Operating Handbook (POH), and his subsequent failure to follow the POH emergency procedures, which resulted in an excessively lean fuel/air mixture and subsequent loss of…Oct 2, 2017 · N5311H · Substantial damageNTSB ERA15LA094Accident · No injuriesLimited investigationFinal reportCessna 172 · Norfolk, VAThe engine’s failure to regain full power after a simulated engine failure for reasons that could not be determined during postaccident examinations and testing.Jan 6, 2015 · N2102P · Substantial damageNTSB ERA13LA291Accident · No injuriesLimited investigationFinal reportCessna 172S · Clearwater, FLA total loss of engine power for reasons that could not be determined because neither postaccident visual examinations nor test runs of the engine revealed any anomalies that would have precluded normal operation.Jun 19, 2013 · N426SJ · Substantial damageNTSB ERA12LA274Accident · No injuriesLimited investigationFinal reportCessna 172S · Daytona Beach, FLA total loss of engine power due to a catastrophic engine failure, the origin of which could not be determined during postaccident examination.Apr 9, 2012 · N375LP · Substantial damageNTSB ERA12IA169Incident · No injuriesIncident investigationFinal reportCessna 172S · Jackson, MSThe separation of the propeller blade tip due to fatigue cracking that initiated at the blade’s leading edge.Jan 28, 2012 · N427CP · No damageNTSB WPR11LA362Accident · Minor injuriesLimited investigationFinal reportCessna 172S · Syracuse, UTThe failure of the maintenance technicians who installed the engine to properly tighten the fuel injection servo to a spider supply line, which caused a loss of engine power due to fuel starvation.Aug 2, 2011 · N235GW · Substantial damageNTSB WPR11LA284Accident · No injuriesLimited investigationFinal reportCessna 172S · Palo Alto, CAA total loss of engine power for undetermined reasons during the landing approach over unsuitable terrain.Jun 24, 2011 · N222MF · Substantial damageNTSB ERA11LA015Accident · No injuriesLimited investigationFinal reportCessna 172SP · Boynton Beach, FLThe loss of engine power for undetermined reasons.Oct 10, 2010 · N423FT · Substantial damageNTSB CEN09LA442Accident · Minor injuriesLimited investigationFinal reportCessna 172S · Boyd, TXA total loss of engine power due to the pilot's improper leaning procedures, resulting in a forced landing and collision with a fence.Jul 14, 2009 · N2446F · Substantial damage