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
| 1975 | 1 |
|---|---|
| 1977 | 2 |
| 1978 | 2 |
| 1979 | 3 |
| 1990 | 1 |
| 1994 | 1 |
| 1995 | 1 |
| 1996 | 1 |
| 1998 | 1 |
| 2001 | 1 |
| 2011 | 1 |
| 2014 | 1 |
| 2017 | 1 |
Where
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.
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" DESCRun it at the DuckDB prompt, or in any tool that reads Parquet over HTTPS. More ways to query the release are on Use the data.
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.NTSB 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…NTSB ERA11CA138Accident · No injuriesData collectionFinal reportCessna 172 · Meriden, CTThe student pilot's loss of directional control during the landing rollout, resulting in a runway excursion.NTSB NYC01LA219Accident · No injuriesLimited investigationFinal reportCessna 172M · Danbury, CTAn inoperative airspeed indicator and the pilot's improper recovery from the bounced landing.NTSB 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…NTSB NYC96LA075Accident · No injuriesLimited investigationFinal reportCessna 172M · Warehouse Point, CTthe pilot's inadequate compensation for the crosswind and gusts. The wind conditions were factors.NTSB 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.NTSB 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.NTSB 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.NTSB NYC80FNE03|NYC80FNE04Accident · No injuriesClosedCessna 172M · Stratford, CTNTSB NYC79FA059Accident · No injuriesClosedCessna 172M · Griswold, CTNTSB NYC79FNE16Accident · No injuriesClosedCessna 172 · Ellington, CTNTSB NYC78FA097Accident · 1 fatalClosedCessna 172M · Windsor Locks, CTNTSB NYC78FNE17Accident · No injuriesClosedCessna 172M · East Windsor, CTNTSB NYC77FNE23Accident · No injuriesClosedCessna 172M · Plainville, CTNTSB NYC77FNE13Accident · No injuriesClosedCessna 172 · Chester, CTNTSB NYC76AN023Accident · 1 fatalClosedCessna 172M · Stamford, CT