FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Wiebe Gortmaker Bell 206B-III accident

25 Feb 1984 · Coalville, UT, United States

Bell 206B-III · Accident: roll over during landing

From WANSHIP, UT to an unrecorded destination

Report a problem

Event

NTSB case
DEN84FA102
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
1 · 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 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
N16803
Onboard fatalities
Unknown
Route
From WANSHIP, UTTo not recorded
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
Landing · flare/touchdown
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
Roll over
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 › Unsuitable terrain or takeoff/landing/taxi area, selected

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

NTSB narrative

THE HELICOPTER WAS EQUIPPED WITH 'BEAR PAWS'. SNOWSHOE-LIKE DEVICES ON THE SKIDS TO DISTRIBUTE WEIGHT ON SOFT SURFACES. THE BEAR PAWS ON THIS ACFT ROTATED FREELY AROUND THE SKIDS, NOT TIGHTENED DOWN AS PER DESIGN SPEC. ALSO, BEAR PAWS ARE NOT APPROVED FOR AMERICAN ACFT BY THE FAA. THIS HELICOPTER LANDED ON WHAT THE PILOT THOUGHT WAS A FIRM LANDING SURFACE BUT WAS ACTUALLY 5 FT OF SNOW COVERED WITH A THIN CRUST OF ICE. A PASSENGER THAT THE PILOT HAD DEBOARDED EARLIER ABOUT 900 FT DOWN THE MOUNTAIN, STATED THAT HE SAW THE HELICOPTER ROLL OVER ON ITS RIGHT SIDE APRX 5 MINS AFTER HE LEFT THE AIRCRAFT. THIS INDIVIDUAL STATED THAT THE PILOT DID NOT SHUT DOWN THE HELICOPTER AFTER HE WAS LEFT OFF. DURING THE ROLLOVER, ONE BLADE OF THE ROTOR SLICED THROUGH THE COCKPIT IT DEPARTED THE ACFT.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record DEN84FA102
Event ID
20001214X38747
Case number
DEN84FA102
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: 4c68c2fd91ab38e18f10e743d93f71edb197ba7fd50a6378d70e696a90b24785; retrieved 2026-09-18T14:28:56.388Z.