NTSB investigations: Cessna 172, 2000
9 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\") = 2000
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") = 2000
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 DEN01FA028Accident · 2 fatalField investigationFinal reportCessna 172 · Lusk, WYthe pilot's VFR flight into instrument meteorological conditions, and his subsequent failure to maintain terrain clearance, which resulted in an in-flight collision with terrain. Contributing factors were the pilot's failure to obtain a weather briefing, low…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 CHI01LA031Accident · No injuriesLimited investigationFinal reportCessna 172 · Carrollton, MOthe misjudged touchdown point by the pilot. Factors were the runway lights not on, the dark night, and the plowed field.NTSB CHI00LA305Accident · No injuriesLimited investigationFinal reportCessna 172 · Buffalo, MOThe inadvertent stall during a go-around. Factors relating to this accident were the student pilot's improper in-flight decisions and his failure to raise the flaps during the go around.NTSB NYC00FA226Accident · 1 fatalField investigationFinal reportCessna 172 · Davis, WVThe pilot-in-command's inadequate weather evaluation, which resulted in a takeoff with a tailwind, and a subsequent inadvertent stall. Factors were a high gross weight, a high density altitude, and a tailwind.NTSB SEA00LA093Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Johnson Creek, IDThe pilot's failure to maintain clearance from the rising terrain. Factors include his poor decision to depart without assurance that he could clear the surrounding terrain under the ambient conditions, his failure to adhere to the accepted procedure of…NTSB NYC00LA095Accident · No injuriesLimited investigationFinal reportCessna 172 · New Brighton, PAThe pilot's inadequate compensation for the gusty wind conditions. A factor was the windshear encountered on final approach.NTSB IAD00LA019Accident · No injuriesLimited investigationFinal reportCessna 172 · Lyndonville, VTthe student pilot's failure to maintain directional control during landing. A factor in the accident was the ditch that ran parallel to the runway.NTSB DEN00LA046Accident · Serious injuriesLimited investigationFinal reportCessna 172 · Tooele, UTThe pilot's failure to correct the descent, and his failure to maintain a visual lookout. Factors were the pilot's improper weather evaluation, his lack of recent experience in type of operation, his inadvertent encounter with instrument meteorological…