NTSB investigations: Cessna 182A, 1996
5 cases on aircraft the registry lists as Cessna 182A. 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 | 48 |
|---|---|
| 1965 | 43 |
| 1966 | 42 |
| 1967 | 28 |
| 1968 | 31 |
| 1969 | 24 |
| 1970 | 17 |
| 1971 | 21 |
| 1972 | 17 |
| 1973 | 16 |
| 1974 | 19 |
| 1975 | 19 |
| 1976 | 15 |
| 1977 | 12 |
| 1978 | 13 |
| 1979 | 8 |
| 1980 | 20 |
| 1981 | 11 |
| 1982 | 7 |
| 1983 | 8 |
| 1984 | 6 |
| 1985 | 13 |
| 1986 | 11 |
| 1987 | 7 |
| 1988 | 8 |
| 1989 | 14 |
| 1990 | 10 |
| 1991 | 13 |
| 1992 | 7 |
| 1993 | 8 |
| 1994 | 6 |
| 1995 | 5 |
| 1996 | 5 |
| 1997 | 8 |
| 1998 | 6 |
| 1999 | 7 |
| 2000 | 3 |
| 2001 | 9 |
| 2002 | 6 |
| 2003 | 8 |
| 2004 | 6 |
| 2005 | 4 |
| 2006 | 3 |
| 2007 | 3 |
| 2008 | 5 |
| 2009 | 5 |
| 2010 | 2 |
| 2011 | 7 |
| 2012 | 6 |
| 2013 | 2 |
| 2014 | 5 |
| 2015 | 4 |
| 2016 | 6 |
| 2017 | 6 |
| 2018 | 4 |
| 2019 | 2 |
| 2020 | 4 |
| 2022 | 1 |
| 2024 | 4 |
| 2025 | 2 |
| 2026 | 2 |
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\") = 1996
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072704'))
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") = 1996
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072704'))
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 LAX97LA015Accident · Minor injuriesLimited investigationFinal reportCessna 182A · Agua Dulce, CAinadequate compliance with the applicable airworthiness directive by other maintenance personnel, and the pilot's inadequate preflight inspection which resulted in fuel exhaustion from a deteriorated fuel cap seal.NTSB ANC96LA156Accident · No injuriesLimited investigationFinal reportCessna 182 · Fairbanks, AKThe pilot's inadequate compensation for gusty wind conditions during the landing roll. A factor associated with the accident is the gusty wind conditions.NTSB FTW96LA312Accident · No injuriesLimited investigationFinal reportCessna 182A · Skiatook, OKa loss of engine power for undetermined reasons. A factor was the lack of suitable terrain for a forced landing.NTSB SEA96LA160Accident · No injuriesLimited investigationFinal reportCessna 182A · Toledo, WAloss of engine power for undetermined reason(s). Factors relating to the accident were: the pilot's need to maneuvering to avoid obstructions near the approach end of the runway, and a ditch in the emergency landing area.NTSB FTW96LA138Accident · No injuriesLimited investigationFinal reportCessna 182A · Walsenburg, COFailure of the pilot to maintain directional control of the airplane after the left main tire went flat during the landing roll. The flat tire was a related factor.