WPR10LA235
2010-05-02 · South Bend, Washington, United States · None · 1 aircraft · Status: Completed
Airport 2S9
Aircraft involved
Probable cause & findings
A loss of engine power during takeoff for undetermined reasons, which resulted in a runway overrun.
Factual narrative
On May 2, 2010, about 1600 Pacific daylight time, a Beech 35, N3174V, sustained substantial damage following a runway overrun at the Willapa Harbor Airport, South Bend (Raymond), Washington. The private pilot and passenger were not injured. The airplane was registered to Bayshore Realty and operated by the pilot as a personal flight under the provisions of 14 Code of Federal Regulations (CFR) Part 91. The cross-country flight departed Bremerton, Washington, at 1430 with a planned destination of Willapa Harbor. Visual meteorological conditions prevailed, and no flight plan had been filed for the visual flight rules (VFR) flight. In a written report submitted to the National Transportation Safety Board, the pilot reported that the winds were from the south and gusting during the approach to runway 29. He reported that his approach airspeed was "90" plus miles per hour (mph) on short final due to wind conditions. The pilot reported that the airplane floated about 10 to 15 feet above the ground before it touched down approximately halfway down the 3,005 foot, hard-surfaced runway. Shortly after the airplane touched down, the pilot aborted the landing and applied full power. The airplane became airborne and as it ascended through about 20 feet above ground, the engine lost power. The pilot reported that the airplane touched down a second time and subsequently overran the runway. The airplane sustained substantial damage to the fuselage, undercarriage and firewall. Following the accident, the airframe was disassembled and both wings were removed by recovery personnel to facilitate removal and storage of the airplane. On December 7, 2010, the engine was examined and functionally tested at AvTech Services, Kent, Washington. For the purposes of the test run an alternate fuel source, which consisted of an auxiliary fuel tank and supply fuel line, was used to deliver fuel to the engine. The supply fuel line was routed directly to the fuel selector valve. After numerous attempts, the engine was started and developed power between varied power settings from idle to full power; however, continuous operation for more than one to two minutes was not attained. The reason for the non-continuous engine operation was not determined. No additional anomalies were noted during the functional test and exam. The Federal Aviation Administration (FAA) Approved Flight Manual for the airplane indicated that the recommended landing approach speed for the accident airplane was 74 miles per hour (mph). The pilot established a higher-than-normal final approach speed due to gusting wind and subsequently touched down near the midpoint of the runway. Shortly after the airplane touched down, the pilot aborted the landing attempt and applied full engine power. The pilot reported that the airplane momentarily became airborne before losing engine power and settling back to the runway. The airplane subsequently overran the runway. Duringpostaccident examination the engine was started and developed power, operating normally between varied power settings from idle to full power. The engine could not maintain continuous operation and would experience a total loss of power after about one to two minutes. The reason for the non-continuous engine operation could not be determined. No other anomalies were noted during the functional test and exam. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
FAA avdata. C = Cause, F = Factor.
- C Not determined-Not determined-(general)-(general)-Unknown/Not determined - C
- C Aircraft-Aircraft power plant-Engine (reciprocating)-(general)-Not specified - C
Verbatim from NTSB's published report. Source file
NTSB_2010_WPR10LA235.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Search this event elsewhere
External sources are reported, not agency: signal that something happened, not fact about what happened.
- TallyAero Live Wire Aviation press
- NTSB CAROL Agency ↗
- NTSB Docket Agency ↗
- Aviation Safety Network Aviation press ↗
- Kathryn's Report Aviation press ↗
- Aviation Herald Aviation press ↗
- AVweb Aviation press ↗
- Pilots of America Community ↗
- Reddit /r/flying Community ↗
- FlightAware Aviation press ↗
- AOPA accident database Aviation press ↗
- Google News News ↗
- DuckDuckGo News ↗
Related research
Matched on aircraft type. All research papers
- Embry-Riddle Scholarly Commons 2025 · Journal article (JAAER) Editor's Note: Celebrating 35 Years of Scholarly Excellence
A letter from the editor, Dr. Dahai Liu, on the JAAER's 35th anniversary.
- NASA NTRS 2024 · Presentation Part 135 and Business Operator Low Altitude Events: An Analysis of ASRS Reports
This presentation provides an aviation SME's human factors analysis of selected Low Altitude and Controlled Flight Towards Terrain (CFTT) events involving Part 135 and business jet operators as report…
- NASA NTRS 2022 · Conference Paper The In-time Aviation Safety Management System Concept for Part 135 Operators
Transformations of the National Airspace System, such as envisioned with Advanced Air Mobility, will enable improvements for managing and assuring safety for Part 135 transportation of passengers and …
- Embry-Riddle Scholarly Commons 2022 · Journal article (JAAER) SMS for Part 135 Commuter and On-Demand Operations - The Practitioner’s Perspective
On May 15th, 2017, N452DA, a Learjet 35A operated by Trans-Pacific Air Charter, LLC, departed from Philadelphia to Teterboro, New Jersey (TEB) on a positioning flight under 14 Code of Federal Regulati…
- NTSB Aircraft Accident Reports 2021 · Accident report Crash of Atlas Air Flight 3591, Boeing 767-300 (N1217A)
Atlas Air 3591 crashed into Trinity Bay, Texas, February 23, 2019. Investigation of the in-flight loss-of-control crash of Atlas Air 3591 into Trinity Bay, Texas.
- Embry-Riddle Scholarly Commons 2020 · Journal article (IJAAA) Analysis of Part 135 Aircraft Accidents to Facilitate Flight Data Monitoring
The scheduled and on-demand air services with Title 14 Code of Federal Regulations (CFR) Part 135 certificate are operating with relatively less stringent safety program criteria compared to Part 121 …