FTW04FA243 · Cessna 421C
Cessna 421C · Accident: partial loss of engine power (non-mechanical) en route
From Angel Fire Airport (AXX) to Austin Bergstrom International Airport (AUS)
Event
- NTSB case
- FTW04FA243
- 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
- 2 · 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
- N729DM
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Angel Fire Airport (AXX), Angel Fire, NMTo Austin Bergstrom International Airport (AUS), Austin, TX
- Aircraft age
- Not recorded
- 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 · descent
- First occurrenceThe 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
- Partial loss of engine power (non-mechanical)
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Fuel starvation
- 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
- Fluid, fuel › Starvation
- Pilot in command › Fuel tank selector position, improper
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The 14,000-hour airline transport pilot was hired to fly the owner of the airplane and his mother on a cross country flight. Approximately 3 hours and 15 minutes into the flight, the pilot reported that he had a rough running engine and declared an emergency. A review of ATC voice communications revealed that the pilot had changed his mind several times during the emergency about diverting to a closer airport or continuing to the intended destination. Prior to his last communication, the pilot informed ATC that he, "was not gonna make it." The sole survivor of the accident reported that the flight was normal until they approached their destination. He said, "all of a sudden the engines did not sound right." The right engine sounded as if the power was going up and down and the left engine was sputtering. The airplane started to descended and the pilot made a forced landing in wooded area. The cockpit, fuselage, empennage, and the right wing were consumed by post-impact fire. A review of fueling records revealed that the pilot had filled the main tanks prior to the flight for a total of 213.4 gallons; of which 206 gallons were usable (103 gallons per side). During the impact sequence, the left wing separated at the wing root and did not sustain any fire damage. No fuel was found in the tank, and there was no discoloration of the vegetation along the left side of the wreckage path or around the area where the wing came to rest. The left fuel selector was found set to the LEFT MAIN tank, and the right fuel selector valve was set between the LEFT and RIGHT MAIN tanks. This configuration would have allowed fuel to be supplied from each tank to the right engine. A review of the airplane's Information Manual, Emergency Procedures-Engine Failure During Flight (speed above air minimum control speed) instructed the pilot to re-start the engine, which included placing both fuel selector handles to the MAIN tanks (Feel for Detent). If the engine did not start, the pilot was to secure the engine, which included closing the throttle and feathering the propeller. The propellers were not feathered. Examination of the airplane and engine revealed no mechanical deficiencies.
Probable cause
The pilot's improper positioning of the fuel selector valves, which resulted in a loss of power to the left engine due to fuel exhaustion. After the power loss, the pilot failed to follow checklist procedures and did not secure (feather) the left propeller, which resulted in a loss of altitude and subsequent forced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW04FA243
- Event ID
- 20040930X01550
- Case number
- FTW04FA243
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: 66d0c3b04d8f3d079c15756b817e4da00cf6337177c3bc1268faf76b59859c54; retrieved 2026-09-20T18:19:54.528Z.