NTSB investigations: Cessna 172S

8 cases on aircraft the registry lists as Cessna 172S, where the sequence of events included Simulated/training event. 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 172S per year, 2008–2026: 8 cases
20082
20091
20151
20172
20181
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\" = '600' 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 ERA25LA118Accident · No injuriesClass 4 · LimitedFinal reportCessna 172 · Kennesaw, GAThe student pilot’s failure to maintain an appropriate glide path and the flight instructor’s inadequate monitoring of the landing approach, which resulted in the airplane contacting the ground short of the runway.Jan 29, 2025 · N1159K · Substantial damageNTSB ERA18LA074Accident · No injuriesLimited investigationFinal reportCessna 172 · Babylon, NYThe partial loss of engine power after a simulated engine failure for reasons that could not be determined because a postaccident examination and an engine test run did not reveal any anomalies that would have precluded normal operation.Jan 29, 2018 · N294ME · Substantial damageNTSB GAA17CA351Accident · No injuriesData collectionFinal reportCessna 172 · Lawrence, KSThe student pilot's incorrect control application during landing after a simulated engine failure, which resulted in a hard, bounced landing, and the flight instructor's delayed action to perform a go-around in gusting wind conditions.Jun 10, 2017 · N99HV · Substantial damageNTSB WPR17FA063Accident · 1 fatalField investigationFinal reportCessna 172 · Ramona, CAThe flight instructor's failure to ensure that adequate clearance from terrain was maintained after performance of a simulated engine failure maneuver, which resulted in controlled flight into terrain.Feb 12, 2017 · N2179L · 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 CEN09CA148Accident · No injuriesData collectionFinal reportCessna 172 · Union Mills, INThe certificated flight instructor's failure to follow correct engine clearing procedures. A factor was the unsuitable landing area.Feb 1, 2009 · N53576 · Substantial damageNTSB NYC08CA230Accident · No injuriesData collectionFinal reportCessna 172 SP · Stevensville, MDThe flight instructor's delayed decision to go around.Jun 25, 2008 · N3504X · Substantial damageNTSB LAX08LA191Accident · 2 fatalLimited investigationFinal reportCessna 172S · Oceanside, CAFailure of the pilot to regain airplane control during an intentional stall/spin maneuver.Jun 23, 2008 · N2436F · Destroyed