FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Help Flight Bell 206L-3 accident

1 Jun 1989 · Big Timber, MT, United States

Bell 206L-3 · Accident: loss of control in flight during takeoff

From No airport to Billings, MT (no airport)

Report a problem

Event

NTSB case
DEN89MA130
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
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-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
N76KM
Operator
Help Flight
Onboard fatalities
Unknown
Route
From No airportTo Billings, MT (no airport)
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
Loss of control in flight
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Pilot in command › Aircraft control, not maintained
  • Pilot in command › Spatial disorientation

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

NTSB narrative

AT ABT 2158 MDT, THE EMERG MED SVC (EMS/MEDEVAC) HELICOPTER (HEL) PLT CTCD BILLINGS TWR & ADZD HE WOULD BE MAKING APCHS TO SAINT VINCENTS HOSP FOR (NGT) CURRENCY. APRX 9 MIN LATER, HE CTCD THE TWR AGAIN & ADZD HE WAS BEING DISPATCHED ON AN EMS FLT. THE EMS FLT WAS TO A RANCH (WNW OF BILLINGS). THE PLT HAD DIFFICULTY FINDING THE RANCH AT NGT, BUT ARRIVED AT 2238 MDT. THE PATIENT WAS LOADED & THE PLT WAS ADZD OF TRRN CONDS. A WITNESS SAID THE HEL LIFTED OFF FAST, THEN SWIVELEDARND QUICKLY (TOWARD EAST) & TOOK OFF W/O HESITATION. AFTER DEPG, THE HEL CROSSED A HILL & CRASHED AT HI SPD ON LWR TRRNIN A SLGT NOSE LOW, RGT BANK ATTITUDE, HDG 330 DEG. NO PREIMPACT MECH PRBLM WAS FND. THE PLT HAD BEEN RECENTLY HIRED BY THE OPERATOR; PREV EMPLOYMENT INVOLVED FLYING A DISSIMILAR HEL (BK-105) IN THE GULF OF MEXICO AREA, LIMITED TO DAY VFR. THE PLT'S LAST RECORDED NGT FLT WAS ON 6/16/87; HIS LAST RECORDED INST FLT WAS PRIOR TO JUNE 1984. NO RECORD WAS FND OF FAMILIARIZATION TRAINING FOR THE GEOGRAPHICAL AREA. RELATIVES OF THE PATIENT DESCRIBED THE ACDNT AREA AS A BLACK HOLE.

Probable cause

FAILURE OF THE PILOT TO MAINTAIN CONTROL OF THE AIRCRAFT DURING TAKEOFF, DUE TO SPATIAL DISORIENTATION, WHICH RESULTED IN A COLLISION WITH THE TERRAIN. CONTRIBUTING FACTORS WERE: DARK NIGHT, PILOT'S VISUAL PERCEPTION, INADEQUATE INITIAL TRAINING OF THE PILOT BY THE OPERATOR, THE PILOT'S LACK OF FAMILIARITY WITH THE GEOGRAPHICAL AREA, AND THE COMPANY'S INSUFFICIENT STANDARDS/REQUIREMENTS.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DEN89MA130
Event ID
20001213X28565
Case number
DEN89MA130
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (5)
  • 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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 1989-06-02.
  • API snapshot SHA-256: 5887e233f83d8d4078692ff4f88fc5ed80e6e2af3b01ab198fe733fb17343d3e; retrieved 2026-09-18T14:08:59.350Z.
  • The NTSB's operator name is blank for N76KM; the operator shown is the name the NTSB records it doing business as.