NTSB investigations: Cessna 172L, 2004
5 cases on aircraft the registry lists as Cessna 172L. 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
| 1970 | 2 |
|---|---|
| 1971 | 17 |
| 1972 | 34 |
| 1973 | 40 |
| 1974 | 28 |
| 1975 | 23 |
| 1976 | 17 |
| 1977 | 19 |
| 1978 | 17 |
| 1979 | 5 |
| 1980 | 8 |
| 1981 | 7 |
| 1982 | 5 |
| 1983 | 2 |
| 1984 | 5 |
| 1985 | 6 |
| 1986 | 4 |
| 1987 | 3 |
| 1988 | 11 |
| 1989 | 4 |
| 1990 | 8 |
| 1991 | 1 |
| 1992 | 6 |
| 1993 | 3 |
| 1994 | 7 |
| 1995 | 6 |
| 1996 | 7 |
| 1997 | 2 |
| 1998 | 6 |
| 1999 | 7 |
| 2000 | 6 |
| 2001 | 9 |
| 2002 | 4 |
| 2003 | 5 |
| 2004 | 5 |
| 2005 | 9 |
| 2006 | 7 |
| 2007 | 5 |
| 2008 | 4 |
| 2009 | 2 |
| 2010 | 1 |
| 2011 | 1 |
| 2012 | 1 |
| 2013 | 4 |
| 2014 | 1 |
| 2015 | 3 |
| 2016 | 1 |
| 2017 | 3 |
| 2018 | 6 |
| 2019 | 4 |
| 2020 | 1 |
| 2021 | 1 |
| 2022 | 4 |
| 2023 | 3 |
| 2024 | 5 |
| 2025 | 5 |
| 2026 | 4 |
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\") = 2004
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072432'))
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") = 2004
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072432'))
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 ATL05CA016Accident · No injuriesData collectionFinal reportCessna 172 · Mobile, ALThe pilot's inadequate preflight planning and his inadequate in-flight planning/decision which resulted in fuel exhaustion and subsequent collision with the ground.NTSB ATL04LA195Accident · 2 fatalLimited investigationFinal reportCessna 172L · Gadsden, ALThe flight instructors failure to maintain clearance and his inadequate visual lookout while flying low over a river resulting in an in-flight collision with a wire.NTSB ATL04CA188Accident · Serious injuriesData collectionFinal reportCessna 172L · Kill Devil Hlls, NCAn in-flight encounter with a downdraft on final approach, which resulted in a loss of control of the airplane and subsequent collision with the ground.NTSB CHI04FA223Accident · 1 fatalField investigationFinal reportCessna 172L · Webster, WIThe high velocity impact with terrain for undetermined reasons.NTSB NYC04LA087Accident · Minor injuriesLimited investigationFinal reportCessna 172L · Turner, METhe pilot's misjudgment of speed/distance and the delayed aborted landing. A factor in this accident was the tail wind condition.