WPR10LA260

A loss of engine power for reasons that could not be determined because postaccident examination of the engine did not reveal any anomalies that would have precluded normal operation. Contributing to the accident was the pilot's failure to obtain the proper touchdown point on the runway, which led to the runway overrun.

During the takeoff initial climb, the pilot reported that the rudder trim became deflected to the left and remained stuck in that position. He stopped the climb, cycled the autopilot, and turned off the yaw damper; however, his efforts did not resolve the rudder trim deflection issue. The pilot input rudder in an attempt to correct the issue, and he thought that the airplane was under control, so he continued the flight to his destination. The avionics failed shortly thereafter, followed by the illumination of the low fuel pressure light. Then the engine lost power. The pilot feathered the propeller and was able to reach an airport for an emergency landing. During the landing, the airplane floated down the runway, touching down about midfield. The pilot was not able to stop the airplane before it exited the runway and collided with terrain. Postaccident, the rudder trim tab was found deflected two inches to the left. However, the rudder trim indicator showed a full deflection to the right. The circuit breaker was found partially open and was recycled, as indicated in the pilot’s operating handbook for rudder trim emergencies, and the anomaly could not be replicated. Postaccident examination also found 90 gallons of fuel in the right tank and no fuel in the left tank. However, this airplane is equipped with a fuel autobalance system, which should have selected fuel to be fed from the right tank with the left tank empty. The reason for the loss of engine power could not be determined during postaccident testing and examination.

On May 23, 2010, about 1600 Pacific daylight time, a Socata TBM-700, N750AB, lost engine power during cruise flight, and the pilot made an emergency landing on runway 33 at the Lost Hills – Kern County Airport (L84), Lost Hills, California. The airplane overran the runway and the nose landing gear was sheared off. The airplane came to rest on its nose. The owner operated the airplane under the provisions of 14 Code of Federal Regulations Part 91 as a personal flight. The pilot/owner and four passengers were not injured; the airplane sustained substantial damage to the wings and fuselage. Visual meteorological conditions prevailed for the flight that departed San Luis Obispo Airport (SBP), San Luis Obispo, California, about 1530, with a planned destination of Fresno-Yosemite Airport (FAT), Fresno, California. No flight plan had been filed; however, the pilot had been receiving flight-following. The pilot was interviewed by a National Transportation Safety Board (NTSB) investigator. He stated that earlier on the day of the incident he had topped off with fuel before departing FAT; total fuel on board the airplane was 282 gallons. He and his family landed at SBP about 1100, went to lunch, and visited a local university campus. They returned to the airport for the return flight to SBP. In preparation for takeoff, he set the flaps to 10 degrees, and set the aileron and rudder trim for a normal takeoff. The takeoff was normal and the pilot stated that after takeoff, his intent was to climb the airplane to an altitude of 13,500 feet. However, during the climb, he reported that the rudder deflected all the way to the left, and he discontinued the climb. He maintained an altitude of 9,500 feet, and started to troubleshoot the problem; which included turning off the yaw dampener and manually flying the airplane. He also cycled the auto pilot, but the issue was not resolved. The pilot reported that Oakland Air Traffic Control Center (OAK ATCT) controllers asked him if he needed assistance, which he initially declined. The pilot stated that he initiated a climb to his original altitude of 13,500 feet. He reported that during the climb, the airplane’s avionics failed, including the global positioning system (GPS), followed by a loss of engine power and illumination of the low fuel pressure light. The pilot further stated that the low fuel pressure light was illuminated for the left fuel tank. He radioed OAK ATCT and requested vectors to the nearest airport. The pilot stated that during landing, with full flaps, the airplane “floated” down the runway. After touchdown, he applied the brakes; however, the airplane continued off the runway and struck debris, shearing off the nose landing gear. According to the pilot’s written statement, the rudder became stuck about 5 minutes out of SBP. The full left rudder deflection caused the airplane to turn to the right. He turned off the auto pilot and flew the airplane manually, utilizing the rudder pedals to compensate. He contacted OAK ATCT, and was asked if he needed assistance, as they had noted that he was having problems keeping the airplane straight. The pilot stated that he thought he had the airplane under control and would continue toward FAT. The pilot added that during the initial contact with OAK ATCT, they were not able to read his transponder, and he was asked to recycle it. He complied with the request, and simultaneously lost both of the GARMINS (Garmin 530 and Garmin 430), the red and yellow warning lights came on, and the engine stopped running. The pilot stated that he noted that the red light illuminated indicating low fuel. He asked for vectors to the nearest airport, and then feathered the propeller, while trying to restart the engine. Subsequent to the accident, the pilot reported to representatives from the Federal Aviation Administration (FAA) that after departure and passing through 9,500 feet, he noticed that the slip/skid indication on the pilot’s flight display indicated a full right deflection. The pilot confirmed this from the rudder deflection indicator located on the pedestal. He turned off the auto pilot and yaw damper systems and was able to gain better control of the airplane; however, the airplane remained in a right turn. After the airplane lost engine power, the pilot feathered the propeller to provide a better glide ratio. He declared an emergency with air traffic control (ATC) and asked for vectors to the nearest airport. He informed ATC that he did not have any indications of navigation since both Garmin’s, the GNS430 and 530, had both temporarily lost power and were rebooting. The pilot continued to the accident airport and made a left base approach for runway 33. The airplane landed midfield and rolled off the end of the runway about 300 feet causing the nose landing gear to shear off and damaging the left wing and fuselage. Retrieval personnel noted that the airplane had come to rest in a nose-down attitude. Both wings remained attached to the fuselage. The left flap was extended with no apparent damage to the left aileron and flap. No fuel was recovered from the left fuel tank. The right wing contained about 90 gallons of fuel. The bottom of the fuselage sustained substantial damage. Two of the four propeller blades were folded underneath the nose of the airplane, but the propeller assembly remained attached to the drive flange. Inside the cockpit, retrieval personnel visually noted that all of the circuit breakers were pushed in (closed). They also noted that the fuel sequencer was selected to AUTO. Prior to recovery of the airplane with an airframe representative, a functional check of the rudder trim and fuel control unit (FCU) was performed. When maintenance personnel turned on the avionics master and autopilot switches, the autopilot tested normally. They noted that the rudder trim indicator showed a full deflection to the right. The rudder trim switch was then activated in the direction to return the rudder trim to the neutral position. Maintenance personnel reported that the rudder trim switch did not move the rudder trim indicator nor was there any noise of a trim motor running. Utilizing the pilot’s operating handbook chapter 3.13 titled EMERGENCY SECTION – RUNWAY TRIMS, it directs the pilot to pull the circuit breaker (CB). As maintenance personnel went to pull the rudder trim CB, he noted that it was already partially out. He then recycled the rudder trim CB and performed the test again with no anomalies noted. Maintenance personnel also reported that the autopilot was retested with no issues, and there were no other avionics failures. A functional test of fuel delivery to the engine was performed. The fuel line was opened up just past the auxiliary pump. The pump was turned on, and fuel was observed to flow through the pump. The fuel line was reconnected and the procedure was performed again but this time to the FCU. Maintenance personnel reported that there was no fuel flow restriction to the FCU, and the pressure differential indicator (PDI) on the fuel filter was extended. An examination of the fuel filter revealed that the fuel bypass indicator had popped. Visual inspection of the airframe and engine revealed no mechanical problems. On June 24, 2010, the engine was inspected by a representative from Pratt and Whitney under the auspices of the NTSB, in Madera, California. During the recovery it was noted that the airframe in-line fuel filter bowl and impending bypass indicator was extended. Visual inspection of the engine revealed no mechanical anomalies; all connections and fittings were intact and secured. The compressor and power turbine inlet areas were inspected; they were found to be intact with no evidence of blade rub or blade shift. A more detailed report is attached to the public docket for this accident. The airframe was inspected on July 21, 2010, by the NTSB investigator-in-charge (IIC) and a representative