OpenAirDocs.org

NTSB investigations: Cessna 172I

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

19842026

Where

Open the map

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 ('2072426')
      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 CHI08FA033Accident · 1 fatalField investigationFinal reportCessna 172I · Gladwin, MIThe pilot's failure to maintain aircraft control while maneuvering at a low altitude. Contributing to the accident was the pilot's diverted attention while attempting to photograph ground objects.Nov 3, 2007 · N8353L · Substantial damageNTSB SEA07CA109Accident · Minor injuriesData collectionFinal reportCessna 172I · Peach Springs, AZThe pilot's failure to adequately compensate for the gusty wind condition encountered on final approach, resulting in a loss of control and an in-flight collision with a dirt berm. A contributing factor was the gusty wind condition.Apr 20, 2007 · N35562 · Substantial damageNTSB DFW05FA111Accident · 2 fatalField investigationFinal reportCessna 172 · Midland, TXThe pilot's failure to maintain airspeed which resulted in an inadvertent stall. A contributing factor was the low altitude.Apr 28, 2005 · N8314L · Substantial damageNTSB SEA05CA080Accident · No injuriesData collectionFinal reportCessna 172 · Yamhill, ORThe pilot's failure to maintain aircraft control while on final approach for landing. A crosswind, a fence post and the pilot's inadequate compensation for the crosswind condition were contributing factors.Apr 9, 2005 · N8400L · Substantial damageNTSB CHI99LA028Accident · No injuriesLimited investigationFinal reportCessna 172I · Jacksonville, ILthe student pilot's failure to maintain directional control of the airplane. Factors associated with the accident were the student's lack of experience and the road which the airplane contacted.Nov 13, 1998 · N35302 · Substantial damageNTSB LAX98FA141Accident · 2 fatalField investigationFinal reportCessna 172 · Ramona, CAThe loss of control of the aircraft on final approach for undetermined reasons.Apr 24, 1998 · N8364L · DestroyedNTSB SEA92FA161Accident · 1 fatalField investigationFinal reportCessna 172I · Donnelly, IDThe pilot's failure to maintain airspeed after takeoff while using improper obstacle takeoff procedures. Factors include excessive flap extension.Jul 24, 1992 · N27JF · Substantial damageNTSB ATL92LA077Accident · No injuriesLimited investigationFinal reportCessna 172I · Knightdale, NCThe pilot's inadequate compensation for crosswind conditions, and his failure to maintain aircraft control. A factor was the crosswind conditions at the airport.Apr 13, 1992 · N8471L · Substantial damageNTSB ATL92LA051Accident · No injuriesLimited investigationFinal reportCessna 172I · Bainbridge, GAThe pilot's failure to maintain airspeed on the initial climbout, and the inadvertent stall/mush which resulted. Factors in this accident were: the high obstructions (trees) near the airstrip.Mar 1, 1992 · N35637 · Substantial damageNTSB ATL92LA041Accident · No injuriesLimited investigationFinal reportCessna 172I · Gadsden, ALThe improper recovery from a bounced landing by the pilot under examination, and his subsequent failure to maintain directional control. Inadequate supervision by the designated examiner was a factor.Jan 22, 1992 · N35308 · Substantial damageNTSB ATL91LA093Accident · Minor injuriesLimited investigationFinal reportCessna 172I · Clanton, ALFailure of the pilot to maintain control of the aircraft during a go-around. The pilot's lack of experience was a related factor.May 14, 1991 · N46240 · Substantial damageNTSB MIA87FA188Accident · 1 fatalField investigationFinal reportCessna 172I · Ellisville, MSBfr the flt, the arpt owner adzd the plt not to fly, since he (the plt) appeared to be intoxicated. The plt 'said ok & left,' but returned aprx 1 hr later. A witness rprtd the plt atmtd to takeoff with full flaps. Drg the takeoff roll, theacft drifted off the…Jun 20, 1987 · N8446L · Substantial damageNTSB DEN87LA128Accident · No injuriesLimited investigationFinal reportCessna 172I · Taos, NMThe private plt and his CFI rated pax were practicing touch and go landings at the local arpt. During landing a wind gust pushed the acft off the runway centerline to the right. The runway shoulder was soft, a go-around attempt was unsuccessful and the acft…May 20, 1987 · N46231 · Substantial damageNTSB NYC85FFA01Accident · Serious injuriesFinal reportCessna 172I · Essex, NYWitnesses stated acft became airborne near the slight rise in the rwy, aprx 1500 ft down the rwy, and climbed to aprx 60 ft AGL. Acft shuttered and nose of acft pitched up. Left wing and nose then dropped. Acft continued descending to the left across a small…Oct 6, 1984 · N215NY · Substantial damage