NTSB investigations: Cessna 210L, 2002
10 cases on aircraft the registry lists as Cessna 210L. 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 | 1 |
|---|---|
| 1973 | 1 |
| 1974 | 10 |
| 1975 | 11 |
| 1976 | 17 |
| 1977 | 13 |
| 1978 | 10 |
| 1979 | 9 |
| 1980 | 8 |
| 1981 | 10 |
| 1982 | 12 |
| 1983 | 5 |
| 1984 | 4 |
| 1985 | 3 |
| 1986 | 3 |
| 1987 | 2 |
| 1988 | 8 |
| 1989 | 6 |
| 1990 | 3 |
| 1991 | 5 |
| 1992 | 4 |
| 1993 | 2 |
| 1994 | 5 |
| 1995 | 5 |
| 1996 | 4 |
| 1997 | 2 |
| 1998 | 1 |
| 1999 | 7 |
| 2000 | 3 |
| 2001 | 3 |
| 2002 | 10 |
| 2003 | 4 |
| 2004 | 1 |
| 2005 | 4 |
| 2007 | 2 |
| 2008 | 1 |
| 2010 | 3 |
| 2011 | 1 |
| 2012 | 1 |
| 2013 | 1 |
| 2014 | 2 |
| 2016 | 1 |
| 2017 | 2 |
| 2019 | 2 |
| 2020 | 3 |
| 2024 | 1 |
| 2025 | 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\") = 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 ('2073448'))
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 ('2073448'))
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 FTW03FA057Accident · 1 fatalField investigationFinal reportCessna 210L · Harrison, ARThe pilot's failure to maintain control of the aircraft and the exceedance of the manufactured limits, which resulted in an in flight break-up. Contributing factors were the dark night conditions and the clouds.NTSB FTW03FA044Accident · 1 fatalField investigationFinal reportCessna 210L · Kentwood, LAThe failure of the #1 and #2 connecting rods during climb to cruise due to overheating, resulting from oil starvation. A contributing factor was the low cloud conditions limiting the pilot's visibility during the ensuing emergency landing.NTSB NYC03FA020Accident · 1 fatalField investigationFinal reportCessna 210L · Rochester, NYA loss of engine power for undetermined reasons. A factor in this accident was the night light condition which precluded the pilot's ability to adequately view suitable forced landing areas.NTSB ATL02LA163Accident · No injuriesLimited investigationFinal reportCessna 210L · Georgetown, SCThe failure of the landing gear to lock in the down position.NTSB CHI02LA251Accident · No injuriesLimited investigationFinal reportCessna 210L · Lacon, ILThe pilot's improper in-flight decision to perform an intentional gear-up precautionary landing instead of continuing to the next available airport. A factor to the accident was the corn crop.NTSB SEA02LA141Accident · No injuriesLimited investigationFinal reportCessna 210L · Cascade, IDThe pilot's failure to maintain the proper rate of descent on short final resulting in a touchdown short of the runway threshold. Contributing factors were the variable winds and swampy terrain at the touchdown site.NTSB NYC02LA144Accident · Serious injuriesLimited investigationFinal reportCessna 210L · Zelienople, PAThe pilot failure to follow the published aborted landing procedures, with the retraction of the flaps to 10 degrees prior to reaching a safe altitude and airspeed, which resulted in an uncontrolled descent.NTSB ATL02IA112Incident · Minor injuriesIncident investigationFinal reportCessna 210L · Sarasota, FLThe pilot's failure to follow the before landing checklist and confirm that the landing gear was extended.NTSB ATL02LA056Accident · No injuriesLimited investigationFinal reportCessna 210L · Atlanta, GAThe pilot's failure to obtain the proper touchdown point and excessive airspeed on landing resulting in the airplane going off the end of the runway, on-ground collision with an embankment, and subsequent nose over.NTSB SEA02LA025Accident · No injuriesLimited investigationFinal reportCessna 210L · Great Falls, MTThe pilot's intentional continuation of a visual flight rules (VFR) flight into instrument meteorological conditions (IMC), and his failure to maintain clearance from the terrain. Factors include low ceilings, snow, mountainous/hilly terrain, and trees.