WPR10LA235 · Beech 35
Beech 35 · Accident: loss of engine power (total) during takeoff
From Bremerton National Airport (PWT) to Willapa Harbor Airport (2S9)
Event
- NTSB case
- WPR10LA235
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Beech 35
- Aircraft type
- Beechcraft 35
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N3174V
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Bremerton National Airport (PWT), Bremerton, WATo Willapa Harbor Airport (2S9), South Bend, WA
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Takeoff
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Loss of engine power (total)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft power plant
- Not determined › Not determined
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
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.
Probable cause
A loss of engine power during takeoff for undetermined reasons, which resulted in a runway overrun.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR10LA235
- Event ID
- 20100510X43553
- Case number
- WPR10LA235
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: dd47abab52f6b1c6dc90811da442fe2033c7c9a4b20bd8a101dae914abf20215; retrieved 2026-09-15T14:03:12.318Z.