NTSB investigations: Cessna 172G, AL
9 cases on aircraft the registry lists as Cessna 172G. 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
| 1966 | 2 |
|---|---|
| 1968 | 2 |
| 1969 | 1 |
| 1987 | 1 |
| 1990 | 1 |
| 1992 | 1 |
| 1997 | 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 ('2072420'))
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 ('2072420'))
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 MIA98LA036Accident · Serious injuriesLimited investigationFinal reportCessna 172G · Hazel Green, ALthe pilot's miscalculating the aircraft's fuel consumption for the flight, resulting in a loss of engine power due to fuel exhaustion. A factor was the lack of suitable terrain for the forced landing.NTSB ATL93FA025Accident · 3 fatalField investigationFinal reportCessna 172 · Brownsboro, ALThe pilot failed to evaluate the wind conditions and took off with a tailwind which resulted in the collision with a tree on the departure end of the runway. Factors were dark night and tailwind.NTSB ATL90LA083Accident · Minor injuriesLimited investigationFinal reportCessna 172G · Gulf Shores, ALFailure of the pilot to obtain proper assistance or properly secure the aircraft when he left it unattended with the engine running.NTSB ATL87LA058Accident · Minor injuriesLimited investigationFinal reportCessna 172G · Tuskegee, ALDuring a touch and go attempt, the pilot experiended an engine failure shortly after liftoff. The pilot safely landed on the runway, but did not have sufficient runway to stop the aircraft before running off the departure end of 31. The aircraft nosed over…NTSB MIA69D0364Accident · No injuriesClosedCessna 172 · Auburn, ALNTSB MIA68F0538Accident · Serious injuriesClosedCessna 172 · Thomaston, ALNTSB MIA68D0520Accident · No injuriesClosedCessna 172 · Gordo, ALNTSB MIA67D0281Accident · No injuriesClosedCessna 172 · Hazel Green, ALNTSB MIA67D0093Accident · No injuriesClosedCessna 172 · Birmingham, AL