Fatal NTSB investigations: Cessna 210D

21 cases on aircraft the registry lists as Cessna 210D. 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

19662026
Fatal NTSB investigations: Cessna 210D per year, 1966–2026: 21 cases
19661
19681
19692
19702
19711
19721
19801
19821
19881
19893
19931
19951
19991
20001
20111
20181
20251

Latest 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 c.\"highestInjuryLevel\" = 'Fatal'
    AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2073414'))
  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.

NTSB CEN25FA348Accident · 2 fatalClass 3 · FieldPreliminary reportCessna 210D · Kearney, NEOn August 27, 2025, about 20:57 central daylight time, a Cessna 210D, N3806Y was destroyed when it was involved in an accident near Kearney, Nebraska. Both pilots were fatally injured. The flight was operated under the provisions of Title 14 Code of Federal…Aug 28, 2025 · N3806Y · Substantial damageNTSB ERA19FA059Accident · 1 fatalField investigationFinal reportCessna 210 · Apalachicola, FLThe pilot's controlled flight into terrain as a result of his spatial disorientation during departure in dark nighttime conditions.Nov 30, 2018 · N3995Y · DestroyedNTSB ERA11FA258Accident · 1 fatalField investigationFinal reportCessna 210D · Altavista, VAThe pilot’s loss of airplane control due to spatial disorientation. Contributing to the accident was the pilot’s lack of experience in actual night instrument conditions.Apr 23, 2011 · N3963Y · Substantial damageNTSB NYC00FA209Accident · 1 fatalField investigationFinal reportCessna 210D · Ashland, VAThe failure of the pilot to maintain control of the airplane due to spatial disorientation. Factors were the dark night, low ceiling and fog.Jul 26, 2000 · N3894Y · DestroyedNTSB CHI00FA042Accident · 2 fatalField investigationFinal reportCessna 210D · Saint Charles, MOthe aircraft control not maintained by the pilot and the pilot exceeded the design limits of the aircraft. The clouds and night conditions were contributing factors.Dec 13, 1999 · N3807Y · DestroyedNTSB SEA96FA021Accident · 3 fatalField investigationFinal reportCessna 210D · Yellow Pine, IDimproper planning/decision by the pilot, his resultant VFR flight into instrument meteorological conditions (IMC), and his failure to maintain altitude and clearance from mountainous terrain. Factors relating to the accident were: the adverse weather…Nov 18, 1995 · N3741Y · DestroyedNTSB CHI93FA234Accident · 1 fatalField investigationFinal reportCessna 210D · Salem, MIthe pilot's physical impairment.Jun 28, 1993 · N3899Y · DestroyedNTSB FTW89FA172Accident · 1 fatalField investigationFinal reportCessna 210D · Covington, LAThe pilot in command's disregard of the weather information provided during two briefings and his decision to continue VFR flight into IMC condtions. Factors contributing to the accident were the pilot's lack of night and instrument experience.Sep 26, 1989 · N3962Y · DestroyedNTSB DEN89FA091Accident · 1 fatalField investigationFinal reportCessna 210D · Eugene, ORThe pilot's decision to continue VFR flight into instrument meteorological conditions (IMC). Factors related to the accident were: the terrain and weather conditions at the accident site, and the pilot's lack of instrument experience.Mar 23, 1989 · N3823Y · DestroyedNTSB CHI89FA039Accident · 2 fatalField investigationFinal reportCessna 210D · Alvin, ILContinued flight by the non-instrument rated pilot into instrument meteorological conditions (IMC), and his failure to maintain sufficient altitude. Factors related to the accident were: darkness, adverse weather conditions, the pilot's lack of instrument…Jan 1, 1989 · N3767Y · DestroyedNTSB ATL89MA023Accident · 1 fatalMajor investigationFinal reportCessna 210D · Nashville, TNDrg west arr at ngt, plt was vctrd for a VFR, straight-in apch to rwy 2R & adzd of Boeing 727 off his rgt front, passingfm rgt to left. He was cautioned abt wake turbc (w/t) & replied, 'okay I see him.' Ctlr then told plt to turn inbnd & maint 'visual' with…Nov 2, 1988 · N3822Y · DestroyedNTSB ATL82FKG09Accident · 1 fatalFinal reportCessna 210D · Near Commerce, GAThe owner had flown a PA-23 from charlotte to jackson county,FL with another plt following him in N3909Y. The owner stated the other plt was very meticulous & always drained fuel prior to flt. After the 1 hr flt to jackson county, they both looked over the…Mar 9, 1982 · N3909Y · Substantial damageNTSB CHI80FA030Accident · 1 fatalClosedCessna 210D · Chicago, ILMar 21, 1980 · N210RV · DestroyedNTSB MIA73AM071Accident · 4 fatalClosedCessna 210D · Hollins, ALDec 31, 1972 · N3773Y · DestroyedNTSB DEN71AD045Accident · 3 fatalClosedCessna 210 · Yeso, NMJun 7, 1971 · N3913Y · DestroyedNTSB OAK71AP015Accident · 2 fatalClosedCessna 210D · Bass Lake, CASep 13, 1970 · N2310F · DestroyedNTSB DEN71AD008Accident · 4 fatalClosedCessna 210D · Yellowstn Prk, WYAug 22, 1970 · N3952Y · DestroyedNTSB SEA70A0006Accident · 6 fatalClosedCessna 210D · Boise, IDJul 30, 1969 · N3735Y · 2 aircraft · DestroyedNTSB DIA69A0041Accident · 1 fatalClosedCessna 210D · Afton, VAFeb 2, 1969 · N3871Y · DestroyedNTSB DEN69A0014Accident · 5 fatalClosedCessna 210 · Fort Morgan, COSep 21, 1968 · N3745Y · DestroyedNTSB FTW67A0006Accident · 4 fatalClosedCessna 210D · Antelope, TXJul 10, 1966 · N3781Y · Destroyed