NTSB CAROL · Event
Event WPR23FA122
Registry · N8424V
FAA Aircraft Registry record.
Make / Model
RANS S-2R
Year of manufacture
1976 · 47 years old at event
Engine
P&W R1340 SERIES (600 hp)
Seats / Engines
1 seats · 1 engine
Last airworthiness date
19760209
ADS-B equipped
Yes — Mode-S AB8A3F
Registrant of record
JONES AVIATION INC
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
The pilot’s failure to maintain clearance from powerlines while flying under multiple conductors during a low-altitude aerial application flight, which resulted in propeller contact with a powerline and a subsequent loss of control.
Factual narrative
HISTORY OF FLIGHTOn March 7, 2023, about 1611 Pacific standard time, a Rockwell International S-2R, N8424V, was substantially damaged when it was involved in an accident near Willows, California. The pilot was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 137 aerial application flight. According to the operator, the pilot was scheduled to spray fungicide over several orchards. Data retrieved from an onboard GPS aerial application guidance system showed that the airplane departed Willows/Glenn County Airport (WLW), Willows, California, about 0848 and sprayed 3 fields in about 5 hours. At 1509, after the pilot finished spraying a field, he flew to the accident almond orchard and performed an orbit of the field. The field was 1/2 mile square, and divided by 2 banks of parallel power transmission lines running north-south, and held by 3 equally spaced sets of 130 ft tall towers. The owner of the plot reported that he employs a ground crew to spray the trees that grow beneath the power lines. The pilot returned to WLW about 1519 and departed at 1541 for the almond orchard and began spraying at 1544. The airplane flew a racetrack pattern in a north-south direction over the field immediately west of the powerlines. During each pass over the field the airplane descended to between 130 ft agl and 140 ft agl, at speeds of about 160 mph. After he refilled the hopper again at 1549, the pilot departed at 1554 to continue spraying. He returned to WLW one more time at 1601 for about 4 minutes and departed for the almond orchard for the last time. The pilot flew the same racetrack pattern as he had previously. The pilot’s 2 final northerly passes over the field took place at 1609:30 and 1610:39 about 100 ft west of the bank of the powerlines at an altitude of 131 ft agl. The flight track ceased at 1611:33 about 0.6 nautical miles (nm) southwest of the accident site. A witness located about 0.5 nm northwest of the accident site reported that he observed the airplane make several passes in a racetrack pattern on a north/south heading directly over him about 25 minutes before the accident. The airplane left the area and then returned about 1610 and made additional passes. He heard a loud noise about 2 minutes after the last pass. Figure 1. GPS flight track with annotations and last data point before accident Figure 2. Diagram of parallel passes about 100 ft west of powerlines PERSONNEL INFORMATIONAlthough the pilot had completed a flight review 2 months before the accident, his paper logbook did not contain any recorded flights beyond 1999 and no additional pilot records were found. The operator reported that the pilot had been flying for about 8 hours when the accident occurred and that he had sprayed the accident field multiple times in the past. According to the pilot’s wife, she did not observe any unusual behavior or sleep habits from the accident pilot in the 72 hours before the accident. She noted that the accident took place during the agricultural “off season” and that the pilot had not been flying long hours. METEOROLOGICAL INFORMATIONThe reported sunset on the day of the accident was 1807 and dusk began at 1834. The sun’s position at the time of the accident was about 21° above the horizon on an azimuth of 244°. WRECKAGE AND IMPACT INFORMATIONThe airplane came to rest inverted in an almond orchard about 500 ft northeast of a powerline tower and was oriented on a heading of 038° magnetic and adjacent to a severed lower conductor (powerline). All the major structural components of the airplane were accounted for at the accident site. The debris field was marked by several broken tree branches about 50 ft southeast of the accident site. A ground scar about 5 ft in diameter was collocated with the main wreckage. Both ailerons and flaps remained attached to their respective wings, which were both attached to the fuselage. The right wing displayed a depression about 3 ft in diameter with accordion style deformation and tree remnants several feet outboard of the wing root. The left wing leading edge exhibited a depression about 10 ft from the wing root. A section of conductor, about 2 inches in diameter, was wrapped around the propeller hub (see Figure 3). The conductor line was traced through the left wing depression to the trees southeast of the accident site. The airplane’s first point of impact was the west inboard powerline about midspan between 2 towers about 500 ft southwest of the accident site. (See annotation on Figure 4, “East set of powerlines”.) According to the operator of the powerlines, the lowest conductor at the towers that held the powerline that was severed was about 75 ft agl at the tower and sagged down to 36 ft agl midspan. The powerlines were in a north-south configuration and were held by 130 ft tall towers that supported multiple powerlines at various heights. An identical set of powerlines, also in a north-south configuration, was located about 115 ft west of the first impact point. Figure 3. View of airplane at accident site from front with cable wrapped around propeller Figure 4. Powerlines and accident site facing south Postaccident examination of the airplane and engine revealed no preimpact mechanical malfunctions or anomalies that would have precluded normal operation. Continuity of the flight control and fuel systems were confirmed, and the auxiliary fuel boost pump functioned normally when tested. The propeller shaft exhibited rotational scoring consistent with engine operation at the time of impact. The propeller spinner dome exhibited braided scoring and cable notches in three of the propeller blade leading edges. Propeller blade 2 displayed a gouge in the trailing edge consistent with cable wrap damage. The propeller also exhibited rotational scoring and leading edge notches/cuts, consistent with an inflight impact of a cable as the propeller rotated. An impact signature noted on the internal surface of the piston corresponded to a 17.7° blade angle, consistent with a power condition in flight. The two dowel pin holes on the mounting flange appeared deformed in the direction of rotation. A counterweight impact mark in the spinner dome was measured at 17.4°, which corresponded with a blade angle of about 4° closer to flight idle and consistent with a lower power signature at the time of impact with terrain. The pilot departed on a routine agricultural flight to spray multiple orchards. Recorded onboard GPS data showed that after spraying three fields, he flew to an almond orchard where he made numerous north-to-south passes over the target area in a racetrack pattern at speeds of about 160 mph, and an altitude of about 135 ft above ground level (agl). Several seconds after he sprayed an area adjacent to a set of 130 ft tall power transmission lines that ran parallel to his flight pattern, he made one more lap in the pattern. The data ceased when the airplane was at the south end of the field while turning north, likely several seconds before impact. The airplane subsequently impacted a powerline and came to rest about 500 ft northeast of the point of initial impact, which was a powerline next to a tower. Postaccident examination revealed no preimpact mechanical anomalies or malfunctions with the airplane or engine that would have precluded normal operation. The propeller signatures indicated that the propeller was rotating at moderate to high power when it impacted the powerline. The powerline was found wrapped around at least one blade and the propeller hub. A witness recount suggests that the accident took place several seconds after the last flight data point. The pilot was familiar with this orchard and was likely not fatigued at the time. In addition, the position of the sun at the time of the accident would not have been a factor. Although a recount of the pilot’s flying habits indicated he was unlikely to have flown beneath the powerlines, the pilot struck the inside wire between two towers at about the lowest point, which suggests he flew under the powerlines. Thus, the accident was the result of the pilot’s failure to maintain clearance from powerlines while attempting to fly beneath multiple conductors during a low-altitude aerial application flight, which resulted in propeller contact with a powerline and a subsequent loss of control. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).
- — Environmental issues-Physical environment-Object/animal/substance-Wire-Effect on equipment
- — Personnel issues-Psychological-Attention/monitoring-Monitoring environment-Pilot
Verbatim from NTSB's published report. Source file
NTSB_2023_WPR23FA122.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (loss of control). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- Embry-Riddle Scholarly Commons 2025 · Journal article (JAAER)
A Scoping Review of Aviation Loss of Control Inflight Research
Loss of control – inflight (LOC-I) contributes to aircraft accidents at unacceptably high rates. Significant industry efforts and research have aimed to improve LOC-I prevention, detection, and recove…
- SKYbrary (Eurocontrol) 2024 · SKYbrary article
Loss of Control In-Flight (LOC-I) — SKYbrary Knowledge Base
SKYbrary comprehensive knowledge-base entry on Loss of Control In-Flight — definitions, contributing factors, accident case studies (Air France 447, Colgan 3407), and prevention strategies.
- NTSB Aircraft Accident Reports 2022 · Accident report
Loss of Control on Takeoff in Icing Conditions — Citation 560XL
Cessna Citation 560XL fatal takeoff icing accident, March 2018. Investigation of a Citation 560XL loss-of-control takeoff accident in icing conditions.
- Semantic Scholar 2021 · Article (Aviation)
ANALYSIS OF GENERAL AVIATION FIXED-WING AIRCRAFT ACCIDENTS INVOLVING INFLIGHT LOSS OF CONTROL USING A STATE-BASED APPROACH
Inflight loss of control (LOC-I) is a significant cause of General Aviation (GA) fixed-wing aircraft accidents. The United States National Transportation Safety Board’s database provides a rich source…
- NASA NTRS 2021 · Presentation
Use of Design of Experiments in Determining Neural Network Architectures for Loss of Control Detection
Abstract—We describe empirical methods for selecting a neural network architecture to implement belief state inference on generic commercial transport aircraft.
- NASA NTRS 2021 · Conference Paper
Use of Design of Experiments in Determining Neural Network Architectures for Loss of Control Detection
We describe empirical methods for selecting a neural network architecture to implement belief state inference on generic commercial transport aircraft.
Browse the full corpus — academia portal ↗