WPR13LA212 · Boeing A75N1
Boeing A75N1 · Accident: fuel related while maneuvering
From Petaluma, CA to Petaluma, CA
Event
- NTSB case
- WPR13LA212
- 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
Boeing A75N1
- Aircraft type
- Boeing A75
- 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
- N985SS
- Operator
- Bell Patrick C
- Onboard fatalities
- Unknown
- Route
- From Petaluma, CATo Petaluma, CA
- 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
- Maneuvering
- 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 related
- 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
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
While joining up in formation flight with a second airplane, the pilot reduced engine power to slow his airplane. When he subsequently tried to increase the engine power, he noticed no response from the engine. The pilot stated that the engine was still running; however, the adjustment of the throttle control and the electric fuel boost pump did not alter the engine's power setting. The pilot performed a forced landing to a vineyard, and the airplane nosed over during the landing roll. Postaccident examination of the engine revealed that the main fuel system screen contained a fuzzy, spongy material along with other debris. The throttle body screen also contained small debris particles. Debris was also found in fuel that was removed from the lower fuel tank. It is likely that the debris within the fuel system restricted fuel flow to the engine and limited the power output. The source of the debris was undetermined.
Probable cause
The partial loss of engine power due to fuel contamination and partially blocked fuel screens.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR13LA212
- Event ID
- 20130430X10448
- Case number
- WPR13LA212
- 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: d74752a424c31e48ff512db7caa22372c8d7739af30b1e1e05caf93f74dddd4b; retrieved 2026-09-15T21:22:39.319Z.