NTSB investigations: Cessna 172H

20 cases on aircraft the registry lists as Cessna 172H, where the sequence of events included Collision with terr/obj (non-CFIT). 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 172H per year, 2008–2026: 20 cases
20082
20091
20103
20112
20121
20141
20152
20182
20193
20221
20241
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 ('2072424')
      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\" = '470' 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 ERA25LA324Accident · Minor injuriesClass 4 · LimitedFinal reportCessna 172 · New Smyrna Beach, FLMaintenance personnel’s failure to detect and address water contamination of the airplane’s fuel system, which resulted in a total loss of engine power during initial climb.Aug 29, 2025 · N1607F · Substantial damageNTSB CEN24LA186Accident · No injuriesClass 4 · LimitedFinal reportCessna 172H · Belle Chasse, LAThe inadequate landing flare by the flight instructor that resulted in a loss of directional control and impact with terrain.May 1, 2024 · N2782L · Substantial damageNTSB ERA22FA161Accident · 1 fatalClass 3 · FieldFinal reportCessna 172 · Dahlonega, GAThe pilot’s delay in initiating a go-around and his failure to maintain airplane control during the initial climb, which resulted in the exceedance of the airplane’s critical angle of attack and an aerodynamic stall.Mar 19, 2022 · N1410F · Substantial damageNTSB CEN19LA233Accident · No injuriesClass 3 · LimitedFinal reportCessna 172 · Kingston, OKThe partial loss of engine power due to a stuck exhaust valve.Jul 22, 2019 · N8251L · Substantial damageNTSB GAA19CA477Accident · No injuriesData collectionFinal reportCessna 172 · Greer, SCThe pilot's improper decision to continue a steep and fast approach to landing, which resulted in a runway overrun and collision with a drainage culvert.Jun 29, 2019 · N724BC · Substantial damageNTSB GAA19CA172Accident · No injuriesData collectionFinal reportCessna 172 · Oskaloosa, IAThe student pilot's failure to maintain directional control during landing with a left quartering tailwind, which resulted in a runway excursion, impact with a snowbank, and a nose-over.Mar 11, 2019 · N334SL · Substantial damageNTSB ANC19LA006Accident · No injuriesLimited investigationFinal reportCessna 172 · Anchorage, AKThe pilot's failure to maintain airplane control during the landing flare, which resulted in the wing striking the runway. Contributing to the accident was a partial loss of engine power, which resulted from fuel contamination.Nov 3, 2018 · N2809L · Substantial damageNTSB GAA18CA485Accident · No injuriesData collectionFinal reportCessna 172 · Sallisaw, OKThe student pilot's loss of directional control during the landing roll.Aug 4, 2018 · N707TM · Substantial damageNTSB GAA15CA136Accident · No injuriesData collectionFinal reportCessna 172H · Cottonwood Falls, KSThe pilot's failure to attain adequate airspeed to climb the airplane out of ground effect, which resulted in an aerodynamic stall and a collision with terrain.Jun 6, 2015 · N2536L · Substantial damageNTSB CEN15LA215Accident · No injuriesLimited investigationFinal reportCessna 172 - H · Circleville, TXThe failure of the engine to regain normal power after a simulated engine failure due to carburetor icing, which resulted in a forced landing on muddy terrain and a subsequent nose-over.Mar 24, 2015 · N8282L · Substantial damageNTSB CEN14LA347Accident · Serious injuriesLimited investigationFinal reportCessna 172H · Baytown, TXThe pilot’s failure to verify the fuel onboard before the flight, which resulted in a total loss of engine power due to fuel exhaustion.Jul 8, 2014 · N3732R · Substantial damageNTSB CEN12CA361Accident · No injuriesData collectionFinal reportCessna 172H · Moscow Mills, MOThe pilot's failure to maintain control of the airplane during takeoff in a gusty crosswind, which resulted in a runway excursion.Jun 10, 2012 · N3736R · Substantial damageNTSB WPR11LA135Accident · No injuriesLimited investigationFinal reportCessna 172H · Wikieup, AZA total loss of engine power during cruise flight resulting from the failure of a fuel line. Contributing to the accident was inadequate maintenance inspections that failed to detect the deteriorating fuel line.Feb 15, 2011 · N2561L · Substantial damageNTSB CEN11LA138Accident · 1 fatalLimited investigationFinal reportCessna 172H · Walnut Grove, MOThe pilot's loss of control for undetermined reasons. Contributing to the accident was the pilot's fatigue.Jan 4, 2011 · N1416F · Substantial damageNTSB ERA10LA293Accident · Minor injuriesLimited investigationFinal reportCessna 172H · Dania Beach, FLThe pilot’s improper fuel management, which resulted in a loss of engine power due to fuel exhaustion.Jun 1, 2010 · N1435F · Substantial damageNTSB ERA10LA233Accident · 1 fatalLimited investigationFinal reportCessna 172H · Archer, FLThe pilot's failure to maintain adequate airspeed for undetermined reasons while maneuvering in the vicinity of an airport, which resulted in an aerodynamic stall and hard landing.Apr 16, 2010 · N8112L · Substantial damageNTSB ANC10CA015Accident · No injuriesData collectionFinal reportCessna 172H · Nightmute, AKThe pilot's failure to maintain control of the airplane in a strong gusting wind, and his decision to taxi for takeoff in such conditions.Jan 23, 2010 · N3718F · Substantial damageNTSB ERA09CA382Accident · No injuriesData collectionFinal reportCessna 172H · Clifton, METhe pilot's mismanagement of his fuel supply which resulted in fuel starvation and a loss of engine power.Jul 3, 2009 · N1782F · Substantial damageNTSB CHI08CA264Accident · No injuriesData collectionFinal reportCessna 172 · Pullman, MIA complete loss of engine power for undetermined reasons. A contributing factor was the rough terrain encountered during the forced landing.Aug 24, 2008 · N3901R · Substantial damageNTSB DEN08CA087Accident · No injuriesData collectionFinal reportCessna 172H · Brookshire, TXThe pilot's decision to duck under marked transmission lines and his failure to maintain clearance from the fence. Contributing to the accident was the marked transmission lines.May 11, 2008 · N3870R · Substantial damage