LAX90DVM03 · Illi THUNDER GULL THUNDER GU
Illi THUNDER GULL THUNDER GU · Accident: airframe, component or system failure while maneuvering
From Santa Margarita, CA (no airport) to 6L3 · CALIF VALLEY, CA
Event
- NTSB case
- LAX90DVM03
- 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
- 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
Illi THUNDER GULL THUNDER GU
- Aircraft type
- Illi THUNDER GULL
- 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
- N2223E
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Santa Margarita, CA (no airport)To 6L3 · CALIF VALLEY, 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
- Maneuvering
- 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
- Airframe, component or system failure
- 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 › Design stress limits of aircraft, exceeded
- Pilot in command › Impairment(drugs)
- Pilot in command › Judgment, poor
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
A WITNESS REPORTED THE AIRCRAFT WAS FLYING STRAIGHT AND LEVEL, THEN IT ENTERED AN ACCELERATING, DESCENDING, RIGHT TURN. THE WITNESS THEN SAW PART OF THE RIGHT WING SEPARATE FROM THE AIRCRAFT. A POST-ACCIDENT EXAMINTATION OF THE WRECKAGE DISCLOSED NO CONSTRUCTION, MATERIAL OR METALLURGICAL DEFECT. BASED ON THE COMPUTED GROSS WEIGHT, CENTER OF GRAVITY, AND TRIM POSTION AT THE TIME OF THE ACCIDENT, THE AIRCRAFT DESIGNER CALCULATED THE TRIM SPEED WAS 10 MPH OVER THE MAXIMUM DESIGNED VNE. TESTS OF THE PILOT'S BLOOD SHOWED A COCAINE LEVEL OF 2.2 MG/L AND BENZOYLECGONINE (METABOLITE OF COCAINE) AT 0.96 MG/L.
Probable cause
POOR JUDGEMENT OF THE PILOT FROM USE OF A DRUG (COCAINE), AND THE PILOT ALLOWING THE DESIGN STRESS LIMITS OF THE AIRCRAFT TO BE EXCEEDED, WHILE MANEUVERING, WHICH RESULTED IN OVERLOAD FAILURE OF THE WING SPAR & WING SEPARATION.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX90DVM03
- Event ID
- 20001212X24033
- Case number
- LAX90DVM03
- 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 1990-08-08.
- API snapshot SHA-256: a347f89cb13f4eb3d0fab9e663fb16267dc168b19299c75355f616a73a3d0688; retrieved 2026-09-21T02:23:19.597Z.