NTSB investigations: Cessna T210L, 2006
5 cases on aircraft the registry lists as Cessna T210L. 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 | 4 |
|---|---|
| 1973 | 6 |
| 1974 | 9 |
| 1975 | 14 |
| 1976 | 16 |
| 1977 | 18 |
| 1978 | 15 |
| 1979 | 18 |
| 1980 | 10 |
| 1981 | 8 |
| 1982 | 8 |
| 1983 | 5 |
| 1984 | 4 |
| 1985 | 11 |
| 1986 | 5 |
| 1987 | 9 |
| 1988 | 5 |
| 1989 | 7 |
| 1990 | 8 |
| 1991 | 4 |
| 1992 | 10 |
| 1993 | 4 |
| 1994 | 8 |
| 1995 | 6 |
| 1996 | 6 |
| 1997 | 5 |
| 1998 | 4 |
| 1999 | 3 |
| 2000 | 3 |
| 2001 | 5 |
| 2002 | 3 |
| 2003 | 6 |
| 2004 | 5 |
| 2005 | 3 |
| 2006 | 5 |
| 2007 | 3 |
| 2008 | 2 |
| 2009 | 6 |
| 2010 | 2 |
| 2011 | 3 |
| 2012 | 5 |
| 2013 | 5 |
| 2014 | 2 |
| 2015 | 4 |
| 2016 | 1 |
| 2017 | 4 |
| 2018 | 1 |
| 2019 | 3 |
| 2020 | 2 |
| 2021 | 1 |
| 2022 | 4 |
| 2024 | 3 |
| 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\") = 2006
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2073449'))
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") = 2006
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2073449'))
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 CHI07CA047Accident · Minor injuriesData collectionFinal reportCessna T210L · North St. Louis, MOFuel starvation due to an inadequate fuel supply. A factor associated with the accident was the soft terrain encountered during the landing.NTSB SEA06LA100Accident · Serious injuriesLimited investigationFinal reportCessna T210L · Battle Ground, WAthe pilot's excessive airspeed and exceeding the proper touchdown point during landing, which resulted in a hard landing and subsequent overrun of the runway. Factors contributing to the accident included the fence, the trees and the pilot's failure to…NTSB LAX06LA178Accident · Serious injuriesLimited investigationFinal reportCessna T210L · Chico, CAThe loss of engine power due to the pilot's inadequate preflight inspection and failure to verify the amount of fuel onboard.NTSB CHI06CA118Accident · No injuriesData collectionFinal reportCessna T210L · Henryville, INThe pilot selected an empty fuel tank during the approach which resulted in fuel starvation and subsequent loss of engine power. A factor associated with the accident were the trees that the airplane contacted during the forced landing.NTSB ATL06CA032Accident · Minor injuriesData collectionFinal reportCessna T210L · Auburn, ALThe pilot's failure to attain the proper touchdown point during landing which resulted in an overrun and subsequent on ground collision with a fence.