NTSB investigations: Cessna 172P, CT

6 cases on aircraft the registry lists as Cessna 172P, where the first occurrence was “Loss of control - on ground/water”. 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

19832026
NTSB investigations: Cessna 172P, CT per year, 1983–2026: 6 cases
19831
19851
19871
19911
19981
20031

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.\"eventStateOrRegion\" = 'CT' AND c.\"eventCountry\" = 'USA'
    AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072436')
      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\" = 260))
  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 NYC03CA167Accident · No injuriesData collectionFinal reportCessna 172P · Plainfield, CTThe pilot's failure to maintain directional control, which resulted in a collision with a ditch. A factor in this accident was the crosswind condition.Jul 25, 2003 · N62152 · Substantial damageNTSB NYC98LA082Accident · No injuriesLimited investigationFinal reportCessna 172P · Plainville, CTThe pilot's inadequate crosswind compensation.Mar 29, 1998 · N9821L · Substantial damageNTSB NYC91LA106Accident · No injuriesLimited investigationFinal reportCessna 172P · Burlington, CTThe failure of the pilot to maintain directional control during the landing. Factors related to the accident were: improper use of the flight controls by the pilot, his lack of recent experience and total time, and the crosswind.Apr 6, 1991 · N64182 · Substantial damageNTSB NYC87LA213Accident · No injuriesLimited investigationFinal reportCessna 172P · Plainfield, CTWhile landing in crosswind conditions, the pilot failed to compensate for the conditions and lost directional control of the aircraft. The aircraft went down an embankment, collided with a fence and then flipped inverted.Aug 4, 1987 · N99171 · Substantial damageNTSB NYC85LA178Accident · Minor injuriesLimited investigationFinal reportCessna C172 · Ellington, CTThe acft collided with the ground during takeoff from rwy 01 at Ellington, Connecticut, and was substantially damaged but there was no fire. The pilot received minor injuries. The aircraft crashed for undetermined reasons.Jul 18, 1985 · N98651 · Substantial damageNTSB NYC83LA058Accident · No injuriesLimited investigationFinal reportCessna 172P · Bridgeport, CTAfter practicing three takeoffs and landings, a fourth takeoff was aborted. The student completed a run-up, checked the controls and received clearance to takeoff. He stated that he began rolling straight down the centerline, then at about 45 KTS, the plane…Jan 30, 1983 · N62264 · Substantial damage