FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR17LA212 · Mooney M20E

22 Sept 2017 · Glendale, CA, United States

Mooney M20E · Accident: fuel exhaustion en route

From Redlands Municipal Airport (REI) to Hollywood Burbank/Bob Hope Airport (BUR)

Report a problem

Event

NTSB case
WPR17LA212
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

Mooney M20E

Aircraft type
Mooney M20
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
N34BE
Operator
Unknown
Onboard fatalities
Unknown
Route
From Redlands Municipal Airport (REI), Redlands, CATo Hollywood Burbank/Bob Hope Airport (BUR), Burbank, CA
Aircraft age
About 51 years (built 1966)
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 · descent
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 exhaustion
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Tree(s)
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

The private pilot and passenger had planned a round trip personal flight in the pilot's single-engine airplane. According to the pilot, he had wanted to service the airplane with fuel before the return leg, but he did not do so due to the passenger's desire to arrive home before a certain time. During the initial descent of the return leg, the engine lost total power. The pilot conducted a series of troubleshooting steps to no avail and then conducted a forced landing onto a residential street and struck trees.

Postaccident wreckage examination revealed that both fuel tanks were empty, and although the right fuel tank sustained a small breach during impact, there was no fuel odor at the accident site. A series of brown streaks were observed trailing from an area adjacent to the right-wing fuel sump drain. The sump valve sealant was badly degraded, and it is possible that a small fuel leak had developed at an undetermined time; however, blue streaking would have been more likely if a significant and recent fuel loss had occurred. Further examination revealed no leaks in the fuel supply system or engine. The engine tachometer was tested for accuracy, and no anomalies were noted. During an engine test run, the engine started normally and operated through its full speed range with no evidence of a mechanical anomaly.

The pilot had purchased the airplane 5 months before the accident and had been tracking fuel consumption since his purchase. He determined a representative fuel burn rate based on fuel purchases and engine tachometer hour-meter readings. The pilot reported that he did this because the fuel gauges were unreliable, and he did not possess a calibrated dipstick to measure the actual fuel quantities. Using his calculated fuel burn and tachometer reading method, the pilot estimated that he had enough fuel remaining to complete the flight and land with the Federal Aviation Administration-required 45-minute fuel reserve. However, he had performed multiple flights since the last fill up, which included one go-around and a full runway-length taxi earlier in the day. The total time for those flights was near the airplane's fuel endurance limit when measured by tachometer time, but the fuel consumption was likely higher due to the increased consumption demanded by the engine during the multiple takeoffs. It is likely that the pilot miscalculated the amount of fuel on board before the flight, which resulted in fuel exhaustion and a subsequent total loss of engine power.

Probable cause

The pilot’s inadequate preflight fuel planning and improper decision to not refuel before the flight, which resulted in fuel exhaustion and the subsequent total loss of engine power.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR17LA212
Event ID
20170923X20448
Case number
WPR17LA212
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. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2017-09-23.
  • API snapshot SHA-256: eab1a18bacfd4c1f9e5efca84fe64937b0390a8c2a8fd681ddd29bb13814b7f8; retrieved 2026-09-16T05:52:28.753Z.