ANC99TA058 · Bell UH-1B
Bell UH-1B · Accident: in flight collision with object while maneuvering
From Wrangell Airport (WRG) to an unrecorded destination
Event
- NTSB case
- ANC99TA058
- 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
- 1
- 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 UH-1B
- Aircraft type
- Bell UH-1
- 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
- N97HM
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Wrangell Airport (WRG), AKTo not recorded
- 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
- In flight collision with object
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- None
Cause areas
No findings designated as a cause are recorded in the NTSB data yet.
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
A restricted category Bell UH-1B helicopter was hovering near high voltage wires at a construction site, performing external load lift operations with a 110 feet long steel cable. The construction project was under the direction of the Alaska Energy Authority, a State of Alaska corporation. The State of Alaska construction project manager reported the electrical wires were energized, and the wires were configured to de-energize if shorted. The pilot had extensive external load experience, but had about 1 hour in the accident helicopter make and model. He said he was not aware the electrical wires were energized. The chief pilot was occupying the right seat, and said he was providing 'guidance' during the flight. The chief pilot said he was aware the wires were hot. Just after the long line was hooked to a load of steel beams on the ground, the cable touched the overhead electrical wire, and electrocuted one ground member standing on the load. The construction project operations manager said that the electrical short, caused when the cable touched the wire, was insufficient to trip the electrical power off. The helicopter company's external load manual includes the following: 'The chief pilot will brief all involved personnel concerning procedures for each operation; the flight crew consists (normally) of one pilot; the use of a hand signalman, separate from the ground crew, shall be assigned no other duties during the operation; the pilot may elect to use a continuous visual observation method, wherein he is directly observing the load by looking out the window, out the door, or by use of mirrors. In this case, release and/or signalmen need not be utilized.' The manual also includes: 'Radio contact between the pilot and the hook-up man is highly desirable, and the presence of a radioman in no way alleviates the need for the hand signalman. A signalman should be present at all times in the event of a radio failure. If the pilot is able to observe the hook-up operation by using a skid-mounted mirror, and VHF two-way radio communications are maintained between the pilot and the hook-up man, a signalman is not required.' During the accident, direct radio communication between the ground crew and the pilot was not maintained, and a signalman was not utilized.
Probable cause
The pilot-in-command's failure to maintain sufficient distance from a transmission wire, arcing of the transmission wire, the failure of company personnel to utilize a nonconducting cable, and an inadequate procedure utilized by the construction project manager to ensure adequate fault protection on an energized transmission wire. Factors in the accident were a failure of the helicopter operator to maintain sufficient standards, including flight and ground crew coordination, and a failure to maintain radio communication between the pilot and ground crew.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC99TA058
- Event ID
- 20001212X18681
- Case number
- ANC99TA058
- 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, damage. 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: ad1b05761c731fa33ca46db8cfdc16f7d7f5ce7588fbc4f6f023a2dc17701cc5; retrieved 2026-09-20T22:07:49.843Z.