NTSB investigations: Cessna 172L

11 cases on aircraft the registry lists as Cessna 172L, where the sequence of events included 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

20102026
NTSB investigations: Cessna 172L per year, 2010–2026: 11 cases
20101
20111
20121
20131
20151
20181
20191
20242
20251
20261

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 ('2072432')
      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\" = '300' 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 WPR26LA303Accident · No injuriesClass 4 · LimitedInvestigation openCessna 172L · Upland, CAAug 16, 2026 · N7526G · Substantial damageNTSB CEN25LA112Accident · No injuriesClass 4 · LimitedFinal reportCessna 172L · Romeo, MIThe pilot's failure to maintain directional control during the landing roll. Contributing to the accident was the soft, wet grass.Mar 7, 2025 · N7550G · Substantial damageNTSB WPR24LA219Accident · No injuriesClass 4 · LimitedFinal reportCessna 172L · Oxnard, CAThe student pilot’s failure to maintain directional control during the takeoff roll.Jun 29, 2024 · N2835Q · Substantial damageNTSB WPR24LA078Accident · No injuriesClass 3 · LimitedFinal reportCessna 172L · Grass Valley, CALoss of control during the landing roll due to a malfunctioning brake for undetermined reasons.Jan 18, 2024 · N7250Q · Substantial damageNTSB GAA19CA192Accident · Minor injuriesData collectionFinal reportCessna 172 · Stephenville, TXThe student pilot's improper landing flare, which resulted in a hard landing, and his subsequent failure to maintain directional control in gusting crosswind conditions that exceeded the airplane’s demonstrated crosswind for landing, which resulted in a…Mar 31, 2019 · N902RA · Substantial damageNTSB GAA18CA161Accident · No injuriesData collectionFinal reportCessna 172 · Green Valley, AZThe pilot’s failure to maintain directional control of the airplane during landing with a tailwind.Mar 12, 2018 · N418DD · Substantial damageNTSB ERA15CA106Accident · No injuriesData collectionFinal reportCessna 172L · New Castle, PAPilot's inadequate control of the airplane during the landing roll, which resulted in a runway excursion.Jan 16, 2015 · N7079Q · Substantial damageNTSB CEN13LA167Accident · No injuriesLimited investigationFinal reportCessna 172L · Idabel, OKThe student pilot's failure to maintain directional control during landing, which resulted in a runway excursion.Feb 7, 2013 · N7974G · Substantial damageNTSB ERA12CA162Accident · No injuriesData collectionFinal reportCessna 172L · Grand Isle, VTThe pilot's inability to stop the airplane on a grass runway with undetected ice.Jan 28, 2012 · N811P · Substantial damageNTSB ERA11CA176Accident · No injuriesData collectionFinal reportCessna 172L · Fayetteville, GAThe pilot's decision to land with excessive speed in gusting, tailwind conditions, resulting in a runway overrun.Mar 3, 2011 · N7067Q · Substantial damageNTSB ERA11LA105Accident · No injuriesLimited investigationFinal reportCessna 172 · Dublin, NCThe pilot’s improper touchdown speed which resulted in a runway overrun. Contributing to the accident was the undetermined malfunction of the airspeed indicator.Dec 31, 2010 · N4383Q · Substantial damage