NTSB investigations: Cessna 172M

16 cases on aircraft the registry lists as Cessna 172M, where the defining event was Runway excursion. 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: 16 cases
20082
20101
20122
20131
20141
20151
20171
20181
20225
20231

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' e WHERE e.case_mkey = x.case_mkey AND e.aircrafts_position = x.position AND e.\"isDefiningEvent\" AND e.\"tier2Number\" = '300'))
  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 WPR23LA315Accident · No injuriesClass 4 · LimitedFinal reportCessna 172M · Marysville, CAThe flight instructor’s failure to monitor the airplane’s speed during a high-speed taxi, resulting in a runway excursion.Aug 10, 2023 · N20268 · 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 CEN22LA445Accident · No injuriesClass 4 · LimitedFinal reportCessna 172M · Monticello, IAThe pilot’s failure to maintain a proper approach airspeed and glidepath which resulted in a long landing and his inability to stop the airplane on available runway and the subsequent runway excursion.Sep 28, 2022 · N5244R · Substantial damageNTSB WPR22LA356Accident · No injuriesClass 4 · LimitedFinal reportCessna 172M · Superior, MTThe pilot’s excessive airspeed during a landing, which resulted in a runway overrun and collision with terrain.Sep 26, 2022 · N12113 · Substantial damageNTSB WPR22LA194Accident · No injuriesClass 4 · LimitedFinal reportCessna 172M · East Sound, WAThe pilot's failure to attain a proper touchdown point which, resulted in a runway overrun and collision with trees.May 30, 2022 · N20487 · Substantial damageNTSB ERA22LA113Accident · No injuriesClass 4 · LimitedFinal reportCessna 172 · Waynesboro, VAThe student pilot’s loss of directional control while landing.Jan 30, 2022 · N1766V · Substantial damageNTSB WPR19TA034Accident · Minor injuriesClass 3Final reportCessna 172 · Colorado Springs, COThe pilot's decision to perform a touch-and-go landing at a high-density altitude airport, with a tailwind, and on an upsloping runway, which resulted in decreased airplane performance and the airplane’s inability to become airborne within the available…Nov 20, 2018 · N27LA · Substantial damageNTSB CEN17LA082Accident · Serious injuriesLimited investigationFinal reportCessna 172M · Hobart, INThe pilot's failure to abort the landing when he recognized the airplane was traveling too fast, which resulted in impact with trees off the end of the runway.Jan 6, 2017 · N80374 · Substantial damageNTSB CEN16CA070Accident · No injuriesData collectionFinal reportCessna 172 · Rush City, MNThe student pilot did not maintain directional control of the airplane and applied excessive right rudder during landing.Nov 20, 2015 · N1180U · Substantial damageNTSB WPR14CA155Accident · No injuriesData collectionFinal reportCessna 172M · Anacortes, WAThe pilot's improper application of brakes during the landing roll resulted in a runway excursion and nose over.Apr 1, 2014 · N19982 · Substantial damageNTSB ANC14LA011Accident · No injuriesLimited investigationFinal reportCessna 172M · Bethel, AKThe pilot’s decision to abort the takeoff with insufficient runway remaining, which resulted in a runway excursion.Dec 15, 2013 · N20109 · Substantial damageNTSB ERA12CA270Accident · No injuriesData collectionFinal reportCessna 172M · Pottstown, PAThe pilot’s inadequate recovery from a bounced landing, which resulted in a loss of control.Apr 5, 2012 · N6871H · Substantial damageNTSB ERA12CA211Accident · No injuriesData collectionFinal reportCessna 172M · Mayaquez, PRThe pilot did not maintain control of the airplane while landing in crosswind conditions.Feb 19, 2012 · N5286H · Substantial damageNTSB CEN10CA158Accident · No injuriesData collectionFinal reportCessna 172M · Waupaca, WIThe student pilot's failure to maintain directional control while taking off in gusting winds.Mar 15, 2010 · N1472U · Substantial damageNTSB ANC09CA010Accident · No injuriesData collectionFinal reportCessna 172M · Girdwood, AKThe pilot's decision to attempt to take off on a snow-covered runway. Contributing to the accident was the snow-covered runway.Nov 8, 2008 · N9099H · Substantial damageNTSB ERA09CA010Accident · No injuriesData collectionFinal reportCessna 172 · Naples, METhe pilot's failure to maintain directional control of the airplane during takeoff. Contributing to the accident was the wet condition of the grass runway.Oct 3, 2008 · N20921 · Substantial damage