FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR21LA104 · Cessna 150 F

4 Feb 2021 · Riverside, CA, United States

Cessna 150 F · Accident: loss of engine power (total) on approach

Report a problem

Event

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

Cessna 150 F

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
N8107S
Operator
Unknown
Onboard fatalities
Unknown
Route
From not recordedTo not recorded
Aircraft age
About 56 years (built 1965)
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 go-around
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)
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 › Task performance

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

NTSB narrative

Toward the end of a banner-tow operation, the pilot made an approach to the runway and released the banner over the runway to prepare for landing. After releasing the banner, the pilot climbed the airplane to the traffic pattern altitude. While on final approach, she performed a go-around due to “extreme wind shear.” During climbout, the pilot made a left turn to the crosswind leg of the traffic pattern, and the engine lost partial power. She continued the left turn and turned back to the runway, intending to complete a forced landing. However, the pilot reported that a “strong and gusty” tailwind existed, and that the airplane’s speed was too fast to safely land, so she aborted the landing. During the climb with partial engine power, the pilot made a 180° turn to the right with the intention of landing on the runway, but the engine lost total power halfway through the right turn. The airplane’s altitude during the right turn was insufficient for the pilot to reach the runway, so she made a forced landing onto a road located about 800 ft southeast of the runway threshold. During the descent, the elevator collided with trees, and the airplane landed upright on the asphalt surface. Subsequently, the nose landing gear collapsed, and the right wing collided with two cars that were parked on the right side of the road. A postaccident examination of the airplane found the fuel selector in the OFF position. Examination of the fuel system revealed that the left and right wing fuel tanks and the auxiliary fuel tank were intact and not breached. The left wing fuel tank was empty, and the right wing fuel tank contained less than 1 gallon of fuel. The auxiliary fuel tank contained about 4 gallons of fuel, but the pilot did not use fuel from the auxiliary tank because she thought that the wing tanks contained about 10 to 12 gallons of fuel. Examination of the engine revealed no preimpact anomalies or malfunctions that would have precluded normal operation, and the engine operated through various speeds during an engine test run. The accident pilot did not request nor received weather information from Leidos Flight Service, or the commercial vendor foreflight. There was no record of the accident pilot receiving or retrieving any other weather information before or during the accident flight. A weather study revealed that at about the time of the accident winds in the vicinity of the accident were gusting to 21 knots at the accident time. The wind flow down the terrain helped to induce areas of low-level wind shear (LLWS) along with up and downdrafts. During a postaccident interview, the owner of the airplane reported that, given his experience flying the accident airplane, the fuel consumption rate during banner-tow operations was about 13 gallons per hour with high-wind conditions, such as those that occurred during the accident flight, because of the higher engine rpm during cruise flight. However, the pilot assumed a fuel consumption rate of 10 gallons per hour, which was below the fuel consumption rate that the owner experienced during banner-tow operations in cruise flight with calm wind (11 gallons per hour). The weather study for this accident revealed that, about the time of the accident, the wind near the accident site was gusting to 21 knots. The wind flow down the terrain would have helped to induce areas of low-level windshear along with up- and downdrafts. One pilot report indicated that severe turbulence was occurring at 4,000 ft near the accident site at the accident time. The weather conditions that occurred during the accident flight were addressed by the National Weather Service forecast conditions. However, the accident pilot did not request or receive weather information from Leidos Flight Service or Foreflight. Also, no evidence indicated that the accident pilot retrieved any other weather information before or during the accident flight. Thus, the pilot likely did not plan for windshear and turbulence during the flight, which likely created a higher pilot workload, increased fuel consumption during the flight, and resulted in fuel starvation and the total loss of engine power.

Probable cause

Fuel starvation due to the pilot’s inadequate weather and fuel planning, which resulted in a total loss of engine power.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR21LA104
Event ID
20210204102603
Case number
WPR21LA104
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: investigation status, cause areas. 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: 7f00d273f7c8bf4a2e3847c2b6c88079664760d46326f805fb005d6e37840caf; retrieved 2026-09-16T13:36:46.132Z.