NTSB investigations: Cessna 172H
14 cases on aircraft the registry lists as Cessna 172H, where the first occurrence was “In flight collision with object”. 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 |
|---|---|
| 1986 | 1 |
| 1989 | 1 |
| 1991 | 1 |
| 1994 | 1 |
| 1995 | 1 |
| 1996 | 2 |
| 1997 | 1 |
| 1998 | 1 |
| 2000 | 2 |
| 2003 | 1 |
| 2005 | 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\" = 220))
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" = 220))
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 SEA05CA055Accident · Minor injuriesData collectionFinal reportCessna 172H · Waldport, ORThe pilot's failure to attain sufficient altitude/clearance during the takeoff initial climb, which resulted in an inflight collision with trees. A factor was the tall grass on the turf runway, which slowed the airplane's acceleration during the takeoff roll.NTSB ANC04LA012Accident · No injuriesLimited investigationFinal reportCessna 172 · Chugiak, AKThe pilot's selection of an unsuitable landing/takeoff area, and his failure to abort the takeoff, which resulted in an in-flight collision with a stump, and subsequent loss of control. Factors associated with the accident were snow-covered terrain and a…NTSB DEN00FA119Accident · 2 fatalField investigationFinal reportCessna 172H · Angel Fire, NMThe pilot's improper inflight decision to prematurely attempt a climb towards rising terrain before sufficient altitude had been attained that would assure adequate obstacle clearance. Factors were high density altitude and trees.NTSB ATL00LA060Accident · Serious injuriesLimited investigationFinal reportCessna 172H · Foley, ALThe pilot exceeding the performance capability of the airplane during takeoff. A factor was the trees.NTSB FTW99LA009Accident · Minor injuriesLimited investigationFinal reportCessna 172H · Conroe, TXThe pilot's failure to maintain clearance with trees. Factors were the fogged front windshield and side windows.NTSB CHI97LA138Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Flushing, MIwas the pilot not maintaining sufficient altitude to clear obstructions. A factor associated with the accident was the pilot was inattentive to the airplane's altitude.NTSB NYC96LA146Accident · No injuriesLimited investigationFinal reportCessna 172H · Cherry Tree, PAthe pilot's failure to assure that adequate takeoff distance was available to clear an obstacle.NTSB MIA96LA164Accident · Serious injuriesLimited investigationFinal reportCessna 172H · Jonesville, SCthe pilot's inadequate visual lookout and failure to maintain altitude and/or clearance from the obstruction (power line) during low altitude flight. The lack of natural lighting at dusk was a related factor.NTSB NYC96LA006Accident · Serious injuriesLimited investigationFinal reportCessna 172 · Honeoye Falls, NYthe pilot's failure to establish a climb in that he failed to raise the flaps and failed to assure full power was applied during the go-around.NTSB ATL95FA014Accident · 2 fatalField investigationFinal reportCessna 172H · Louisville, GAThe pilot's failure to maintain clearance from trees during a low pass maneuver. A factor was the trees at the vicinity of the low pass.NTSB LAX91LA345Accident · No injuriesLimited investigationFinal reportCessna 172N · Lake Elsinore, CAThe pilot's poor judgement for unwarranted low flying and poor visual lookout.NTSB BFO89LA026Accident · Minor injuriesLimited investigationFinal reportCessna 172H · Odenton, MDThe inflight collision with birds.NTSB DEN86LA117Accident · No injuriesLimited investigationFinal reportCessna 172H · Crossroads, NMAccording to the plt, he was attempting to underfly powerlines over a public road during landing, when the aircraft contacted an unseen wire and crashed.NTSB MKC84LA215Accident · No injuriesLimited investigationFinal reportCessna 172H · Marvell, ARThe acft collided with telephone lines as the plt was making a low pass over the passengers place of business. The plt said he did not know the lines were there when his passenger asked for the low pass. The acft stalled and contacted the ground on the…