Thrush Aircraft INC S2R accident near Hebron, North Dakota, June 17, 2024
On June 17, 2024 at about 12:10 pm local time, a 2012 Thrush Aircraft INC S2R, registered N529KC, was substantially damaged in an accident during approach (VFR pattern downwind) near Hebron, North Dakota. It was an aerial application (crop spraying) flight under agricultural flying rules (Part 137). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
Foreign object debris in the Negative Torque Sensing (NTS) system check valve, which impeded the flow of oil to the NTS system and the propeller governor (PG) reset piston, resulting in a total loss of engine power and an off-airport forced landing. Contributing to the accident was the mechanic’s improper adjustment of the PG.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- June 17, 2024 · about 12:10 pm local time
- Place
- Hebron, North Dakota · map
- Type
- Accident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Thrush Aircraft INC S2R G10, built 2012 · all S2Rs on the register
- Registration
- N529KC · registry record · serial G10-173
- Damage
- Substantial damage
- Flight
- Aerial application (crop spraying) flight · agricultural flying rules (Part 137)
The NTSB's narrative final · quoted from the NTSB record
The airplane departed from the operator’s airstrip to apply a liquid chemical to a rural wheat field, in an area with rolling hills. After the completion of the A-B pass and during the descent of the C pass, the engine abruptly accelerated on its own. The pilot then decided to climb out of the field to gain some altitude and assess the situation. The pilot noticed that the exhaust gas temperature and the engine torque were both high. Due to the abrupt engine fluctuations and the abnormal engine indications, the pilot decided to return to the airstrip. While maneuvering the airplane for a left downwind leg to the turf runway, the engine lost all power. The pilot maneuvered the airplane for a forced landing and performed an emergency hopper dump. After the successful completion of the emergency hopper dump, the pilot performed an off-field landing on a rural dirt road. During the landing, the airplane departed the road and came to rest upright, partially in a grass ditch. The airplane sustained substantial damage to the rudder. Postaccident examination of the airframe revealed no preimpact anomalies that would have precluded normal operation. A computerized tomography (CT) examination of the propeller governor (PG) found no internal abnormalities or contamination. The PG was further examined at the manufacturer; visual examination revealed an unusually large offset field adjustment on the maximum and minimum stop settings of the propeller speed lever. Further investigation revealed that the speed setting lever had been re-indexed on the speed setting shaft spline by two spline tooth widths relative to the manufacturer’s original factory setting, which was an unapproved field adjustment that a mechanic previously performed. During the acceptance test procedure of the as-received PG, the speed limit settings were not within factory or operational limits. The PG was returned to factory settings by adjusting the speed adjusting set screws and the follow-on test found the PG within operational limits. Examination of the engine oil passages and the in-line fittings of the accessory gearbox found a small red piece of foreign object debris (FOD) within the barrel of the check valve, between the valve ball and seat. The FOD was consistent with the torque stripe paint material that was applied to many of the external air, oil, and fuel line connectors on the engine. The CT inspection of the check valve showed the ball was not properly seated. Given the size of the FOD, it would not have been able to flow past the oil screen in the PG mounting flange, and so was not introduced upstream of the oil screen or the PG. FOD clogging this orifice would prevent oil from being correctly ported downstream to both the Negative Torque Sensing (NTS) system and the reset piston within the PG; the lack of oil pressure available to the PG hydraulic reset piston would result in an increase to the PG governing setpoint. According to the engine manufacturer, this may result in a perceived shift in engine rpm that could be overcome by re-indexing the splined joint between the speed setting lever and the speed setting shaft by two spline tooth widths. It is likely that the FOD blocking the check valve orifice passed through the orifice during the flight, enabling oil pressure to be re-established to the PG reset piston. The sudden return of oil pressure at the PG reset piston would result in a decrease of the PG governing setpoint of 5-8% rpm and subsequently create an abnormal engine control system interaction with the fuel control unit (FCU), resulting in thrust fluctuations. The investigation was unable to determine how or when the FOD entered the PG oil system. Although torque stripe paint material is used to enhance the safety of external air, oil, and fuel line connectors on both turbine and reciprocating engines, it can also become a FOD hazard. Honeywell Aerospace Technologies Service Bulletin TPE331-72-2168 recommends the incorporation of a new check valve design, which relocates the orifice downstream of the check valve’s ball/seat and adds an integral filter screen contained in a flange with a diameter of 0.070 inches. Given the dimensions of the FOD recovered from the accident check valve, it is likely that the flow of oil would not have been completely blocked and oil pressure would have been maintained on the PG reset piston had the new check valve been installed, potentially mitigating the mechanic’s improper repair and adjustment of the PG speed lever.
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
- Loss of engine power (partial) during maneuvering (low-alt flying)
- Attempted remediation/recovery during enroute
- Loss of engine power (total) during approach (VFR pattern downwind) defining event
- Off-field or emergency landing during emergency descent
- Abnormal runway contact during landing (flare/touchdown)
- Runway excursion during landing (landing roll)
- Collision during takeoff/land during landing (landing roll)
- Landing gear collapse during landing (landing roll)
- Evacuation during post (impact)
The NTSB's findings
- Aircraft › Aircraft power plant › Engine (turbine/turboprop) › Oil system › Damaged/degraded
- Aircraft › Aircraft power plant › Engine (turbine/turboprop) › Oil system › Malfunction
- Aircraft › Aircraft power plant › Engine (turbine/turboprop) › (general) › Failure
- Environmental issues › Physical environment › Object/animal/substance › Debris/dirt/foreign object › Effect on equipment
- Environmental issues › Physical environment › Object/animal/substance › Debris/dirt/foreign object › Contributed to outcome
- Environmental issues › Physical environment › Object/animal/substance › Debris/dirt/foreign object › Unknown/Not determined
- Personnel issues › Action/decision › Action › Incorrect action selection › Maintenance personnel
Pilot
- Certificate: commercial pilot
- Ratings: single-engine land
- Flight time: 3,855 hours in all; 2,625 in this make and model; 75.7 in the last 90 days; 61.1 in the last 30 days; 3,810 as pilot in command
- Last flight review: March 20, 2023
- Medical certificate: Class 2 (without waivers/limitations)
- Seat: sngl
- Injury: no injuries
The aircraft
- Airframe total time: 2,184.2 hours
- Last inspection: 100-hour inspection, June 12, 2024; 0.8 hours since
- Maximum gross weight: 6,000 lb
- Seats: 1
- Landing gear: fixed
- Engine: Honeywell Aerospace Technologi TPE331-10-511 (turboprop); 20,023 hours total
- Operator: Aerial Crop Care CO
The flight
- Departed from: 6NA5 Hebron ND at 11:50 am
- Destination: 6NA5 Hebron ND
- Flight plan: none
Weather at the time
- Light: daylight
- Visibility: 10 statute miles
- Sky: overcast at 10,000 ft
- Temperature: 50°F (10°C), dew point 46°F (8°C)
- Altimeter: 29.86 inHg
- Observation at 6:55 am from KD57, 8 miles away
Weather report (METAR): KD57 171155Z AUTO 00000KT 10SM OVC100 10/08 A2986 RMK AO2
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Photographs from the investigation 8 pictures from the NTSB's docket, as the NTSB released them
Photograph 1 – Overall view of the accident site
Photograph 2 – View of the front of the airplane at the accident site
Photograph 3 – View of the right side of the airplane at the accident site
Photograph 4 – View of the left side of the airplane at the accident site
Photograph 5 – View of the airplane recovered to the operator’s hangar
Photograph 6 – View of the substantial damage sustained to the rudder
Photograph 7 – View of the engine being removed from the airframe
Photograph 8 – View of the engine removed from the airframeThe NTSB's photographs with the NTSB's captions, at screen size. Open a picture to see it full size or to report one that should not be shown.
Documents from the investigation the NTSB's docket: the evidence folder behind the report
20 documents, released by the NTSB on August 19, 2026. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
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.
