NTSB investigations: Cessna 210, 1989
6 cases on aircraft the registry lists as Cessna 210. 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 | 37 |
|---|---|
| 1965 | 31 |
| 1966 | 29 |
| 1967 | 20 |
| 1968 | 21 |
| 1969 | 14 |
| 1970 | 14 |
| 1971 | 12 |
| 1972 | 10 |
| 1973 | 5 |
| 1974 | 13 |
| 1975 | 12 |
| 1976 | 13 |
| 1977 | 8 |
| 1978 | 5 |
| 1979 | 6 |
| 1980 | 6 |
| 1981 | 2 |
| 1982 | 10 |
| 1983 | 4 |
| 1984 | 2 |
| 1985 | 1 |
| 1986 | 2 |
| 1987 | 4 |
| 1988 | 3 |
| 1989 | 6 |
| 1990 | 6 |
| 1991 | 7 |
| 1992 | 5 |
| 1993 | 4 |
| 1995 | 1 |
| 1996 | 4 |
| 1997 | 2 |
| 1998 | 2 |
| 1999 | 4 |
| 2000 | 2 |
| 2001 | 1 |
| 2002 | 2 |
| 2003 | 5 |
| 2004 | 3 |
| 2005 | 2 |
| 2006 | 3 |
| 2007 | 2 |
| 2008 | 4 |
| 2009 | 4 |
| 2010 | 2 |
| 2011 | 1 |
| 2012 | 4 |
| 2013 | 1 |
| 2014 | 2 |
| 2016 | 1 |
| 2017 | 3 |
| 2018 | 1 |
| 2020 | 2 |
| 2021 | 1 |
| 2022 | 1 |
| 2023 | 1 |
| 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\") = 1989
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2073402'))
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") = 1989
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2073402'))
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 LAX90LA030Accident · Minor injuriesLimited investigationFinal reportCessna 210 · North Hollywood, CAImproper planning/decision by the pilot, which resulted in fuel exhaustion from an inadequate supply of fuel. Factors related to the accident were: false fuel gage indications, lack of a suitable area for a forced landing, and obstructions (utility pole &…NTSB DEN90LA007Accident · No injuriesLimited investigationFinal reportCessna 210 · Ogden, UTAn engine stoppage for undetermined reasons.NTSB MIA90LA007Accident · No injuriesLimited investigationFinal reportCessna 210 · Jacksonville, FLInadequate preflight by the pilot, and fuel starvation, due to his improper positioning of the fuel selector.NTSB LAX89LA250Accident · No injuriesLimited investigationFinal reportCessna 210 · Thermal, CAA twisted nose gear uplock due to an elongated bolt hole which prevented the nose gear from extending.NTSB MKC89LA144Accident · No injuriesLimited investigationFinal reportCessna 210 · Kaiser, MOFailure of the pilot to extend the landing gear. A factor in the accident was the pilot's failure to use the checklist.NTSB SEA89LA034Accident · No injuriesLimited investigationFinal reportCessna 210 · Carson City, NVSeparation of the throttle cable due to wear as power was applied for a landing go-around. Contributing to the accident was rough terrain at the touchdown point of the forced landing.