FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA Helicopters Bell 412 accident

6 May 1989 · Girdwood, AK, United States

Bell 412 · Accident: airframe, component or system failure en route

From Valdez Pioneer Field (VDZ) to Ted Stevens Anchorage International Airport (ANC)

Report a problem

Event

NTSB case
ANC89FA069
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 412

Aircraft type
Bell 412
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
N524EH
Onboard fatalities
Unknown
Route
From Valdez Pioneer Field (VDZ), Valdez, AKTo Ted Stevens Anchorage International Airport (ANC), Anchorage, AK
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
Airframe, component or system failure
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

  • Other maintenance personnel › Maintenance, improper
  • Rotorcraft flight control, cyclic control › Disconnected

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

NTSB narrative

WHILE IFR AT 10,000 FEET OVER MOUNTAINOUS TERRAIN, THE HELCIOPTER EXPERIENCED VIOLENT VERTICAL VIBRATIONS, WHICH CONTINUED UNTIL THE CRASH-LANDING ABOUT FIVE MINUTES LATER. ON BOARD WEATHER RADAR WAS USED TO GUIDE THE HELICOPTER AROUND THE MOUNTAIN TOPS, WHICH WERE IN THE CLOUDS. AT ABOUT 200 FEET ABOVE THE GROUND, THE HELICOPTER CAUGHT FIRE, TAIL ROTOR CONTROL WAS LOST, BOTH ENGINES QUIT, AND CYCLIC CONTROL BECAME UNRESPONSIVE. THE HELICOPTER WAS DESTROYED BY POST-CRASH FIRE. ABOUT ONE HOUR OF FLT TIME EARLIER, THE HELICOPTER HAD UNDERGONE AN INSPECTION, DURING WHICH THE MAIN ROTOR FLIGHT CONTROL SYSTEM BOLTS HAD BEEN RETORQUED. ALL BUT ONE OF THESE BOLTS WERE FOUND IN THE WRECKAGE. HOWEVER, THE ROD END FOR THE MISSING BOLT WAS FOUND.

Probable cause

A MAIN ROTOR FLIGHT CONTROL BOLT (PART NUMBER 20-057-6-38D) CAME OUT OF ITS ROD END BEARING WHILE IN FLIGHT DUE TO THE BOLT BEING IMPROPERLY TORQUED DURING MAINTENANCE.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC89FA069
Event ID
20001213X28212
Case number
ANC89FA069
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: 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: 5034d99678e8d1e176966870568c6d5c0bb13c4f34a992a08e89ff83d0b39be0; retrieved 2026-09-18T19:12:01.054Z.
  • The NTSB's operator name is blank for N524EH; the operator shown is the name the NTSB records it doing business as.