What happened
While operating in the cruise phase of flight, the pilot notified air traffic control regarding issues with engine fuel pressure. Although the controller provided information on nearby landing options, the pilot elected to proceed with the original flight path. Flight data from the onboard avioness recorded a momentary loss of engine power approximately 20 seconds prior to the pilot's initial report. Roughly seven minutes later, while at an altitude of approximately 7,000 feet, the engine suffered a complete loss of power that could not be recovered.
Following the second engine failure, the pilot attempted to reach an airport located 10 miles away. However, the aircraft type crashed in a field roughly 3 miles from the destination. There were 0 fatalities and 0 injuries reported in the provided text.
Findings
Analysis of GPS and flight data revealed that fuel pressure drops preceded both instances of engine power loss. The data also showed sustained lateral g-forces, suggesting the aircraft was in a side-slip condition. Investigators found the rudder trim tab was displaced 3/8 inch to the left, a setting consistent with the requirements for a typical climb segment. While the autopilot was engaged—a state that should have activated the yaw damper—the yaw damper was not functioning or engaged, leading to uncoordinated flight.
It was determined that the pilot's failure to properly trim the rudder caused a prolonged uncoordinated flight state. While the fuel system is designed to handle brief periods of uncoordinated flight, it could not prevent fuel unporting during this extended period, which led to the loss of fuel pressure. Additionally, the propeller was not feathered, causing it to windmill and increase the descent rate. The pilot also maintained a glide airspeed 20 knots below the recommended speed in the Pilot's Operating Handbook. These factors combined to reduce the aircraft's gliding range, preventing it from reaching the intended airport.