NTSB investigations: Cessna 172H, AL
9 cases on aircraft the registry lists as Cessna 172H. 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
| 1969 | 1 |
|---|---|
| 1971 | 1 |
| 1973 | 1 |
| 1982 | 1 |
| 1985 | 1 |
| 1992 | 1 |
| 1999 | 1 |
| 2000 | 1 |
| 2016 | 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\" = 'AL' 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 ('2072424'))
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" = 'AL' 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 ('2072424'))
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 ERA17LA075Accident · Serious injuriesLimited investigationFinal reportCessna 172 · Bridgeport, ALThe pilot's decision to make steep turns to the right while operating on the right fuel tank with low fuel quantity, which led to a loss of engine power due to unporting of the right fuel tank and fuel starvation.NTSB ATL00LA060Accident · Serious injuriesLimited investigationFinal reportCessna 172H · Foley, ALThe pilot exceeding the performance capability of the airplane during takeoff. A factor was the trees.NTSB MIA99LA144Accident · No injuriesLimited investigationFinal reportCessna 172H · Sylvan Springs, ALThe total loss of engine power for undetermined reasons.NTSB ATL92LA134Accident · No injuriesLimited investigationFinal reportCessna 172H · Huntsville, ALThe pilot's inadequate compensation for the wind conditions at the airstrip, and the excessive airspeed on final approach. A factor was the prevailing tailwind at the airstrip.NTSB ATL85LA108Accident · No injuriesLimited investigationFinal reportCessna 172H · Bessemer, ALThe plt was taxiing to the rwy on a narrow taxiway when the left wing struck a t hangar support post.NTSB ATL83LA027Accident · Serious injuriesLimited investigationFinal reportCessna 172H · Birmingham, ALPilot made a hard off airport landing after loss of power. He had used a prolonged slip to lose altitude and the engine stopped. Then he could not reach the runway. The fuel selector was found on left tank. Left tank had less than two gallons of fuel.NTSB MIA73DKJ65Accident · No injuriesClosedCessna 172H · Birmingham, ALNTSB MIA71FKJ49Accident · Minor injuriesClosedCessna 172H · Camden, ALNTSB MIA69F0442Accident · No injuriesClosedCessna 172 · Opelika, AL