NTSB investigations: Cessna 172R, 2017

8 cases on aircraft the registry lists as Cessna 172R. 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

19982026
NTSB investigations: Cessna 172R, 2017 per year, 1998–2026: 228 cases
19982
199912
20008
20018
20026
20038
20049
200513
20067
200718
200812
20094
20106
201112
201210
20135
201410
20155
20169
20178
201810
20198
20206
20218
20224
20237
20246
20254
20263

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\") = 2017
    AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072401'))
  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 ANC18LA013Accident · No injuriesLimited investigationFinal reportCessna 172R · Huntingdon, TNA total loss of engine power for reasons that could not be determined because a postaccident engine examination and testing revealed no preimpact mechanical malfunctions or failures that would have precluded normal operation.Dec 2, 2017 · N9730F · Substantial damageNTSB ANC18LA014Accident · No injuriesLimited investigationFinal reportCessna 172 · Miami, FLThe pilot's decision to continue the landing after a loss of visual cues during a night landing.Dec 1, 2017 · N537HF · Substantial damageNTSB WPR18LA039Accident · No injuriesClass 3 · LimitedFinal reportCessna 172R · Redding, CAThe fatigue separation of the crankshaft due to a fatigue fracture, which resulted in a total loss of engine power and a subsequent off-airport landing and impact with a fence.Nov 2, 2017 · N2103T · Substantial damageNTSB GAA17CA482Accident · No injuriesData collectionFinal reportCessna 172 · Kearney, NEThe pilot’s failure to maintain directional control of the airplane during the landing roll, which resulted in a runway excursion.Aug 2, 2017 · N91966 · Substantial damageNTSB GAA17CA389Accident · No injuriesData collectionFinal reportCessna 172 · Shreveport, LAThe student’s improper landing flare, which resulted in a hard landing.Jul 3, 2017 · N2173Z · Substantial damageNTSB ERA17CA216Accident · No injuriesData collectionFinal reportCessna 172 · Emporia, VAThe student pilot's failure to maintain an adequate airspeed for landing and his improper landing flare and recovery from a bounced landing.Jun 28, 2017 · N2460A · Substantial damageNTSB CEN17CA140Accident · No injuriesData collectionFinal reportCessna 172R · Cahokia, ILA hard landing for reasons that could not be determined based on the available evidence.Feb 23, 2017 · N51827 · Substantial damageNTSB ERA17LA095Accident · No injuriesLimited investigationFinal reportCessna 172 · Clearwater, FLThe pilot's improper landing flare, which resulted in damage to the engine firewall.Jan 26, 2017 · N2382R · Substantial damage