FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN13FA267 · Beech 58

4 May 2013 · Mena, AR, United States

Keet Management Beech 58 · Incident: loss of engine power (total) during initial climb

From Mena Intermountain Municipal Airport (MEZ) to Bill & Hillary Clinton National Airport/Adams Field (LIT)

Report a problem

Event

NTSB case
CEN13FA267
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
Incident
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

Beech 58

Aircraft type
Beechcraft 58
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
N44GC
Onboard fatalities
Unknown
Route
From Mena Intermountain Municipal Airport (MEZ), Mena, ARTo Bill & Hillary Clinton National Airport/Adams Field (LIT), Little Rock, AR
Aircraft age
About 39 years (built 1974)
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
Initial climb
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)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Minor

Cause areas

  • Aircraft › Aircraft power plant
  • 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 and the pilot-rated passenger were preparing to depart from an airport where the twin-engine airplane had just undergone refurbishment of the interior. The pilot stated that both engines started normally. They taxied to the runway and used the checklist to perform an engine run-up on both engines. The pilot said the engine run-up was normal. He then lined the airplane up on the runway, applied full power to each engine (red line is 2,700 rpm), and departed. Once airborne, the pilot initiated a right turn. The pilot said that, when the airplane was at an altitude of between about 1,200 and 1,400 feet, he brought the propeller controls back to 2,500 rpm and left the power on both engines at 30 inches of manifold pressure. The mixture controls remained full forward. Almost immediately after reducing the rpm, the pilot heard a "faint" and indistinguishable "pop" from the left engine. Both engines simultaneously went from "full power" to idle, but the manifold pressure remained at 30 inches. The pilot said he made an immediate turn back to the runway and landed gear-up on the grassy area adjacent to the departure runway threshold.

A postaccident examination of the airplane revealed only minor damage to the right wing, left horizontal stabilizer, and fuselage. The propeller blades also exhibited slight twisting, which was consistent with them rotating at the time of impact. Several slash marks made by the propellers were observed in the grass where the airplane made the forced landing. The measured distance between these marks was consistent with both engines operating between 1,570 and 1,890 rpm at the time the propellers contacted the ground.

Data from the onboard engine monitor, which recorded exhaust gas temperature (EGT), cylinder head temperature (CHT), and turbocharger turbine inlet temperature on each engine, were downloaded and plotted. The data revealed that the left engine lost power several seconds before the right engine. A rise in EGT was observed at this time as well. According to the engine manufacturer, if the mixture control were leaned, it would have decreased the mechanical fuel pumps' fuel flow and might have caused the smooth rise in EGT. However, the CHT continued to climb for several seconds after the decline of EGT on both engines. The data also indicated that the EGT appeared to rise again slightly before the data ended. The pilot reported that he did not move the mixture control at any time during the short flight. Due to the engine monitor's limited parameters (no rpm or fuel flow data), a conclusive cause for the power loss could not be determined. Examination of the airplane's fuel, electrical, and flight control systems revealed no preincident mechanical deficiencies that would have led to a loss of engine power. Both engines were examined then test run on the airframe using the airplane's fuel system. No mechanical deficiencies were identified that would have contributed to a loss of engine power.

Probable cause

A partial loss of power on both engines during takeoff for reasons that could not be determined because examination of the airframe and a test run of both engines revealed no mechanical anomalies that would have precluded normal operation.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN13FA267
Event ID
20130509X40743
Case number
CEN13FA267
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: d15300b43ce8510c99faea2f18cbb71202b4775a0561bb3715136d9489cc1c31; retrieved 2026-09-15T21:28:59.333Z.