FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR13GA128 · Bell 206B

18 Feb 2013 · Eureka, NV, United States

Bell 206B · Accident: low altitude operation/event while maneuvering

From Ely Airport Yelland Field (ELY) to Ely Airport Yelland Field (ELY)

Report a problem

Event

NTSB case
WPR13GA128
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
Government
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
N20620
Onboard fatalities
Unknown
Route
From Ely Airport Yelland Field (ELY), Eureka, NVTo Ely Airport Yelland Field (ELY), Eureka, NV
Aircraft age
About 32 years (built 1981)
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
Public Aircraft
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

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Psychological

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

NTSB narrative

The pilot was flying a helicopter as part of a Department of Interior (DOI) reseeding project when the helicopter struck the static line above a set of power transmission lines. Postaccident examination of the engine and airframe revealed no evidence of mechanical malfunctions or failures that would have precluded normal operation. The length and direction of the debris field was consistent with the helicopter traveling in the direction of, and at a rate of speed consistent with, a seed dispersal run.

The pilot was familiar with the area and was aware of the transmission lines, having performed a reconnaissance flight and flown over them multiple times during the previous flights that day. In the area of the accident site, the power lines began an ascent up an adjacent hill, with the static lines diverging such that they were about 40 feet higher than the power lines at the collision location. The static lines were of thinner gauge and could easily have been obscured by the surrounding hilly terrain. The lines were depicted on the relevant Federal Aviation Administration sectional chart. The helicopter was not equipped with a wire strike protection system nor was it required to be under the terms of the DOI contract. Neither the power nor static lines were equipped with visibility markers nor were they required to be due to their elevation above ground level.

The pilot had flown 40.5 hours over the last 5 days as part of the reseeding project, which was just short of the DOI contract maximum. A review his sleep history indicated that he received adequate rest the night before the accident. On the morning of the accident, he had flown 10 application runs in an area about 70 miles away. He took a lunch break about 3 hours before the accident, then flew 20 separate seed application runs and 10 reloads. His total flight time for that day was 6.6 hours. The low-level and "nap of the earth" flight operations required considerable concentration, most likely resulting in task-and/or work-related fatigue at the end of the day. By comparison, the United States Army recommends a maximum flight time of 8 hours per day or 37 hours per week, with a reduction of a factor of 1.3 to 1.6 for low-level and "nap of the earth" flying; thus the pilot would have exceeded their duty hour recommendations for each of the 5 days leading up to and including the accident day.

The pilot held an assisted special issuance second-class medical certificate based on a reported history of diabetes for which he was taking medication. His most recent medical examination revealed a new diagnosis for hypertension, as well as preexisting cataracts in both eyes, which exhibited no change since his last examination a year prior. In part due to the lack of an autopsy, the relevance of these findings, combined with his likely work-related fatigue, could not be determined.

Probable cause

The pilot’s failure to maintain clearance from a wire while maneuvering during low-altitude operations. Contributing to the accident was task- and/or work-related fatigue.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR13GA128
Event ID
20130218X22833
Case number
WPR13GA128
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: 416464ca44fb2ebf142ba934c136a7aa7ec111e650c2f4698f2d6b35a16b3ec1; retrieved 2026-09-14T15:53:13.202Z.