LAX92LA296 · Grumman AA5
Advanced Aero Dynamics & Struc Grumman AA5 · Accident: loss of engine power during landing
From Hollywood Burbank/Bob Hope Airport (BUR) to Mineta San Jose International Airport (SJC)
Event
- NTSB case
- LAX92LA296
- 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 AA5
- Aircraft type
- Grumman AA5
- 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
- N28410
- Operator
- Advanced Aero Dynamics & Struc
- Onboard fatalities
- Unknown
- Route
- From Hollywood Burbank/Bob Hope Airport (BUR), Burbank, CATo Mineta San Jose International Airport (SJC), San Jose, 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
- Landing
- 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
- Loss of engine power
- 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
- Reason for occurrence undetermined
- Terrain condition › None suitable
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
AFTER APPROXIMATELY ONE HOUR AND FIFTEEN MINUTES INTO A CROSS COUNTRY FLIGHT THE PILOT OBSERVED THE ENGINE OIL PRESSURE DECREASING. HE ELECTED TO MAKE A PRECAUTIONARY LANDING ON A HIGHWAY. WHEN THE AIRCRAFT TURNED ONTO THE FINAL APPROACH THE ENGINE LOST POWER AND THE AIRCRAFT'S RIGHT WING COLLIDED WITH A TREE. THE AIRCRAFT THEN STRUCK THE ROAD IN A NOSE-DOWN ATTITUDE, COLLAPSING THE NOSE AND LEFT MAIN LANDING GEARS. EXAMINATION OF THE ENGINE FAILED TO DISCLOSE ANY PREEXISTING MALFUNCTIONS OR FAILURES.
Probable cause
THE LOSS OF ENGINE POWER FOR UNDETERMINED REASONS AND THE LACK OF SUITABLE TERRAIN FOR A FORCED LANDING.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX92LA296
- Event ID
- 20001211X15191
- Case number
- LAX92LA296
- 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 1992-07-11.
- API snapshot SHA-256: d48377195452c53ae8d80cd2c09bc18f7e003ac8117c710ffb693edf19de390c; retrieved 2026-09-21T23:12:47.225Z.