NTSB investigations: Cessna 172C
5 cases on aircraft the registry lists as Cessna 172C, where the first occurrence was “Loss of engine power”. 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
| 1985 | 1 |
|---|---|
| 2001 | 1 |
| 2005 | 2 |
| 2007 | 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 ('2072408')
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\" = 350))
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 ('2072408')
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" = 350))
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 DFW07LA172Accident · No injuriesLimited investigationFinal reportCessna 172C · Pascagoula, MSThe loss of engine power for undetermined reasons. A contributing factor was the lack of suitable terrain for the forced landing.NTSB MIA05LA158Accident · 2 fatalLimited investigationFinal reportCessna 172C · Saint Cloud, FLThe pilot's failure to maintain the airspeed while maneuvering following loss of engine power resulting in a stall/mush, an uncontrolled descent, and collision with trees and the ground.NTSB NYC05FA138Accident · 1 fatalField investigationFinal reportCessna 172C · Winthrop, METhe pilot's inadequate preflight inspection, which resulted in a loss of engine power due to fuel exhaustion, and a subsequent forced landing and impact with terrain.NTSB CHI01LA219Accident · No injuriesLimited investigationFinal reportCessna 172C · Grand Island, NEThe procedures for using carburetor heat not followed by the student pilot and the unsuitable terrain encountered during the forced landing. Additional factors included the carburetor icing conditions, the carburetor icing, the student pilot's lack of…NTSB MIA85LA124Accident · No injuriesLimited investigationFinal reportCessna 172 · Big Pine Key, FLThe plt stated that while in cruise flt at about 1200 ft & 2300 RPM the eng lost pwr & the acft was ditched aprx 100 yards off shore in the ocean waters. The acft was found to have sufficient fuel in both tanks. The fuel selector was on, the fuel screen was…