CEN14LA324 · Cessna 414 UNDESIGNAT
Cessna 414 UNDESIGNAT · Accident: loss of engine power (total) on approach
From Creve Coeur Airport (1H0) to Campbell Army Airfield (Fort Campbell) (HOP)
Event
- NTSB case
- CEN14LA324
- 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
- 0 · 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 414 UNDESIGNAT
- Aircraft type
- Cessna 414
- 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
- N1552T
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Creve Coeur Airport (1H0), Maryland Heights, MOTo Campbell Army Airfield (Fort Campbell) (HOP), FORT CAMPBELL/HOPKINSVILLE, KY
- Aircraft age
- About 42 years (built 1972)
- 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 downwind
- 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 engine power (total)
- 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
- Wire
- 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
- Not determined › Not determined
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 reported that, shortly after takeoff, the twin-engine airplane's left front baggage door opened. He attempted to return to the airport, but the left engine lost engine power while the airplane was on the downwind leg of the traffic pattern. The airplane subsequently impacted power lines and terrain. An explosion occurred during the impact sequence, and a fire ensued that almost completely consumed the airframe.
Teardown examination of the right engine revealed no anomalies. A test run of the left engine revealed no anomalies; however, due to impact and fire damage, it was not possible to fully test or examine the left engine's fuel system. The reason for the left engine's loss of power could not be determined.
Probable cause
The loss of left engine power for reasons that could not be determined due to impact and fire damage.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN14LA324
- Event ID
- 20140626X55709
- Case number
- CEN14LA324
- 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: 178f02bc374d65b8a15081e28bc2e2b41831635e116ec4c47d2ac45046def9bd; retrieved 2026-09-16T00:29:33.555Z.