LAX93LA216 · Grumman American AA5
Grumman American AA5 · Accident: in flight collision with object en route
From Mefford Field (TLR) to an unrecorded destination
Event
- NTSB case
- LAX93LA216
- 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 AA5
- Aircraft type
- Grumman American 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
- N9520L
- Operator
- Steven P. Haworth · private individual
- Onboard fatalities
- Unknown
- Route
- From Mefford Field (TLR), Tulare, CATo not recorded
- 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 · 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
- In flight collision with object
- 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
- Pilot in command › Impairment(alcohol)
- Pilot in command › Visual lookout, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE AIRPLANE COLLIDED WITH TRANSMISSION WIRES OVER A RIVER. WITNESSES REPORTED THAT THE AIRPLANE CAUGHT ON FIRE AFTER COLLIDING WITH THE WIRES. THE PILOT LANDED THE AIRPLANE IN AN OPEN FIELD, AND IT WAS CONSUMED BY THE FIRE. A DEPUTY SHERIFF INVESTIGATING THE ACCIDENT NOTED A HEAVY ODOR OF ALCOHOL ON THE PILOT'S BREATH. THE PILOT WAS GIVEN A FIELD SOBRIETY TEST AT THE SCENE OF THE ACCIDENT AND LATER AT THE JAIL. HE FAILED THESE TESTS, AND THEN REFUSED TO TAKE A CHEMICAL BLOOD ALCOHOL TEST. WITH THE PERMISSION OF THE DISTRICT ATTORNEY, BLOOD WAS FORCIBLY TAKEN FROM THE PILOT FOR A TOXICOLOGICAL EXAM. THE BLOOD SAMPLE WAS TAKEN ABOUT 2 HRS 35 MIN AFTER THE ACCIDENT. THE RESULTS OF THE TEST WERE POSITIVE WITH A BLOOD ALCOHOL LEVEL OF 0.12%.
Probable cause
THE PILOT'S FAILURE TO SEE AND AVOID THE WIRES DUE TO ALCOHOL IMPAIRMENT. A FACTOR WHICH CONTRIBUTED TO THE ACCIDENT WAS UNWARRANTED LOW FLYING OVER THE RIVER.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX93LA216
- Event ID
- 20001211X12429
- Case number
- LAX93LA216
- 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 1993-05-16.
- API snapshot SHA-256: 285aff28d3d55f21c4f4e4d2da5561d4d28f568419720959a78a1fa46b098871; retrieved 2026-09-23T02:05:51.119Z.