# Accident 20030112001679A: Skrsky S61A, Glady, WV, January 12, 2003

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: January 12, 2003, 13:05 local time
- Place: Glady, WV
- Damage: Substantial damage
- Phase of flight: Hovering
- Operating rules: Rotorcraft external load (Part 133)
- Operator: NBEL
- Location: 38.7986° N, 79.7181° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=38.7986&lon=-79.7181&mi=10
- Aircraft: N8170V, a cancelled registration (https://openairdocs.org/deregistered/N8170V-2017-10-26) (OpenAirDocs)
- Registry model: Sikorsky S-61A (registry code 814210C, https://openairdocs.org/model/sikorsky-s-61a) (OpenAirDocs)
- Reported make and model: SKRSKY S61A
- Fatal injuries: 0
- Pilot flight hours: 17,000 total, 8,000 in this make and model, 180 in the last 90 days
- NTSB investigation: [NTSB NYC03LA037](https://openairdocs.org/ntsb/NYC03LA037) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20030112001679A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

(-23) PILOT STATED THAT HE LOST TAIL ROTOR CONTROL WHILE HOVERING ABOVE A FIELD AT AROUND 3600 FT MSL DURING A LOGGING OPERATION. ATTEMPTS TO RECOVER FROM THE RESULTING SPIN WILL FULL OPPOSITE PEDAL WAS INEFFECTIVE. POWER WAS REDUCED TO COUNTER THE SPIN AND THE AIRCRAFT SETTLED INTO TREES ADJACENT TO THE FIELD. THE AIRCRAFT RECEIVED SUBSTANTIAL DAMAGE. LOSS OF CONTROL WAS DUE TO THE BREAKAGE OF A CABLE WHICH CONTROLS TAIL ROTOR PITCH. ^PRIVACY DATA OMITTED^ (.19) ON JANUARY 12, 2003, ABOUT 1220 EASTERN STANDARD TIME, A SIKORSKY S-61A, N8170V, WAS SUBSTANTIALLY DAMAGED WHEN IT IMPACTED TERRAIN DURING A FORCED LANDING NEAR GLADY, WEST VIRGINIA. BOTH CERTIFICATED COMMERCIAL PILOTS SUSTAINED SERIOUS INJURIES. VISUAL METEOROLOGICAL CONDITIONS PREVAILED FOR THE COMMERCIAL LOGGING FLIGHT, AND A COMPANY FLIGHT PLAN WAS FILED FOR THE FLIGHT CONDUCTED UNDER 14 CFR PART 133. ACCORDING TO THE CREW, AFTER THE HELICOPTER CAME OUT OF MAINTENANCE, THE CAPTAIN AND FIRST OFFICER CONDUCTED A TEST FLIGHT, AND THEN FERRIED THE HELICOPTER TO THE AREA OF OPERATION. ON THE DAY OF THE ACCIDENT, THE FIRST OFFICER FLEW FLIGHTS ONE AND THREE, AND                                                                THE CAPTAIN FLEW FLIGHTS TWO AND FOUR. EACH FLIGHT LASTED ABOUT 1 HOUR 20 MINUTES, THE HELICOPTER WAS HOT REFUELED BETWEEN FLIGHTS, AND THE FLYING PILOT WOULD OCCUPY THE LEFT SEAT. DURING THE PREVIOUS FLIGHTS, NO FLIGHT CONTROL ANOMALIES WERE IDENTIFIED, AND ON THE ACCIDENT FLIGHT, THE CAPTAIN WAS IN THE LEFT SEAT AND FLYING THE HELICOPTER. AFTER COMPLETING APPROXIMATELY THE SEVENTH LOAD OF THE FLIGHT, THE CAPTAIN MANEUVERED THE HELICOPTER OVER THE GROUND TENDERS, AND ENTERED A 155-FOOT OUT OF GROUND EFFECT HOVER. THE TENDERS CONNECTED THE CHOKERS TO THE CARGO HOOK, AND CALLED "CLEAR." ABOUT THE SAME TIME, THE HELICOPTER STARTED A SLOW UNCOMMANDED YAW TO THE RIGHT. THE CAPTAIN APPLIED FULL LEFT PEDAL, RELEASED THE LOAD, AND THE GROUND TENDERS CALLED "KICK OUT." WITH FULL LEFT PEDAL APPLIED, THE HELICOPTER CONTINUED TO YAW RIGHT. DURING THE FIRST REVOLUTIONS, THE CAPTAIN IDENTIFIED A SMALL CLEAR AREA TO THE NORTH. THE AREA WAS APPROXIMATELY LEVEL WITH THE HELICOPTER, AND APPROXIMATELY 150 FEET AWAY ON A RIDGELINE. THE CAPTAIN TRIED TO MANEUVER THE HELICOPTER TO THE CLEAR AREA, BUT BY THE FOURTH REVOLUTIONS, THE YAW RATE HAD INCREASED DRASTICALLY, AND HELICOPTER CONTROLLABILITY BECAME A MAJOR ISSUE. THE FIRST OFFICER PLACED HIS LEFT HAND ON THE THROTTLES, AND THE CAPTAINED CALLED FOR ENGINES TO IDLE. THE CAPTAIN ENTERED AN AUTOROTATION, AND APPLIED FULL COLLECTIVE BEFORE ENTERING THE TREES. THE HELICOPTER IMPACTED THE GROUND, CAME TO REST UP RIGHT, AND BOTH PILOTS EXITED WITH THE ASSISTANCE OF ONE OF THE GROUND TENDERS. THE CREW ESTIMATED THEY HAD CONDUCTED 75 LOADS ON THE DAY OF THE ACCIDENT. IN ADDITION, THE FIRST OFFICER ESTIMATED THE WINDS WERE APPROXIMATELY 270 DEGREES AT 10 KNOTS. EXAMINATION OF THE ANTI-TORQUE FLIGHT CONTROL SYSTEM REVEALED THAT THE LEFT ANTI-TORQUE CONTROL CABLE WAS BROKEN. THE BREAK WAS IN THE AFT PART OF THE CABIN AND ASSOCIATED WITH A PULLEY ASSEMBLY. EXAMINATION OF THE CABLE BREAK REVEALED THAT SOME OF THE CABLE STRANDS WERE BENT REARWARD, AND DEFORMED. EXAMINATION OF THE CABLE FRACTURE SURFACES UNDER A STEREOMICROSCOPE REVEALED THAT SOME OF THE FRACTURES WERE IRREGULAR AND DEFORMED. EXAMINATION OF THE ASSOCIATED KEEPER PINS UNDER A STEREOMICROSCOPE REVEALED THAT BOTH PINS DISPLAYED WEAR MARKS, AND LIGHT SCRATCHES CONSISTENT WITH CONTROL CABLE CONTACT. THE ASSOCIATED PULLEY WAS INTACT. THE PULLEY CHANNEL CONTAINED AN OIL-BASED DEBRIS, AND CONTROL CABLE FRAGMENTS. EXAMINATION OF THE MAINTENANCE RECORDS REVEALED THE HELICOPTER HAD UNDERGONE EXTENSIVE REPAIRS BEFORE BEING RETURNED TO SERVICE ON JANUARY 11, 2003. WHILE IN MAINTENANCE, BOTH TAIL ROTOR CABLES WERE REMOVED AND THEN REINSTALLED ON JANUARY 9, 2003. AT THE TIME OF THE ACCIDENT THE HELICOPTER HAD APPROXIMATELY 8 HOURS OF FLIGHT TIME SINCE RETURNING TO SERVICE, AND 14,603 HOURS OF TOTAL FLIGHT TIME.

## The NTSB's investigation of this event (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB NYC03LA037](https://openairdocs.org/ntsb/NYC03LA037), Jan 12, 2003: Sikorsky S-61A (N8170V), Glady, WV, substantial damage. Probable cause: The improper installation of the left tailrotor control cable by company maintenance personnel.

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.
