NTSB investigations: Cessna 172, 1996
12 cases on aircraft the registry lists as Cessna 172. 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
| 1964 | 80 |
|---|---|
| 1965 | 77 |
| 1966 | 84 |
| 1967 | 85 |
| 1968 | 65 |
| 1969 | 35 |
| 1970 | 32 |
| 1971 | 37 |
| 1972 | 40 |
| 1973 | 35 |
| 1974 | 35 |
| 1975 | 15 |
| 1976 | 29 |
| 1977 | 25 |
| 1978 | 27 |
| 1979 | 15 |
| 1980 | 21 |
| 1981 | 27 |
| 1982 | 11 |
| 1983 | 6 |
| 1984 | 8 |
| 1985 | 13 |
| 1986 | 8 |
| 1987 | 13 |
| 1988 | 21 |
| 1989 | 15 |
| 1990 | 6 |
| 1991 | 11 |
| 1992 | 12 |
| 1993 | 10 |
| 1994 | 10 |
| 1995 | 9 |
| 1996 | 12 |
| 1997 | 4 |
| 1998 | 13 |
| 1999 | 9 |
| 2000 | 9 |
| 2001 | 9 |
| 2002 | 6 |
| 2003 | 2 |
| 2004 | 2 |
| 2005 | 11 |
| 2006 | 4 |
| 2007 | 9 |
| 2008 | 8 |
| 2009 | 3 |
| 2010 | 4 |
| 2011 | 6 |
| 2012 | 4 |
| 2013 | 7 |
| 2014 | 3 |
| 2015 | 5 |
| 2016 | 3 |
| 2017 | 6 |
| 2018 | 6 |
| 2019 | 6 |
| 2020 | 3 |
| 2021 | 8 |
| 2022 | 4 |
| 2023 | 3 |
| 2024 | 2 |
| 2025 | 5 |
| 2026 | 3 |
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 ('2072402'))
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 ('2072402'))
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 LAX97LA064Accident · No injuriesLimited investigationFinal reportCessna 172 · Big Bear City, CAthe pilot's inadequate compensation for the wind condition, and his failure to maintain alignment with the runway. The gusty crosswind was a related factor.NTSB IAD96LA149Accident · No injuriesLimited investigationFinal reportCessna 172P · Richwood, WVimproper in-flight planning/decision by the flight crew, and inadequate supervision by the check pilot, which resulted in the flight crew's failure to maintain altitude/clearance from trees on rising terrain. A factor relating to the accident was:…NTSB CHI96LA329Accident · No injuriesLimited investigationFinal reportCessna 172 · Wellston, MIThe pilot failed to maintain control of the aircraft. Factors were the rough road, the tree, and the tire.NTSB ANC96FA141Accident · 3 fatalField investigationFinal reportCessna 172 · Eagle River, AKThe first pilot's failure to maintain sufficient distance/altitude from terrain. A box canyon and mountainous terrain are factors in the accident.NTSB CHI96LA249Accident · No injuriesLimited investigationFinal reportCessna 172 · Emily, MNthe pilot misjudged his altitude and distance to the runway on final approach, and he failed to maintain obstacle clearance during landing. A factor relating to the accident was: the parked car.NTSB MIA96LA192Accident · Serious injuriesLimited investigationFinal reportCessna 172 · Okeechobee, FLfailure of the pilot to maintain control of the airplane during a high speed taxi check, which resulted in a lift-off and subsequent collision with the terrain.NTSB LAX96LA278Accident · 1 fatalLimited investigationFinal reportCessna 172 · Midas, NVthe decision of the pilot to perform a low-level steep turn which resulted in an inadvertent loss of control and subsequent stall/spin. Factors were high density altitude and inadequate altitude for recovery.NTSB LAX96LA209Accident · No injuriesLimited investigationFinal reportCessna 172 · Marana, AZthe pilot's improper flare and improper recovery from a bounced landing.NTSB IAD96FA057Accident · 3 fatalField investigationFinal reportCessna 172 · Barkhamsted, CTthe CFI pilot/passenger's poor judgment which led to spatial disorientation and subsequent loss of control of the airplane. Factors involved in this accident were the night marginal visual flight conditions and continuing flight with a known nonfunctioning…NTSB LAX96LA143Accident · Serious injuriesLimited investigationFinal reportCessna 172 · Upland, CAfuel system contamination and the pilot's intentional operation of a known unairworthy aircraft.NTSB CHI96LA100Accident · No injuriesLimited investigationFinal reportCessna 172 · Ankeny, IAthe pilot's poor judgment in attempting flight operations in the existing wind condition, and the high gusting wind.NTSB ATL96LA050Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Jackson, MSloss of engine power during takeoff for undetermined reason(s). A factor relating to the accident was: the lack of suitable terrain for a forced landing.