LAX01LA213 · Cessna 150E
Red Baron Air Cessna 150E · Accident: total loss of engine power (non-mechanical) while maneuvering
From Whiteman Airport (WHP) to Whiteman Airport (WHP)
Event
- NTSB case
- LAX01LA213
- 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
Cessna 150E
- Aircraft type
- Cessna 150
- 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
- N3937U
- Operator
- Red Baron Air
- Onboard fatalities
- Unknown
- Route
- From Whiteman Airport (WHP), Los Angeles, CATo Whiteman Airport (WHP), Los Angeles, 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
- 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 supply, inadequate
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
After waiting about 55 minutes for a fuel truck to service his airplane, the pilot noted that the airplane's fuel tank gauges registered 1/4-full, so he took off on the banner tow flight. Fuel exhaustion occurred about 26 minutes later. Unable to reach the nearest airport, the pilot made a forced landing on a hillside. A police officer examined the airplane and reported that no fuel was found in its tanks. The pilot indicated that no mechanical malfunction or failure had precipitated the loss of engine power. The pilot had about 4,000 hours of flight time, of which 1,100 hours were acquired flying the Cessna 150. He held a certified flight instructor certificate for airplanes, an instrument rating, and an airframe and engine powerplant certificate.
Probable cause
Fuel exhaustion while maneuvering during a banner tow flight due to an inadequate fuel supply. A factor was the pilot's improper preflight preparation.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX01LA213
- Event ID
- 20010706X01322
- Case number
- LAX01LA213
- 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: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2001-06-17.
- API snapshot SHA-256: 5279dc55ff9ea8a033fbfc881ad919ec211f8b7ef42e9a9fc74a0daf48f7de61; retrieved 2026-09-21T19:55:36.386Z.