NTSB investigations: Cessna 172P, SC
9 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
| 1983 | 2 |
|---|---|
| 1987 | 1 |
| 1989 | 1 |
| 1990 | 1 |
| 1997 | 1 |
| 1999 | 1 |
| 2006 | 1 |
| 2022 | 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\" = 'SC' 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" = 'SC' 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 ERA23LA049Accident · Serious injuriesClass 4 · LimitedFinal reportCessna 172 · Greenville, SCThe pilot’s improper fuel management, which resulted in a total loss of engine power due to fuel starvation. Contributing was the pilot’s failure to use the checklist aboard the airplane during her attempts to restore engine power.NTSB ATL06CA123Accident · No injuriesData collectionFinal reportCessna 172P · Chester, SCThe CFI's failure to initiate a go-around when he noticed the flight was high and fast during the approach resulting in the flight landing long, overrunning the runway, and colliding with trees. Factors in the accident were a tail wind and a wet runway.NTSB MIA99LA090Accident · No injuriesLimited investigationFinal reportCessna 172P · Pelion, SCThe pilot's loss of directional control during landing roll as a result of improper recovery from a bounced landing and the subsequent excursion from the runway, collision with the adjacent terrain, and collapse of the nose landing gear.NTSB ATL97LA117Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Rockhill, SCThe pilot's failure to plan and have adequate fuel for the flight.NTSB ATL90LA159Accident · No injuriesLimited investigationFinal reportCessna 172 · Ridge Spring, SCThe failure of the maintenance facility/owner to follow standard preventive maintenance procedures. A factor was the pilot's failure to extend the flaps during the forced landing.NTSB BFO89FA048Accident · 4 fatalField investigationFinal reportCessna 172P · Caesars Head, SCFailure of the pilot to maintain sufficient airspeed while flying over rising terrain, which resulted in an inadvertent stall and collision with wooded terrain. Factors related to the accident were: the terrain conditions and failure of the pilot to maintain…NTSB ATL88LA001Accident · No injuriesLimited investigationFinal reportCessna 172P · Hilton Head, SCThe student plt was performing a crosswind landing which resulted in a hard landing. The acft drifted to the side of the rwy and one wheel was off the paved surface upon the next touchdown. The student plt attempted to hold the acft straight in the direction…NTSB ATL84LA002Accident · No injuriesLimited investigationFinal reportCessna 172P · Columbia, SCThe student plt reported he was practicing touch-and-go takeoffs & landings on rwy 11. While rolling after the 4th landing, power was applied for takeoff. At about that time, the acft veered to the left & ran off the rwy. Subsequently, it struck a drainage…NTSB ATL83LA255Accident · No injuriesLimited investigationFinal reportCessna 172P · Charleston, SCThe acft nosed over during a forced landing after a stall during a low pass. The plt said he was flying around an islandat 500 ft AGL taking pictures when the acft began to settle. He added power and applied elevator back pressure. Then carburetor heat was…