FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR20LA311 · North American B25N

19 Sept 2020 · Stockton, CA, United States

PROAIR Holding North American B25N · Accident: loss of engine power (total) en route

From Nut Tree Airport (VCB) to Stockton, CA

Report a problem

Event

NTSB case
WPR20LA311
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
Event fatalities
Unknown
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

North American B25N

Aircraft type
North American B25
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
N7946C
Onboard fatalities
Unknown
Route
From Nut Tree Airport (VCB), Vacaville, CATo Stockton, CA
Aircraft age
About 76 years (built 1944)
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
En route
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 › Fluids/miscellaneous hardware
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

While the airplane was in cruise flight and being flown by the copilot, the left engine fuel pressure fluctuated, which was followed by a brief loss of engine power. Concerned that the airplane might have a failed engine-driven fuel pump, the pilot turned the boost pumps to high and asked the passenger (the airplane’s mechanic) to open the fuel cross-feed valve. As the airplane approached its intended destination, both fuel pressure needles began to fluctuate. The pilot assumed that fuel starvation to the engines was occurring and decided to make an off-airport landing to a field behind their airplane’s position due to residential areas located between the airplane’s location and the airport. The pilot stated that he took control of the airplane from the copilot and initiated a right turn toward the field, and that, shortly afterward, both engines lost total power. During the landing roll, the pilot observed a ditch in front of the airplane and was able to get the airplane airborne briefly to avoid the first ditch; however, he was not able to avoid a second, larger ditch. Subsequently, the airplane struck the second ditch, became airborne, and impacted the ground, which resulted in substantial damage to the fuselage.

Recovery company personnel reported that, during recovery of the wreckage, about 1 gallon of fuel was removed from the two forward and the two aft wing fuel tanks. Postaccident examination of the airplane revealed no evidence of any pre-existing anomalies that would have precluded normal operation of either engine except that all four main fuel tank fuel gauges displayed erroneous indications after each tank was filled with water. No leaks were observed throughout the fuel system. The airplane was last refueled on the day before the accident with 497.7 gallons. When the airplane was last refueled, the fuel tanks were reportedly filled to about 3 inches below the fuel filler neck. The investigation could not determine, based on the available evidence for this accident, how much of the airplane’s fuel load (maximum capacity was 670 gallons) the airplane had onboard after it was refueled.

Additionally, the pilot reported that he commonly used a fuel burn rate of 150 gallons per hour for flight planning purposes; that figure included takeoff fuel burn. Recorded automatic dependent surveillance-broadcast data showed that the airplane had flown for 4 hours 1 minute since refueling and included six takeoffs and five landings (but did not include taxi times). As part of the investigation, the pilot estimated that 485.9 gallons of fuel had been used since the last refueling. However, on the basis of the pilot’s initial planned fuel load and recorded flight times, the airplane would have used about 600 gallons of fuel. The pilot later submitted an estimated fuel burn for the flights since refueling of 485.9 gallons. The flight manual did not have fuel burn references for the exact power settings and altitudes flown; thus, the hourly fuel burn could not be determined.

The pilot, copilot, and passenger did not visually verify the fuel levels in all four main fuel tanks before the accident flight. The pilot also underestimated the amount of fuel that would be used for the planned flights. As a result, fuel exhaustion occurred, which led to a total loss of engine power.

Probable cause

A total loss of engine power due to fuel exhaustion. Contributing to the accident was the erroneous fuel gauge indications and inadequate preflight planning and inspection

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR20LA311
Event ID
20200920X41002
Case number
WPR20LA311
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: local date, investigation status, cause areas. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2020-09-20.
  • API snapshot SHA-256: 9abd56f51daf1f253d3729121c489cd86fbc9c9ef1af315e59015d43f0d6ce91; retrieved 2026-09-16T13:04:22.276Z.