Pilot Debrief

RAYTHEON AIRCRAFT COMPANY G36 near Horseshoe Bay, TX — 2015-05-28

Final reportCEN15LA247
Sign in to save
Date
2015-05-28
Location
Horseshoe Bay, TX, USA
Airport
DZB
Aircraft
RAYTHEON AIRCRAFT COMPANY G36
Registration
N224TB
Category
Airplane
Highest injury
Serious
Fatalities
0
Phase of flight
Takeoff roll

Probable cause

The pilot’s failure to abort the takeoff after the partial loss of engine power before liftoff, and the partial loss of engine power for undetermined reasons.

NTSB narrative

About six weeks before the accident, the pilot aborted a takeoff when the airplane’s engine did not develop the expected manifold pressure required for takeoff. After the aborted takeoff, the pilot completed several engine runups to troubleshoot the engine issue. The fuel flow to the engine would suddenly decrease when the engine power was increased above 24 inches of manifold pressure. The pilot’s aviation mechanic was unable to replicate the engine issue on two subsequent occasions. On the day of the accident, the pilot completed an uneventful before-takeoff engine runup. The airplane then had a loss of engine power during the takeoff run when the pilot increased the engine power to about 25 inches of manifold pressure. The pilot immediately reduced engine throttle, and the engine resumed normal operation at a lower manifold pressure. The pilot aborted the takeoff, taxied off the runway, and attempted to troubleshoot the engine issue. However, he was unable to replicate the engine issue during a subsequent engine run-up, during which the engine ran normally at 28 inches of manifold pressure. He also verified proper operation of the fuel selector, magnetos, battery and alternator, engine-driven fuel pump, auxiliary fuel pump, and mixture control. The pilot decided that he would fly the airplane to another location where it could be further examined by his aviation mechanic. The pilot selected 30 inches of manifold pressure and 33 gallons per hour (gph) for the takeoff, but the engine power decreased to 25 inches of manifold pressure and 12 gph at some point during the takeoff roll. The pilot stated that he believed the airplane would have departed the end of the runway if he had aborted the takeoff and that, despite the partial loss of engine power, he thought he could save the airplane by continuing the takeoff. The pilot was unable to restore full engine power and a forced landing was completed to a nearby highway. The airplane was subsequently destroyed by a postimpact fire. A mobile phone video showed the airplane began its takeoff roll about 175 ft from the start of the runway. The airport manager reported that the airplane did not appear to accelerate normally during the takeoff roll. Video of the takeoff showed the airplane became airborne about 3,560 ft down the runway from where it started its takeoff roll. Takeoff performance calculations determined that about 1,250 ft of the 5,977 ft-long asphalt runway was required for a normal takeoff at maximum gross weight and with the wing flaps retracted. Based on the available information, the pilot was aware of the partial loss of engine power during the takeoff run and should have aborted the takeoff before liftoff, which required about 3 times the expected runway distance. After liftoff, the airplane was observed in a shallow climb before it rolled to the left and descended into trees and terrain. The airplane was subsequently destroyed during a postimpact fire. Postaccident examination of the engine and its accessories did not reveal any mechanical malfunction that would have resulted in a loss of engine power. However, the engine, fuel system, and turbo-normalizing components sustained extensive damage that precluded the additional testing required to determine why the engine lost power.

Analysis

Primary failure mode
Engine power loss
First missed decision gate
Pilot could have aborted takeoff after initial partial loss of engine power.

NTSB coding

Evidence available

  • Video
  • 12 docket documents
View NTSB final reportView NTSB docket

Docket documents12

Related mishaps