NTSB investigations: Cessna 172M, CT

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

19752026
NTSB investigations: Cessna 172M, CT per year, 1975–2026: 17 cases
19751
19772
19782
19793
19901
19941
19951
19961
19981
20011
20111
20141
20171

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 ('2072418'))
  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 ERA17FA272Accident · 1 fatalField investigationFinal reportCessna 172 · New Milford, CTThe flight instructor's failure to ensure that the wing flaps were properly configured for takeoff, which resulted in an aerodynamic stall and loss of control during the initial climb.Aug 11, 2017 · N1727V · Substantial damageNTSB ERA14CA430Accident · Minor injuriesData collectionFinal reportCessna 172M · Watertown, CTThe pilot's decision to takeoff from a field which resulted in a collision with trees and the ground. Contributing to the accident was the pilot's failure to correctly identify the destination airport and runway, which resulted in an off-airport landing in…Sep 9, 2014 · N20469 · Substantial damageNTSB ERA11CA138Accident · No injuriesData collectionFinal reportCessna 172 · Meriden, CTThe student pilot's loss of directional control during the landing rollout, resulting in a runway excursion.Feb 7, 2011 · N9622Q · Substantial damageNTSB NYC01LA219Accident · No injuriesLimited investigationFinal reportCessna 172M · Danbury, CTAn inoperative airspeed indicator and the pilot's improper recovery from the bounced landing.Aug 26, 2001 · N9869Q · Substantial damageNTSB IAD98FA072Accident · 1 fatalField investigationFinal reportCessna 172M · Hebron, CTThe pilot's failure to obtain a weather briefing which resulted in inadvertent flight into instrument meteorological conditions, and his failure to maintain control of the airplane due to spatial disorientation. Factors in this accident were low ceilings and…Jun 22, 1998 · N12912 · DestroyedNTSB NYC96LA075Accident · No injuriesLimited investigationFinal reportCessna 172M · Warehouse Point, CTthe pilot's inadequate compensation for the crosswind and gusts. The wind conditions were factors.Feb 24, 1996 · N12219 · Substantial damageNTSB NYC95LA135Accident · No injuriesLimited investigationFinal reportCessna 172M · Bridgewater, CTthe loss of engine power for undetermined reasons resulting in a forced landing, and a subsequent collision with trees.Jun 28, 1995 · N9176H · Substantial damageNTSB NYC94LA093Accident · No injuriesLimited investigationFinal reportCessna 172M · Groton, CTthe pilot's inadequate visual lookout during taxi, which resulted in the airplane's wing tip striking ground support equipment.May 24, 1994 · N6891H · Substantial damageNTSB NYC90LA056Accident · Serious injuriesLimited investigationFinal reportCessna 172 · Danbury, CTImproper maintenance, inadequate surveillance by the company/operator, and inadequate preflight by the pilot, which resulted in a fire during an attempted engine start. A factor related to the accident was: the unsecured fuel line.Jan 16, 1990 · N9093H · DestroyedNTSB NYC80FNE03|NYC80FNE04Accident · No injuriesClosedCessna 172M · Stratford, CTNov 19, 1979 · N13660 · 2 aircraft · Substantial damageNTSB NYC79FA059Accident · No injuriesClosedCessna 172M · Griswold, CTJul 14, 1979 · N73297 · Substantial damageNTSB NYC79FNE16Accident · No injuriesClosedCessna 172 · Ellington, CTJun 6, 1979 · N13435 · Substantial damageNTSB NYC78FA097Accident · 1 fatalClosedCessna 172M · Windsor Locks, CTSep 20, 1978 · N20285 · DestroyedNTSB NYC78FNE17Accident · No injuriesClosedCessna 172M · East Windsor, CTApr 1, 1978 · N12219 · Substantial damageNTSB NYC77FNE23Accident · No injuriesClosedCessna 172M · Plainville, CTJun 19, 1977 · N9574H · Substantial damageNTSB NYC77FNE13Accident · No injuriesClosedCessna 172 · Chester, CTApr 8, 1977 · N9920Q · Substantial damageNTSB NYC76AN023Accident · 1 fatalClosedCessna 172M · Stamford, CTAug 17, 1975 · N22234 · Destroyed