FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX99LA164 · Beech 36TC

25 Apr 1999 · Lake Elsinore, CA, United States

Beech 36TC · Accident: total loss of engine power (non-mechanical) en route

From Jacqueline Cochran Regional Airport (TRM) to Chino Airport (CNO)

Report a problem

Event

NTSB case
LAX99LA164
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
0
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 36TC

Aircraft type
Beechcraft 36
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
N36MN
Operator
Unknown
Onboard fatalities
Unknown
Route
From Jacqueline Cochran Regional Airport (TRM), Thermal, CATo Chino Airport (CNO), Chino, 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
En route · cruise
First occurrenceThe 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
Total loss of engine power (non-mechanical)
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
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

  • Fluid, fuel › Starvation
  • Pilot in command › Aircraft preflight, inadequate
  • Pilot in command › Fuel supply, not verified

Approximate · Estimated position: the centre of Lake Elsinore, CA, the place the record names. Not the accident site.

NTSB narrative

The pilot stated that the aircraft had been in a local paint shop for the past 60 days for repainting. This was the first flight after the aircraft was picked up. The pilot reported that he had not used a dipstick to accurately determine the fuel load on the airplane, but rather used a method relying on the gages and consumption calculations. On the morning of the accident, he decided to fly from his home base to an airport in the Southern California interior and did this using the right fuel tank. On engine start for the return leg, he selected the left tank and was en route when the engine smoothly quit. He switched fuel tanks, turned on the electric boost pump and attempted to obtain a restart, without success. As the aircraft descended, he selected a clear area on the shoulder of the interstate highway for a landing. Nearing touchdown, he had to maneuver to avoid a highway sign and the right wing contacted the back of a pickup truck. The pilot further reported that as the aircraft touched down, the engine restarted and went to full power. The aircraft was recovered without the necessity of disassembly or disturbance to any aircraft system. The fuel tanks and lines were intact with no evidence of leakage. One pint of fuel was drained from the left tank while the right tank contained 15 gallons. The fuel indicating system was examined and the right tank sending unit and cockpit gage was found to be accurate. The left tank sending unit and gage displayed erratic indications of quantity. On initial power up the left tank gage displayed 3/4 tank. Subsequent shutdowns and power ups of the system yielded tank quantity indications of 1/4, full, and 3/4 again. No discrepancies were noted with the engine.

Probable cause

Fuel starvation due to the pilot's inadequate preflight inspection procedures and his failure to accurately determine the amount of fuel onboard prior to departure. A factor in the accident was the erratic fuel quantity sensor in the left fuel tank.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX99LA164
Event ID
20001205X00508
Case number
LAX99LA164
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: 831a5071307d1d8ad2c125655cd15f36bb22052447c6efb8a202d55e7f41cd2a; retrieved 2026-09-22T15:25:00.546Z.