FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA18FA122 · MD Helicopter 600 N

8 Apr 2018 · Smethport, PA, United States

High Line Helicopters MD Helicopter 600 N · Accident: external load event (Rotorcraft) while maneuvering

From Smethport, PA to Smethport, PA

Report a problem

Event

NTSB case
ERA18FA122
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
2 · 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

MD Helicopter 600 N

Aircraft type
MD Helicopters 600
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
N602BP
Onboard fatalities
Unknown
Route
From Smethport, PATo Smethport, PA
Aircraft age
About 20 years (built 1998)
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 133: Rotorcraft Ext. Load
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 · hover
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
External load event (Rotorcraft)
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
Destroyed

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Environmental issues › Physical environment
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot of the helicopter was conducting a power line construction flight. The power lines were supported by a series of structures made of either wood (dual-pole, H-frame) or steel (single pole). A static line was affixed to the top of the structures above the power lines. The purpose of the flight was to remove the static line from the wheeled, pulley device (dolly) that temporarily secured the static line and permanently secure the static line to the structures. One lineman completed the task from the skid of the hovering helicopter, and another lineman inside the helicopter passed tools and equipment back and forth to the lineman on the skid. The accident occurred when the crew (the pilot and the two linemen) were working on the second structure, which was constructed of wood. During work on that structure, the helicopter hovered facing westbound adjacent to the wooden structure with the pilot, both linemen, and the structure on the helicopter's left side. The static line sloped upward aft of the helicopter toward the uphill structure and downward and to the right toward the downhill structure.

The initial steps taken for the task included wrapping the line with a spiraled wire coating (armor rod) and attaching a safety strap (safety). The lineman on the helicopter skid attached the first half of the armor rod ahead of the dolly and manipulated the line and the dolly to complete the wrap. According to the pilot, the lineman opened the spring-loaded locking gate on the dolly above the static line to wrap the second half of the armor rod, which was "normal" before the attachment of the safety. About that time, the pilot felt the helicopter being "pulled" toward the structure. The pilot stated that he made cyclic and pedal inputs to avoid the structure but reported that "all I remember is rolling over the structure." The pilot stated that he neither felt nor heard anything unusual before the helicopter was pulled toward the structure.

Visual examination of the static line, helicopter rotor blades, and visual and metallurgical examination of the dolly revealed that, as the lineman on the skid wrapped the armor rod, and before he attached the safety, the aft portion of the main rotor struck the static line, which broke the locking gate that secured the line inside the dolly. Once free of the dolly, the static line fell between the uphill and downhill structures and over the left front skid of the helicopter, which created the pivot point over which the helicopter rolled inverted.

The pilot and the linemen began work without installing a safety. According to the operator's director of safety, the safety strap aboard the helicopter was "not long enough" to install it before work began. The holding company of the subsidiary that hired the operator as an independent contractor had a safety manual for linemen who performed work from helicopters. The manual indicated that "secondary securement systems shall be utilized" when clipping wire (permanently securing a static line to the structures).

Probable cause

The helicopter pilot's failure to maintain adequate clearance during power line construction work, which resulted in the helicopter's main rotor striking and becoming entangled with a wire and a subsequent dynamic rollover and collision with terrain. Contributing to the accident was the pilot's and linemen's decision to continue work without a secondary safety device installed, which was contrary to standard operating procedures.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA18FA122
Event ID
20180408X85603
Case number
ERA18FA122
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. 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: 99ca736e5f473166da6b10fb20b54a7d177997a0946d175aa89aadce3d03cea7; retrieved 2026-09-15T06:38:12.167Z.