NTSB investigations: Cessna 210-5(205)
128 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
| 1964 | 10 |
|---|---|
| 1965 | 10 |
| 1966 | 9 |
| 1967 | 9 |
| 1968 | 4 |
| 1969 | 5 |
| 1970 | 6 |
| 1971 | 3 |
| 1972 | 5 |
| 1973 | 3 |
| 1974 | 3 |
| 1975 | 5 |
| 1976 | 2 |
| 1977 | 2 |
| 1978 | 2 |
| 1979 | 3 |
| 1980 | 2 |
| 1981 | 1 |
| 1982 | 3 |
| 1983 | 1 |
| 1984 | 2 |
| 1985 | 1 |
| 1986 | 1 |
| 1987 | 2 |
| 1988 | 3 |
| 1989 | 1 |
| 1990 | 2 |
| 1991 | 1 |
| 1992 | 1 |
| 1995 | 2 |
| 1996 | 1 |
| 1997 | 2 |
| 1999 | 3 |
| 2001 | 1 |
| 2003 | 1 |
| 2004 | 1 |
| 2005 | 1 |
| 2007 | 1 |
| 2008 | 1 |
| 2009 | 2 |
| 2011 | 2 |
| 2012 | 1 |
| 2013 | 1 |
| 2014 | 1 |
| 2016 | 1 |
| 2019 | 1 |
| 2022 | 1 |
| 2024 | 1 |
| 2025 | 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 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.
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."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" 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 ANC25LA077Accident · No injuriesClass 3 · LimitedPreliminary reportCessna 210-5 · Yakutat, AKOn July 23, 2025, about 1700 Alaska daylight time, a Cessna 210-5 (205) airplane, N8457Z, was substantially damaged when it was involved in an accident on a remote beach about 50 miles southeast of Yakutat, Alaska. The pilot was uninjured. The airplane was…NTSB CEN24LA371Accident · No injuriesClass 4 · LimitedFinal reportCessna 210-5(205) · Bryan, TXThe pilot’s failure to maintain aircraft control during the landing.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.NTSB WPR19LA196Accident · No injuriesClass 3 · LimitedFinal reportCessna 210 5(205) · Dallesport, ORThe pilot’s improper pitch control during the aborted takeoff, which resulted in a bounced landing and landing gear collapse.NTSB GAA16CA514Accident · No injuriesData collectionFinal reportCessna 205 · Ellington, CTThe pilot's exceedance of the airplane's critical angle-of-attack during the initial climb after an attempted go-around, which resulted in an aerodynamic stall.NTSB ERA15LA071Accident · Minor injuriesLimited investigationFinal reportCessna 210 5(205) · Sussex, NJMaintenance personnel’s inadequate inspection of the No. 2 cylinder valve area during the most recent annual inspection, which resulted in the in-flight failure of the intake valve springs due to rust on the spring surfaces and subsequent fatigue cracking.NTSB CEN13LA565Accident · No injuriesLimited investigationFinal reportCessna 210-5(205) · Weatherford, OKThe pilot’s inadequate preflight inspection and fuel planning, which resulted in fuel exhaustion and a total loss of engine power during descent.NTSB WPR12CA284Accident · Minor injuriesData collectionFinal reportCessna 210-5 · West Glacier, MTThe pilot elected to abort the takeoff without sufficient runway available to land and stop the airplane. Contributing to the accident was the illusion created by the rising terrain, which influenced the pilot's decision to abort the takeoff.NTSB WPR11FA348Accident · Minor injuriesField investigationFinal reportCessna 210-5(205) · Darby, MTThe fatigue failure of the aluminum air intake duct, which resulted in material being ingested into the engine cylinders and a subsequent loss of engine power during cruise flight.NTSB WPR11CA330Accident · No injuriesData collectionFinal reportCessna 210-5(205) · McKenzie Bridge, ORThe pilot's improper landing flare and inadequate recovery from a bounced landing.NTSB ERA09CA366Accident · Minor injuriesData collectionFinal reportCessna 210-5(205) · Porterdale, GAThe loss of engine power due to fuel exhaustion as a result of the pilot's use of improper fuel caps. Contributing to the accident was the pilot’s selection of an unsuitable area for landing.NTSB 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.NTSB WPR09CA006Accident · No injuriesData collectionFinal reportCessna 210-5(205) · Payson, UTThe total loss of engine power during cruise flight for undetermined reasons. Contributing to the accident were a dark night and a cherry orchard at the location where the pilot executed the forced landing.NTSB 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.NTSB SEA06CA024Accident · No injuriesData collectionFinal reportCessna 210-5 · Lopez Island, WAThe pilot's failure to maintain adequate clearance from an airport sign during the visual approach. The sign was a factor in the accident.NTSB LAX04LA194Accident · No injuriesLimited investigationFinal reportCessna 205 · Page, AZthe fatigue fracture and separation of the pilot's control wheel, which resulted in a momentary loss of control and a hard landing.NTSB 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.NTSB 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.NTSB LAX99LA297Accident · No injuriesLimited investigationFinal reportCessna 205 · Gualala, CAThe pilot's failure to attain a proper touchdown point due to his misjudgment of the aircraft's speed, altitude, and distance to the runway. The pilot's failure to initiate a go-around is also causal.NTSB 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…NTSB SEA99LA046Accident · Minor injuriesLimited investigationFinal reportCessna 205 · Edison, WAA total loss of engine power due to fatigue of the number six crankcheek resulting in crankshaft separation, and the lack of suitable terrain. Contributing factors were the sign and the ditch.NTSB 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…NTSB FTW97LA102Accident · Serious injuriesLimited investigationFinal reportCessna 210-5 · Hobbs, NMThe loss of engine power due to fuel starvation for undetermined reasons. A factor was the pilot's continued flight after a fuel consumption anomaly was encountered.NTSB FTW96LA345Accident · No injuriesLimited investigationFinal reportCessna 210-5 · Muskogee, OKloss of engine power due to fuel contamination. The lack of suitable terrain for a forced landing was a related factor.NTSB 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.NTSB ANC95LA052Accident · No injuriesLimited investigationFinal reportCessna 205 · Anchorage, AKA failure of the engine driven fuel pump. Factors in the accident were the pilots' inadequate in-flight planning and unsuitable terrain in the area of the forced landing.NTSB FTW92LA056Accident · No injuriesLimited investigationFinal reportCessna 205A · Spring, TXThe partial power loss due to cylinder fatigue and resultant engine vibrations. Factors were the oil covered windshield restricting the pilot's vision and the wet terrain.NTSB 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.NTSB FTW91LA026Accident · No injuriesLimited investigationFinal reportCessna 205 · Medford, OKThe pilot's use of improper starting procedures which resulted in the loss of control of the airplane. A factor in the accident was the airplane's encounter with rough terrain during the unmanned taxi.NTSB MKC90LA125Accident · No injuriesLimited investigationFinal reportCessna 205 · Jonesburg, MOThe pilot in commands failure to attain a touchdown on the runway resulting in touchdown to the side of the runway and a nose over in soft terrain.NTSB NYC90LA028Accident · No injuriesLimited investigationFinal reportCessna 205 · Morristown, NJIn-flight collision with object.NTSB 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'…NTSB 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…NTSB CHI88DEE04Accident · Minor injuriesFinal reportCessna 205 · Moline, ILDuring initial climb on a pleasure flight the airplane experienced a loss of fuel pressure and then total engine failure. The airplane nosed over during the subsequent off airport landing. Post accident examination of the engine driven fuel pump revealed…NTSB 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…NTSB BFO87LA029Accident · Minor injuriesLimited investigationFinal reportCessna 205 · Midland, VAThe plt stated that this was the first time he had ever landed on rwy 32. During the lndg apch, about 15 secs before touchdown, his eyeglasses broke and fell off his face. He reached for his spare eyeglasses that were on top of the instrument panel; however,…NTSB NYC86FNC09Accident · Minor injuriesFinal reportCessna 205 · Twin Mountain, NHDuring a 'bomb drop' contest at an organized 'fly-in', the pilot was maneuvering at low airspeed so his passenger could drop a water-filled balloon on a target which had been placed on runway 27. The acft suddenly banked to the right and pitched down striking…NTSB DEN85LA207Accident · Minor injuriesLimited investigationFinal reportCessna 205 · Pueblo, COThe plt/owner departed Pueblo, CO, on a VFR pleasure flt to California. During the flt the plt encountered IMC and elected to return to Pueblo. Witnesses observed the plt making low passes over his parent's home in west Pueblo just prior to impacting rolling…NTSB 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…NTSB 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…NTSB 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…NTSB SEA82DA086Accident · Minor injuriesFinal reportCessna 210-5(205) · Jerome, IDDuring takeoff, the engine lost power at about 100 ft AGL. The pilot elected to land in a newly planted bean field. After touchdown, the wheels sank into soft terrain and the plane nosed over. An examination of the aircraft and engine revealed no precrash…NTSB ATL82DA131Accident · No injuriesFinal reportCessna 205 · Hopkinsville, KYDuring landing roll the pilot applied right brake and rudder. The application seemed ineffective so he applied more rudder and the aircraft veered off the runway to the right, colliding with a ditch. The aircraft then nosed over. The wind was calm.NTSB FTW82DA133Accident · No injuriesFinal reportCessna 205 · Albuquerque, NMThe pilot stated that the landing was normal and that he applied light braking for passenger comfort while keeping the aircraft on the runway centerline and looking for the runway end. Heavy braking was applied when the runway end lights were observed. The…NTSB CHI82FEV02Accident · Minor injuriesClosedCessna 205 · Danville, ILNTSB LAX80DUJ84Accident · No injuriesClosedCessna 210-5 · Prescott, AZNTSB CHI80FEE13Accident · Minor injuriesClosedCessna 210 · Monee, ILNTSB CHI80FEI06Accident · Minor injuriesClosedCessna 205 · Mansfield, OHNTSB DEN79FTE29Accident · No injuriesClosedCessna 205 · Englewood, CONTSB LAX79DUJ44Accident · No injuriesClosedCessna 205 · Casa Grande, AZ