FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR14LA371 · Ayres Corporation S2R T34

9 Sept 2014 · Buckeye, AZ, United States Possible conflict

Farm Ag Enterprises Ayres Corporation S2R T34 · Accident: fuel contamination during takeoff

From Buckeye, AZ to Buckeye, AZ

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
WPR14LA371
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
Unknown
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

Ayres Corporation S2R T34

Aircraft type
Ayres S2
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
N3097F
Onboard fatalities
Unknown
Route
From Buckeye, AZTo Buckeye, AZ
Aircraft age
About 25 years (built 1989)
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
Takeoff
Defining eventThe 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
Fuel contamination
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

  • Aircraft › Fluids/miscellaneous hardware

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The operator reported that the commercial pilot had conducted agricultural flights in the airplane for about 2 to 3 hours earlier on the morning of the accident without problems. During the initial climb for the accident flight, about 30 ft above ground level, the engine lost partial power. Subsequently, the pilot conducted an emergency landing straight ahead, and the airplane descended and impacted a field, during which the wings and fuselage were substantially damaged.

Postaccident examination of the airplane revealed no evidence of any preimpact mechanical malfunctions or failures that would have precluded normal operation. Fuel samples were taken from the fuel tanks and the operator's fuel supply tank. Testing of the samples revealed that the fuel from both the airplane's fuel tanks and the operator's supply tank were essentially water. It is likely that the loss of engine power was due to water contamination of the fuel.

Probable cause

A partial loss of engine power due to water contamination of the fuel.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR14LA371
Event ID
20140909X92814
Case number
WPR14LA371
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, coordinates. 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: 906a2c53fc8ed8d545a174272140874eb767b60b66e5b0c9dc70dc55f7164049; retrieved 2026-09-16T01:44:19.239Z.