NTSB investigations: Cessna 172
12 cases on aircraft the registry lists as Cessna 172, 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
| 1982 | 2 |
|---|---|
| 1985 | 1 |
| 1988 | 2 |
| 1991 | 1 |
| 1994 | 1 |
| 1995 | 1 |
| 1996 | 1 |
| 2000 | 1 |
| 2001 | 1 |
| 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 ('2072402')
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 ('2072402')
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 CHI02LA077Accident · No injuriesLimited investigationFinal reportCessna 172 · Manito, ILThe pilot's improper planning and decision and his failure to maintain adequate airspeed, which resulted in a stall and hard landing. The gusting crosswind conditions were a contributing factor.NTSB ATL01LA101Accident · No injuriesLimited investigationFinal reportCessna 172 · Mobile, ALThe pilot's improper landing flare that resulted in a hard landing. A factor was the pilot induced porpoise.NTSB ATL01LA018Accident · No injuriesLimited investigationFinal reportCessna 172 · Mobile, ALThe pilot's improper flare during landing that resulted in a hard landing and the subsequent overload failure of the nose gear assembly.NTSB LAX96LA209Accident · No injuriesLimited investigationFinal reportCessna 172 · Marana, AZthe pilot's improper flare and improper recovery from a bounced landing.NTSB CHI95LA220Accident · Serious injuriesLimited investigationFinal reportCessna 172 · Cedar Rapids, IAthe pilot's lack of experience in flying from the right seat. A factor was the steep final approach.NTSB CHI94LA338Accident · No injuriesLimited investigationFinal reportCessna 172 · Mora, MNwas an improper touchdown by the pilot-in-command. Factor's associated with this accident were the pilot's diverted attention due to his perception of a crosswind condition and the pilot not performing a recovery from a bounced landing.NTSB CHI91LA149Accident · No injuriesLimited investigationFinal reportCessna 172 · Neosho, WIThe pilot's failure to properly flare the airplane and an improper recovery from a bounced landing.NTSB BFO88LA077Accident · No injuriesLimited investigationFinal reportCessna 172 · Oakland, MDAccording to the pilot the landing approach for runway 22 was made over power lines. He stated that during the approach the stall warning horn activated and he increased power to maintain 60 mph with 20 degs of flaps. Once estimating that his intended point…NTSB ATL88LA203Accident · No injuriesLimited investigationFinal reportCessna 172 · Greenville, SCThe student & instructor (CFI) were on a practice short field apch, simulating a 50' obstacle. The CFI rprtd that as the acft came over the threshold at about 40' AGL, the airspeed was 60 mph & the flaps were extended 40 deg. The studentreduced the power to…NTSB MKC86LA003Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Guilford, MOThe plt reports that he landed hard, bounced and came down on the nose gear. The nose gear broke and the acft went over on its back.NTSB FTW82DA224Accident · No injuriesFinal reportCessna 172 · Duncan, OKThe student pilot was practicing touch-and-go landings in winds from the southeast at 10 gusting 15 KTS. Just prior to landing, the aircraft encountered a gust of wind, then touched down hard. The engine fire wall was buckled and two tires blew out.NTSB LAX82DA197Accident · No injuriesFinal reportCessna 172 · Fresno, CAThe acft landed hard, bounced, veered left & collided with a parked acft. The CFI recognized that the approach speed wastoo slow & waited too long before taking over. A deliberate turn was made to avoid residences.