FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX83FVA01 · Eagle DW-1

14 Oct 1982 · NEAR BAKERSFIEL, CA, United States

Eagle Aircraft Eagle DW-1 · Accident: airframe, component or system failure while maneuvering

From SHATER, CA to SHATER, CA

Report a problem

Event

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

Eagle DW-1

Aircraft type
Eagle DW-1
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
N88126
Onboard fatalities
Unknown
Route
From SHATER, CATo SHATER, 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 137: Agricultural
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 · aerial application
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 › Diverted attention

Not plotted · Location withheld: coordinates are missing, conflicting, invalid, or have no accepted acquisition method. No substitute location has been invented.

NTSB narrative

DURING A TURN-AROUND WHILE SPRAYING A COTTON FIELD, THE AIRCRAFT STARTED ROLLING TO THE LEFT AND THE PILOT COULD NOT STOP IT. HE STATED THE LEFT SPOILER REMAINED DEPLOYED AND WOULD NOT CLOSE. HE FOUGHT THE ROLL UNTIL IT IMPACTED WITH THE GROUND. THE LEFT SPOILER WAS FOUND IN THE VERTICAL POSITION AND THE RIGHT SPOILER WAS FLUSH WITH THE WING SURFACE. DUE TO POOR ROLL RATE AND HIGH ASPECT RATIO, SPOILERS HAD BEEN ADDED TO THE LOWER WING. THEY CAN BE INDEPENDENTLY OPERATED FROM THE COCKPIT OR WORK IN CONJUNCTION WITH THE AILERONS. ACCORDING TO AN FAA ENGINEERING TEST PLT, THE SPOILERS HAVE LIMITED AUTHORITY, AND IF ONE IS MANUALLY DEPLOYED TO THE FULL UP POSITION IT CAN BE OVER- RIDDEN WITH OPPOSITE AILERON. THE PLT STATED THAT THIS WAS THE THIRD OR FOURTH TIME A SPOILER HAD STUCK OPEN. THE WING WAS CUT OPEN AND NO REASON FOR THE SPOILERS STICKING COULD BE FOUND.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record LAX83FVA01
Event ID
20020917X04823
Case number
LAX83FVA01
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. 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: c1accfc0d96b22ddb362cbef618181aac5a8e1cbb7fb962326a36b478b275a2e; retrieved 2026-09-21T18:05:16.798Z.