FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA11FA391 · Cessna 421C

9 Jul 2011 · Demopolis, AL, United States

Cessna 421C · Accident: loss of control in flight on approach

From Creve Coeur Airport (1H0) to Destin Executive Airport (DTS)

Report a problem

Event

NTSB case
ERA11FA391
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
7 · 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
Not recorded

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
N692TT
Operator
Unknown
Onboard fatalities
Unknown
Route
From Creve Coeur Airport (1H0), St. Louis, MOTo Destin Executive Airport (DTS), Destin, FL
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
Approach · VFR pattern final
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 › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The multi-engine airplane was in cruise flight at flight level 210 when the pilot declared an emergency due to a rough-running right engine and diverted to a non-towered airport about 10 miles from the airplane’s position. About 4 minutes later, the pilot reported that he had shut down the right engine. The pilot orbited around the diversion airport during the descent and reported to an air traffic controller that he did not believe he would require any assistance after landing. The airplane initially approached the airport while descending through about 17,000 feet mean sea level (msl) and circled above the airport before entering a left traffic pattern approach for runway 22. About 7,000 feet msl, the airplane was about 2.5 miles northeast of the airport. The airplane descended through 2,300 feet msl when it was abeam the runway threshold on the downwind leg of the traffic pattern. According to the airplane information manual, procedures for landing with an inoperative engine call for “excessive altitude;” however, the airplane's last radar return showed the airplane at an altitude of 700 feet msl (about 600 feet above ground level) and about 3 miles from the approach end of the runway.

The airplane was configured for a single-engine landing and was likely on or turning to the final approach course when it rolled and impacted trees. The airplane came to rest in a wooded area about 0.8 miles north of the runway threshold, inverted, in a flat attitude with no longitudinal deformation. A majority of the airplane, including the cockpit, main cabin, and left wing, were consumed by a postcrash fire. Search operations located the airplane about 6 hours after its expected arrival time. Due to the severity of the postcrash fire, occupant survivability after the impact could not be determined. Examination of the airframe, the left engine, and both propellers did not reveal any preaccident mechanical malfunctions or failures that would have precluded normal operation. The investigation revealed that the right engine failed when the camshaft stopped rotating after the camshaft gear experienced a fatigue fracture on one of its gear teeth. The remaining gear teeth were fractured in overstress and/or were crushed due to interference contact with the crankshaft gear. Spalling observed on an intact gear tooth suggested abnormal loading of the camshaft gear; however, the origin of the abnormal loading could not be determined.

Probable cause

The pilot's failure to maintain airplane control during a single-engine approach and his failure to fly an appropriate traffic pattern for a single-engine landing. Contributing to the accident was a total loss of engine power on the right engine due to a fatigue failure of the right engine cam gear.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA11FA391
Event ID
20110710X31135
Case number
ERA11FA391
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. 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: 48a3832881c9953a2c886d94e81f03d2df50f70cd9fba29b851cbe3369ee675d; retrieved 2026-09-13T21:33:23.872Z.