The U.S. aircraft register, updated daily
Accidents · NTSB CEN25LA297 · Preliminary: the investigation is not finished

Ayres Corporation S2R accident near Akron, Iowa, July 28, 2025

On July 28, 2025 at about 8:37 pm local time, a 1994 Ayres Corporation S2R, registered N524SL, was substantially damaged in an accident during maneuvering (low-alt flying) near Akron, Iowa. It was an aerial application (crop spraying) flight under agricultural flying rules (Part 137). 1 person was seriously injured. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The NTSB has not yet published a probable cause for this accident. Investigations usually take one to two years; this page updates when the final report is released.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
July 28, 2025 · about 8:37 pm local time
Place
Akron, Iowa · map
Type
Accident
Injuries
1 person was seriously injured.
Weather
visual conditions (good weather)
Aircraft
Ayres Corporation S2R T34, built 1994 · all S2Rs on the register
Registration
N524SL · registry record · serial T34203DC
Damage
Substantial damage
Flight
Aerial application (crop spraying) flight · agricultural flying rules (Part 137)

The NTSB's narrative preliminary · quoted from the NTSB record

On July 28, 2025, about 1537 central daylight time, an Ayres Corporation S2R-T34 airplane, N524SL, sustained substantial damage when it was involved in an accident near Akron, Iowa. The pilot sustained serious injuries. The airplane was operated as a Title 14 Code of Federal Regulations Part 137 agricultural flight. The purpose of the low-level aerial application flight was to apply liquid chemical to a field of corn in a rural area. The airplane departed from the Sioux County Regional Airport (SXK), Maurice, Iowa, about 1456. After the completion of the aerial application work, the intent was to return to SXK. At the time of departure, the airplane had about 175 gallons of Jet A fuel on board and about 422 gallons of a mixture of AccuDrop, Aproach Prima, and Lamda-CY AG in the hopper. When the airplane arrived at the field, the pilot maneuvered the airplane for two reconnaissance passes, to identify any obstacles, wires, and sensitive areas to avoid. After verifying the engine power settings, he began the aerial application work. After several spray passes, the pilot maneuvered the airplane to turn for another spray pass to the north, when the engine sustained a total loss of power. The pilot reported the total loss of engine power occurred about 70 ft above ground level, and the engine “sounded like it exploded.” Prior to the total loss of power, there were no indications of abnormal performance from the engine. The pilot immediately brought the airplane to a level attitude and began to troubleshoot the emergency. The pilot quickly scanned the cockpit instruments and observed the torque (TQ) indication was below 30 psi and the inter-turbine temperature (ITT) indication was well below 700° Celsius. The pilot pushed the propeller lever forward to obtain a response from power lever inputs. No response was received, so he pulled the propeller lever to the feather position, and he felt the airplane begin to glide. Directly in the airplane’s flight path was a house and a church, so the pilot decided not to perform an emergency hopper dump to prevent possible chemical exposure to any ground personnel. Additionally, beyond the house and church, the concern was that if an emergency hopper dump was performed, the resulting increase in altitude may cause the airplane to land near other homes, farm buildings, and wires on the other side of the field. The pilot reported the decision not to perform an emergency hopper dump was a calculated decision to avoid injury to ground personnel and to avoid damage to property. The pilot maneuvered the airplane to a nearby soybean field to perform the forced landing. The pilot was able to land the airplane to the field. During the landing roll, the main landing gear dug into the wet ground and the airplane nosed over. The pilot released himself from the 4-point restraint system he was utilizing and egressed from the inverted airplane via the fractured left window. The pilot then walked to a nearby home for assistance. The airplane sustained substantial damage to both wings, the fuselage, and the empennage. The airplane was recovered from the accident site, and it was transported to a secure location for future examination. The pilot was utilizing an airplane flight helmet with a visor, and he reported that the sun did not interfere with his vision during the forced landing. Additionally, he reported that he did not feel fatigued during the accident flight. Prior to the accident occurring, the pilot reported there were no known issues with the airplane. On May 15, 2025, at a total of 1,073.1 hours since overhaul, the engine had an annual inspection performed by a mechanic. On May 16, 2025, at a total of 13,268.4 airframe hours, the airframe had an annual inspection performed by a mechanic. The operator, Crop Dusters LLC, based at SXK, utilizes a fleet of Ayres Corporation S2R series airplanes for aerial application work. The airplane, known as a Turbo Thrush, was manufactured in 1994 and has a 500-gallon capacity hopper. The airplane is a dual cockpit configuration, with two tandem seats. The Federal Aviation Administration (FAA) Type Certificate for the airplane, A4SW, is currently held by Thrush Aircraft, LLC, Albany, Georgia. The airplane was equipped with a Pratt & Whitney Canada PT6A-34AG turboprop engine. The airplane was also equipped with a Hartzell Propeller HC-B4TN-3C/T10702NS four-blade controllable pitch aluminum propeller. The FAA-approved airplane flight manual discusses the indications of an engine flameout and states in part: The indications of an engine flameout will be a drop in the inter-turbine temperature, a drop in the torque pressure, and a drop in RPM. The flameout may result from the engine running out of fuel or possibly caused by an unstable engine operation. The calculated density altitude for the closest meteorological reporting station was 3,615 ft.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Loss of engine power (total) during maneuvering (low-alt flying) defining event

The aircraft

  • Seats: 2
  • Landing gear: fixed
  • Operator: Crop Dusters LLC

The flight

  • Departed from: SXK Maurice IA at 7:56 pm
  • Destination: SXK Maurice IA
  • Flight plan: none

Weather at the time

  • Light: daylight
  • Wind: from 200° at 8 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 90°F (32°C), dew point 79°F (26°C)
  • Altimeter: 30.02 inHg
  • Observation at 2:52 pm from KSUX, 27 miles away

Weather report (METAR): KSUX 281952Z 20008KT 10SM CLR 32/26 A3002 RMK AO2 SLP157 T03220256 $

Injuries

FatalSeriousMinorNone
Flight crew1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

The NTSB has not released the docket for this case yet. The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), is usually released when the investigation is nearly complete, and the list here is refreshed when it appears. Check at the NTSB.

Other NTSB records under N524SL the same tail number, which may have belonged to a different aircraft at the time

2015-07-09ERA15LA270 · accident near Climax, GA · substantial damage · no injuries

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.