NTSB investigations: Cessna 172F

5 cases on aircraft the registry lists as Cessna 172F, 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

20112026
NTSB investigations: Cessna 172F per year, 2011–2026: 5 cases
20112
20161
20191
20201

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 ('2072414')
      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 ERA21LA056Accident · No injuriesClass 3 · LimitedFinal reportCessna 172 · Atlanta, GAThe Cessna pilot’s failure to tune his radio to the common traffic advisory frequency, which resulted in a lack of awareness of the other aircraft operating at the airport. Contributing to the accident was the Cessna pilot’s lack of understanding of the…Nov 25, 2020 · N8125U · 2 aircraft · Substantial damageNTSB GAA19CA323Accident · No injuriesData collectionFinal reportCessna 172 · Yellow Pine, IDThe pilot's improper approach, which resulted in the airplane touching down with insufficient runway remaining to stop on the runway, a runway overrun, and subsequent collision with bushes and terrain.Jun 9, 2019 · N5344R · Substantial damageNTSB WPR16LA138Accident · 3 fatalLimited investigationFinal reportCessna 172 · Brookings, ORThe pilot's spatial disorientation and loss of situational awareness during the departure turn in dark night conditions, which resulted in an in-flight collision with water.Jul 5, 2016 · N7870U · DestroyedNTSB ERA12CA053Accident · Serious injuriesData collectionFinal reportCessna 172F · Smoketown, PAThe pilot did not maintain a proper approach path, which resulted in a collision with a tree.Oct 28, 2011 · N5613R · Substantial damageNTSB CEN11LA388Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Ironton, OHThe total loss of engine power for reasons that could not be determined because postaccident examination did not reveal any anomalies that would have precluded normal operation.May 28, 2011 · N5663R · Substantial damage