NTSB investigations: Cessna 210, 2003
5 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\") = 2003
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") = 2003
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 LAX04LA083Accident · Minor injuriesLimited investigationFinal reportCessna 210 · Rialto, CAThe pilot's inadequate in-flight planning/decision by his fuel mismanagement and his delay in initiating remedial action which resulted in fuel exhaustion and the loss of engine power.NTSB FTW04LA042Accident · Serious injuriesLimited investigationFinal reportCessna 210 · Clarendon, TXthe loss of engine power due the separation of the number six cylinder as a result of a fatigue failure from the loosening of the cylinder attachment hardware.NTSB CHI03LA326Accident · No injuriesLimited investigationFinal reportCessna 210 · St. Paul, MNThe pilot in command performing an improper flare.NTSB LAX03LA218Accident · No injuriesLimited investigationFinal reportCessna 210 · Henderson, NVA bolt in the fuel selector that restricted the flow of fuel to the engine, which resulted in fuel starvation and a partial loss of engine power during the final approach to land.NTSB CHI03LA059Accident · No injuriesLimited investigationFinal reportCessna 210 · Clarence, IAA failure of the crankshaft for undetermined reasons. Factors associated with the accident were the rough terrain on which the forced landing was made and the night conditions.