BEECH K35 near Philadelphia, MS — 2010-07-26

Probable cause

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

NTSB narrative

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.

Analysis

Primary failure mode

Mechanical failure

First missed decision gate

Pilot could have aborted the landing when throttle became unresponsive.

NTSB coding

• Powerplant sys/comp malf/fail · Landing-landing roll

Evidence available

• Photos
• 4 docket documents

Docket documents4

• Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 and pilot statmentmentsform
• Interview Memoranduminterview
• Maintenance Records (excerpts)other
• Photograph # 1 - Airplane as it came to rest (Provided by FAA)photos

Related mishaps

• PIPER PA-20-135

  2021-01-01 · Riverside, UT

• Beech 33

  2019-07-20 · Battleground, WA