FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX99FA225 · Cessna 402A

23 Jun 1999 · Van Nuys, CA, United States

Balter Worldwide Cessna 402A · Accident: total loss of engine power (non-mechanical) on approach

From Laughlin Bullhead International Airport (IFP) to Van Nuys Airport (VNY)

Report a problem

Event

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

Cessna 402A

Aircraft type
Cessna 402
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
N186BA
Onboard fatalities
Unknown
Route
From Laughlin Bullhead International Airport (IFP), Bullhead City, AZTo Van Nuys Airport (VNY)
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
Approach · VFR pattern final
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 exhaustion
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 › Exhaustion
  • Pilot in command › Fuel consumption calculations, not performed
  • Pilot in command › Fuel management, improper
  • Pilot in command › Mixture, excessive
  • Pilot in command › Refueling, not performed

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

NTSB narrative

The airplane collided with two school buses during a forced landing on a city street. During a straight-in approach for landing, the pilot lost all power on his left engine. After switching to the left auxiliary tank the engine did not restart. About a minute later all power was lost on the right engine. No attempt was made to switch to the right auxiliary tank because the pilot felt the airplane was too low and he concentrated on making a forced landing on a city street directly in front of the airplane. After touchdown, the airplane's wing tip main fuel tanks collided with the front ends of two approaching school buses. The two main fuel tanks were ruptured in the accident and found empty. Only residual fuel was found in the lines, with 1 quart of fuel recovered from the left auxiliary tank and 4 gallons from the right auxiliary tank. Investigators could not determine the exact fuel load onboard before the first departure that morning; however, based on refueling records, the airplane would have had no less than 122 gallons. During the first leg of flight, a high cylinder head temperature reading led the pilot to make a precautionary landing at an airport just over halfway to the original destination; the total elapsed time at this landing was 1.3 hours. The pilot was then told to reposition the aircraft back to the point of departure. He said he relied on a preplanned flight plan provided by company dispatchers, and he did not recompute the fuel required for the return. No fuel was added before the return flight. The elapsed time on the return flight was 1.2 hours for a total of 2.5 hours. The pilot said that for both legs of the flight he set a fuel flow of 18 gallons per hour per engine (which is above the red line gage limit); the performance charts show that the proper fuel flow setting was 13.35 gallons per hour per engine. Even at the high fuel flow of 18 gph, investigators computed that the airplane should have had a minimum of 12 gallons at the time of the accident, and this fuel remains unaccounted for. The pilot said that at some point during the two legs he switched to his auxiliary tanks until the gauges read 2 and 5 gallons, and then switched back to his main tanks. He could not specifically recall how long he had been flying on the mains when he switched tanks, or on which leg the switch occurred. To avoid unwanted venting of fuel overboard, a specific fuel tank use sequence must be used. The engine driven fuel pumps supply 50 percent more fuel than is required to the metering valves for each engine, with the excess fuel returned to the corresponding main tank. The auxiliary tanks should not be selected until the main tanks have been used for at least 60 minutes so that the mains have room for the returned excess flow from the auxiliary tanks. No evidence of leakage or staining was found around the wing filler caps. Staining found on the pavement around both buses could not be differentiated between fuel and a fire suppressive agent. After the accident, both engines were started and test run with no anomalies noted.

Probable cause

The pilot's inadequate fuel management that resulted in fuel exhaustion and the subsequent collision with vehicles during a forced landing on a city street.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX99FA225
Event ID
20001212X19019
Case number
LAX99FA225
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: 4f10c509b207bf2d31ae95926fc4f12b5366ee5204604414d3fa7219773a6dbf; retrieved 2026-09-21T20:30:04.751Z.