26 Jun 2014: CESSNA 414 UNDESIGNAT

26 Jun 2014: CESSNA 414 UNDESIGNAT (N1552T) — Unknown operator

No fatalities • Maryland Heights, MO, United States

Probable cause

The loss of left engine power for reasons that could not be determined due to impact and fire damage.

— NTSB Determination

Accident narrative

On June 26, 2014, about 0457 central daylight time, a Cessna 414 airplane, N1552T, was destroyed by impact forces and a post-impact fire following a loss of control during landing approach to runway 34, at the Creve Coeur Airport (1H0), near Maryland Heights, Missouri. The pilot received serious injuries during the accident. The aircraft was registered to Tango Two Aviation, LLC and operated by the private pilot under the provisions of 14 Code of Federal Regulations Part 91 as a personal flight. Visual meteorological conditions prevailed for the flight. An instrument flight rules flight plan had been filed but not yet activated. The flight was originating at the time of the accident and the intended destination was Fort Campbell, Kentucky.

The pilot reported that he performed a normal pre-flight inspection and pre-takeoff run-up of the airplane before the flight. He then departed from runway 16, intending to open the instrument flight plan once airborne. About 15 to 20 seconds after rotation, when the airplane was about 400 to 500 feet above ground level (agl), the left front baggage door opened. The pilot stated that he leveled the airplane and turned to a right crosswind with the intention of landing on runway 16 so that he could close the baggage door and then continue the flight. Shortly after turning downwind for runway 16, the left engine stopped producing power. The pilot stated that while in the process of feathering the left engine, and maintaining airspeed, the airplane struck power lines and then the ground. The airplane exploded during the impact sequence.

During a postaccident examination of the airplane, fire and impact damage of the wreckage prevented a comprehensive determination of all aircraft systems. Partial continuity of the flight control system was confirmed. The instrument panel and cabin section of the airplane were consumed by the post-impact fire. The majority of the fuel system components were consumed by the post-impact fire. The postaccident examination of the airframe revealed no evidence of a mechanical failure or malfunction that would have precluded normal operation.

The airplane's engines were transported to the manufacturer's facility for further examination. It was determined that too much damage had been incurred to the right engine making a test run of that engine unfeasible. As a result, the right engine was subjected to a teardown examination. The teardown examination revealed no preimpact anomalies.

The airplane's left engine was sufficiently intact, allowing an engine run to be attempted in a test cell at the manufacturer's facilities. Due to damage incurred in the accident sequence, several components of the engine's fuel system were replaced with surrogate units prior to the engine test run. During the test run, the engine started normally, and produced full rated power. It was noted during the engine run that the fuel pump pressure and flow were high and the engine test was completed with the mixture manually leaned to the proper fuel flow settings. The fuel pump was subsequently tested on a flow bench and the test readings indicated that the fuel pump was set high (rich) when compared to the engine manufacturer's production test specifications. The higher than normal fuel flow could have resulted in reduced power due to a richer than normal fuel mixture but would not have accounted for a complete loss of engine power. Additionally, it was not possible to determine if the fuel pump output as installed in the airframe was within specifications due to differences between the airframe installation and that of the test cell. No further abnormalities in engine operation were noted during the test run.

Contributing factors

  • Contributed to outcome

Conditions

Weather
VMC, vis 10sm

Loading the flight search…

What you can do on Flight Finder

  • Search flights between any two airports with live fares.
  • By aircraft — pick a plane model (e.g. Boeing 787, Airbus A350) and see every route it flies from your origin.
  • Route map — click any airport worldwide to explore its destinations, or draw a radius to find nearby airports.
  • Global aviation safety — aviation accident database, 5,200+ records since 1980, with map and rankings by aircraft and operator.
  • NTSB safety feed — recent U.S. aviation accidents and incidents from the official NTSB CAROL database, updated daily.

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.