FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX89DVA10 · Air Tractor AT-301

13 Sept 1989 · Mendota, CA, United States

Air Tractor AT-301 · Accident: loss of control in flight while maneuvering

From Mendota, CA to an unrecorded destination

Report a problem

Event

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

Air Tractor AT-301

Aircraft type
Air Tractor AT-301
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
N8578S
Operator
Unknown
Onboard fatalities
Unknown
Route
From Mendota, 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 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
Loss of control in flight
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
Stall/mush
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

  • Pilot in command › Airspeed(vso), not identified
  • Pilot in command › Stall/mush, not corrected

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

REPORTEDLY, THE AIRCRAFT SETTLED DOWNWARD AS IT WAS SLOWED TO BEGIN A SPRAY RUN. THE PILOT ADDED FULL THROTTLE AND JETTISONED THE HOPPER CONTENTS BEFORE THE AIRCRAFT COLLIDED WITH THE GROUND. INSPECTION OF THE STALL WARNING SYSTEM REVEALED THE STALL WARNING WAS NOT CONNECTED. THE ENGINE HAD BEEN OPERATING WITH AUTOMOTIVE FUEL. THERE WERE NO MECHANICAL MALFUNCTIONS FOUND WITH THE AIRCRAFT OR ENGINE PRIOR TO THE ACCIDENT SEQUENCE.

Probable cause

A LOSS OF AIRCRAFT CONTROL BY THE PILOT WHEN HE SLOWED THE AIRCRAFT TO BEGIN A SPRAY RUN. CONTRIBUTING TO THE LOSS OF CONTROL WAS THE INOPERATIVE STALL WARNING SYSTEM.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX89DVA10
Event ID
20001213X29393
Case number
LAX89DVA10
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: 3d845efe80d1373357279bceb886dacc35298e0f7d7a83f87e3f0cbe9f4eaa18; retrieved 2026-09-23T07:09:54.852Z.