FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX89LA084 · Grumman American AA-1B

14 Jan 1989 · WESTLAKE, CA, United States

Grumman American AA-1B · Accident: total loss of engine power (non-mechanical) on approach

From Fallbrook Community Airpark (L18) to Camarillo International Airport (CMA)

Report a problem

Event

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

Grumman American AA-1B

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
N7174L
Operator
Unknown
Onboard fatalities
Unknown
Route
From Fallbrook Community Airpark (L18), Fallbrook, CATo Camarillo International Airport (CMA), Camarillo, 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
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; Utility pole
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

  • Fluid, fuel › Exhaustion
  • Pilot in command › Planning/decision, improper

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

NTSB narrative

BEFORE REACHING THE DESTINATION ARPT, THE ENG LOST POWER. THE PLT ATTEMPTED TO RESTART THE ENG, BUT WAS UNABLE. SHE MANEUVERED TO LAND ON A ROADWAY & REMAINED OVER THE MEDIAN AS LONG AS POSSIBLE TO AVOID VEHICLES. DRG THE LANDING, THE RIGHT WING HIT A UTILITY POLE NEXT TO THE CURB OF THE ROADWAY & THE WING WAS TORN OFF THE ACFT. THE ACFT THEN WENT DOWN AN EMBANKMENT & CAME TO REST INVERTED. AFTER THE ACDNT, THE PLT RPRTD THE ACFT HAD RUN OUT OF FUEL, WHILE THE GAUGE OF THE FULLEST TANK WAS INDICATING 1/4 FULL.

Probable cause

IMPROPER PLANNING AND DECISION BY THE PILOT WHICH RESULTED IN FUEL EXHAUSTION. CONTRIBUTING FACTORS WERE: FAULTY FUEL INDICATION, UTILITY POLE & UNEVEN TERRAIN.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX89LA084
Event ID
20001213X27609
Case number
LAX89LA084
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. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 1989-01-15.
  • API snapshot SHA-256: b32ff0a3acb10c56a4368aa859cdbe41083659335d4dd60a0de98cae848bd5e3; retrieved 2026-09-22T00:18:33.175Z.