NTSB investigations: Cessna 172S, MI
9 cases on aircraft the registry lists as Cessna 172S. 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
| 2000 | 1 |
|---|---|
| 2002 | 1 |
| 2003 | 2 |
| 2005 | 1 |
| 2010 | 1 |
| 2013 | 1 |
| 2015 | 1 |
| 2022 | 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\" = '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 ('2072439', '2072442'))
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 ('2072439', '2072442'))
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 CEN22LA194Accident · No injuriesClass 3 · LimitedFinal reportCessna 172S · Traverse City, MIThe failure of maintenance personnel to properly torque a fuel line “B” nut, which resulted in a total loss of engine power.NTSB GAA15CA140Accident · No injuriesData collectionFinal reportCessna 172 - S · Traverse City, MIThe student pilot's failure to maintain pitch control during the landing, resulting in a hard landing.NTSB CEN13CA335Accident · No injuriesData collectionFinal reportCessna 172S · Ann Arbor, MIThe pilot’s failure to make a go-around in a timely manner and his loss of control during landing.NTSB CEN10CA325Accident · No injuriesData collectionFinal reportCessna 172 · Traverse City, MIDamage to the firewall for undetermined reasons.NTSB CHI05CA124Accident · No injuriesData collectionFinal reportCessna 172S · Port Huron, MIThe pilot not performing a go-around and misjudging the flare leading to a hard landing.NTSB CHI03FA149Accident · 1 fatalField investigationFinal reportCessna 172S · Sidnaw, MIThe improper short/soft field landing procedure by the pilot and his lack of recent experience in type of operation. Contributing factors were the short/soft field runway, the trees and his delay in aborting the takeoff.NTSB CHI03LA073Accident · No injuriesLimited investigationFinal reportCessna 172 · Clare, MIThe student pilot failed to maintain directional control of the airplane during takeoff roll. A factor was the snow bank.NTSB CHI02LA291Accident · No injuriesLimited investigationFinal reportCessna 172S · Boyne Falls, MIThe pilot's improper flare during landing.NTSB CHI00LA113Accident · Minor injuriesLimited investigationFinal reportCessna 172S · Near Muskegon, MIthe pilot failed to maintain altitude after inadvertently flying to instrument meteorological conditions. Factors associated with the accident were the low ceilings and visibility, the pilot became disoriented after inadvertently flying into IMC, and the…