NTSB investigations: Cessna 172RG
10 cases on aircraft the registry lists as Cessna 172RG, where the first occurrence was “Loss of engine power(total) - mech failure/malf”. 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 | 1 |
|---|---|
| 1985 | 1 |
| 1988 | 1 |
| 1990 | 1 |
| 1992 | 1 |
| 1995 | 1 |
| 1999 | 1 |
| 2001 | 2 |
| 2002 | 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.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072438')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o.\"occurrenceNumber\" = 1 AND o.\"occurrenceCode\" = 351))
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."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072438')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o."occurrenceNumber" = 1 AND o."occurrenceCode" = 351))
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 LAX02LA292Accident · No injuriesLimited investigationFinal reportCessna 172RG · Del Mar, CAThe loss of engine power due to failure of the number three connecting rod cap. Also causal was the failure of the pilot of a previous flight to report an engine overspeed event precluding the performance of the appropriate maintenance inspection.NTSB FTW01LA085Accident · No injuriesLimited investigationFinal reportCessna 172RG · Waco, TXthe failure of the number four cylinder exhaust valve which resulted in a total loss of engine power during cruise. A contributing factor was the lack of suitable terrain for the forced landing.NTSB LAX01LA123Accident · No injuriesLimited investigationFinal reportCessna 172RG · Stanford, CAFailure of company maintenance personnel to properly install and safety wire the oil filter, which subsequently lead to a loss of engine power.NTSB LAX99LA134Accident · No injuriesLimited investigationFinal reportCessna 172RG · Moorpark, CAThe failure and separation of the number two cylinder for undetermined reasons. A factor was the soft terrain at the forced landing site.NTSB FTW95LA117Accident · No injuriesLimited investigationFinal reportCessna 172RG · Plano, TXThe disengagement of the crankshaft gear due to the loosening of the gear retaining bolt and the subsequent fracture of the gear alignment dowel. A factor was the lack of suitable terrain available for the forced landing.NTSB DEN92LA047Accident · No injuriesLimited investigationFinal reportCessna 172RG · Elbert, COFailure of the crankshaft left accessory gear which resulted in a complete power loss. A factor was: lack of suitable terrain for a forced landing.NTSB ATL90LA172Accident · No injuriesLimited investigationFinal reportCessna 172RG · Ozark, ALInadequate engine overhaul procedures which allowed the installation of the engine plug without safety wire to hold it in place, and which resulted in oil starvation of the engine.NTSB CHI88LA209Accident · No injuriesLimited investigationFinal reportCessna 172RG · Mt. Vernon, OHWhile in cruise flight in VFR conditions and on an IFR flight plan, the pilot experienced a total loss of engine power. The pilot executed a forced landing in a soy bean field after an unsuccessful restart attempt. Examination of the oil cooler hose revealed…NTSB MKC85LA188Accident · No injuriesLimited investigationFinal reportCessna 172RG · Lee'S Summit, MOThe plt reported that the eng start & run-up were normal before he took off on a night currency & proficiency flt. After 2 normal takeoffs & full stops, he made a 3rd takeoff. He climbed to 1000 ft AGL on a x-wind leg, reduced power to 20' manifold pressure &…NTSB FTW83LA077Accident · No injuriesLimited investigationFinal reportCessna 172RG · San Angelo, TXThe acft had reached an alt of 3500 ft MSL when the engine started to lose power. The pilot turned back toward his departure airport. The engine then lost all power and the pilot elected to land in a plowed field with landing gear down. When the acft touched…