NTSB investigations: Cessna 172N

10 cases on aircraft the registry lists as Cessna 172N, where the sequence of events included Landing area overshoot. 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 172N per year, 2008–2026: 10 cases
20082
20091
20102
20111
20191
20242
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 ('2072434')
      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\" = '380' 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 CEN25LA099Accident · No injuriesClass 4 · LimitedFinal reportCessna 172N · Pearland, TXThe pilot’s poor flight planning and decision making, which resulted in a loss of engine power due to fuel exhaustion.Feb 17, 2025 · N2913E · Substantial damageNTSB ERA24LA339Accident · No injuriesClass 4 · LimitedFinal reportCessna 172 · Medina, OHThe student pilot’s failure to attain a proper touchdown point, which resulted in a runway overrun and subsequent noseover.Aug 6, 2024 · N6543E · Substantial damageNTSB WPR24LA229Accident · Minor injuriesClass 3 · LimitedFinal reportCessna 172N · San Diego, CAA failure of the No. 2 cylinder due to fatigue cracking as the result of an undersized fillet radius around the edge of the cylinder head dome.Jul 2, 2024 · N74C · Substantial damageNTSB GAA19CA122Accident · No injuriesData collectionFinal reportCessna 172 · Miami, FLThe student pilot's failure to control the airplane's speed and direction during the approach, which resulted in landing long, a runway excursion, and impact with a windsock.Jan 19, 2019 · N734AY · Substantial damageNTSB ERA11LA168Accident · Serious injuriesLimited investigationFinal reportCessna 172N · Welch, WVThe unlicensed pilot’s decision to land on a closed runway with a tailwind, his failure to attain the proper touchdown point, and his delayed decision to attempt a go-around, resulting in a collision with trees.Feb 27, 2011 · N739NY · Substantial damageNTSB CEN11CA004Accident · No injuriesData collectionFinal reportCessna 172N · Wabash, INThe student pilot's failure to maintain proper airspeed during the landing and certificated flight instructor's failure to execute a go-around.Oct 1, 2010 · N2140E · Substantial damageNTSB ERA10LA322Accident · Serious injuriesLimited investigationFinal reportCessna 172N · West Milford, NJThe student pilot’s control interference which resulted in a landing with a higher than normal airspeed, and the commercial pilot’s failure to initiate a go-around to avoid the runway overrun.Jun 20, 2010 · N738QZ · Substantial damageNTSB ERA09CA539Accident · Minor injuriesData collectionFinal reportCessna 172 · Factoryville, PAThe flight instructor's delayed decision to take control of the airplane and execute a missed approach. Contributing to the accident was the lack of communication between the certificated flight instructor and the pilot receiving instruction.Sep 27, 2009 · N5123E · Substantial damageNTSB CHI08CA291Accident · No injuriesData collectionFinal reportCessna 172 · Wadsworth, OHThe pilot's excessive airspeed during the approach and landing and failure to perform a go-around. Contributing to the accident were the barricade and the down-sloping terrain at the end of the runway.Sep 19, 2008 · N739BX · Substantial damageNTSB NYC08CA248Accident · No injuriesData collectionFinal reportCessna 172N · Edgewater, MDThe pilot's misjudged distance/speed during landing.Jul 12, 2008 · N734AT · Substantial damage