ERA21LA269 · Garlick Helicopters Inc OH-58A+
Ewing Flying Service Garlick Helicopters Inc OH-58A+ · Accident: low altitude operation/event while maneuvering
From Alpine, AL (no airport) to an unrecorded destination
Event
- NTSB case
- ERA21LA269
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 1 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Garlick Helicopters Inc OH-58A+
- Aircraft type
- Garlick OH-58
- Category
- Helicopter
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N372NS
- Operator
- Ewing Flying Service
- Onboard fatalities
- Unknown
- Route
- From Alpine, AL (no airport)To not recorded
- Aircraft age
- About 51 years (built 1970)
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 137: Agricultural
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Maneuvering · low-altitude flying
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Low altitude operation/event
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Wire
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Environmental issues › Physical environment
- Personnel issues › Action/decision
- Personnel issues › Psychological
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
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.
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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA21LA269
- Event ID
- 20210626103346
- Case number
- ERA21LA269
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, cause areas. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 46685da18bc80e676170271d335c677a8bfdf7366b0a05a690f38e4de06ea05c; retrieved 2026-09-15T07:30:27.517Z.