Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

May 2, 2010 · Beech 35 · N3174V

South Bend, WA

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
May 2, 2010
Injury Outcomes
No injuries (2 uninjured)
Location
South Bend, WA
Aircraft
Beech 35
Tail Number
N3174V
Injuries
None
Aircraft Damage
Substantial
NTSB Number
WPR10LA235

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.

NTSB Probable Cause

A loss of engine power during takeoff for undetermined reasons, which resulted in a runway overrun.

Full 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).

Flight

Event TypeAccident
Event Time16:00 PDT
Nearest AirportWillapa Harbor Airport (0nm)
Runway29
Runway Length3000 ft
Runway Width52 ft
Flight Plan FiledNone
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftBeech 35
Tail NumberN3174V
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsCont Motor · E185 SERIES · Reciprocating · 205
Seats4

People & Injuries

Injury SummaryNo injuries (2 uninjured)
Fatal0
Serious0
Minor0
Uninjured2
Total2
Crew 1Age 67 · Third Class · None

Conditions

ConditionsVMC
LightDaylight
Wind12 kt, gusting 15 kt
Visibility10 sm
CeilingOvercast 1200 ft
Temperature / Dew Point48 / 0 C
Altimeter0
Weather SourcePILO

Appendix: Source Data