NTSB investigations: Cessna 172G, 2002
6 cases on aircraft the registry lists as Cessna 172G. 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
| 1965 | 2 |
|---|---|
| 1966 | 67 |
| 1967 | 81 |
| 1968 | 41 |
| 1969 | 35 |
| 1970 | 27 |
| 1971 | 32 |
| 1972 | 22 |
| 1973 | 21 |
| 1974 | 14 |
| 1975 | 11 |
| 1976 | 14 |
| 1977 | 11 |
| 1978 | 11 |
| 1979 | 7 |
| 1980 | 5 |
| 1981 | 9 |
| 1982 | 5 |
| 1983 | 6 |
| 1984 | 4 |
| 1985 | 4 |
| 1986 | 6 |
| 1987 | 8 |
| 1988 | 8 |
| 1989 | 9 |
| 1990 | 7 |
| 1991 | 10 |
| 1992 | 9 |
| 1993 | 4 |
| 1994 | 5 |
| 1995 | 8 |
| 1996 | 6 |
| 1997 | 6 |
| 1998 | 5 |
| 1999 | 7 |
| 2000 | 4 |
| 2001 | 2 |
| 2002 | 6 |
| 2003 | 4 |
| 2005 | 2 |
| 2006 | 3 |
| 2007 | 2 |
| 2010 | 2 |
| 2011 | 1 |
| 2012 | 1 |
| 2013 | 2 |
| 2015 | 4 |
| 2017 | 3 |
| 2018 | 6 |
| 2019 | 3 |
| 2020 | 1 |
| 2021 | 6 |
| 2022 | 3 |
| 2023 | 3 |
| 2024 | 3 |
| 2025 | 5 |
| 2026 | 2 |
Where
Latest 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\") = 2002
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072420'))
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") = 2002
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072420'))
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 NYC03LA025Accident · No injuriesLimited investigationFinal reportCessna 172G · Stow, MAThe pilot's failure to maintain adequate altitude/clearance. A factor in this accident was gusty wind conditions.NTSB FTW03LA030Accident · Minor injuriesLimited investigationFinal reportCessna 172G · Fort Stockton, TXThe pilot's decision to conduct VFR flight into IMC and his failure to maintain terrain clearance. Contributing factors were the dark night, clouds, fog, and the lack of suitable terrain.NTSB LAX02LA290Accident · No injuriesLimited investigationFinal reportCessna 172G · Vail, AZThe pilot's inadequate fuel consumption calculations, which resulted in fuel exhaustion.NTSB NYC02LA165Accident · Minor injuriesLimited investigationFinal reportCessna 172G · Sangerville, METhe pilot's failure to maintain airspeed during a go-around, which resulted in an inadvertent stall.NTSB ATL02LA135Accident · Serious injuriesLimited investigationFinal reportCessna 172 · Perry, GAThe pilot's inadequate preflight inspection that resulted in fuel starvation due to fuel system contamination and the subsequent loss of engine power.NTSB CHI02LA167Accident · Minor injuriesLimited investigationFinal reportCessna 172G · Butler, MOThe fuel exhaustion, the inadequate fuel consumption calculations by the pilot, and the inadequate in-flight planning/decision by the pilot. The unsuitable terrain encountered during the forced landing is a contributing factor.