NTSB investigations: Cessna 172H
15 cases on aircraft the registry lists as Cessna 172H, 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
| 1984 | 1 |
|---|---|
| 1985 | 1 |
| 1991 | 1 |
| 1996 | 4 |
| 1999 | 2 |
| 2003 | 3 |
| 2004 | 1 |
| 2005 | 1 |
| 2006 | 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 ('2072424')
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 ('2072424')
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 ATL06LA099Accident · Serious injuriesLimited investigationFinal reportCessna 172H · Ringgold, GAThe pilot's improper fuel management resulting in a total loss of engine power due to fuel starvation resulting in a forced landing, and collision with trees and the ground.NTSB ATL05CA074Accident · No injuriesData collectionFinal reportCessna 172H · Oakwood, GALoss of engine power due to fuel system contamination.NTSB CHI05LA037Accident · No injuriesLimited investigationFinal reportCessna 172H · Belle Plaine, MNA loss of engine power for undetermined reasons during descent, and the unsuitable terrain encountered during the forced landing.NTSB FTW04LA028Accident · Minor injuriesLimited investigationFinal reportCessna 172H · Wichita Falls, TXThe loss of engine power due to an obstruction in the fuel line.NTSB CHI03LA082Accident · Minor injuriesLimited investigationFinal reportCessna 172H · Callao, MOA loss of engine power due to the erosion of the number 2 piston, resulting in loss of compression on that cylinder. Contributing factors were the tailwind, the muddy runway condition, and the roadway and ditch.NTSB ATL03LA057Accident · No injuriesLimited investigationFinal reportCessna 172 · Camden, SCThe pilot's inadequate preflight planning which resulted in fuel exhaustion, subsequent loss of engine power and an in-flight collision with terrain.NTSB NYC99LA173Accident · Minor injuriesLimited investigationFinal reportCessna 172H · Falmouth, KYA stuck intake-valve on the number one cylinder which resulted in a loss of engine power.NTSB MIA99LA144Accident · No injuriesLimited investigationFinal reportCessna 172H · Sylvan Springs, ALThe total loss of engine power for undetermined reasons.NTSB ATL96FA119Accident · 1 fatalField investigationFinal reportCessna 172H · St. Petersburg, FLAn engine malfunction for undetermined reasons. A factor was the pilot's selection of an unsuitable landing site.NTSB ATL96LA105Accident · No injuriesLimited investigationFinal reportCessna 172H · Hickory, NCEngine stoppage for undetermined reasons. A factor was the terrain furrows.NTSB FTW96LA281Accident · No injuriesLimited investigationFinal reportCessna 172H · Pierce, COa loss of engine power for undetermined reasons. A factor was the unsuitable terrain.NTSB FTW96LA254Accident · No injuriesLimited investigationFinal reportCessna 172H · Crockett, TXLoss of engine power for undetermined reason(s).NTSB MIA91LA225Accident · Minor injuriesLimited investigationFinal reportCessna 172H · Atlantic Ocean (Atlantic Ocean)Total loss of engine power due to undetermined reasons.NTSB ATL85FA189Accident · 2 fatalField investigationFinal reportCessna 172H · Hendersonville, NCThe plt reported that during takeoff, the eng lost power as the acft was climbing thru about 100 to 125 ft AGL. He made a rgt turn back toward the arpt to land. However, the acft stalled, then impacted in a parking lot near the departure end of the rwy &…NTSB NYC84LA126Accident · Serious injuriesLimited investigationFinal reportCessna 172H · Hagerstown, MDThe plt initiated a 5 mi straight-in approach. When the acft was within 2 mi of the arpt, the plt reduced power, appliedcarb heat & slowed the acft. When it appeared he was going to land short, he added power, but the eng would not respond. The acft was…