WPR15LA167 · Beech F33A
Beech F33A · Accident: fuel starvation during initial climb
From Pierce County-Thun Field (PLU) to Pierce County-Thun Field (PLU)
Event
- NTSB case
- WPR15LA167
- 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 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
- N84MD
- Operator
- Clark Daniel W
- Onboard fatalities
- Unknown
- Route
- From Pierce County-Thun Field (PLU), Puyallup, WATo Pierce County-Thun Field (PLU), Puyallup, WA
- Aircraft age
- About 40 years (built 1975)
- 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
- Initial climb
- 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
- Fuel starvation
- 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 systems
- Aircraft › Fluids/miscellaneous hardware
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The private pilot was conducting the airplane's first flight after an annual inspection. On the morning of the accident, the pilot picked up the airplane and conducted a run-up, during which the engine lost power. The airplane was towed back to the maintenance shop, and a mechanic recommended that the pilot wait until a more detailed examination could be completed. The pilot downloaded the data from the airplane's engine data monitor and took it home to examine. After returning to the airport later that day, the pilot reported to the mechanic that he did not observe anything abnormal in the data, and he got back in the airplane to depart for the accident flight. The pilot reported that, about 350 ft above the ground during initial climb, the engine lost power with no abnormal noises or sounds, and he landed in a field. The airplane subsequently rolled down an embankment, the nosewheel collapsed, and the airplane then came to rest.
During a postaccident engine run, the airplane started without hesitation; however, it lost power after the fuel boost pump was turned off. Further examination revealed that the B-nut to the fuel pump inlet was loose. The B-nut was tightened, and the engine then started and operated up to about 2,100 rpm with no additional anomalies. Data from the engine's data management system were analyzed, and the data revealed seven separate data sessions on the day of the accident, six leading up to the accident session. Based on the evidence, it is likely that the mechanic did not properly tighten the B-nut to the fuel pump inlet during the annual inspection and that the loose B-nut at the fuel pump resulted in the airplane being starved of fuel without the assistance of the pump. The accident likely would have been avoided if the pilot had not attempted to take off with indications that the airplane was not operating normally.
Probable cause
A total loss of engine power due to fuel starvation as a result of a mechanic’s failure to properly tighten the B-nut to the fuel pump inlet during a recent annual inspection. Contributing to the accident was the pilot's decision to take off despite indications that the engine was not operating normally.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR15LA167
- Event ID
- 20150526X85029
- Case number
- WPR15LA167
- 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. 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: 0707f38bf8ed21f681c79b2424aff6ec247ec429835c9c9dec50822448e54306; retrieved 2026-09-16T02:21:10.934Z.