FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA22FA114 · Cessna 310 R

1 Feb 2022 · Danville, VA, United States

Cessna 310 R · Accident: loss of control in flight en route

From Danville Regional Airport (DAN) to an unrecorded destination

Report a problem

Event

NTSB case
ERA22FA114
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
0
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 310 R

Aircraft type
Cessna 310
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
N622QT
Operator
Unknown
Onboard fatalities
Unknown
Route
From Danville Regional Airport (DAN), Danville, VATo not recorded
Aircraft age
About 45 years (built 1977)
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
En route · climb to cruise
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
Destroyed

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Aircraft › Aircraft power plant
  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Physical

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

NTSB narrative

The pilot was performing an aerial survey flight, and after completing a preflight inspection, he taxied toward the runway for engine run-up and surveying computer start-up. During taxi and the subsequent run-up, the airplane was positioned for about 8-10 minutes with a quartering tailwind. Track data revealed that shortly after takeoff, the airplane’s climb rate decreased, and its acceleration stopped. Shortly thereafter, the airplane began a 10°-bank-angle left turn at an airspeed of about 136 knots, followed by a rapidly descending right turn and impact with terrain. Postaccident examination of the wreckage revealed that the left fuel tank selector handle was in the OFF position, the left throttle was near idle, the left propeller control was near the feather position, and the rudder was trimmed to the right. These control positions were consistent with the left engine being partially secured, which would result in a lack of power and the loss of climb rate noted shortly after takeoff. Additionally, the right fuel tank selector handle was found in the left main fuel tank position. The examination of both engines revealed no evidence of any preimpact anomalies or malfunctions that would have precluded normal operation, and no reason for why the pilot might have partially secured the left engine. In the event of an engine failure during takeoff, the airplane manufacturer’s Pilot’s Operating Handbook (POH) assumes that the inoperative propeller is feathered and that 5° of bank toward the operating engine is used to balance the side force generated by a full rudder input. If these conditions do not exist, the airplane can quickly become uncontrollable at airspeeds much higher than the published single-engine minimum controllable airspeed (Vmc). The physical evidence, along with a performance analysis of the airplane’s flight track, showed that the left engine was not fully secured, the right engine fuel selector was set to the left tank, and the airplane banked 10° into the inoperative engine at an airspeed of about 136 kt shortly before the airplane entered a steep, descending right turn. This turn toward the inoperative engine would have dramatically increased the airplane’s minimum controllable airspeed above that assumed by the POH (80 knots), and the pilot's ability to maintain control of the airplane would have been significantly reduced. It is likely that during this left turn, the pilot allowed the airplane's airspeed to decrease below a speed for which the airplane would have been controllable, which resulted in a loss of control and led to the airplane's roll to the right and rapid descent toward the terrain.

Postaccident toxicological testing performed by a state office of forensic science revealed that the pilot’s carboxyhemoglobin, a marker of carbon monoxide (CO) exposure, was elevated at 31%. Although the Federal Aviation Administration Forensic Sciences Laboratory toxicology results did not show elevated carboxyhemoglobin, these test results might have been misleadingly low if there was an actual postmortem decrease of carboxyhemoglobin in the tested blood. This may have occurred if the specimens were obtained from a collection site where blood intermixed with gastric acid. The carboxyhemoglobin percentage measured in the blood specimen tested by the state forensic science office was confirmed by a second distinct technique, and the probability is small that the elevated result was attributable to postmortem changes. Examination of the airplane’s combustion heater assembly revealed no defects that could have allowed the combustion biproducts to intermix with the ventilation air, and examination of the wreckage revealed no evidence of inflight or post-impact fire. A postaccident test with an exemplar airplane (the same make/model as the accident airplane) that was equipped with an electronic CO detector revealed that when taxiing and performing an engine run-up with a quartering tailwind, the exhaust from the left engine was able to penetrate the cockpit. Based on the observations from this test, it is possible that engine exhaust gasses containing CO could have entered the cockpit while the pilot was conducting his pre-takeoff tasks. Given that the airplane was equipped only with a disposable “spot” CO detector, the pilot would not have been alerted to increasing CO levels unless he had looked at the device and observed a color change. Given that the temperature on the day of the accident was 33° F, it is likely that the airplane’s heater was operating. It is possible that its fan could have drawn additional air containing engine exhaust gasses and CO into the cabin heater air intake, and then into the cockpit, which would have increased the pilot’s the level of CO exposure. No other source of abnormal CO was identified. Based on available operational and physical evidence, it is likely that the pilot was impaired due to CO exposure. It is possible that this impairment could have resulted in his perception of a left engine problem, and resulted in him partially securing it, as demonstrated by the postaccident positions of the engine controls. Ultimately, the turn into the partially secured engine resulted in a loss of control and impact with terrain.

Probable cause

The pilot’s impairment due to exposure to carbon monoxide as a result of undetected engine exhaust penetration into the cockpit, resulting in the pilot's failure to maintain a minimum controllable airspeed after partially securing an engine after takeoff.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA22FA114
Event ID
20220201104587
Case number
ERA22FA114
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, cause areas. 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: e18f6e5c2dcb9f61fba4bd9243efe577c463051cafdf075628eeaf3acf452f0e; retrieved 2026-09-15T07:40:45.025Z.