NTSB investigations: Cessna 172M

10 cases on aircraft the registry lists as Cessna 172M, where the sequence of events included Landing gear collapse. 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: 10 cases
20082
20101
20173
20181
20202
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 ('2072418')
      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\" = '094' 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 CEN25LA230Accident · No injuriesClass 4 · LimitedFinal reportCessna 172 · Wichita, KSThe student pilot’s failure to maintain directional control during the takeoff that resulted in a runway excursion.Jun 28, 2025 · N1591V · Substantial damageNTSB CEN20CA351Accident · No injuriesClass 4 · Data collectionFinal reportCessna 172 · Conway, ARThe pilot’s improper recovery from a bounced landing.Aug 2, 2020 · N13184 · Substantial damageNTSB CEN20CA154Accident · No injuriesData collectionFinal reportCessna 172 · Ft Worth, TXThe student pilot’s failure to maintain a stabilized approach and the flight instructor's delayed remedial action to initiate a go-around, which resulted in a runway overrun and impact with runway lights and fences.Apr 22, 2020 · N13005 · Substantial damageNTSB GAA18CA201Accident · Minor injuriesData collectionFinal reportCessna 172 · Livermore, CAThe student pilot’s failure to maintain runway centerline and flight instructor’s delayed remedial action during landing.Apr 5, 2018 · N1438U · Substantial damageNTSB GAA18CA097Accident · No injuriesData collectionFinal reportCessna 172 · Monroe, MIThe student pilot’s improper yaw control during the landing flare and the flight instructor’s failure to take remedial action, which resulted in a hard landing.Dec 21, 2017 · N4491R · Substantial damageNTSB GAA17CA394Accident · No injuriesData collectionFinal reportCessna 172 · TamuningThe pilot's improper landing flare, which resulted in a porpoised landing.Jul 2, 2017 · N80328 · Substantial damageNTSB GAA17CA254Accident · No injuriesData collectionFinal reportCessna 172 · Columbia, KYThe pilot’s failure to maintain a flare during landing in variable, gusting wind conditions.Apr 28, 2017 · N64144 · Substantial damageNTSB WPR10CA323Accident · No injuriesData collectionFinal reportCessna 172M · Twin Falls, IDThe student pilot's improper landing flare.Jul 1, 2010 · N64427 · Substantial damageNTSB LAX08CA165Accident · No injuriesData collectionFinal reportCessna 172M · Byron, CAThe flight instructor's inadequate compensation for the wind conditions, and his inadequate supervision of the student pilot. Factors contributing to the accident were a sudden wind shift and wind gusts.Jun 6, 2008 · N73403 · Substantial damageNTSB MIA08CA104Accident · No injuriesData collectionFinal reportCessna 172M · Savannah, GAThe pilot's failure to maintain directional control on landing touchdown with a crosswind.May 23, 2008 · N73471 · Substantial damage