NTSB investigations: Cessna 172H
14 cases on aircraft the registry lists as Cessna 172H, where the first occurrence was “Hard landing”. 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 |
|---|---|
| 1984 | 1 |
| 1985 | 1 |
| 1986 | 1 |
| 1987 | 1 |
| 1990 | 1 |
| 1996 | 2 |
| 2000 | 3 |
| 2003 | 1 |
| 2005 | 2 |
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\" = 200))
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" = 200))
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 ATL06CA033Accident · No injuriesData collectionFinal reportCessna 172H · Waycross, GAThe student pilot's improper landing flare and the CFI's inadequate supervision resulting in a hard landing.NTSB MIA05CA067Accident · No injuriesData collectionFinal reportCessna 172 · Jacksonville, FLThe pilot's improper landing flare which resulted in a hard landing.NTSB CHI03LA166Accident · No injuriesLimited investigationFinal reportCessna 172H · Council Bluffs, IAMisjudgment of the landing flare by the pilot in command resulting in a hard landing.NTSB LAX01LA008Accident · No injuriesLimited investigationFinal reportCessna 172H · Hilo, HIAn inadvertent pilot-induced porpoise resulting from the pilot's improper landing flare and inadequate power management.NTSB IAD00LA061Accident · No injuriesLimited investigationFinal reportCessna 172H · Friendly, MDthe student pilot's inadequate compensation for winds that resulted in his failure to maintain runway alignment and a hard landing.NTSB FTW00LA148Accident · No injuriesLimited investigationFinal reportCessna 172H · Mesquite, TXThe flight instructor's inadequate supervision of the student pilot during the landing.NTSB NYC97LA002Accident · No injuriesLimited investigationFinal reportCessna 172H · Chatham, MAthe pilot's improper flare, which resulted in a hard landing. A factor relating to the accident was: the pilot's lack of experience in the make and model of airplane.NTSB FTW96LA362Accident · No injuriesLimited investigationFinal reportCessna 172H · Durango, COthe pilot's improper flaring of the airplane at too high an altitude, resulting in a hard landing.NTSB DEN91LA011Accident · No injuriesLimited investigationFinal reportCessna 172H · Buena Vista, COThe failure of the pilot to flare properly during landing. The pilot's total lack of experience is a factor.NTSB CHI87LA169Accident · No injuriesLimited investigationFinal reportCessna 172 · Madison, WIThe instructor (CFI) & pvt plt (student) were on a renter's check-out flt to familiarize the student with a Cessna 172. While practicing landings, tower psnl provided a windshear alert. Drg an apch to land, the acft went into a high sink rate over the apch…NTSB LAX86LA232Accident · No injuriesLimited investigationFinal reportCessna 172 · Huntington Bch, CAThe acft contacted a parked car and a hangar following a loss of control during an attempted go-around. The plt reported the acft was high and fast on final apch. He selected full flaps and a nose up attitude to lose airspeed and alt. He flared the acft at 20…NTSB ATL85LA116Accident · No injuriesLimited investigationFinal reportCessna 172H · Buena Vista, GAAcft slipped on final due to being high. Landed hard and bounced. On second touchdown rudder was still applied and acft veered off runway colliding with ditch bank.NTSB LAX85LA009Accident · No injuriesLimited investigationFinal reportCessna 172H · Long Beach, CAThe plt said that after he returned to the arpt for a night landing, he applied back pressure during the flare, then heard the stall warning horn. Subsequently, the acft was damaged when it landed hard & bounced. However, the plt was able to taxi to the…NTSB CHI83LA246Accident · No injuriesLimited investigationFinal reportCessna 172H · Dayton, OHThe plt stated he was aware of the displaced threshold due to barriers across the approach end of the rwy. After clearing the last barrier he felt the acft start to fall. He nosed over & added power but the nose gear struck the rwy first. The firewall &…