NTSB investigations: Cessna 172P, AL
12 cases on aircraft the registry lists as Cessna 172P. 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
| 1986 | 1 |
|---|---|
| 1989 | 1 |
| 1990 | 1 |
| 1992 | 1 |
| 1993 | 1 |
| 2003 | 1 |
| 2004 | 1 |
| 2005 | 2 |
| 2006 | 1 |
| 2017 | 1 |
| 2024 | 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 ('2072436'))
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 ('2072436'))
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 ERA24LA232Accident · Serious injuriesClass 3 · LimitedFinal reportCessna 172P · Citronelle, ALA total loss of engine power due to fuel starvation as a result of a fuel vent line that was clogged by an insect nest.NTSB ERA17LA319Accident · No injuriesLimited investigationFinal reportCessna 172 · Gulf Shores, ALThe pilot's improper landing flare, which resulted in a hard landing.NTSB ATL06CA043Accident · No injuriesData collectionFinal reportCessna 172P · Birmingham, ALAn in-flight collision with a deer during a go around, which resulted in damage to the left main landing gear and subsequent collapse of the left main landing gear.NTSB ATL05CA125Accident · No injuriesData collectionFinal reportCessna 172P · Monroeville, ALThe student pilot's failure to maintain directional control and the subsequent collision with the ground during landing.NTSB ATL05CA062Accident · Minor injuriesData collectionFinal reportCessna 172P · Redstone Arsnl, ALThe pilot's failure to maintain adequate airspeed during approach, which resulted in an inadvertent stall and subsequent collision with the runway. Factors were the turbulence and crosswind conditions.NTSB ATL04CA131Accident · No injuriesData collectionFinal reportCessna 172 · Meridianville, ALThe pilot's failure to maintain directional control during an attempted takeoff, which resulted in the on ground collision with the ground.NTSB ATL04LA013Accident · No injuriesLimited investigationFinal reportCessna 172P · Pell City, ALThe pilot's inadequate compensation for wind and his failure to maintain directional control during landing. A factor was the crosswind.NTSB ATL93LA129Accident · No injuriesLimited investigationFinal reportCessna 172 · Summerdale, ALThe pilot's failure to attain the proper touchdown point.NTSB ATL92LA125Accident · No injuriesLimited investigationFinal reportCessna 172 · Auburn, ALThe pilot's improper landing flare, and his improper recovery from a bounced landing.NTSB ATL90FA095Accident · 2 fatalField investigationFinal reportEmbraer EMB-120 · Gadsden, ALInadequate visual lookout by the pilots of both aircraft, which resulted in their failure to see-and-avoid oncoming traffic. A factor related to the accident was: the sun's glare, which restricted the vision of the Cessna 172 pilot.NTSB ATL90FA024Accident · 4 fatalField investigationFinal reportBeech C90 · Gadsden, ALFailure of the pilots of both aircraft to maintain adequate visual lookout to see-and-avoid the other aircraft.NTSB ATL86LA068Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Alexander City, ALThe acft was observed to make one takeoff and landing from an umimproved pasture. The second takeoff attempted was unsuccessful and the acft collided with a tree and crashed to the ground. The plt did not report any mechanical problems with the acft. There…