Accident Details
Probable Cause and Findings
The pilot’s failure to maintain clearance from powerlines during a low-level aerial application flight, resulting in main rotor blade impact with a fiber-optic cable, a loss of control, and the helicopter’s subsequent impact with terrain.
Aircraft Information
Registered Owner (Current)
Analysis
On June 25, 2021, about 1650 central daylight time, a Garlick Helicopters OH-58+, N372NS, was substantially damaged when it was involved in an accident in Alpine, Alabama. The pilot was fatally injured. The helicopter was operated as a Title 14 Code of Federal Regulations Part 137 aerial application flight.
Before the accident flight, the pilot, along with a loader/fueler (ground crewmember), had been conducting chemical spraying operations from an abandoned drag strip about 3/4 mile southwest of the accident site. The ground crewmember stated the pilot had sprayed about 5 loads (500 acres) and had 5 loads remaining to spray. Each load took between 15 and 20 minutes. The ground crewmember was not aboard the helicopter during the accident flight.
About 1650, a local resident heard a helicopter that was flying “real low,” but she could not see the helicopter because of trees. The helicopter kept getting closer, and she heard a sound “like propellers hitting a tree, and then a boom like an explosion.” When she eventually saw the helicopter, it was “turned all to pieces.” The local resident could smell fuel, and she “started to see a little bit of smoke, but there was no fire.”
A video recording captured the helicopter during an application flight over an adjacent cornfield before the accident flight. Review of the video recording revealed that the helicopter was flying at a low altitude and below the trees and powerlines that surrounded the field, and the helicopter would gain altitude at the end of each pass over the field to clear the surrounding trees and powerlines. The helicopter would then turn back and descend once again below the trees and powerlines for the next pass.
According to Federal Aviation Administration (FAA) and pilot records, the pilot held a type rating in the C/S-70 (UH-60) helicopter. He had accrued flight time in multiple aircraft, including the PA-28, 7GCAA, C150, C170, C210, S2R-T34, OH-58, and UH-60.
On June 22, 2005, the helicopter was involved in an accident while maneuvering during an aerial application flight in Graham, Texas (NTSB case no. DFW05CA172). The helicopter struck wires during a pull-up maneuver. Evidence at the accident site showed that the tailboom struck the top wire of a hightension string and separated in flight. After the tailboom separated, the helicopter entered an uncontrolled descent to ground impact. The wires did not have fixed aerial obstruction features (for example, orange balls) installed to make the wires more conspicuous. A review of FAA airworthiness records revealed that FAA Form 337, Major Repair and Alteration, had not been filed with the FAA when the helicopter was rebuilt after the accident.
At the time of the accident, the helicopter was equipped with high-skid landing gear; a spray system; and a wire strike protection system, which consisted of cable cutters mounted above the windshield and below the forward fuselage. The helicopter was not equipped with a wire strike prevention system.
The helicopter was not required to have, and was not equipped with, a cockpit voice recorder or a flight data recorder. Other electronic devices that might have contained nonvolatile memory were recovered from the wreckage, including a Garmin GPS unit and an AgNav unit. The NTSB Vehicle Recorders Laboratory found that the GPS track log recording function was “off,” so no data could be recovered. Also, the internal memory module from the Ag-Nav unit was removed and sent to the manufacturer, which determined that the module sustained internal damage and that no data could be recovered.
Examination of the accident site indicated that the helicopter had struck a fiber-optic cable that was collocated with high-voltage transmission lines on the south side of the cornfield and then impacted terrain about 415 ft from the initial wire strike with the fiber-optic cable. The transmission lines were not equipped with wire markers (aircraft warning markers). Further examination of the accident site revealed a debris path that contained a piece of cable in a tree near the south side of the field and a section of bent cable core that had come to rest in the cornfield. This debris path began near the area of the wire strike and continued on a magnetic heading of about 300° to the helicopter’s impact location.
Examination of the helicopter revealed that it was substantially damaged and had broken into numerous pieces on impact, with the landing gear (skids), fuselage, and tailboom all receiving varying degrees of impact damage. Further examination of the helicopter also revealed that the main rotor mast, pitch change links, main rotor hub, tail rotor, and tail rotor drive shaft were substantially damaged.
Examination of the flight control system revealed numerous breaks in the cyclic control system, collective control system, and anti-torque system. Flight control continuity was able to be established from the cockpit to the breaks in the flight control system, and from the breaks in the system to the main rotor and tail rotor.
Examination of the engine revealed that it displayed signatures consistent with operation during the impact sequence as some of the blades in the compressor section downstream of the air inlet were broken off opposite the direction of rotation, with the remaining blades displaying bend back and leading edge gouging. Additionally, rotational scoring was present on the walls of the compressor section.
Examination of the drive train revealed that the tail rotor drive shaft displayed twisting at several breaks in the drive shaft which was indicative of production of engine power. Drivetrain continuity was able to be established from the engine to the main transmission and from the main transmission to the rotor head. Drivetrain continuity was also established from the main transmission to the breaks in the tail rotor drive shaft and from the breaks in the tail rotor drive shaft to the tail rotor gearbox, and from the tail rotor gearbox to the tail rotor. Both the main rotor hub and tail rotor could be rotated by hand, and the magnetic chip detectors were free of debris.
Examination of the two tail rotor blades revealed that they had remained attached, but both had been bent near the blade root, with one blade bent about 45 degrees away from the tail boom, and the other bent about 135 degrees towards the tail boom.
Examination of the two main rotor blades revealed that one blade displayed an area, on the outboard section of the blade, that contained leading-edge damage, scratching oriented at an angle of about 45° from the tip inward and toward the trailing edge. That same blade had a wire strike signature about 8 inches inboard of the blade tip. The other blade was missing about 3 1/2 ft of the outboard portion of the blade.
According to the FAA Safety Briefing magazine article, “Avoiding Wire Strikes in Rotorcraft Operations,” dated October 30, 2020, the number of wire strike accidents has increased, and wire strikes remain one of the leading fatal accident causes in low-level helicopter operations. The safety briefing continued as follows:
Many pilots mistakenly believe that just watching for wires will provide sufficient reaction time. Statistics show that all pilots flying low are susceptible to a strike, regardless of experience and ability. Several capable and experienced pilots who have survived a wire strike say the same things: ’I just didn’t see it.’ ’The wires just appeared.’ ’There was no time to think or react.’
According to the US Energy Information Administration, the United States has about 200,000 miles of high-voltage transmission lines and millions of miles of low-voltage distribution lines throughout the United States. Wire strike hazards exist for operations below 500 ft above ground level. Because this environment has an inherent risk of wire strikes, flight crews must be properly trained to assess the environment and verify the presence of wires without relying solely on “see and avoid.” The FAA Safety Briefing article presented the following tips for wire hazard mitigation:
o Avoid low-level flight whenever it is not essential to the operation.
o Become familiar with all known hazards in the operations area prior to low-level flight.
o Brief all crew and passengers to speak up and be specific if they see power lines, towers, or other obstacles.
o Look for all indicators of a power line (e.g., right of way clearing or support structures).
o Always cross transmission lines at the point of the supporting structure.
o Be prepared to climb out of the wire environment if any distraction or confusion occurs (e.g., irrelevant crew conversation, radio call, etc.).
o Assume that wires are always present in any unfamiliar operations area until proper high reconnaissance confirms otherwise.
Data Source
Data provided by the National Transportation Safety Board (NTSB). For more information on this event, visit the NTSB Records Search website. NTSB# ERA21LA269