NTSB investigations: Cessna 172F, 2001
5 cases on aircraft the registry lists as Cessna 172F. 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 | 2 |
|---|---|
| 1965 | 60 |
| 1966 | 57 |
| 1967 | 47 |
| 1968 | 24 |
| 1969 | 14 |
| 1970 | 24 |
| 1971 | 23 |
| 1972 | 21 |
| 1973 | 19 |
| 1974 | 10 |
| 1975 | 16 |
| 1976 | 15 |
| 1977 | 15 |
| 1978 | 10 |
| 1979 | 10 |
| 1980 | 3 |
| 1981 | 13 |
| 1982 | 6 |
| 1983 | 6 |
| 1984 | 7 |
| 1985 | 5 |
| 1986 | 7 |
| 1987 | 5 |
| 1988 | 10 |
| 1989 | 7 |
| 1990 | 3 |
| 1992 | 4 |
| 1993 | 6 |
| 1994 | 7 |
| 1995 | 8 |
| 1996 | 7 |
| 1997 | 4 |
| 1998 | 7 |
| 1999 | 3 |
| 2000 | 1 |
| 2001 | 5 |
| 2002 | 4 |
| 2003 | 4 |
| 2004 | 3 |
| 2005 | 5 |
| 2006 | 4 |
| 2007 | 2 |
| 2008 | 3 |
| 2009 | 2 |
| 2010 | 1 |
| 2011 | 4 |
| 2012 | 2 |
| 2013 | 3 |
| 2014 | 3 |
| 2015 | 3 |
| 2016 | 3 |
| 2017 | 2 |
| 2018 | 1 |
| 2019 | 7 |
| 2020 | 2 |
| 2021 | 3 |
| 2022 | 4 |
| 2023 | 1 |
| 2024 | 2 |
| 2025 | 3 |
| 2026 | 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 year(c.\"eventDate\") = 2001
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072414'))
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") = 2001
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072414'))
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 MIA01LA139Accident · No injuriesLimited investigationFinal reportCessna 172F · Fort Pierce, FLa loss of engine power due to fuel exhaustion which resulted in a forced landing, and subsequent impact with a sign and a ditch.NTSB FTW01LA075Accident · No injuriesLimited investigationFinal reportCessna 172F · Clovis, NMthe pilot's failure to maintain directional control during take off roll resulting in a ground loop. A contributing factor was the crosswind.NTSB DEN01LA055Accident · No injuriesLimited investigationFinal reportCessna 172F · Larkspur, COthe flight instructor inadvertently stalling the airplane during a forced landing. Contributing factors were fuel exhaustion due to inadvertent opening of the fuel drain, lack of familiarity with the airplane, inadequate supervision of the flight, and the…NTSB ATL01LA026Accident · Serious injuriesLimited investigationFinal reportCessna 172 F · Greenwood, MSAn in-flight fire for undetermined reasons. Finding: A factor is the maintenance modification was performed by company personnel prior to the flight.NTSB LAX01FA070Accident · 2 fatalField investigationFinal reportCessna 172F · San Luis Obispo, CAThe pilot's failure to maintain a proper climb rate to VFR conditions on-top.