FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA00LA020 · Bell 206L-1

17 Nov 1999 · NEIHART, MT, United States

Bell 206L-1 · Accident: in flight collision with object during takeoff

From an unrecorded airport to 95U · Great Falls, MT

Report a problem

Event

NTSB case
SEA00LA020
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
0 · all aircraft and ground
Ground fatalities
0
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
Charter & commuter
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-1

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
N519EH
Operator
Unknown
Onboard fatalities
Unknown
Route
From not recordedTo 95U · Great Falls, MT
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 135: Air Taxi & Commuter
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
Takeoff
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
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
Tower
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

  • Pilot in command › Clearance, not maintained

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

NTSB narrative

The pilot reported that, due to trees directly in front of him for the departure from a remote site located near ski lift towers, he elected to turn the nose of the helicopter 45 to 50 degrees to the left, hover over to an open area, and depart downslope building airspeed and altitude. After the helicopter moved to the left about 20 to 30 feet, the pilot felt the tail of the helicopter rotate abruptly to the left. The pilot applied left pedal which slowed, but did not stop the rotation. The pilot applied cyclic control to return to the landing zone. During the maneuver, the helicopter drifted over to one of the ski lift towers, striking the tail rotor on the tower. The rotation increased, and the pilot closed the throttle and utilized collective to cushion the landing which was hard. The pilot reported that there were no mechanical failures or malfunctions with the helicopter at the time of the accident. Shortly after the accident, as the pilot was waiting for company personnel to arrive, he noted that at 10 to 15 minute intervals, the wind gusts would become stronger for a short period of time, then die down. The pilot reported that the wind was from 180 degrees at five knots, gusting to 15 knots.

Probable cause

Clearance from an object was not maintained. Gusting wind conditions was a factor.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA00LA020
Event ID
20001212X20178
Case number
SEA00LA020
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. 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: 6dec4473899aeb24889e5e4fef11440dd8d72d73bd3ad6c989e1033e7340e83c; retrieved 2026-09-18T16:51:11.261Z.