Fatal NTSB investigations: Cessna 210-5(205)

25 cases on aircraft the registry lists as Cessna 210-5(205). 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

19642026
Fatal NTSB investigations: Cessna 210-5(205) per year, 1964–2026: 25 cases
19641
19651
19661
19671
19681
19692
19701
19721
19731
19831
19842
19871
19882
19911
19951
19971
19991
20011
20031
20071
20091
20221

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 ('2073202'))
  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 CEN23FA057Accident · 2 fatalClass 3 · FieldFinal reportCessna 210-5(205) · Cleburne, TXAn in-flight loss of control as a result of spatial disorientation in night instrument meteorological conditions.Dec 5, 2022 · N8149Z · DestroyedNTSB WPR09FA096Accident · 2 fatalField investigationFinal reportCessna 205 · Flagstaff, AZThe pilot's loss of situational awareness and failure to maintain clearance from hilly terrain while flying in an area of a low cloud ceiling. Contributing to the accident was the pilot's decision to continue flight due to a self-induced pressure.Jan 23, 2009 · N8298Z · Substantial damageNTSB SEA07FA148Accident · 2 fatalField investigationFinal reportCessna 210-5 (205) · Quilcene, WAThe pilot's continued flight into instrument meteorological conditions, which resulted in controlled flight into mountainous terrain. Factors contributing to the accident included the low clouds which obscured the rising, mountainous terrain.Jun 7, 2007 · N8308Z · Substantial damageNTSB NYC03FA131Accident · 4 fatalField investigationFinal reportCessna 205 · Jeannette, PAThe loss of power caused by fragments of the air filter being ingested in the engine. A factor was the pilot's delayed decision to perform a forced landing after experiencing a partial loss of engine power.Jun 15, 2003 · N124A · Substantial damageNTSB FTW01FA171Accident · 4 fatalField investigationFinal reportCessna 205 · De Queen, ARthe pilot's VFR flight into IMC, which resulted in spatial disorientation and a loss of aircraft control. A contributing factor to the accident was the pilot's lack of total instrument flight time.Jul 28, 2001 · N8324Z · DestroyedNTSB IAD99FA043Accident · 6 fatalField investigationFinal reportCessna 205 · Celina, OHwas the pilot's failure to refuel the airplane which resulted in fuel exhaustion and a loss of engine power. Also causal to the accident was the pilot's failure to maintain aircraft control after the power loss. A factor in the accident was a lack of…May 9, 1999 · N8157Z · DestroyedNTSB MIA97FA173Accident · 6 fatalField investigationFinal reportCessna 205 · Homestead, FLThe pilot-in-command's failure to maintain airspeed as he slowed for a parachutist to jump from the aircraft, and his failure to apply spin recovery emergency procedures prior to ground impact. Contributing to the accident was the pilot-in-command's lack of…May 25, 1997 · N8214Z · DestroyedNTSB MIA96FA047Accident · 3 fatalField investigationFinal reportCessna 205 · Culebra, PRFailure of the pilot to maintain sufficient altitude/clearance above the terrain, while maneuvering at night. Factors relating to the accident were: darkness with no visible horizon, and the pilot's lack of recent experience in night flight.Dec 18, 1995 · N8415Z · DestroyedNTSB LAX91FA207Accident · 4 fatalField investigationFinal reportCessna 205 · Fallon, NVThe pilot-in-command's improper handling of the airplane and failure to maintain airspeed on initial takeoff climb resulting in an in flight loss of control, stall/spin, and subsequent in flight collision with terrain.May 11, 1991 · N8360Z · DestroyedNTSB SEA89LA030Accident · 1 fatalLimited investigationFinal reportCessna 205 · Cottage Grove, ORThe student pilot took off on a solo flight from an uncontrolled airport at Cottage Grove in marginal weather conditions. Shortly after takeoff, he transmitted to eugene tower (which was approximately 15 miles north) that he had encountered 'white-out'…Dec 27, 1988 · N8403Z · DestroyedNTSB FTW88FA119Accident · 4 fatalField investigationFinal reportCessna 205 · Elgin, TXThe pilot radioed that he was running out of fuel while being vectored for landing. The ceiling was about 900 feet with 5 miles visibility and the accident occurred in a level grass field. Witnesses heard the engine cutting out and a loss of control occurred…Jun 10, 1988 · N8181Z · DestroyedNTSB ATL87FA168Accident · 4 fatalField investigationFinal reportCessna 205C · Bowling Green, KYShortly after takeoff from Bowling Green, the pilot reported a problem. He did not report the details of the problem, but witnesses heard the aircraft backfiring as it descended. The aircraft had taken on fuel at Bowling Green. The investigation failed to…Jun 16, 1987 · N1823Z · DestroyedNTSB FTW84FA180Accident · 4 fatalField investigationFinal reportCessna 210-5(205) · Beaumont, TXThe acft was flown into IMC wx after the flt had been advised by the wx service that VFR flt was barely feasible. No wx briefing by FAA was recorded & no flt plan was filed. The accident occurred during the hrs of darkness. A witness near the accident site…Apr 1, 1984 · N8150Z · DestroyedNTSB ATL84FA092Accident · 1 fatalField investigationFinal reportCessna 210 · Newport News, VAThe flight had been airborne for aprx 38 mins when the pilot began experiencing communication problems. Nine minutes later the pilot reported 'instrument problems' and began to receive radar vectors to a landing. 15 minutes later she declared an emergency and…Feb 5, 1984 · N8437Z · DestroyedNTSB LAX84FA012Accident · 2 fatalField investigationFinal reportCessna 210-5 (205) · Schurz, NVThe acft was on a crosscountry flight in VFR conditions. The non-instrument rated pilot encountered instrument conditions at night and lost control of the acft in flight. The post crash investigation revealed evidence of an inflight structural failure due to…Oct 14, 1983 · N8370Z · DestroyedNTSB OAK74DVD33Accident · 3 fatalClosedCessna 205 · Yecora, MexicoOct 28, 1973 · N8299Z · DestroyedNTSB SEA72AS035Accident · 1 fatalClosedCessna 205 · Canyonville, ORMar 3, 1972 · N8161Z · DestroyedNTSB OAK71AP025Accident · 2 fatalClosedCessna 205A · Castro Vlly, CANov 11, 1970 · N8167Z · DestroyedNTSB LAX70A0029Accident · 1 fatalClosedCessna 210-5 · Yucca Valley, CANov 9, 1969 · N8194Z · DestroyedNTSB OAK70A0030Accident · 2 fatalClosedCessna 205 · Orangeville, CANov 1, 1969 · N8314Z · DestroyedNTSB CHI68F0611Accident · 1 fatalClosedCessna 210-5 · Detroit, MIFeb 21, 1968 · N8348Z · Substantial damageNTSB DIA67A0017Accident · 4 fatalClosedCessna 205 · New Castle, VAMay 4, 1967 · N1301G · DestroyedNTSB MKC67F0291Accident · 1 fatalClosedCessna 205 · Fredericktown, MOOct 2, 1966 · N1852Z · DestroyedNTSB MIA66F0045Accident · 1 fatalClosedCessna 210-5 · Del Rio, TNJun 22, 1965 · N8424Z · DestroyedNTSB UNK64X3635Accident · 2 fatalClosedCessna P206 · Wichita, KSAug 27, 1964 · N8464Z · Substantial damage