NTSB investigations: Cessna 172N, CT
7 cases on aircraft the registry lists as Cessna 172N. 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
| 1980 | 1 |
|---|---|
| 1983 | 1 |
| 1987 | 1 |
| 1993 | 1 |
| 2000 | 1 |
| 2004 | 1 |
| 2025 | 1 |
Where
Open the mapLatest 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 ('2072434'))
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 ('2072434'))
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 ERA26LA033Accident · No injuriesClass 4 · LimitedFinal reportCessna 172 · Oxford, CTThe pilot’s failure to compensate for gusty crosswind conditions, which resulted in a loss of control of the airplane and subsequent collision with terrain.NTSB NYC04CA104Accident · No injuriesData collectionFinal reportCessna 172N · Bridgeport, CTThe pilot's inadequate compensation for wind conditions and his failure to maintain aircraft control which resulted in a hard landing. A factor was the gusty winds.NTSB NYC01LA030Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Ridgefield, CTThe pilot's failure to verify the airplane's fuel tank selector position, which resulted in a loss of engine power.NTSB NYC93LA136Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Voluntown, CTThe pilot's failure to achieve the proper touchdown point which resulted in an overrun of the runway and collision with trees. A factor is the pilot's improper compensation for the wind condition.NTSB NYC87LA102Accident · No injuriesLimited investigationFinal reportCessna 172N · Danbury, CTStudent pilot lost directonal control on landing and the aircraft veered to the left of the runway and collided with a snowbank.NTSB NYC83FA122Accident · Serious injuriesField investigationFinal reportCessna 172N · N. Stonington, CTThe acft collided with a tree during a go-around at night following a downwind precautionary landing. During the flt the plt had noted the fuel gauges at low readings and said he suspected a 'fuel leak'. He made radio calls to try to go to an arpt before fuel…NTSB NYC80FA068Accident · 3 fatalClosedCessna 172 · Burlington, CT