NTSB investigations: Cessna 172M

15 cases on aircraft the registry lists as Cessna 172M, where the sequence of events included Collision during takeoff/land. 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: 15 cases
20082
20091
20101
20111
20122
20131
20151
20211
20221
20231
20241
20252

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\" = '490' 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 CEN26LA035Accident · No injuriesClass 4 · LimitedFinal reportCessna 172 · Grantsburg, WIThe collision with a white-tail deer during the landing in dark night visual conditions.Nov 5, 2025 · N9490H · Substantial damageNTSB 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 ERA25LA081Accident · Minor injuriesClass 4 · LimitedFinal reportCessna 172 · Lakewood, NJThe pilot’s delay in performing a go-around, which resulted in a collision with trees at the end of the runway.Dec 19, 2024 · N12194 · Substantial damageNTSB ERA23LA271Accident · Minor injuriesClass 4 · LimitedFinal reportCessna 172 · Seymore, TNThe flight instructor’s failure to properly configure the wing flaps for a soft-field takeoff on a short runway, which resulted in a runway overrun and collision with trees.Jun 18, 2023 · N12395 · Substantial damageNTSB ERA23LA043Accident · Minor injuriesClass 4 · LimitedFinal reportCessna 172M · Roberta, GAThe pilot’s failure to maintain a stabilized approach speed on landing, which resulted in a runway excursion and collision with logs.Oct 27, 2022 · N4349R · Substantial damageNTSB WPR21LA230Accident · No injuriesClass 4 · LimitedFinal reportCessna 172 · Fields, ORThe pilot’s failure to maintain directional control during landing on a highway, which resulted in an impact with terrain and subsequent nose over.Jun 12, 2021 · N20406 · Substantial damageNTSB GAA16CA011Accident · No injuriesData collectionFinal reportCessna 172M · McMinnville, ORThe flight instructor's failure to correct the student pilot's approach path during the final approach, which resulted in a collision with runway threshold lights. Contributing to the accident was the student pilot's failure to attain and maintain the…Oct 2, 2015 · N20488 · Substantial damageNTSB ERA13CA170Accident · No injuriesData collectionFinal reportCessna 172M · Hendersonville, NCThe student pilot’s failure to maintain control of the airplane during an attempted go-around in gusty tailwind conditions.Mar 15, 2013 · N61756 · Substantial damageNTSB ERA12CA546Accident · No injuriesData collectionFinal reportCessna 172M · Bardstown, KYThe flight instructor's decision to turn the fuel selector to the off position and his delayed remedial actions to restart the engine, which resulted in fuel starvation and a subsequent forced landing.Aug 30, 2012 · N21214 · Substantial damageNTSB CEN12CA270Accident · No injuriesData collectionFinal reportCessna 172M · Three Rivers, MICollision with a deer during the takeoff roll.May 1, 2012 · N30380 · Substantial damageNTSB ERA11CA205Accident · Minor injuriesData collectionFinal reportCessna 172M · Statesville, NCThe certified flight instructor's inadequate remedial action during the go-around, which resulted in a collision with trees.Mar 23, 2011 · N32SF · Substantial damageNTSB WPR10FA384Accident · Minor injuriesField investigationFinal reportCessna 172 · Roche Harbor, WAThe pilot’s failure to attain an adequate climb airspeed due to his use of flaps for takeoff, and his selection of a runway, which resulted in an uphill, and possibly downwind, takeoff and subsequent collision with a known obstacle. Contributing to the…Aug 6, 2010 · N9730H · Substantial damageNTSB WPR09FA316Accident · 2 fatalField investigationFinal reportCessna 172M · Rimrock, WAThe pilot's failure to maintain clearance from trees during a go-around. Contributing to the accident was the pilot's lack of flight experience, and his delayed initiation of a go-around.Jun 28, 2009 · N4396R · Substantial damageNTSB LAX08CA234Accident · No injuriesData collectionFinal reportCessna 172M · Leavenworth, WAThe pilot's inadequate preflight planning and failure to attain a sufficient airspeed to continue the takeoff. A contributing factor was the high density altitude and short runway.Jul 20, 2008 · N80849 · Substantial damageNTSB SEA08CA126Accident · No injuriesData collectionFinal reportCessna 172M · Dixie, IDThe pilot's failure to maintain adequate clearance from the vegetation during takeoff.May 3, 2008 · N20406 · Substantial damage