NTSB investigations: Cessna 182P, 1997
13 cases on aircraft the registry lists as Cessna 182P. 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
| 1972 | 13 |
|---|---|
| 1973 | 23 |
| 1974 | 24 |
| 1975 | 29 |
| 1976 | 40 |
| 1977 | 36 |
| 1978 | 42 |
| 1979 | 31 |
| 1980 | 20 |
| 1981 | 19 |
| 1982 | 25 |
| 1983 | 22 |
| 1984 | 13 |
| 1985 | 17 |
| 1986 | 14 |
| 1987 | 7 |
| 1988 | 8 |
| 1989 | 10 |
| 1990 | 13 |
| 1991 | 8 |
| 1992 | 8 |
| 1993 | 11 |
| 1994 | 20 |
| 1995 | 8 |
| 1996 | 15 |
| 1997 | 13 |
| 1998 | 10 |
| 1999 | 7 |
| 2000 | 9 |
| 2001 | 13 |
| 2002 | 7 |
| 2003 | 8 |
| 2004 | 13 |
| 2005 | 7 |
| 2006 | 5 |
| 2007 | 13 |
| 2008 | 3 |
| 2009 | 9 |
| 2010 | 10 |
| 2011 | 9 |
| 2012 | 8 |
| 2013 | 6 |
| 2014 | 3 |
| 2015 | 4 |
| 2016 | 7 |
| 2017 | 7 |
| 2018 | 8 |
| 2019 | 6 |
| 2020 | 7 |
| 2021 | 4 |
| 2022 | 6 |
| 2023 | 2 |
| 2024 | 6 |
| 2025 | 9 |
| 2026 | 5 |
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\") = 1997
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2075816'))
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") = 1997
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2075816'))
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 NYC98LA042Accident · No injuriesLimited investigationFinal reportCessna 182P · Chatham, MAloss of engine power for undetermined reason(s). The tail wind component and an encounter with a ditch were related factors.NTSB ATL98LA013Accident · Minor injuriesLimited investigationFinal reportCessna 182P · Opa Locka, FLthe pilot's continued flight into adverse weather conditions, and failure to maintain clearance above the ground while attempting a VFR approach to an airport with low clouds. The low clouds (ceiling) and condition of light at dusk were related factors.NTSB NYC98FA016Accident · 1 fatalField investigationFinal reportCessna 182P · Morgantown, WVThe loss of engine power due to carburetor ice and the pilot's failure to follow ATC instructions during the emergency descent.NTSB FTW98LA026Accident · No injuriesLimited investigationFinal reportCessna 182P · Thompsons, TXThe loss of engine power resulting from a disconnected carburetor float due to improper maintenance. A factor was the lack of suitable terrain for a forced landing.NTSB CHI97LA307Accident · No injuriesLimited investigationFinal reportCessna 182 · Dassel, MNthe pilot's failure to attain the proper touchdown point on the airstrip. Factors associated with the accident were the high vegetation which skewed the pilot's visual perception of threshold, and the embankment which the airplane contacted.NTSB FTW97LA308Accident · No injuriesLimited investigationFinal reportCessna 182P · Arriba, COfailure of the pilot to properly plan the flight and determine the field conditions before landing. The soft runway condition was a related factor.NTSB CHI97LA243Accident · No injuriesLimited investigationFinal reportCessna 182P · Oshkosh, WIwake turbulence from another airplane encountered at an altitude which precluded regaining control of the airplane by the pilot.NTSB SEA97LA151Accident · No injuriesLimited investigationFinal reportCessna 182P · Yakima, WAThe loss of engine power for undetermined reasons. Contributing to the accident was the soft terrain.NTSB IAD97LA077Accident · No injuriesLimited investigationFinal reportCessna 182P · Wentworth, NHPilot's inadequate preflight planning to determine the suitability of an unimproved field for landing.NTSB NYC97LA094Accident · Minor injuriesLimited investigationFinal reportCessna 182P · Red Hook, NYThe pilot's improper compensation for the wind conditions and his failure to initiate a go-around.NTSB MIA97LA153Accident · No injuriesLimited investigationFinal reportCessna 182P · Mobile, ALthe pilot's inadequate compensation for wind conditions and failure to maintain directional control during landing rollout, which resulted in a collision with a runway light.NTSB CHI97LA115Accident · Serious injuriesLimited investigationFinal reportCessna 182P · Duluth, MNthe loss of engine power for undetermined reasons and the pilot's failure to maintain aircraft control.NTSB CHI97LA082Accident · No injuriesLimited investigationFinal reportCessna 182 · Kirksville, MOthe pilot failed to adequately compensate for the wind conditions on the runway during landing roll. Factors included the crosswind and gusts.