ANC92FA159 · Hughes 369D
Hughes 369D · Accident: airframe, component or system failure en route
From CRYSTAL CR LODG, AK to KOKWOK RIVER, AK
Event
- NTSB case
- ANC92FA159
- 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
Hughes 369D
- Aircraft type
- Hughes 369
- 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
- N8697F
- Operator
- Eberle, Terrance · private individual
- Onboard fatalities
- Unknown
- Route
- From CRYSTAL CR LODG, AKTo KOKWOK RIVER, 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 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
- 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
- Substantial
Cause areas
- Rotor system, tail rotor blade abrasion strip › Separation
- Rotor system, tail rotor blade › Separation
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
SHORTLY AFTER TAKEOFF, AT 1,000 FT AGL, THE PILOT EXPERIENCED AIRFRAME VIBRATION AND A GRINDING SOUND. HE ENTERED AUTOROTATION, AND AT 200 FT AGL THE TAIL ROTOR AND PART OF THE T/R GEAR BOX SEPARATED FROM THE HELICOPTER. IT THEN ROTATED APPROXIMATELY 720 DEG AND IMPACTED THE GROUND. ONE OF THE T/R BLADES WAS MISSING THE ABRASION STRIP. AN AIRWORTHINESS DIRECTIVE (AD) & SERVICE BULLETIN (SB) WERE IN EFFECT DIRECTING INSTALLATION OF RIVETS WITHIN 300 HRS TO PREVENT POSSIBLE LOSS OF TAILROTOR CONTROL. DUE TO SEASONAL USE, HELICOPTER HAD LESS THAN 160 HRS SINCE ISSUANCE OF THE AD. TAIL ROTOR BLADE FOUND INTACT WAS 40% DEBONDED, BUT WOULD PASS A 'TAP TEST' IAW MANUFACTURER'S SB. FAILED BLADE ESTIMATED TO BE 90% DEBONDED. DAILY VISUAL INSPECTION REQUIRED BY SB REPORTEDLY DID NOT DETECT DEBONDING IN PROGRESS.
Probable cause
THE SEPARATION OF THE TAIL ROTOR ABRASION STRIP AND THE SUBSEQUENT TOTAL LOSS OF THE TAIL ROTOR. FACTORS CONTRIBUTING TO THE ACCIDENT WERE: INSUFFICIENT MANUFACTURER'S MAINTENANCE DESIGN CHANGES, INADEQUATE AIRCRAFT EQUIPMENT DESIGN BY THE MANUFACTURER AND INSUFFICIENT STANDARDS OF THE FAA CERTIFICATION ORGANIZATION.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC92FA159
- Event ID
- 20001211X15553
- Case number
- ANC92FA159
- 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: 2e71fabf1ed927c18e59faf9ba17293f8d423cd4d4df11bae09f140eeed3a8d9; retrieved 2026-09-21T14:44:14.515Z.