FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR12LA367 · Aeronca 11AC

25 Aug 2012 · Pacoima, CA, United States Narrative disagrees

Aeronca 11AC · Accident: fuel related on approach

From Whiteman Airport (WHP) to Whiteman Airport (WHP)

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.

Event

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

Aeronca 11AC

Aircraft type
Aeronca 11
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
N9409E
Operator
Unknown
Onboard fatalities
Unknown
Route
From Whiteman Airport (WHP), Pacoima, CATo Whiteman Airport (WHP), Pacoima, 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
Approach · VFR pattern final
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
Fuel related
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

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

NTSB narrative

Witnesses reported that, while the airplane was on approach for landing, the engine lost power. During the forced landing, the right wing struck a power pole, and the airplane spun right and subsequently came to rest on top of a cinderblock wall. During on-site wreckage examination, a small amount of fuel was found in the fuel tanks and on the ground.

Postaccident examination of the engine and airframe revealed no evidence of mechanical malfunctions or failures that would have precluded normal operation. During postaccident examination of the fuel system, the main fuel tank was found void of fuel. The fuel sump was drained, and the recovered liquid appeared to be a mixture of aviation fuel and some type of solvent. No other usable amounts of fuel were recovered from the fuel system. It is likely that the combination of the low fuel level and fuel contamination led to the loss of engine power.

Probable cause

A total loss of engine power on approach for landing due to a combination of the low fuel level and fuel contamination.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR12LA367
Event ID
20120825X91616
Case number
WPR12LA367
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. 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: dd6c61d4b5212b7921873e71b8303ca045b8b1be02dc71051f6ece033ccac38a; retrieved 2026-09-15T19:30:15.510Z.