NTSB investigations: Cessna 172P, GA
16 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
| 1981 | 1 |
|---|---|
| 1982 | 1 |
| 1984 | 1 |
| 1987 | 1 |
| 1992 | 1 |
| 1996 | 1 |
| 2000 | 1 |
| 2003 | 1 |
| 2004 | 1 |
| 2005 | 1 |
| 2007 | 1 |
| 2021 | 1 |
| 2022 | 2 |
| 2023 | 1 |
| 2026 | 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\" = 'GA' 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" = 'GA' 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 ERA26LA092Accident · No injuriesClass 4 · LimitedFinal reportCessna 172P · Flemington, GAThe pilot’s inadvertent manipulation of the mixture control, which resulted in a total loss of engine power during initial climb and a subsequent forced lading.NTSB ERA23LA386Accident · No injuriesClass 4 · LimitedFinal reportCessna 172 · Greensboro, GAThe pilot’s failure to maintain clearance from a light pole during taxi.NTSB ERA22LA324Accident · No injuriesClass 4 · LimitedFinal reportCessna 172P · Lawrenceville, GAThe student pilot’s failure to maintain directional control while landing with a crosswind.NTSB ERA22LA167Accident · Serious injuriesClass 3 · LimitedFinal reportCessna 172P · Winder, GAMaintenance personnel’s failure to detect the damaged aileron cable during the most recent inspections, which resulted in the separation of the aileron control cable and subsequent loss of airplane control.NTSB ERA22LA021Accident · No injuriesClass 4 · LimitedFinal reportCessna 172P · Kennesaw, GAThe pilot's improper landing flare, which resulted in a hard, bounced landing.NTSB ATL07CA099Accident · No injuriesData collectionFinal reportCessna 172P · Perry, GAThe student pilot's failure to maintain directional control on landing roll out resulting in the airplane departing the runway and collision with a ditch.NTSB ATL05CA132Accident · No injuriesData collectionFinal reportCessna 172P · Savannah, GAThe pilot's failure to maintain directional control on landing roll out resulting in a ground loop, and on ground collision of the right wing with the ground.NTSB ATL04CA133Accident · No injuriesData collectionFinal reportCessna 172 · Kennesaw, GAThe student pilot's failure to maintain directional control during landing roll that resulted in the on ground collision with the ground, and the subsequent collapse of the nose gear.NTSB ATL03LA097Accident · No injuriesLimited investigationFinal reportCessna 172P · Newnan, GAThe pilot's failure to maintain directional control during the landing roll that resulted in the collapse of the right main landing gear.NTSB MIA00LA223Accident · No injuriesLimited investigationFinal reportCessna 172P · Jesup, GAThe failure of the student pilot to maintain directional control during takeoff resulting in an excursion off the runway and collision with adjacent foliage. A factor in the accident was the student's decision to takeoff downwind.NTSB MIA97LA051Accident · Serious injuriesLimited investigationFinal reportCessna 172P · Atlanta, GAfailure of the pilot to initiate an immediate climb (go-around or missed approach) after encountering fog, while on final approach to land. Darkness and fog at the end of the runway were related factors.NTSB ATL93LA010Accident · No injuriesLimited investigationFinal reportCessna 172P · Buford, GAFuel exhaustion due to the pilot's inadequate inflight planning.NTSB ATL87FA130Accident · 2 fatalField investigationFinal reportCessna 182R · Kennesaw, GAN5511N was in the traffic pattern at cobb county airport-mc collum field and was near the turning point from crosswind to dwnd when it was struck by N52995. N52995 was making a straight-in entry into the downwind leg of the traffic pattern from the west with…NTSB ATL84FKG07Accident · No injuriesFinal reportCessna 172P · Atlanta, GAThe plt was having trouble with his radios, electrical system, fuel/eng gages & ammeter, so he turned off his electrical equipment & prepared to make an emergency landing. Because he was afraid of fuel exhaustion, his spacing behind another acft in the…NTSB ATL82DA143Accident · No injuriesFinal reportCessna 172P · Jonesboro, GAThe pilot stated that after applying brakes on landing roll the aircraft began to hydroplane on water that was on the runway. He elected to raise the flaps and apply full power in a attempt to go-around but was unable to clear trees off the end of the runway.NTSB ATL81FKG16Accident · No injuriesClosedCessna 172P · Carnesville, GA