FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

DEN89LA059 · Bell 206B III

8 Jan 1989 · Park City, UT, United States

Avman Bell 206B III · Accident: on ground/water collision with terrain/water while standing

From No airport to No airport

Report a problem

Event

NTSB case
DEN89LA059
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
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 206B III

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
N16733
Operator
Avman
Onboard fatalities
Unknown
Route
From No airportTo 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 91: General Aviation
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
Standing · idling rotors
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
On ground/water collision with terrain/water
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
  • Pilot in command › Unsuitable terrain or takeoff/landing/taxi area, selected

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

NTSB narrative

THE COMMERCIAL PLT FLEW A RESCUE TEAM TO A MOUNTAIN AVALANCHE AREA. THE TEAM DEPLANED AND DURING THE UNLOADING PROCEDURE THE HELICOPTER SETTLED BACKWARDS INTO LOOSE SNOW. THE PLT ADDED COLLECTIVE PITCH AND ATTEMPTED TO HOVER. AS THE HELICOPTER LEFT THE GROUND, AN UNCOMMANDED RIGHT SPIN BEGAN. THE PLT PERFORMED A HOVERING AUTOROTATION 30 FEET AWAY FROM THE GROUND PERSONNEL. AT TOUCHDOWN THE TAIL BOOM ENTERED DEEP SNOW AND THE ACFT CAME TO REST NOSE HIGH. THE PLT DISCOVERED THE TAIL ROTOR SHAFT HAD BROKEN FORWARD OF THE TAIL ROTOR GEAR BOX. A POST ACCIDENT INVESTIGATION SHOWED EVIDENCE THAT THE TAIL ROTOR BLADES ENTERED LOOSE SNOW AND WERE SUBJECTED TO RAPID DECELERATION. THE SHAFT HAD SHEARED UNDER APPLIED TORQUE.

Probable cause

THE SELECTION OF AN UNSUITABLE LANDING SITE BY THE PILOT, RESULTING IN TAIL ROTOR CONTACT WITH THE TERRAIN AND SHEARING OF THE TAIL ROTOR DRIVESHAFT.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DEN89LA059
Event ID
20001213X27572
Case number
DEN89LA059
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: e3190d5dd15112d999ed893df18e08da1624262f99a83976b92055f96a19edd0; retrieved 2026-09-23T08:01:31.705Z.