NTSB investigations: Cessna 172P, MD
22 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
| 1987 | 1 |
|---|---|
| 1988 | 2 |
| 1989 | 1 |
| 1992 | 1 |
| 1995 | 1 |
| 1997 | 1 |
| 1999 | 2 |
| 2001 | 2 |
| 2002 | 1 |
| 2005 | 1 |
| 2006 | 2 |
| 2011 | 1 |
| 2013 | 1 |
| 2014 | 1 |
| 2015 | 2 |
| 2016 | 1 |
| 2025 | 1 |
Where
Latest 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\" = 'MD' 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" = 'MD' 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 ERA25LA127Accident · Minor injuriesClass 3 · LimitedFinal reportCessna 172 · Mayo, MDA total loss of engine power at low altitude due to an accumulation of carburetor ice while in a cruise-power descent, which resulted in a forced landing.NTSB ERA16FA329Accident · 1 fatalField investigationFinal reportCessna 172 · Laytonsville, MDThe pilot/mechanic's failure to maintain airspeed following a loss of engine power, which resulted in the airplane exceeding its critical angle of attack and experiencing an aerodynamic stall. Also causal was the pilot/mechanic's failure to service the engine…NTSB GAA16CA064Accident · No injuriesData collectionFinal reportCessna 172 · Gaithersburg, MDThe student pilot's improper flare during landing, which resulted in a bounced landing, and a runway excursion.NTSB ERA15CA222Accident · No injuriesData collectionFinal reportCessna 172P · Mitchellville, MDThe pilot’s improper landing flare, which resulted in a bounced landing and damage to the airplane.NTSB ERA14CA354Accident · No injuriesData collectionFinal reportCessna 172P · Hagerstown, MDThe student pilot's improper landing flare.NTSB ERA13CA377Accident · No injuriesData collectionFinal reportCessna 172P · Mitchellville, MDThe pilot’s decision to depart with a known deficiency following a hard landing. Contributing to the accident was an anomaly of the airplane’s nosewheel steering that could not be replicated during post-accident examination.NTSB ERA11CA385Accident · No injuriesData collectionFinal reportCessna 172P · Baltimore, MDThe student pilot's failure to maintain aircraft control following a bounced landing.NTSB NYC06CA221Accident · No injuriesData collectionFinal reportCessna 172P · Baltimore, MDThe pilot's improper flare, which resulted in a hard landing.NTSB NYC06CA088Accident · No injuriesData collectionFinal reportCessna 172-P · Cambridge, MDThe student pilot's improper recovery from a bounced landing.NTSB NYC05CA146Accident · No injuriesData collectionFinal reportCessna 172P · Mitchellville, MDThe pilot's failure to maintain directional control during landing.NTSB IAD02FA037Accident · 4 fatalField investigationFinal reportCessna 172P · Ocean City, MDThe pilot's spatial disorientation, which resulted in his subsequent loss of control of the airplane. A factor was the dark night, over water visual conditions.NTSB NYC01LA188Accident · No injuriesLimited investigationFinal reportCessna 172P · Odenton, MDA loss of engine power for undetermined reasons.NTSB NYC01LA163Accident · No injuriesLimited investigationFinal reportCessna 172P · Stevensville, MDThe pilot's improper flare and his improper recovery from a bounced landing.NTSB IAD99LA068Accident · No injuriesLimited investigationFinal reportCessna 172P · Friendly, MDThe pilot's misjudgment of speed during the landing approach. The inoperative airspeed indicator was a contributing factor.NTSB IAD99FA051Accident · No injuriesField investigationFinal reportCessna 172P · Gaithersburg, MDwas the pilot's failure to obtain the proper rotation speed and his subsequent loss of directional control. A factor in the accident was the improper setting of the elevator trim.NTSB NYC98LA040Accident · No injuriesLimited investigationFinal reportCessna 172P · Mitchellville, MDThe pilot's improper recovery from a bounced landing.NTSB NYC95LA081Accident · No injuriesLimited investigationFinal reportCessna 172 · Mitchellville, MDThe pilot's failure to maintain directional control and the instructor's inadequate supervision. Related factors: high winds, and a crosswind.NTSB BFO92FA044Accident · 2 fatalField investigationFinal reportCessna 172P · Accokeek, MDThe pilot experienced spatial disorientation which resulted in loss of control of the airplane.NTSB BFO90LA013Accident · No injuriesLimited investigationFinal reportCessna 172 · Mitchellville, MDThe pilot allowed the aircraft to enter an inadvertent porpoise during an aborted takeoff.NTSB BFO89LA006Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Cambridge, MDThe stu plt did three takeoffs & lndgs with the instr aboard and then three more during solo flight. On his fourth takeoff try he used aileron and rudder to maintain directional control on the rwy. There was an 8 to 10 kt crosswind. The stu said when the acft…NTSB BFO88LA053Accident · No injuriesLimited investigationFinal reportCessna 172P · Gaithersburg, MDAccording to the plt, after touchdown the acft encountered a crosswind gust. The acft drifted left of the rwy where it collided with trees. The plt reported no mechanical malfunction.NTSB BFO87FA050Accident · Minor injuriesField investigationFinal reportCessna 172P · Whitemarsh, MDThe pilot stated that he touched down near the end of the 22OO foot runway. However, witnesses said he landed so FAR down the runway that they did not believe he could stop on the runway. The pilot delayed his go around attempt to the point where it was not…