WPR19LA200 · Beech 33 F33A
Beech 33 F33A · Accident: powerplant system/component malfunction/failure during landing
From Jefferson County International Airport (0S9) to Parkside Airpark (WA87)
Event
- NTSB case
- WPR19LA200
- 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 33 F33A
- Aircraft type
- Beechcraft 33
- 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
- N873BC
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Jefferson County International Airport (0S9), Port Townsend, WATo Parkside Airpark (WA87), Battleground, WA
- Aircraft age
- About 31 years (built 1988)
- 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
- Landing · landing roll
- 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
- Powerplant system/component malfunction/failure
- 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
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 selected the most favorable runway and flew his approach to land at his home airport. The airplane touched down normally near the runway threshold at the pilot's normal landing speed. Based on landing distance calculations, he should have been able to stop the airplane before the end of the runway. However, it was not until the airplane was about midfield that the pilot realized the airplane was not decelerating. At this point, the pilot attempted to reduce power further by twisting the knob of the throttle control counterclockwise, but the engine power did not decrease. As the airplane rapidly approached the end of the runway, the pilot used the mixture control to shut down the engine, but the airplane overran the runway end and the left wing impacted a pole, which resulted in substantial damage. Postaccident examination of the airplane revealed no anomalies with the engine and most of the engine controls except for the throttle control. During engine runs, the throttle knob push button became intermittently stuck in a depressed position. Normally, turning the throttle knob counterclockwise from this position would reduce power; however, during the postaccident engine runs, a corresponding minor increase in power was observed. Although disassembly of the throttle mechanism revealed a loose nut in the throttle control assembly, it likely did not contribute to the throttle failure, as the nut would not have affected the knob’s use to make power adjustments. Further, the throttle control could still be manipulated by rotating the throttle knob during the postaccident engine run. Based on the pilot's practices, it is likely that the pushbutton became partially depressed when the pilot reduced the engine power to descend while inbound to his home airport. When the pilot realized the airplane had not decelerated and attempted to make a minor power adjustment by rotating the throttle knob counterclockwise, the throttle control failed, and the pilot either experienced sustained or a subtle increase in engine power, which resulted in a runway overrun and impact with an obstacle. The reason for the failure of the throttle control assembly could not be determined based on available evidence.
Probable cause
A failure of the throttle control assembly for reasons that could not be determined based on available evidence, which resulted in a runway overrun and impact with an obstacle.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR19LA200
- Event ID
- 20190723X50222
- Case number
- WPR19LA200
- 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: a7c53dbe3d93fac856c3d7717f6c7f6d76d4f489509dadbdca1353d10c8bd9b0; retrieved 2026-09-16T09:31:24.135Z.