MIA95LA233 · Air Tractor 301
Air Tractor 301 · Accident: total loss of engine power (non-mechanical) while maneuvering
From Everett-Stewart Regional Airport (UCY) to an unrecorded destination
Event
- NTSB case
- MIA95LA233
- 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 301
- Aircraft type
- Air Tractor 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
- N5095S
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Everett-Stewart Regional Airport (UCY), Union City, TNTo 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
- Total loss of engine power (non-mechanical)
- 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
- Fuel exhaustion
- 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 › Fuel management, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT WAS MANEUVERING ON A SWATH RUN AT ABOUT 100 TO 140 FEET AGL WHEN THE AIRPLANE EXPERIENCED A TOTAL LOSS OF ENGINE POWER. DURING THE FORCED LANDING THE AIRPLANE COLLIDED WITH TREES AND CRASHED IN A CORN FIELD. BEFORE THE FLIGHT THIRTY-FIVE GALLONS OF FUEL WAS ADDED TO THE LEFT FUEL TANK. NO FUEL WAS ADDED TO THE RIGHT FUEL TANK. THE AIRPLANE FLEW 25 MINUTES, LANDED, DEPARTED 5 MINUTES LATER, AND FLEW AN ADDITIONAL 20 MINUTES BEFORE THE ENGINE QUIT. EXAMINATION OF THE ENGINE ASSEMBLY AND ACCESSORIES BY THE FAA REVEALED NO EVIDENCE OF A PRECRASH FAILURE OR MALFUNCTION. FOUR OR FIVE DROPS OF FUEL WAS PRESENT IN THE CARBURETOR BOWL. NO FUEL WAS PRESENT IN THE ENGINE DRIVEN FUEL PUMP, AIRFRAME FUEL VALVE, FUEL MANIFOLD OR WOBBLE PUMP.
Probable cause
THE PILOT-IN-COMMAND'S FAILURE TO PROPERLY MANAGE THE FUEL REQUIRED FOR THE FLIGHT, RESULTING IN A TOTAL LOSS OF ENGINE POWER DUE TO FUEL EXHAUSTION AND SUBSEQUENT IN FLIGHT COLLISION WITH TREES AND TERRAIN.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA95LA233
- Event ID
- 20001207X04553
- Case number
- MIA95LA233
- 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: 43b091d949477883596b015216d1f15cf43c240d7ceae1d0df4b2d1767b68958; retrieved 2026-09-22T23:13:59.584Z.