NTSB investigations: Cessna 172S, 2011

9 cases on aircraft the registry lists as Cessna 172S, 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 172S, 2011 per year, 2008–2026: 117 cases
20089
20098
20107
20119
201212
20136
20146
20155
20168
20177
20187
20199
20206
20215
20222
20232
20244
20254
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 year(c.\"eventDate\") = 2011
    AND 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_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 WPR12CA038Accident · No injuriesData collectionFinal reportCessna 172S · Phoenix, AZThe student pilot's inadequate directional control during takeoff.Nov 12, 2011 · N24350 · Substantial damageNTSB WPR11CA466Accident · Minor injuriesData collectionFinal reportCessna 172S · Phoenix, AZThe pilot’s failure to maintain directional control during the landing rollout.Sep 26, 2011 · N169ME · Substantial damageNTSB WPR11CA440Accident · No injuriesData collectionFinal reportCessna 172 · Phoenix, AZThe pilot's failure to maintain directional control during the landing roll.Sep 8, 2011 · N5275S · Substantial damageNTSB ERA11CA343Accident · No injuriesData collectionFinal reportCessna 172S · Covington, GAThe pilot's failure to maintain directional control during takeoff.Jun 14, 2011 · N6026P · DestroyedNTSB WPR11LA201Accident · No injuriesLimited investigationFinal reportCessna 172S · Payson, AZThe pilot's decision to conduct a touch-and-go arrival during his first flight to a high elevation airport, which resulted in an improper mixture adjustment and a partial loss of engine power for the takeoff and attempted climbout.Apr 16, 2011 · N1835U · Substantial damageNTSB ERA11CA244Accident · No injuriesData collectionFinal reportCessna 172S · Saint Petersburg, FLThe failure of the student pilot to maintain directional control during a touch-and-go landing.Apr 13, 2011 · N2468Z · Substantial damageNTSB ERA11FA146Accident · 2 fatalField investigationFinal reportCessna 172S · New Smyrna Beach, FLThe flight instructor's failure to recognize or implement adequate remedial action to counter the effects of spatial disorientation. Contributing to the accident was the spatial disorientation experienced by one or both pilots.Feb 16, 2011 · N6345L · Substantial damageNTSB ERA11CA132Accident · No injuriesData collectionFinal reportCessna 172S · St. Petersburg, FLThe student pilot's failure to maintain directional control while attempting to turn the airplane onto a taxiway after landing.Jan 29, 2011 · N6013J · Substantial damageNTSB ERA11FA118Accident · 2 fatalField investigationFinal reportCessna 172S · North Myrtle Beach, SCThe pilot's loss of airplane control during a missed approach due to spatial disorientation.Jan 18, 2011 · N2100V · Substantial damage