FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA22FA126 · Beech 58

16 Feb 2022 · Lexington, NC, United States

Beech 58 · Accident: loss of engine power (partial) during takeoff

Report a problem

Event

NTSB case
ERA22FA126
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
1 · 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
N58LF
Operator
Unknown
Onboard fatalities
Unknown
Route
From not recordedTo not recorded
Aircraft age
About 50 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
Takeoff
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 (partial)
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

  • Aircraft › Aircraft oper/perf/capability
  • Aircraft › Aircraft power plant
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

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

NTSB narrative

The pilot was initiating takeoff following completion of an annual inspection, which included replacing and repairing components of the right engine’s No. 1 cylinder, likely due to detonation that occurred during the flight before the accident flight. During the takeoff on the accident flight, witnesses noted significant smoke trailing the right engine at rotation. The witnesses noted that, as the airplane continued over the runway, the right engine lost power and the right propeller feathered. The landing gear retracted and, at the departure end of the runway, white/blue or white smoke was noted trailing the left engine, followed by a perceived loss of power from that engine. The airplane continued off-airport, encountered an aerodynamic stall, and impacted a tractor-trailer travelling on a nearby highway, resulting in a postimpact fire. Postaccident examination of the airframe revealed no evidence of preimpact failure or malfunction of the flight controls or flaps, and there was no evidence of an in-flight left engine fire. Examination of the engines revealed early signs of detonation on the No. 1 piston of the right engine. In addition, the No. 3 cylinder fuel injector nozzle of the left engine was not installed in the cylinder but remained attached to the fuel injector line throughout the flight. Given these findings, it is likely that both engines sustained a partial loss of engine power during takeoff. The witness reports of seeing smoke trailing the left engine when at the departure end of the runway were likely the result of the No. 3 cylinder fuel injector nozzle that was not installed on its respective cylinder. Based on blade impact angles and performance estimates from the propeller manufacturer, it is likely that the left engine exhibited about a 15% power reduction from full rated power during the takeoff. The reduction of left engine power and corresponding rpm would likely have been evident to the pilot from the moment of full power application until about 60 knots, at which point the airflow over the left propeller would have been sufficient for the propeller to operate at full rated rpm. The witness report of the right engine’s power loss and the feathering of the right propeller was likely the pilot’s response to the start of detonation in the No. 1 cylinder. Causes for detonation include improper ignition timing, high inlet air temperature, engine overheating, oil in the combustion chamber, carbon build-up in the combustion chamber, an issue with the fuel octane, or a lean fuel to air mixture. Although the position of the right mixture control at the start of the takeoff could not be determined from the available evidence, it is unlikely that the pilot would have leaned the fuel to air ratio, especially since it was the first takeoff after repairs due to detonation damage following a flight for which he was the pilot. In addition, operating the engines with the fuel to air ratio leaned during the accident takeoff would have been contrary to the takeoff procedure specified in the Pilot’s Operating Handbook and FAA-approved airplane flight manual. Aside from signs of detonation, the No. 1 cylinder and piston, spark plugs, fuel injector nozzle and line, manifold valve, and engine-driven fuel pump of the right engine were eliminated as having any evidence of preimpact failure or malfunction. Impact and/or heat damage, along with impact-separated components of the ignition system, including both magnetos and ignition harness, baffling, cowling, air induction, and fuel metering systems, as well as there being no remaining fuel due to the postimpact fire, precluded determination of preimpact failure or malfunction for these components. Although the root cause of detonation could not be determined from the available evidence, had maintenance facility personnel thoroughly investigated the fuel metering, ignition, and air induction systems and reviewed data from the engine monitor from the previous flight in which the No. 1 cylinder of the right engine exhibited detonation, it is likely that they could have identified and addressed any mechanical reason for the detonation. While moderate atherosclerosis was detected in one segment of the pilot’s left anterior descending coronary artery, there was no evidence to suggest an acute cardiac event occurred; from medical records, he was in good cardiovascular health. Although a disqualifying stimulant used to treat attention deficit hyperactivity disorder (ADHD) was detected during postaccident toxicological testing, the circumstances of this accident do not suggest inattention or fatigue. Thus, the pilot’s cardiovascular medical condition, the effects of his use of methylphenidate, and his ADHD were likely not factors in this accident.

Probable cause

Inadequate maintenance, which led to a partial loss of both right and left engine power during takeoff, and the pilot’s subsequent failure to maintain airspeed while maneuvering with one engine at low altitude. Contributing to the accident was the pilot’s failure to detect the partial loss of left engine power during the early part of the takeoff.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA22FA126
Event ID
20220216104653
Case number
ERA22FA126
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, cause areas. 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: b79d6aba40bb6f7c66f9464323a97c307138ce07292d788320bf8b39e70ead56; retrieved 2026-09-15T07:41:10.149Z.