18 Jun 2020: Robinson R66 No Series — KRITTER CROPDUSTING INC

18 Jun 2020: Robinson R66 No Series (N4QW) — KRITTER CROPDUSTING INC

1 fatality • Pikeville, NC, United States

Probable cause

The pilot’s failure to see and avoid a small diameter wire during low altitude agricultural spraying operations. Contributing to the accident was the pilot’s insufficient property survey.

— NTSB Determination

Accident narrative

On June 18, 2020, at 1700 eastern daylight time, a Robinson R66 helicopter, N4QW, was substantially damaged when it was involved in an accident near Pikeville, North Carolina. The pilot was fatally injured. The helicopter was being operated as a Title 14 Code of Federal Regulations Part 137 aerial application flight.

According to company personnel familiar with the operation, this was the first time the pilot had sprayed the farm field, and the pilot had not received any information about hazards in the area to be sprayed. The pilot arrived at the field about 3 hours later than planned. Prior to the application of the insecticide, the pilot performed two circular passes over the field to look for any hazards or obstructions; he then landed, and the ground crew loaded the insecticide into the hopper. Shortly after takeoff, the pilot began spraying operations. The helicopter was flying over the field during the spraying operation when an eyewitness heard a "popping" sound and saw the helicopter’s sudden descent and impact with the terrain.

The helicopter impacted a non-energized wire, also known as a "dove wire" that was used for hunting. The wire was mounted about 30 feet up a 40 ft pole that also contained a hunting stand and was stretched across the width of the corn field (250 ft) from west to east (See figure 1). The wire was connected to a tree on the east side of field, perpendicular to the helicopter’s flightpath. The wire had no markings and was 5/16 inch thick. According to the farmer, the wire was installed at least 20 years earlier and was installed high enough for a tractor or combine to get underneath it during harvest.

Figure 1 - Accident site overview of pole, wire, and wreckage location.

The wreckage path was oriented on a heading of about 030° magnetic, and the distance from the wire impact to the final wreckage location was about 275 ft. The tail rotor empennage separated about 2 ft aft of the rotating beacon light and was found in a nearby irrigation ditch. The tail rotor assembly and blades separated from the empennage. All major components of the helicopter were accounted for at the accident site. Both main rotor blades remained attached to the hub. About 20 ft of 5/16 inch diameter braided steel wire was wrapped around the blade pitch change horns, swashplate, pitch links, rotor hub, and both rotor blades.

In addition, there were tears and scuff mark damage to the blades that was consistent with contact with the wire. Cyclic and collective control continuity was confirmed. Tail rotor control continuity could not be confirmed due to impact damage. Examination of the wreckage revealed no mechanical discrepancies or anomalies that would have precluded normal operation.

According to the autopsy performed by the North Carolina Department of Health and Human Services, Office of the Chief Medical Examiner, the cause of death was multiple blunt force injuries, and the manner of death was accident.

Toxicology testing performed by the FAA’s Forensic Sciences Laboratory identified trimethoprim (a prescription antibiotic) and tamsulosin (a prescription medication used to treat symptoms of an enlarged prostate) in the pilot’s blood and urine. Neither of these are considered impairing.

According to the US Naval Observatory Astronomical Applications department, bright daylight conditions existed at the time of the accident. The sun was at 39.85° above the horizon (altitude) at an azimuth of 272.39°.

Contributing factors

  • Awareness of condition
  • Pilot

Conditions

Weather
VMC, wind 150/04kt, 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.