29 Jul 2023: BELL 206-L4

29 Jul 2023: BELL 206-L4 (N652HA) — Unknown operator

1 fatality • Springfield, OH, United States

Probable cause

The pilot’s failure to remain clear of powerlines during an agricultural spraying operation.

— NTSB Determination

Accident narrative

HISTORY OF FLIGHT On July 29, 2023, about 1206 eastern standard time, a Bell 206-L-4 helicopter, N652HA, was involved in an accident near Springfield, Ohio. The commercial pilot was fatally injured. The helicopter was operated as an agricultural spraying flight conducted under the provisions of Title 14 Code of Federal Regulations Part 137. The pilot departed an off-airport location about 1152 and flew eastbound toward Springfield to spray a cluster of corn fields south of Interstate 70. A ground crew was scheduled to meet the pilot at another off-field location later in the day. While driving to the scheduled rendezvous point, the ground crew was stopped in traffic on the interstate adjacent to where the pilot was spraying. A supervisor called the ground crew because he had noticed that the helicopter’s flight information had disappeared from a commercial flight tracking website. The ground crew tried to contact the pilot via radio and telephone, but there was no answer. The ground crew noticed that the reason for the traffic was due to a downed powerline and notified another company pilot who was operating in the area nearby to conduct an aerial search of the cornfield. The pilot flew to their location and confirmed the accident helicopter had impacted the cornfield south of the interstate near a set of powerlines. The helicopter came to rest in a cornfield about 150 ft east of a set of four high-tension powerlines that ran northeast-southwest through the cornfield and over Interstate 70. The middle two powerline wires, which were about 75-100 ft tall, were severed. The top and bottom wires were not damaged. A review of ADS–B data revealed the helicopter made an initial pass over the cornfield on an easterly heading. It crossed over the powerlines, then made a right turn and flew northeast along the length of the powerlines. The helicopter made several east-west passes over the cornfield (and powerlines) before the data ended at 1206:39. At that time, the helicopter was on an easterly track at an altitude of 1,079 ft msl, or about 34 ft agl, about .26 miles west of the powerlines (see figure 1). Figure 1. ADS-B track of the helicopter’s flight path The helicopter was also equipped with an AG-Nav GUIA Platinum console. The AG-Nav device recorded the helicopter’s flight track and when the sprayer was turned on and off. A review of the flight data downloaded from the device revealed the last data point was recorded at 1206:26 when the helicopter was in its last turn to the east before it impacted the powerline wires. At that time, the sprayer was turned off. PILOT INFORMATION The pilot held a commercial pilot certificate for rotorcraft-helicopter. His last FAA second-class medical certificate was issued on April 8, 2023. According to the operator, the pilot had accrued a total of about 5,166 flight hours, of which 400 hours were in the same make/model as the accident helicopter. METEOROLOGICAL INFORMATION The weather reported at Springfield/Beckley Municipal Airport (SGH), about 10 miles southwest of the accident site, at 1133, was wind from 280 degrees at 13 knots gusting to 19 knots. The visibility was statute 10 miles with broken clouds at 2,800 ft. The temperature was 26 degrees C; the dewpoint was 20 degrees C; and the barometric altimeter setting was 29.99 inches of mercury. WRECKAGE INFORMATION The helicopter came to rest on its right side oriented on a heading of about 360° and at an approximate field elevation of 1,045 ft msl. All major components of the helicopter were accounted for at the accident site. Pieces of the helicopter’s spray boom and upper windshield were found along the wreckage path. The tail boom had separated near the aft portion of the fuselage and was found forward of the main wreckage. A 3-ft section of both main rotor blades remained attached to the main rotor mast. The remainder portion of the main rotor blades were found co-located with the fuselage. The main rotor blades exhibited a variety of gouges, knicks, and creases. The helicopter’s bottom wire strike protection unit was largely free from impact damage and was free from scraping. The top wire strike protection unit was bent over to the left. There were some areas of scraping observed. Both skids remained attached to the fuselage and sustained impact related damage. Several scratches and gouges were observed at multiple locations along the fuselage and skids. Scratching was observed on the main rotor mast. The right cyclic remained attached; the left cyclic was not installed. When the cyclic was moved by hand in all directions, applicable push rod linkage movement was observed at the main rotor mast. The tail rotor pedals remained intact. When they were moved by hand, the respective push rods moved at the tail boom area. The collective had broken from its attachment area consistent with impact damage. When a rod was re-inserted at the collective attachment area, and moved by hand, movement was observed at the swashplate. The tail rotor drive shaft was broken consistent with impact. The fractured section near the engine was pulled aft from its gear attachment area and impact damage was noted along the tail rotor drive shaft. Within the tail boom section that had separated, control continuity and drive shaft continuity was observed to the tail rotor. The tail rotor blades remained attached and displayed minimal impact damage. The fuel tank was intact, and a significant amount of fuel remained in the tank. A fuel sample showed the fuel was absent of debris and water. No mechanical deficiencies or malfunctions were observed that would have precluded normal operation of the helicopter at the time of the accident. MEDICAL AND PATHOLOGICAL INFORMATION An autopsy on the pilot was conducted by the Montgomery County Coroner’s Office. The cause of death was determined to be “multiple blunt force injuries.” Toxicology testing completed by the FAA’s Toxicology Laboratory was negative for all specimens tested.

Contributing factors

  • Pilot
  • Altitude — Not attained/maintained
  • Response/compensation

Conditions

Weather
VMC, wind 280/13kt, vis 10sm

Loading the flight search…

What you can do on Flight Finder

  • Search flights between any two airports with live fares.
  • By aircraft — pick a plane model (e.g. Boeing 787, Airbus A350) and see every route it flies from your origin.
  • Route map — click any airport worldwide to explore its destinations, or draw a radius to find nearby airports.
  • Global aviation safety — aviation accident database, 5,200+ records since 1980, with map and rankings by aircraft and operator.
  • NTSB safety feed — recent U.S. aviation accidents and incidents from the official NTSB CAROL database, updated daily.

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.