FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR21LA338 · Bell 206L-3

8 Sept 2021 · Tillamook, OR, United States

Wilbur Ellis Bell 206L-3 · Accident: collision with terrain/object (non-CFIT) while maneuvering

From Tillamook, OR to Tillamook, OR

Report a problem

Event

NTSB case
WPR21LA338
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
Event fatalities
Unknown
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 206L-3

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
N6516K
Operator
Wilbur-Ellis
Onboard fatalities
Unknown
Route
From Tillamook, ORTo Tillamook, OR
Aircraft age
About 31 years (built 1990)
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 137: Agricultural
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
Collision with terrain/object (non-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

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

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

NTSB narrative

The helicopter pilot reported that he was on a low reconnaissance over a field in a canyon intended for agricultural application. During a climb out that was on a heading facing the sun, he lost sight of a previously identified powerline, and attempted to avoid it by referencing the two supporting powerline poles. As the helicopter flew closer, he located the wires and believed that the helicopter’s trajectory would clear the obstacle; however, the helicopter struck the powerline, the pilot lost control, and the helicopter descended and impacted terrain. The helicopter sustained substantial damage to the fuselage and main rotor system. The pilot reported that there were no preaccident mechanical malfunctions or failures with the helicopter that would have precluded normal operation.

Probable cause

The pilot's failure to maintain clearance from a powerline during a low reconnaissance, with sun glare.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR21LA338
Event ID
20210909103825
Case number
WPR21LA338
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, cause areas. 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: ce14176310af85108c58ae40e5754eb6f45dac85fd1816d10af8682150d588c5; retrieved 2026-09-16T14:30:32.330Z.