FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA04TA163 · Bell 206B

17 Aug 2004 · Mead, WA, United States

Bell 206B · Accident: loss of control in flight while maneuvering

From Spokane International Airport (GEG) to Mead, WA

Report a problem

Event

NTSB case
SEA04TA163
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

Bell 206B

Aircraft type
Bell 206
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
N34698
Operator
Unknown
Onboard fatalities
Unknown
Route
From Spokane International Airport (GEG), Spokane, WATo Mead, WA
Aircraft age
Not recorded
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 out of ground effect
First occurrenceThe 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
Loss of control in flight
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

  • Company/operator management › Procedure inadequate
  • Pilot in command › Aircraft control, not possible
  • Towing/advertising/external load equipment › Reversed

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The helicopter was pulling sock line (rope) that was to be used to install a static wire at the top of 220-foot-tall towers supporting a 500-kV power line. (The stringing of sock line is a Class C external load operation, meaning an operation in which the external load is jettisonable and remains in contact with land or water during the rotorcraft operation.) The sock line was attached to the helicopter's remote cargo hook and played out of a truck mounted reel machine operating in the power payout mode. The reel machine operator stated that "suddenly the rope wrapped over another rope or pulled down in the drum, causing the rope to reverse on the drum." The reel machine operator immediately moved the machine's shift lever from "OUT" to "NEUTRAL," but by the time he had accomplished this, the rope between the reel and the helicopter went taut. Numerous witnesses, who were all members of the line crew installing the wires, reported that when the rope went taut, the helicopter pitched up and rolled right. The helicopter descended, impacted the ground and came to rest on its right side. Post-accident interviews revealed that the pilot, the line crew, and company management did not adequately recognize and mitigate the risks inherent in the procedures they were using to conduct the sock line pull. Specifically, the rigging used was a 25-foot long line with a 31-pound ballast weight, while other operators pulling sock line use longer long lines (50 to 100 feet) and heavier ballast (150 to 300 pounds) in order to provide pilots with an earlier warning of an impending shock load due to a snag so that the pilot will have more time to respond. Additionally, at the pilot's request, the reel machine was being operated in the power payout mode, instead of the free wheeling mode. This was due to a miscommunication between the pilot and the chief pilot, who stated that when he discussed the operation with the pilot, he assumed the pilot understood that he intended for the reel to be freewheeling. In the freewheel mode, when a snag occurs, at worst, the reel stops. In the power payout mode, when a snag occurs, the line can double back on the reel and begin to pull back in, as occurred in this accident. Also, while preparing for the sock line pull, the line crew was paying out sock line on the ground and experienced a snag, which resulted in the line being pulled in instead of paying out, just as occurred in the accident. However, there was no communication of this occurrence to the pilot. Finally, although the pilot had 21,803 hours rotorcraft flight time, 16,000 hours in the accident make and model helicopter, and 4,000 hours conducting external load operations, his most recent Class C external load experience was 5 years and 3 months prior to the accident.

Probable cause

The reversal of the reel machine during a sock line pull which resulted in a loss of control while hovering out of ground effect. Factors were the failure of company management to develop adequate procedures for conducting sock line pulls, the inadequate communication between the chief pilot and the pilot, the inadequate communication between the ground personnel and the pilot, and the pilot's lack of recent experience in Class C external load operations.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA04TA163
Event ID
20040825X01284
Case number
SEA04TA163
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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, coordinates. 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: f722c05e339477df1510f2f1d733d6df07ca28b73b7a1efa9c3f44c92b77aa95; retrieved 2026-09-20T18:22:26.096Z.