# NTSB ERA21LA269: Garlick Helicopters OH-58A+, N372NS, Alpine, AL, June 25, 2021

- Type: NTSB accident investigation
- Classification: Accident · Fatal · Class 3 · Limited · Final report
- Date: June 25, 2021, 16:50 local (21:50 UTC)
- Place: Alpine, AL · Wreckage near Edwards Road
- Coordinates: 33.256369, -86.251594 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=33.2564&lon=-86.2516&mi=10
- Phase of flight: [Maneuvering](https://openairdocs.org/ntsb-phases/450) (OpenAirDocs' grouping)
- Defining event: [Maneuvering-low-alt flying: Low altitude operation/event](https://openairdocs.org/ntsb-events/220)
- Highest injury: Fatal
- Injuries: 1 fatal
- Status: Completed
- Report: Approved by Office Director
- Investigation class: Class 3
- NTSB office: Eastern Region Aviation
- Parties: FAA/FSDO
- NTSB case key (mKey): 103346
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA21LA269
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/103346/pdf
- NTSB docket: https://data.ntsb.gov/Docket?ProjectID=103346
- Page: https://openairdocs.org/ntsb/ERA21LA269

## Probable cause

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.

## Findings

NTSB's coded findings; those marked are part of the probable cause.

- [Info processing/decision: identification/recognition](https://openairdocs.org/ntsb-findings/02041510): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Garlick Helicopters OH-58A+, 2 cases](https://openairdocs.org/ntsb-findings/02041510/cases.md?model=3740006), [All aircraft, 559 cases](https://openairdocs.org/ntsb-findings/02041510/cases.md)
- [Info processing/decision: decision making/judgment](https://openairdocs.org/ntsb-findings/02041520): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Garlick Helicopters OH-58A+, 2 cases](https://openairdocs.org/ntsb-findings/02041520/cases.md?model=3740006), [All aircraft, 3,098 cases](https://openairdocs.org/ntsb-findings/02041520/cases.md)
- [Attention/monitoring: monitoring environment](https://openairdocs.org/ntsb-findings/02021545): Personnel issues › Psychological · Pilot (probable cause); cases with it: [Garlick Helicopters OH-58A+, 1 case](https://openairdocs.org/ntsb-findings/02021545/cases.md?model=3740006), [All aircraft, 809 cases](https://openairdocs.org/ntsb-findings/02021545/cases.md)
- [Object/animal/substance: wire](https://openairdocs.org/ntsb-findings/03022032): Environmental issues › Physical environment · Effect on equipment (probable cause); cases with it: [Garlick Helicopters OH-58A+, 1 case](https://openairdocs.org/ntsb-findings/03022032/cases.md?model=3740006), [All aircraft, 588 cases](https://openairdocs.org/ntsb-findings/03022032/cases.md)
- [Object/animal/substance: wire](https://openairdocs.org/ntsb-findings/03022032): Environmental issues › Physical environment · Decision related to condition (probable cause); cases with it: [Garlick Helicopters OH-58A+, 1 case](https://openairdocs.org/ntsb-findings/03022032/cases.md?model=3740006), [All aircraft, 588 cases](https://openairdocs.org/ntsb-findings/03022032/cases.md)
- [Object/animal/substance: wire](https://openairdocs.org/ntsb-findings/03022032): Environmental issues › Physical environment · Response/compensation (probable cause); cases with it: [Garlick Helicopters OH-58A+, 1 case](https://openairdocs.org/ntsb-findings/03022032/cases.md?model=3740006), [All aircraft, 588 cases](https://openairdocs.org/ntsb-findings/03022032/cases.md)

## Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event best describes what happened.

- [Maneuvering-low-alt flying: Low altitude operation/event](https://openairdocs.org/ntsb-events/220) (defining event); cases with it: [Garlick Helicopters OH-58A+, 1 case](https://openairdocs.org/ntsb-events/220/sequence.md?model=3740006), [All aircraft, 780 cases](https://openairdocs.org/ntsb-events/220/sequence.md)
- [Maneuvering-low-alt flying: Part(s) separation from AC](https://openairdocs.org/ntsb-events/338); cases with it: [Garlick Helicopters OH-58A+, 1 case](https://openairdocs.org/ntsb-events/338/sequence.md?model=3740006), [All aircraft, 563 cases](https://openairdocs.org/ntsb-events/338/sequence.md)
- [Uncontrolled descent: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Garlick Helicopters OH-58A+, 4 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=3740006), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md)

## Analysis

The pilot had completed multiple aerial application flights over a cornfield on the day of the accident. During the accident flight, the helicopter contacted a fiber-optic cable that was collocated with high-voltage transmission lines. The wire strike resulted in a loss of control, and the helicopter impacted terrain, fatally injuring the pilot and substantially damaging the helicopter. A video recording of the helicopter during a previous application flight that day revealed that the helicopter was flying at low altitude and below the trees and powerlines that surrounded the field. After each pass over the field, the helicopter gained altitude to clear the surrounding trees and powerlines, turned back, and then descended again below the trees and powerlines for the next pass. Also, a witness heard a helicopter that sounded as if it was flying “real low,” but she could not see the helicopter because of trees. The witness reported that she heard a sound “like propellers hitting a tree, and then a boom like an explosion.” No evidence indicated a preimpact mechanical malfunction or anomaly that would have precluded normal operation of the helicopter. Postaccident examination of the wreckage revealed that one of the main rotor blades displayed an area, on the outboard section of the blade, that contained leading-edge damage, a wire strike signature about 8 inches inboard of the blade tip and scratching oriented at an angle that was about 45°-from the tip inward and toward the trailing edge. The other main rotor blade was missing about 3 1/2 ft of the outboard portion of the blade. These observations were consistent with the helicopter being in a right turn when the main rotor blades contacted the fiber-optic cable. It is likely that the pilot lost positional awareness during the turnaround at the end of the final application pass. Also, because the helicopter was not equipped with a wire strike prevention system and the transmission lines did not have fixed aerial obstruction features such as wire markers, which would have made the transmission lines more visible, the pilot’s attention was not likely drawn to the wires before the wire strike. Additionally, even though the helicopter was equipped with a wire strike protection system, the areas of damage on the outboard portions of the main rotor blades indicated that the contact with the fiber-optic cable likely occurred outside of the effective angle of the cable cutters.

## Factual narrative

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 high tension 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 preventionsystem. 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 Ag Nav 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 rotorgearbox 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.

## Aircraft

- Registration: [N372NS](https://openairdocs.org/aircraft/N372NS), registered now, S/N 70-15372, built 1970 (OpenAirDocs)
- Reported make and model: GARLICK HELICOPTERS INC OH-58A+
- Registry model: [Garlick Helicopters OH-58A+](https://openairdocs.org/model/garlick-helicopters-oh-58a-plus) (registry code 3740006) (OpenAirDocs)
- Registry engine: [Allison 250-C20 series](https://openairdocs.org/engine/allison-250-c20-series) (registry code 03020, turbo-prop) (OpenAirDocs)
- Category: Helicopter
- Serial number: 70-15372
- Year built: 1970
- Airframe hours: 7827.1
- Engines: Allison T63-A-720 420 horsepower turbo shaft
- Damage: Substantial damage
- Flight: Aerial application, Part 137
- Operator: Ewing Flying Service LLC
- Registered owner: Ewing Flying Service LLC
- Airworthiness certificate: Special, Restricted (Special)
- Last inspection: 100 hour, March 24, 2021
- Departed: None, Alpine, AL
- Equipment: Handheld GPS

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 30; injuries: fatal; commercial; airplane ratings: single-engine land; instrument ratings: helicopter; medical: class 2, without waivers/limitations; last flight review February 27, 2021; seat: right; restraint: 4-point; toxicology performed; flight hours: 1,255 total, 840 in this make and model, 1,030 as pilot in command

## Weather

- Conditions: Visual (VMC), Day
- Wind: 130° at 7 knots
- Visibility: 10 statute miles
- Lowest ceiling: 11,000 ft overcast
- Temperature: 84 °F, dew point 68 °F
- Altimeter: 30.12 inHg
- Observed at: KSCD, 6 nm away
- METAR: KSCD 252215Z AUTO 13007KT 10SM SCT040 SCT050 OVC110 29/20 A3012 RMK AO2 T02880201

## FAA reports on this event (1)

The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs).

- [Accident 20210625006969A](https://openairdocs.org/incident/20210625006969A), Jun 25, 2021: Garlick Helicopters Inc OH-58A+, Alpine, AL, Substantial damage, 1 fatal. N372NS was conducting low level agricultural spraying when it struck power lines. After striking the power lines, the aircraft descended striking the ground,…

## Other investigations on N372NS (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB DFW05CA172](https://openairdocs.org/ntsb/DFW05CA172), Jun 22, 2005: Garlick Helicopters OH-58A+ (N372NS), Graham, TX, substantial damage. Probable cause: The pilot's failure to maintain clearance with the wire while maneuvering during an aerial application flight. Low altitude flight is a contributing factor.

## Docket (9 files)

The files NTSB released with the investigation on August 30, 2023, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=103346. 140 MB in all.

- Pilot/operator aircraft accident report, NTSB form 6120.1 (item 1, PDF, 11 pages, 2.1 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=15939280&FileExtension=pdf&FileName=NTSB%20Form%206120%20Signed_Redacted-Rel.pdf
- Witness statements and interview summaries (item 2, PDF, 2 pages, 664 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=15939290&FileExtension=pdf&FileName=Witness%20Statements%20and%20Interview%20Summaries-Rel.pdf
- Video - previous flight of helicopter (adjacent field) (item 3, MP4, 122 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=15940063&FileExtension=mp4&FileName=Helicopter%202-Rel.mp4
- Aerial image of accident area (item 4, PDF, 1 page, 251 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=15939098&FileExtension=pdf&FileName=Satellite%20Image%20of%20Accident%20Area-Rel.pdf
- Photo array (item 5, PDF, 20 pages, 12.4 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=15939820&FileExtension=pdf&FileName=Photo%20Array-Rel.pdf
- Memorandum for record - wreckage examination (item 6, PDF, 2 pages, 149 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=15939328&FileExtension=pdf&FileName=Memorandum%20For%20Record%20-%20Wreckage%20and%20Impact%20Information-Rel.pdf
- Toxicological report (item 7, PDF, 1 page, 316 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=15940073&FileExtension=pdf&FileName=Forensic%20Toxicology%20Report_Redacted-Rel.pdf
- Electronic devices report (item 8, PDF, 7 pages, 1.2 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=15940083&FileExtension=pdf&FileName=Electronic%20Devices%20Email%20Report-Rel.pdf
- Wreckage release and evidence control (item 9, PDF, 3 pages, 831 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=15939711&FileExtension=pdf&FileName=Wreckage%20Release%20and%20Evidence%20Control_Redacted-Rel.pdf

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.
