NTSB investigations: Cessna 172B

9 cases on aircraft the registry lists as Cessna 172B, where the first occurrence was “Loss of control - in flight”. 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

19862026
NTSB investigations: Cessna 172B per year, 1986–2026: 9 cases
19861
19881
19911
19922
19942
20031
20071

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 ('2072406')
      AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o.\"occurrenceNumber\" = 1 AND o.\"occurrenceCode\" = 250))
  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 SEA07CA107Accident · Minor injuriesData collectionFinal reportCessna 172B · Los Angeles, CAThe pilot's failure to maintain adequate airspeed during performance of a go around, resulting in an inadvertent stall and in-flight collision with the ground.Apr 19, 2007 · N7546X · Substantial damageNTSB FTW03LA116Accident · No injuriesLimited investigationFinal reportCessna 172B · Tulsa, OKThe pilot's failure to maintain airspeed which resulted in an inadvertent stall.Mar 26, 2003 · N6947X · Substantial damageNTSB CHI95LA055Accident · No injuriesLimited investigationFinal reportCessna 172 · Allegan, MIthe student pilot's failure to maintain directional control which resulted in the inability to obtain proper runway alignment. Related factors are the student pilot's lack of total flight experience and the snowbank.Dec 21, 1994 · N7656X · Substantial damageNTSB CHI94LA216Accident · Serious injuriesLimited investigationFinal reportCessna 172B · Shiocton, WIthe pilot's failure to maintain Vso during takeoff. Factors related to the accident was the disregard for performance data and trees.Jul 1, 1994 · N7472X · DestroyedNTSB ATL92FA108Accident · 3 fatalField investigationFinal reportCessna 172B · Cherokee, NCThe failure of the pilot to maintain control of the aircraft as a result of spatial disorientation. The lack of total flight time, and rain in the accident area were factors in the accident.May 24, 1992 · N8102X · DestroyedNTSB FTW92LA088Accident · No injuriesLimited investigationFinal reportCessna 172B · Scottsville, TXPilots' inadequate compensation for unfavorable windshift. A facator was the unfavorable wind.Apr 1, 1992 · N7492X · Substantial damageNTSB DEN91LA058Accident · Minor injuriesLimited investigationFinal reportCessna 172B · La Junta, COThe pilot's failure to maintain adequate airspeed and the resultant inadvertent stall. The pilot's failure to raise the flaps was a factor in the accident.Mar 31, 1991 · N6904X · Substantial damageNTSB CHI89LA020Accident · Minor injuriesLimited investigationFinal reportCessna 172B · Columbus, OHStudent pilot's failure to maintain control of the airplane during landing flare.Oct 29, 1988 · N7418X · Substantial damageNTSB DEN86LA140Accident · No injuriesLimited investigationFinal reportCessna 172B · Alamosa, COThe student plt had soloed that morning. After a short rest period he flew with his instructor. He then flew a second solo flt. The student plt made two landings. On the third approach the plt made a go-around. On the next approach the acft stalled close to…May 19, 1986 · N6990X · Substantial damage