FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX92LA319 · Bell UH-1B

28 Jul 1992 · Hayfork, CA, United States

Northwest Helicopters Bell UH-1B · Accident: airframe, component or system failure while maneuvering

Show on map Search Wikipedia NTSB source dataset
Report a problem

Event

NTSB case
LAX92LA319
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 UH-1B

Aircraft type
Bell UH-1
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
N89NW
Onboard fatalities
Unknown
Route
From not recordedTo 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 133: Rotorcraft Ext. Load
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
Maneuvering · hover
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
Substantial

Cause areas

  • Company maintenance personnel › Maintenance, installation, improper
  • Lubricating system, oil seal › Leak
  • Lubricating system, oil seal › Loose
  • Rotor drive system, engine to transmission drive › Failure, total
  • Rotor drive system, engine to transmission drive › Overtemperature

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

NTSB narrative

THE PILOT HAD JUST DROPPED OFF A LOAD OF LOGS AND WAS EN ROUTE BACK TO THE CUTTING AREA WHEN HE HEARD A LOUD BANG CONCURRENT WITH A LEFT YAW AND A RAPID LOSS OF ROTOR SPEED. THE PILOT ENTERED AN AUTOROTATION AND COLLIDED WITH TREES DURING THE DESCENT. EXAMINATION REVEALED THAT THE MAIN ROTOR DRIVE SHAFT HAD FAILED. EXAMINATION OF THE SHAFT REVEALED EVIDENCE OF A LOSS OF GREASE FROM THE SHAFT'S BOOT, WHICH RESULTED IN AN OVERHEATING CONDITION AND CATASTROPHIC FAILURE OF THE UNIT. THE 'O' RING, WHICH PROVIDES THE GREASE SEAL FOR THE SHAFT BOOT, WAS FOUND DEFORMED WITH EVIDENCE THAT GREASE HAD BEEN SLUNG FROM THE BOOT. THE MAIN ROTOR DRIVE SHAFT HAD BEEN REMOVED FOR MAINTENANCE AND REPLACED THREE DAYS AND 6 HOURS PRIOR TO THE ACCIDENT. THE MAINTENANCE INSTRUCTIONS CALL FOR A NEW 'O' RING TO BE INSTALLED WHEN THE DRIVE SHAFT AND BOOT ARE REASSEMBLED. ACORDING TO THE BELL LABORATORY, THE 'O' RING APPEARED TO HAVE NOT BEEN REPLACED.

Probable cause

THE FAILURE OF THE MAIN ROTOR DRIVE SHAFT DUE TO THE IMPROPER INSTALLATION BY COMPANY MAINTENANCE PERSONNEL OF AN 'O' RING SEAL, WHICH ALLOWED THE PACKING GREASE TO ESCAPE AND CAUSED THE OVER TEMPERATURE FAILURE OF THE DRIVE SHAFT. A FACTOR IN THE ACCIDENT WAS THE LACK OF SUITABLE TERRAIN IN WHICH TO PERFORM AN AUTOROTATION.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX92LA319
Event ID
20001211X15211
Case number
LAX92LA319
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: b2c84d9b63997bb81a2d751e2cd9d62af18382f2c62578b82d672fee8398e91a; retrieved 2026-09-21T23:11:47.631Z.