FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX03LA238 · Piper PA-28-161

20 Jul 2003 · Lomita, CA, United States

Piper PA-28-161 · Accident: total loss of engine power (non-mechanical) during initial climb

From Zamperini Field (TOA) to Compton Woodley Airport (CPM)

Report a problem

Event

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

Piper PA-28-161

Aircraft type
Piper PA-28
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
N3091M
Operator
Henry B. Bunker · private individual
Onboard fatalities
Unknown
Route
From Zamperini Field (TOA), Torrance, CATo Compton Woodley Airport (CPM), Compton, 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
Initial climb
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
Stall/mush
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Pilot in command › Airspeed(vs), not maintained
  • Pilot in command › Carburetor heat, not used
  • Pilot in command › Stall/mush, inadvertent
  • Weather condition › Carburetor icing conditions

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

During climb out from an aborted precautionary landing after a partial loss of power, the pilot stalled the airplane and descended until impacting power lines, trees, and the ground. According to the pilot, prior to initiating the planned round-robin flight he had experienced a left magneto problem during the engine run-up procedure at the Whiteman Airport in Los Angeles. The pilot stated that he had "cleared the problem during the run-up..." and his takeoff from Whiteman was normal. No evidence of any engine problem was encountered during the flight to Torrance, whereupon the pilot landed without incident. However, the pilot reported to the local air traffic controller during his subsequent departure (initial climb) that he would like to turn around and land in the opposite direction to the departure runway. The pilot broadcast to the controller that he has "...got a little engine trouble here." The pilot reported that during the climb to about 700 feet above ground level, only partial engine power was attained. The controller responded by clearing the pilot to land on any runway and provided the local wind condition. Thereafter, the pilot reversed course. With a 10-knot tailwind, the pilot misjudged his downwind approach and landing on the mile-long runway. The pilot opined that he touched down too long to decelerate on the remaining available runway, so he responded by applying engine power to take off again. With extended wing flaps, the airplane became airborne. The pilot lost control of the airplane while he again reversed course to return to the airport. The airplane's stall warning horn activated, and the airplane buffeted and crashed while in an uncontrolled descent. During the subsequent engine examination, no evidence of any mechanical malfunction was found. At the time of the accident the Torrance airport METAR was reporting a temperature of 26 degrees Centigrade and dew point 21 degrees. With reference to a carburetor icing probability chart, the temperature and dew point falls into an area of the chart labeled moderate icing in cruise power or serious icing at glide power.

Probable cause

The partial loss of engine power due to carburetor icing and the pilot's failure to use carburetor heat. Also causal was the pilot's failure to attain and maintain an adequate airspeed during the aborted landing, which resulted in a stall/mush.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX03LA238
Event ID
20030724X01183
Case number
LAX03LA238
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, coordinates. 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: 36fe3e06decf4629f5a0e6d8f23dde7c342923f382c8aaee90d1d442699c16c6; retrieved 2026-09-21T19:24:58.349Z.