FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN16FA188 · Cessna P210N

18 May 2016 · Sheridan Lake, CO, United States

Cessna P210N · Accident: loss of control in flight while maneuvering

From Southwest Wyoming Regional Airport (RKS) to Wiley Post Airport (PWA)

Report a problem

Event

NTSB case
CEN16FA188
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
1 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Cessna P210N

Aircraft type
Cessna 210
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N6609P
Operator
Unknown
Onboard fatalities
Unknown
Route
From Southwest Wyoming Regional Airport (RKS), Rock Springs, WYTo Wiley Post Airport (PWA), Oklahoma City, OK
Aircraft age
About 38 years (built 1978)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Maneuvering · aerobatics
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Loss of control in flight
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Action/decision
  • Personnel issues › Physical
  • Personnel issues › Task performance

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The private pilot was conducting a cross-country flight at 17,500 ft mean sea level (msl) while operating on a visual flight rules clearance. About 2 hours after takeoff, the pilot stated over the radio, "(unintelligible) I'm going down and I'm going down hard." Based on the pilot's speech, it became apparent to the controller that the pilot was experiencing some type of distress. The controller attempted to communicate with the pilot, concerned that he was possibly experiencing hypoxia, carbon monoxide exposure, or another medical condition that was affecting his speech and ability to control the airplane. Throughout the remainder of the flight, the controller provided numerous altimeter setting updates recommending that the pilot descent to a lower altitude in a continued effort to assist the pilot; however, the pilot did not acknowledge or reply to these requests. During three different radio transmissions, the pilot stated, "I can show you…" what the airplane can do. He also stated, "(unintelligible) guys want me to do Muller?", which is an aerobatic maneuver that involves a flat spin and recovery. (The airplane is not approved for aerobatics or spins.) Radar data indicated that the airplane entered a series of turns, climbs, and descents. The final recorded radar return indicated the airplane was about 9,200 ft msl. The airplane subsequently impacted a field in a flat spin. Examination of the airframe, engine, and airplane pressurization system revealed no mechanical malfunctions or anomalies that would have precluded normal operation.

Given that the airplane's descent did not improve the pilot's control of the airplane's heading or the quality of his communication with the controller, it is likely that the pilot's behavior was not the result of hypoxia.

Toxicology testing on the pilot was positive for ethanol at ranges between 0.247 gm/dl and 0.335 gm/dl, which is significantly higher than the legal limit of 0.040 gm/dl. While ethanol can be produced in tissues after death, this occurs by microbial action; and vitreous, where the levels were highest in specimens from the pilot, is typically a sterile fluid. In addition, an approximately half-full bottle of vodka was found in the wreckage, suggesting that the majority of the identified ethanol had been ingested. Further, the tested samples were positive for three additional impairing substances; diphenhydramine, lorazepam, and zolpidem. The pilot's impaired speech and behavior were most likely caused by the effects of high levels of alcohol along with effects from the three prescription medications, which likely led him to believe that he could perform maneuvers in the airplane that it was not capable of performing.

Probable cause

The pilot's severe impairment from the combined effects of high levels of ingested alcohol as well as three impairing medications (zolpidem, lorazepam, and diphenhydramine), which resulted in his decision to attempt an aerobatic maneuver that the airplane was not approved for.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN16FA188
Event ID
20160518X42840
Case number
CEN16FA188
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 7613f9513ad439e577a662797511853d6ec1e123cd5c2242f85e90203a64f596; retrieved 2026-09-14T21:46:46.489Z.