WPR24FA123 · Ayres Corporation S2R-G10
Jones Aviation Ayres Corporation S2R-G10 · Accident: fuel exhaustion while maneuvering
From Alturas, CA to an unrecorded destination
Event
- NTSB case
- WPR24FA123
- 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
- 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-G10
- 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
- N40261
- Operator
- Jones Aviation
- Onboard fatalities
- Unknown
- Route
- From Alturas, CATo not recorded
- Aircraft age
- About 25 years (built 1999)
- 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 · low-altitude flying
- 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 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
- Aircraft › Fluids/miscellaneous hardware
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
On the morning of the accident, the pilot departed from the operator’s base and flew the airplane about 174 miles northeast, to an airstrip near a rice farm. About 1230, after performing multiple flights to drop wild rice in the paddies near the airstrip, the pilot asked the fuel truck operators to fuel the airplane until the tanks were 3/4 full and subsequently departed the airstrip to continue spreading rice. When the pilot returned to the airstrip about 1400, he said he was not feeling well and was going to apply one last load of rice before leaving work. The pilot declined to have more fuel added to the fuel tanks. The pilot was seen with his safety harnesses fastened when he last departed. About 1444, witnesses near the rice farm heard the airplane crash and saw it inverted and partially submerged in the rice paddy. When they opened the airplane’s canopy, they found the pilot unbuckled from the safety harness, unresponsive. Examination of the airplane revealed an unusable amount of fuel (less than 2 gallons) in the fuel system, and no fuel sheen was observed in the water. No preaccident mechanical failures or malfunctions that would have precluded normal operation were found. The propeller blade damage signatures at the accident site were consistent with low rotational energy at impact. The airplane’s fuel system was intact, and there was no evidence of fuel leakage. After the pilot departed the operator’s facility, he had texted the mechanic stating the airplane’s fuel gauge was inoperative and that the airplane’s fuel gauge was slower to respond to fuel quantity changes than other airplanes. The mechanic explained that the gauge did not read fuel quantities greater than 82 gallons per tank; additionally, the cockpit fuel gauge noted that fuel quantities above 82 gallons were “ungageable.” Postaccident testing of the airplane’s fuel gauge and level senders indicated that they were operating to the manufacturer’s specifications. Fuel consumption calculations indicate that, with the reported fuel load, the airplane would have had an endurance of 2.1 to 2.9 hours. Although the airplane sustained substantial damage, the accident appeared to be survivable. The pilot’s autopsy identified no obvious fatal traumatic injuries, and the cause of death was determined to be hypertensive and atherosclerotic cardiovascular disease. However, the accident circumstances provide no clear evidence of in-flight pilot incapacitation, and it is unlikely that the pilot’s cardiovascular disease contributed to the accident. Additionally, severe acute mental or physical stress may be a trigger for cardiac events in individuals with underlying heart disease. It is possible that the airplane’s impact with the water of the rice paddy, followed by it becoming partially submerged and inverted, could have resulted in such a cardiac event in the setting of the pilot’s preexisting heart disease. The lack of fuel at the accident site and onboard the airplane during postaccident examination is consistent with fuel exhaustion, which resulted in the airplane’s impact with terrain. Though the pilot reported he was feeling unwell in the hours before the accident, available evidence is insufficient to determine what specific symptoms he was experiencing, or whether his symptoms contributed to the accident.
Probable cause
The pilot’s failure to adequately monitor his fuel supply, resulting in fuel exhaustion, a total loss of engine power, and the airplane’s impact with terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR24FA123
- Event ID
- 20240409194065
- Case number
- WPR24FA123
- 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, cause areas. 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: a2a0b02f17ae245c6f3222d593d0d04599df32f557a000307428c631ce5ac3ca; retrieved 2026-09-15T08:12:30.668Z.