NTSB investigations: Cessna 172I, MI
8 cases on aircraft the registry lists as Cessna 172I. 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
| 1971 | 1 |
|---|---|
| 1976 | 1 |
| 1983 | 1 |
| 1986 | 1 |
| 1989 | 1 |
| 1993 | 1 |
| 2007 | 1 |
| 2022 | 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\" = 'MI' 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 ('2072426'))
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" = 'MI' 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 ('2072426'))
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 CEN22LA398Accident · No injuriesClass 3 · LimitedFinal reportCessna 172I · Olivet, MIThe pilot’s failure to attain/maintain a proper glidepath that resulted in a hard landing and impact with the runway.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.NTSB CHI94FAMS1Accident · 1 fatalMissing aircraftFinal reportCessna 172I · Kalamazoo, MIUndetermined.NTSB CHI89LA107Accident · Serious injuriesLimited investigationFinal reportCessna 172I · New Era, MIThe pilot's misjudgement of the proper touchdown point.NTSB CHI86FEM09Accident · 2 fatalFinal reportCessna 172I · Nunica, MIThe acft was seen flying over the water at an alt of aprx 150-200 ft AGL prior to hitting wires. The acft was flying into the sun at the time of the wire strike.NTSB CHI83LA435Accident · No injuriesLimited investigationFinal reportCessna 172 · Plymouth, MIThe plt reported that during an apch to land on rwy 18, he encountered heavy turbulence & elected to go around. He reported the wind was from 180 deg at 15, gusting 25 KTS. On the 2nd apch, turbulence was encountered again. The acft was fast & began to float…NTSB CHI77FEM03Accident · No injuriesClosedCessna 172 · Watersmeet, MINTSB CHI71DBJ63Accident · No injuriesClosedCessna 172 · Battle Creek, MI