NTSB CAROL · Event
Event IAD97LA099
Aircraft involved
Probable cause & findings
The pilot's failure to retard the engine throttle to idle during the landing roll. A related factor was the diverted attention.
Factual narrative
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. The day prior, the engine would only accelerate to 2,000 rpm. After some adjustments, the engine attained the manufacturer's maximum rpm of 2,300. The pilot stated that there were no indications of any malfunctions during the engine run up and the acceleration during take off felt normal. Once airborne, the pilot was unable to reduce the propeller rpm by turning the propeller control knob. He stated that the propeller control knob was pulled out for the remainder of the flight and landing. Maintaining 95-100 mph on short final, the pilot stated that he touched down about one-third of the way down the runway. The pilot applied brakes immediately, but the airplane did not slow down and continued off the end of the runway into a ditch. The pilot stated that the propeller control problem distracted him and that he did not pull the throttle to the idle position. No other mechanical problems were found with the airplane. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_1997_IAD97LA099.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.