ASN Wikibase Occurrence # 153359
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information.
If you feel this information is incomplete or incorrect, you can submit corrected information.
| Date: | Monday 18 February 2013 |
| Time: | 14:24 |
| Type: |  Bell 206B-3 JetRanger III |
| Owner/operator: | Bureau of Land Management |
| Registration: | N20620 |
| MSN: | 3369 |
| Year of manufacture: | 1981 |
| Total airframe hrs: | 15540 hours |
| Engine model: | Rolls Royce 250-C20 |
| Fatalities: | Fatalities: 1 / Occupants: 1 |
| Aircraft damage: | Destroyed |
| Category: | Accident |
| Location: | 7 miles east of Eureka, NV -
 United States of America
|
| Phase: | Manoeuvring (airshow, firefighting, ag.ops.) |
| Nature: | Unknown |
| Departure airport: | Eureka, NV (ELY) |
| Eureka, NV (ELY) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
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.
Accident investigation:
 |
|
Sources:
NTSB
FAA register: http://registry.faa.gov/aircraftinquiry/NNum_Results.aspx?NNumbertxt=20620
https://www.planecrashmap.com/plane/nv/N20620/
Location
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 19-Feb-2013 09:35 | gerard57 | Added |
| 19-Feb-2013 12:49 | Geno | Updated [Time, Cn, Operator, Location, Source, Narrative] |
| 19-Feb-2013 15:21 | RobertMB | Updated [Aircraft type, Source, Narrative] |
| 02-Sep-2014 08:46 | Aerossurance | Updated [Source, Narrative] |
| 21-Dec-2016 19:28 | ASN Update Bot | Updated [Time, Damage, Category, Investigating agency] |
| 28-Nov-2017 14:08 | ASN Update Bot | Updated [Operator, Other fatalities, Nature, Departure airport, Destination airport, Source, Narrative] |
| 09-Jul-2022 07:14 | rvargast17 | Updated [Aircraft type, Location, Source, Damage] |
Corrections or additions? ... Edit this accident description
The Aviation Safety Network is an exclusive service provided by:
Quick Links:
| ASN Home | Send Correction / Feedback |
| FSF Home | Disclaimer | Copyright |
| Contact Us | Privacy Policy |
| Press / Media |
CONNECT WITH US:
©2024 Flight Safety Foundation