Accident Details
Probable Cause and Findings
The pilot's failure to retard the engine throttle to idle during the landing roll. A related factor was the diverted attention.
Aircraft Information
Registered Owner (Historical)
Analysis
On July 12, 1997, approximately 1215 eastern daylight time, a Beech BE-35, N2738V, was substantially damage as it ran off the end of the runway during the landing roll out at the Weltzien Skypark Airport, Wadsworth, Ohio. The certificated private pilot/owner was not injured. Visual meteorological conditions prevailed and no flight plan was filed for the personal flight conducted under 14 CFR Part 91.
The pilot indicated that the night prior to the accident during a ground run-up, the engine was unable to accelerate above 2,000 rpm. The next morning after adjustments were made, the engine accelerated to its maximum rpm of 2,300 during a test run-up. The pilot stated that the pre-takeoff checks and the acceleration during takeoff felt normal and the engine rpm gauge indicated 2,300 rpm. Once airborne, the pilot reduced the manifold pressure and attempted to reduce the propeller rpm by turning the propeller control vernier knob. The pilot stated that "turning the vernier (knob) was inoperative. He had to pulled the propeller control knob out and kept his hand on it for the rest of the flight and landing."
The pilot returned to the airport and lowered the landing gear and flaps at 100 mph. He maintained 95-100 mph on short final, and thought he touched down in the first one-third of the runway. The pilot stated that he "started braking almost immediately but the airplane did not slow down as expected." The airplane departed the end of the runway, impacted a ditch, and came to rest in an upright position.
The pilot stated that he was distracted by the propeller control problem and did not remember to pull the throttle to the idle position after touch down. The pilot did not report any other problems, nor were any found with the airplane.
Data Source
Data provided by the National Transportation Safety Board (NTSB). For more information on this event, visit the NTSB Records Search website. NTSB# IAD97LA099