FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR10GA097 · Bell 206B

5 Jan 2010 · Auberry, CA, United States

California Department of Fish and Game Bell 206B · Accident: controlled flight into terrain/object (CFIT) while maneuvering

From Trimmer, CA to Trimmer, CA

Report a problem

Event

NTSB case
WPR10GA097
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
4 · 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
N5016U
Onboard fatalities
Unknown
Route
From Trimmer, CATo Trimmer, CA
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
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
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
Controlled flight into terrain/object (CFIT)
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

  • Environmental issues › Physical environment
  • Personnel issues › Psychological

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

NTSB narrative

The pilot was flying a deer-surveying mission under contract with a state government agency with three state employees onboard. About 2 hours into the flight, witnesses observed the helicopter flying along a valley and colliding with one of two “skylines,” or cables strung between the towers of power transmission lines. The transmission lines consisted of two parallel steel skylines on top and three power conductor lines mounted about 20 feet below. The helicopter appeared to be flying straight and level prior to the collision, exhibiting no indications of distress. Examination of the engine and damage to the rotor system indicated that the engine was producing power at the time of the collision. Examination of the airframe and engine did not reveal any evidence of preaccident failure or malfunction. The transmission lines were depicted on the applicable sectional map, as well as a printed survey map located in the debris field. The power conductor lines were observed to sag about 70 feet below the skyline in the area of the accident. The power conductor lines were about twice as thick as the skyline. Additionally, the position of the sun would have hindered identification of the skyline by the pilot. In the area of the collision a second set of power lines were located about 200 feet below the lines depicted on the maps. As such, it is possible that the pilot misidentified these as the lines depicted on the maps. Neither of the sets of power lines were equipped with spherical visibility markers or similar identification devices.

The helicopter was equipped with a wire strike protection system; however, examination of its cutting surfaces revealed that it did not make contact with any lines. The helicopter struck the second skyline along the direction of flight, indicating that it flew below the first line with the main rotor blades striking the second line from below; since the wire struck outside of the cutters’ capture envelope, the wire strike protection system would not have been in a position to protect the helicopter. Federal regulations require that any planned construction of structures over 200 feet above ground level (agl) be filed with the Federal Aviation Administration. While the power lines’ height exceeds 200 feet agl at the center of the span, their construction predates adoption of the regulation. At the time of the accident, the state agency did not have any formal safety or operational training systems in place for passengers who fly on surveying missions.

Probable cause

The pilot's failure to see and avoid a wire while maneuvering during low-altitude operations.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR10GA097
Event ID
20100105X94046
Case number
WPR10GA097
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: fed4e581db7fe349d67c0e75cdc8e1c607c88734fa49598869cd2891e65bca8a; retrieved 2026-09-13T20:36:16.947Z.