NTSB investigations: Cessna 172S

11 cases on aircraft the registry lists as Cessna 172S, where NTSB found Tree(s). 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 172S per year, 2008–2026: 11 cases
20083
20102
20121
20141
20151
20171
20181
20191

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 ('2072439', '2072442')
      AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_findings.parquet' f WHERE f.case_mkey = x.case_mkey AND f.aircrafts_position = x.position AND starts_with(f.\"findingCode\", '03022020')))
  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 GAA19CA401Accident · No injuriesData collectionFinal reportCessna 172 · Vineyard Haven, MAThe pilot's failure to maintain lateral position in relation to the instrument approach course at night in instrument meteorological conditions, which resulted in collision with a tree.Jul 11, 2019 · N677DM · Substantial damageNTSB GAA18CA323Accident · No injuriesData collectionFinal reportCessna 172 · Fuquay Varina, NCThe flight instructor’s failure to maintain adequate clearance from overgrown brush during taxi, which resulted in entanglement with the brush and a subsequent impact with a tree.Jun 2, 2018 · N1305B · Substantial damageNTSB GAA18CA074Accident · No injuriesData collectionFinal reportCessna 172 · Bowie, MDThe pilot’s failure to maintain situational awareness during the approach to land. Contributing to the accident was the pilot’s distraction by the instrument panel during the approach.Nov 30, 2017 · N474SP · Substantial damageNTSB ERA15LA094Accident · No injuriesLimited investigationFinal reportCessna 172 · Norfolk, VAThe engine’s failure to regain full power after a simulated engine failure for reasons that could not be determined during postaccident examinations and testing.Jan 6, 2015 · N2102P · Substantial damageNTSB WPR15LA014Accident · Serious injuriesLimited investigationFinal reportCessna 172S · Big Bear, CAA partial loss of engine power for reasons that could not be determined because postaccident examination of the airframe and engine did not reveal any anomalies that would have precluded normal operation.Oct 16, 2014 · N612SP · Substantial damageNTSB ERA12CA496Accident · Minor injuriesData collectionFinal reportCessna 172S · Culpeper, VAThe pilot’s failure to maintain directional control during an attempted takeoff.Aug 3, 2012 · N6276Z · Substantial damageNTSB WPR11CA037Accident · No injuriesData collectionFinal reportCessna 172S · Port Townsend, WAThe pilot's improper flare/touchdown while landing, resulting in a loss of directional control and a runway excursion.Nov 4, 2010 · N14511 · Substantial damageNTSB WPR11CA035Accident · No injuriesData collectionFinal reportCessna 172S · Branscomb, CAThe pilot's failure to maintain clearance from trees during the landing roll on an unimproved airstrip.Nov 1, 2010 · N3542V · Substantial damageNTSB ERA09LA064Accident · Minor injuriesLimited investigationFinal reportCessna 172S · Groton, CTThe student pilot’s failure to maintain a proper descent profile to avoid trees during the night visual approach and the flight instructor’s inadequate oversight.Nov 19, 2008 · N2337F · Substantial damageNTSB MIA08CA124Accident · No injuriesData collectionFinal reportCessna 172S · Orangeburg, SCThe pilot's failure to obtain the proper touchdown point on landing.Jun 20, 2008 · N65357 · Substantial damageNTSB LAX08CA102Accident · No injuriesData collectionFinal reportCessna 172S · Gualala, CAThe pilot's decision not to use all of the available runway, his premature rotation and failure to obtain and maintain an adequate airspeed to continue the takeoff that resulted in a stall/mush, an aborted takeoff, a runway overrun, and a collision with…Apr 13, 2008 · N21705 · Substantial damage