FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Rocky Mountain Helicopters Bell 222UT accident

23 Sept 1986 · Galax, VA, United States

Bell 222UT · Accident: in flight encounter with weather en route

From Smith Reynolds Airport (INT) to Galax, VA

Show on map Search Wikipedia NTSB source dataset
Report a problem

Event

NTSB case
ATL86FA264
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
3 · 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
Instrument Meteorological Cond

Bell 222UT

Aircraft type
Bell 222
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
N251CC
Onboard fatalities
Unknown
Route
From Smith Reynolds Airport (INT), Winston-Salem, NCTo Galax, VA
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
En route · cruise
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 encounter with weather
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
Visual flight rules (VFR) flight into instrument meteorological conditions (IMC)
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 › In-flight planning/decision, improper
  • Pilot in command › Proper altitude, not maintained
  • Pilot in command › VFR flight into imc, continued

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

NTSB narrative

THE HELICOPTER WAS DISPATCHED ON AN EMERG MED SVC (EMS/MED-EVAC) FLT TO TRANSPORT A PATIENT WITH SUBCRANIAL BLEEDING BACK TO A HOSPITAL IN WINSTON-SALEM. BFR TAKEOFF, THE PLT RECEIVED A WX BRIEFING. AT THAT TIME, WIDESPREAD IMC PREVAILEDTHRU-OUT THE AREA & VFR FLT WAS NOT RECOMMENDED. WHILE EN ROUTE, THE PLT CLIMBED TO 4500' MSL. IN THE LAST TRANSMISSION FROM THE ACFT (TO HOSPITAL DISPATCH), THE HELICOPTER WAS RPRTD TO BE APRX 12 MI FROM GALAX (THE DESTN). A WITNESS IN THAT AREA HEARD THE SOUND OF A HELICOPTER WHICH CEASED WITH A 'THUD' WHEN IT CRASHED. HE LOOKED IN THE DIRECTION OF THE NOISE, BUT HE COULD NOT SEE ANYTHING DUE TO FOG. THE WRECKAGE WAS FND APRX 10 MI SE OF GALAX. THE HELICOPTER HAD CRASHED JUST BELOW THE TOP OF A MTN RIDGE AT AN ELEV OF ABOUT 3500'. THERE WAS EVIDENCE THE HELICOPTER WAS IN ABOUT A 20 DEG RGT BANK WHEN IT CRASHED. NO PREIMPACT PART FAILURE OR MALFUNCTION WAS FND DURING THE INVESTIGATION.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record ATL86FA264
Event ID
20001213X34694
Case number
ATL86FA264
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: 5eaaed0661e1ae08825ec35c763075a06e4fd2bb684b88ba26dba79386dd5013; retrieved 2026-09-18T14:18:36.258Z.