NTSB investigations: Cessna 172L
14 cases on aircraft the registry lists as Cessna 172L, 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
| 1985 | 1 |
|---|---|
| 1990 | 1 |
| 1992 | 2 |
| 1996 | 3 |
| 1998 | 1 |
| 2001 | 3 |
| 2004 | 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 ('2072432')
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 ('2072432')
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 LAX07CA279Accident · No injuriesData collectionFinal reportCessna 172L · Helena, MTunexpected collision with birds on short final that damaged the airplane wing structure.NTSB ATL04LA195Accident · 2 fatalLimited investigationFinal reportCessna 172L · Gadsden, ALThe flight instructors failure to maintain clearance and his inadequate visual lookout while flying low over a river resulting in an in-flight collision with a wire.NTSB NYC04LA087Accident · Minor injuriesLimited investigationFinal reportCessna 172L · Turner, METhe pilot's misjudgment of speed/distance and the delayed aborted landing. A factor in this accident was the tail wind condition.NTSB LAX01LA286Accident · 1 fatalLimited investigationFinal reportCessna 172L · Tucson, AZthe pilot's controlled descent into a residence for undetermined reasons.NTSB NYC01LA203Accident · Serious injuriesLimited investigationFinal reportCessna 172L · Parkersburg, WVThe student pilot's failure to obtain a proper rate of climb, resulting in a collision with trees.NTSB CHI01LA069Accident · No injuriesLimited investigationFinal reportCessna 172L · Culver, INthe proper glide path not attained by both pilots during a short field landing. The snow bank was a contributing factor.NTSB SEA98LA121Accident · No injuriesLimited investigationFinal reportCessna 172L · Lapwai, IDThe pilot's inadequate preflight planning or preparation from unsuitable terrain. Factors include an embedded railroad tie in the takeoff path, and high vegetation..NTSB IAD97FA014Accident · 2 fatalField investigationFinal reportCessna 172L · Brandy Station, VAthe certificated flight instructor's failure to ensure that proper altitude/clearance was maintained above the terrain and trees, while on final approach. Darkness was a related factor.NTSB FTW96LA290Accident · No injuriesLimited investigationFinal reportCessna 172L · Johnstown, COfailure of the pilot to maintain proper altitude/clearance from obstructions, while buzzing.NTSB SEA96LA116Accident · No injuriesLimited investigationFinal reportCessna 172L · Sisters, ORthe pilot's inadequate compensation for wind conditions during a go-around, which resulted in his failure to maintain proper runway alignment. Factors relating to the accident were: the variable/gusty crosswind condition, and the proximity of the hanger and…NTSB FTW92LA194Accident · No injuriesLimited investigationFinal reportCessna 172L · Ozona, TXThe pilot's failure to maintain obstacle clearance.NTSB SEA92LA117Accident · No injuriesLimited investigationFinal reportCessna 172L · Yakima, WAThe pilot's failure to maintain the proper descent rate and inadequate remedial action.NTSB DEN90LA191Accident · No injuriesLimited investigationFinal reportCessna 172L · Mason, TXThe failure of the pilot to maintain an adequate visual lookout.NTSB CHI86LA030Accident · Minor injuriesLimited investigationFinal reportCessna 172L · Coldwater, OHThe plt flying at a low altitude during a civil air patrol training maneuver struck a 30-FT high power line with the nose gear. The acft then nosed over and impacted the ground.