NTSB investigations: Cessna 172K, 1996
12 cases on aircraft the registry lists as Cessna 172K. 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
| 1967 | 1 |
|---|---|
| 1968 | 3 |
| 1969 | 29 |
| 1970 | 48 |
| 1971 | 66 |
| 1972 | 52 |
| 1973 | 43 |
| 1974 | 40 |
| 1975 | 21 |
| 1976 | 30 |
| 1977 | 29 |
| 1978 | 25 |
| 1979 | 15 |
| 1980 | 12 |
| 1981 | 13 |
| 1982 | 11 |
| 1983 | 6 |
| 1984 | 5 |
| 1985 | 7 |
| 1986 | 6 |
| 1987 | 12 |
| 1988 | 9 |
| 1989 | 5 |
| 1990 | 7 |
| 1991 | 11 |
| 1992 | 4 |
| 1993 | 7 |
| 1994 | 12 |
| 1995 | 6 |
| 1996 | 12 |
| 1997 | 5 |
| 1998 | 6 |
| 1999 | 6 |
| 2000 | 10 |
| 2001 | 5 |
| 2002 | 8 |
| 2003 | 10 |
| 2004 | 7 |
| 2005 | 4 |
| 2006 | 2 |
| 2007 | 8 |
| 2008 | 3 |
| 2009 | 1 |
| 2010 | 4 |
| 2011 | 6 |
| 2012 | 6 |
| 2013 | 5 |
| 2014 | 7 |
| 2015 | 2 |
| 2016 | 6 |
| 2017 | 1 |
| 2018 | 2 |
| 2019 | 8 |
| 2020 | 1 |
| 2021 | 3 |
| 2022 | 4 |
| 2023 | 4 |
| 2024 | 4 |
| 2025 | 4 |
| 2026 | 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 year(c.\"eventDate\") = 1996
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072430'))
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 year(c."eventDate") = 1996
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072430'))
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 NYC96LA189Accident · No injuriesLimited investigationFinal reportCessna 172K · Deal, NJthe pilot's improper decision/planning, which resulted in fuel exhaustion and a subsequent forced landing.NTSB ANC96LA112Accident · No injuriesLimited investigationFinal reportCessna 172K · Nikiski, AKThe pilot's inadequate compensation for wind conditions. A factor was the windshear.NTSB NYC96LA154Accident · No injuriesLimited investigationFinal reportCessna 172K · West Milford, NJthe pilot's failure in attaining the proper touchdown point, and his delay in initiating a go-around (aborted landing).NTSB IAD96LA118Accident · No injuriesLimited investigationFinal reportCessna 172 · Frederick, MDthe private pilot's inadvertently stalling the airplane immediately after takeoff. A related factor was the pilot's improper procedures during lift-off.NTSB NYC96LA124Accident · No injuriesLimited investigationFinal reportCessna 172 · Gardner, MAthe pilot 's misjudgment of speed and distance during landing.NTSB MIA96LA145Accident · No injuriesLimited investigationFinal reportCessna 172K · Englewood, FLFailure of the pilot-in-command to maintain visual lookout while taxiing to takeoff resulting in an on-ground collision with a tree.NTSB FTW96LA203Accident · No injuriesLimited investigationFinal reportCessna 172K · Leadville, COthe pilot's failure to adequately compensate for the wind conditions and to maintain directional control. Factors were: the gusting cross wind and the pilot's lack of total experience in make and model of aircraft.NTSB ATL96LA079Accident · No injuriesLimited investigationFinal reportCessna 172K · Lebanon, TNthe student pilot's failure to maintain directional control during landing.NTSB FTW96LA160Accident · No injuriesLimited investigationFinal reportCessna 172K · Danville, ARthe student pilot's inadequate compensation for the crosswind. Factors were the crosswind and the soft terrain.NTSB ATL96LA059Accident · No injuriesLimited investigationFinal reportCessna 172K · Asheville, NCfailure of the brake on the right main landing gear as a result of water (ice) in the brake fluid, which resulted in a loss of braking control.NTSB FTW96LA116Accident · No injuriesLimited investigationFinal reportCessna 172K · Hedley, TXthe failure of maintenance personnel to properly torque the connecting rod bolts. A factor was the lack of suitable terrain for the forced landing.NTSB SEA96LA041Accident · No injuriesLimited investigationFinal reportCessna 172K · Park City, MTInadequate visual lookout by the pilot, and his failure to maintain sufficient altitude/clearance from the transmission line.