Aviation Accident Summaries

Aviation Accident Summary ERA10LA376

Philadelphia, MS, USA

Aircraft #1

N6035E

BEECH K35

Analysis

The pilot reported that the airplane touched down on the first third of the 4,000-foot-long asphalt runway. After touchdown he was unable to move the throttle control forward or back. He applied brake pressure; however, the airplane departed the end of the runway and struck a moving vehicle before stopping upright on a road. Postaccident examination of the airframe and engine, which included the throttle control, did not reveal evidence of mechanical malfunctions. There were no known witnesses to the landing and the airplane's touchdown point on the runway could not be determined. The reason for the throttle malfunction could not be determined.

Factual Information

On July 26, 2010, about 1320 central daylight time, a Beech K35, N6035E, registered to a private individual, was substantially damaged while landing at Barrett Field (MS96), Philadelphia, Mississippi. The commercial pilot was not injured. Visual meteorological conditions prevailed and no flight plan was filed for the personal flight conducted under the provisions of 14 Code of Federal Regulations Part 91. The flight originated from the Monroe County Airport, Aberdeen, Mississippi. According to information provided by a Federal Aviation Administration (FAA) inspector, the pilot reported that the airplane was landing on runway 6, a 4,000-foot-long, by 70-foot-wide, asphalt runway, when he experienced a stuck throttle. The airplane touched down on the first one-third of the runway and the pilot was unable to move the throttle control forward or back. He applied brake pressure; however, the airplane departed the end of the runway, and struck a moving vehicle before stopping upright on a road. Both wings, the fuselage, and nose gear were substantially damaged. Examination of the airframe and engine by an FAA inspector who responded to the accident site did not reveal evidence of mechanical malfunctions. The throttle was observed in the aft position, and could be moved freely. There were no known witnesses to the landing and the airplane's touchdown point on the runway could not be determined.

Probable Cause and Findings

A throttle control malfunction during landing for undetermined reasons, resulting in a runway overrun.

 

Source: NTSB Aviation Accident Database

Get all the details on your iPhone or iPad with:

Aviation Accidents App

In-Depth Access to Aviation Accident Reports