NTSB investigations: Cessna 172, 2005
11 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\") = 2005
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") = 2005
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 LAX06LA064Accident · 4 fatalLimited investigationFinal reportCessna 172 · Gilroy, CAThe non-instrument rated pilot's poor judgment to fly in dark night instrument conditions, which resulted in his spatial disorientation and loss of aircraft control while maneuvering. Contributing factors were the dark night light condition and the low…NTSB ANC06CA006Accident · No injuriesData collectionFinal reportCessna 172 · Naknek, AKThe pilot's inadequate removal of frost from the wings, and his failure to attain adequate airspeed during takeoff initial climb, which resulted in a stall and collision with terrain. Factors contributing to the accident were the pilot's delayed aborted…NTSB SEA06LA012Accident · No injuriesLimited investigationFinal reportCessna 172 · Gleneden Beach, ORThe pilot's failure to maintain clearance from objects while maneuvering over the airport environment. Dark night conditions, trees, and ground fog were factors.NTSB LAX05LA286Accident · 1 fatalLimited investigationFinal reportCessna 172 · Yuma, AZthe pilot's failure to maintain an adequate airspeed on short final, which resulted in an inadvertent stall.NTSB CHI05CA155Accident · No injuriesData collectionFinal reportCessna 172 · Willis, MIThe pilot's inability to maintain directional control of the airplane due to undetermined reasons. A factor associated with the accident were the trees that the airplane contacted during the aborted takeoff.NTSB CHI05CA084Accident · No injuriesData collectionFinal reportCessna 172 · Baudette, MNThe pilot's inadequate compensation for the crosswind which resulted in the failure to maintain directional control of the airplane. Factors associated with the accident were the crosswind, the snow covered surface on which the landing was being made, and the…NTSB DFW05CA090Accident · Minor injuriesData collectionFinal reportCessna 172 · Nachogdoches, TXThe pilot's improper in-flight planning which resulted in a loss of engine power due to fuel exhaustion. A factor was the lack of suitable terrain for the forced landing.NTSB SEA05CA062Accident · No injuriesData collectionFinal reportCessna 172 · Gooding, IDThe pilot's inadequate compensation for the wind conditions which resulted in a loss of control during taxi. A contributing factor was the wind gusts.NTSB DEN05LA058Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Montrose, COthe pilot's improper in-flight planning during the descent which resulted in partial loss of engine power due to carburetor ice. Contributing factors were the pilot's failure to select carburetor heat during the descent and unsuitable terrain for the forced…NTSB DFW05CA076Accident · No injuriesData collectionFinal reportCessna 172 · Marshall, TXThe pilot's improper engine starting procedure resulting in a loss of control.NTSB IAD05LA028Accident · 2 fatalLimited investigationFinal reportCessna 172 · Knottsville, KYthe pilot's loss of control in flight due to spatial disorientation. Also causal to the accident was the pilot's inadequate preflight planning which resulted in his inadvertent flight into night instrument meteorological conditions.