FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN23FA038 · Cessna 421C

18 Nov 2022 · Decatur, TX, United States

Regional Aviation Cessna 421C · Accident en route

From Denton Enterprise Airport (DTO) to Bridgeport Municipal Airport (XBP)

Report a problem

Event

NTSB case
CEN23FA038
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 421C

Aircraft type
Cessna 421
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
N6797L
Onboard fatalities
Unknown
Route
From Denton Enterprise Airport (DTO), Denton, TXTo Bridgeport Municipal Airport (XBP), Bridgeport, TX
Aircraft age
About 41 years (built 1981)
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 · 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
Unknown or undetermined
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 power plant
  • Aircraft › Fluids/miscellaneous hardware

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

NTSB narrative

After takeoff, the pilot proceeded about 30 miles and climbed to an altitude of about 2,200 ft mean sea level (msl). About 8 minutes after takeoff, the airplane entered a descending left turn that continued until impact. A witness observed a twin-engine airplane at a low altitude and in a descent. After the airplane descended below the tree line, a fireball emerged followed by some smoke; however, the smoke was thin and dissipated quickly. A second witness observed the airplane at a low altitude and in a slow, descending turn. The flight path was steady and the wings “never dipped.” Shortly after the airplane descended out of sight, he observed an explosion. Both engines were on fire when he arrived at the accident site, and there was a fuel leak from the right engine toward the cockpit area. He used a fire extinguisher to keep the fire off the fuselage until first responders arrived. The airplane impacted a utility pole and terrain. Burned vegetation was present over portions of the accident site. The left wing was separated outboard of the engine and was located near the utility pole. A postaccident examination revealed that the left main fuel tank was partially consumed by the postimpact fire; therefore, the amount of fuel in the tank could not be determined. The left engine nacelle was discolored consistent with the postimpact fire. The left nacelle fuel tank appeared intact, and no fuel was visible in the left nacelle fuel tank. However, the amount of fuel in the left nacelle fuel tank at the time of impact could not be determined. The right main fuel tank appeared intact, and about 1 gallon of fuel was drained from the tank during recovery of the airplane. While the postimpact fire was consistent with fuel present onboard the airplane at the time of the accident, the lack of an extensive and sustained ground fire suggested that a limited amount of fuel was present. The left and right engine cockpit fuel selectors were both positioned to the “RIGHT MAIN” fuel tank. The left fuel selector valve, located in the engine nacelle, was in the “OFF” position at the time of the exam. The right fuel selector was in the “RIGHT” fuel tank position. A teardown examination of the left engine did not reveal any anomalies consistent with a preimpact failure or malfunction. A teardown examination of the right engine revealed damage consistent with oil starvation throughout the engine. A teardown examination of the left propeller assembly revealed indications that the blades were at or near the feather pitch stop position during the impact sequence. A teardown examination of the right propeller assembly revealed indications that the blades were on or near the low pitch stop position during the impact sequence. The fuel flow indicator displayed the total fuel remaining as 8.3 gallons when powered up on a test bench. However, the fuel quantity indications are dependent on the pilot properly configuring the device when the airplane is refueled. The fuel flow indicator does not directly provide fuel quantity information. According to the airplane flight manual, the total unusable fuel for the airplane, with one engine nacelle fuel tank installed, was 7.8 gallons. Engine performance data recovered from the onboard engine monitor revealed a reduction in right engine power to near idle power. About 1 minute later, the airplane entered a descending left turn which continued until impact. About 3 minutes after the reduction in right engine power, the left engine completely lost power. Immediately afterward, right engine power increased to near full (takeoff) power. However, about 30 seconds later the right engine completely lost power. The airplane impacted the pole and the terrain a few seconds later. The pilot likely detected an impending failure of the right engine and intentionally reduced power. However, shortly afterward, the left engine lost power due to fuel starvation. At that time, the pilot likely set the left engine to crossfeed from the right main fuel tank to restore power. Unsuccessful, the pilot then decided to feather the left propeller and attempted to use any available power from the right engine, but the right engine immediately lost power as well. Whether the right engine lost power at that moment due to fuel starvation or oil starvation could not be determined. The pilot was obese and had hypertension, high cholesterol, and an enlarged heart with left ventricular thickening. While these cardiovascular conditions placed him at an increased risk for a sudden incapacitating cardiac event, the autopsy did not show any acute or remote myocardial infarction, and the flight path suggests intentional actions until the crash. Thus, the pilot’s cardiovascular disease was not a factor in this accident. Toxicology testing detected the muscle relaxant cyclobenzaprine and its active metabolite norcyclobenzaprine in the pilot’s femoral blood at low therapeutic levels. The sedative-hypnotic medication zolpidem was detected at subtherapeutic levels. While these substances are associated with side effects such as drowsiness and dizziness, the operational findings of this accident do not suggest performance issues related to fatigue. Thus, it is unlikely that the effects from the pilot’s use of cyclobenzaprine and zolpidem were factors in this accident.

Probable cause

A loss of power on the left engine due to fuel starvation and the subsequent loss of power on the right engine for undetermined reasons.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN23FA038
Event ID
20221118106319
Case number
CEN23FA038
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: c63d2bc2303e992eacb8ac714c0766563117e56509062c0fa1b57564ea1dcc49; retrieved 2026-09-15T07:54:17.397Z.