FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX03FA005 · Grumman AA-5A

12 Oct 2002 · Phoenix, AZ, United States

Grumman AA-5A · Accident: total loss of engine power (mechanical failure) en route

From Phoenix Deer Valley Airport (DVT) to UNKNOWN

Report a problem

Event

NTSB case
LAX03FA005
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
1 · 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

Grumman AA-5A

Aircraft type
Grumman AA-5
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
N9566U
Operator
Unknown
Onboard fatalities
Unknown
Route
From Phoenix Deer Valley Airport (DVT), Phoenix, AZTo UNKNOWN
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
En route · climb to cruise
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 (mechanical failure)
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
Wire, transmission
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

  • Engine assembly, bearing › Deteriorated
  • Engine assembly, bearing › Overtemperature
  • Lubricating system › Low pressure

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

NTSB narrative

Following a loss of engine power after takeoff, the airplane banked left, hit power lines, and went nose down vertically into a mobile home. The pilot departed downwind, and a few minutes later the pilot reported to the air traffic control tower that he was returning with a problem. The pilot made a second transmission, and said that he had no oil pressure. Then he transmitted that he was landing just west of a freeway near the airport. Witnesses along the flight path heard the engine backfire, and saw the propeller stopped at the 3-o'clock and 9-o'clock positions. An intense post crash fire consumed the airframe and severely damaged the engine, with most accessories and fluid lines destroyed. The top and bottom spark plug electrodes were circular, not mechanically damaged, and the gaps were similar. The magnetos could not be tested, and the magneto to engine timing could not be established. The steel quick oil drain was closed and the o-ring was in place. All oil lines, including the pressure line to the gauge, were accounted for and all oil line B-nuts on the accessory housing were secure. Fire consumed the oil cooler. The oil pump had metal material burnished and extruded at the drive gear thrust surface; however, there was no scoring on the internal housing, the gears were undamaged, and the pump drive meshed with the crankshaft interface. The main oil pressure screen was clean. None of the combustion chambers, valves, or pistons exhibited mechanical damage. The camshaft was intact, and each of the camshaft lobes appeared similar in shape. The crankshaft remained intact. The main bearings' tangs were undamaged, and the bearings were on their respective dowels. There was no discoloration, fretting, or mechanical damage to the bearing surface. All four connecting rods remained secure at each of their respective crankshaft journals and rotated freely on the crankshaft, but all had fore and aft movement as well as lateral play. All four journals exhibited discoloration. All connecting rod bearings exhibited some extrusion and metal transfer from the bearing to the journal. Cylinder No. 1 connecting rod bearing extruded the most; it had the most metal transfer. Cylinder No. 3 bearing sustained the next worse damage. Cylinders No. 1 and 4 were the least damaged. Investigators found no obvious obstructions or preimpact contaminates in the oil passages of the engine. Despite exhaustive examinations, the exact nature of the lubricating system problem and its underlying cause could not be determined.

Probable cause

failure of the lubricating system resulting in a total loss of engine power and an off airport forced landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX03FA005
Event ID
20021018X05337
Case number
LAX03FA005
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: dc7e83162b18ad9397d28fbaf54dc6905bf2877750441dccf9bc87d3fe5e4bf0; retrieved 2026-09-20T19:44:08.368Z.