ASN Wikibase Occurrence # 145393
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information.
If you feel this information is incomplete or incorrect, you can submit corrected information.
| Date: | Tuesday 17 April 2012 |
| Time: | 11:55 LT |
| Type: |  Sikorsky S-76B |
| Owner/operator: | RDC Marine Inc |
| Registration: | N56RD |
| MSN: | 760368 |
| Year of manufacture: | 1991 |
| Total airframe hrs: | 4376 hours |
| Engine model: | P&W PT6 SERIES |
| Fatalities: | Fatalities: 0 / Occupants: 7 |
| Aircraft damage: | Substantial |
| Location: | MODU Joe Douglas, Vermilion VR376A, Gulf of Mexico -
 United States of America
|
| Phase: | Landing |
| Nature: | Offshore |
| Departure airport: | New Iberia, LA (ARA) |
| MODU Joe Douglas, Vermilion VR376A | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
Four days before the accident flight, the accident helicopter experienced an intermittent loss of power to the No. 2 engine that lasted about 10 to 20 seconds while it was in cruise flight. The pilot described the event as a "rollback" but was uncertain as to how much power the engine actually lost during the event. He reported that the No. 2 engine reestablished power by itself. When he arrived at his destination, he shut down the helicopter and checked for any fault codes generated by the electronic engine control (EEC) units. No faults were recorded. He then performed ground and hover checks, and the helicopter appeared to be operating normally. He continued to fly and completed another two flights to oil platforms that same day. The next day the pilot flew another three flights without incident. A mechanic checked for fault codes, but none were recorded. The helicopter was released for flight with no further ground or flight checks. Because the pilot continued to fly the helicopter without determining the reason for the intermittent loss of engine power, the risk of another engine power loss remained high.
On the day of the accident, the pilot departed for an oil platform with six passengers and full fuel. The postaccident calculated takeoff weight was about 515 pounds over the maximum gross weight. The postaccident calculated weight of the helicopter during the approach to the oil platform was about 55 pounds below the maximum gross weight. Although the helicopter was within weight limits during the approach, its higher gross weight as compared to what it would have weighed if the pilot had loaded it within limits for the departure decreased its performance capability. The closest surface weather station, located 21 miles away, indicated that the wind was from 070 degrees at 5 knots at the time of the accident, but the pilot believed his last GPS reading of the wind was from 220 degrees at 5 to 6 knots. The pilot flew a visual approach to the oil platform on a 190-degree heading, which limited the go-around potential since it was on a direct course for the oil platform's super structure. The pilot reported that the helicopter was about 60 feet from and 15 to 20 feet above the landing pad with a nose-high attitude in the flare when there was a loss of engine power. The pilot was unsure which engine had the loss of power. With the loss of power, the pilot realized that the trajectory of the helicopter placed it short of the landing pad and that the helicopter was going to hit the platform. He pulled collective pitch and moved the cyclic control aft and to the left to clear the platform. Once clear of the platform, he attempted to lower the collective and gain airspeed, but the helicopter was in a high rate of descent with low airspeed. He pulled collective pitch and flared the helicopter before water impact. The pilot reported that it was about 3 to 4 seconds from the time he maneuvered to avoid hitting the platform to water impact. The helicopter remained on top of the surface as the pilot kept power on the helicopter to keep it from sinking. He deployed the emergency floatation bags and attempted to water taxi toward the oil platform, but there was no directional control since the tail boom was partially separated from the fuselage. All personnel were rescued without injury.
The examination of the wreckage revealed an anomaly within the stepper motor for the No. 2 engine's fuel control. The examination revealed that the end of the output shaft of the stepper motor had overstress fractures and that the shaft was bent. During the overhaul of the stepper motor 8 years before the accident, the pin that attaches the flapper valve lever to the output shaft was pressed onto the output shaft. The force applied to the external lever was sufficient to both crack and bend the output shaft. This condition eventually resulted in a "stuck" stepper motor which limited the fuel flow to the engine and resulted in an intermittent loss of engine power. The EECs did not monitor the performance of the output shaft or the flapper.
Probable Cause: The intermittent loss of engine power due to a "stuck" stepper motor in the No. 2 engine's fuel control as a result of an inadequate overhaul.
Contributing to the accident was the pilot's decision to continue flying the helicopter with a known defect, his decision to depart with the helicopter over its maximum gross weight, and his decision to fly the approach to the oil platform at a high gross weight in a direction that provided limited go-around potential.
Accident investigation:
 |
|
Sources:
NTSB
http://aerossurance.com/?p=1882
Location
Media:
Bizarre 2012 US S-76B Ditching https://t.co/YglnuVVNcF #flightsafety pic.twitter.com/GqXEeRxLqZ
— Aerossurance (@Aerossurance) November 2, 2016
#OTD 2012: An overweight #helicopter, flown with a known defect, ditched during a poorly executed approach to a GOM drilling rig, then water taxying was attempted and the tail was chopped off…https://t.co/YglnuVEbO5 #accident #aviationsafety #flightsafety #ntsb pic.twitter.com/f3wDYos0Pk
— Aerossurance (@Aerossurance) April 17, 2021
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 02-May-2012 17:44 | Geno | Added |
| 14-Sep-2012 06:21 | TB | Updated [Location, Destination airport, Source, Damage, Narrative] |
| 22-Dec-2014 14:50 | Aerossurance | Updated [Location, Nature, Destination airport, Source, Narrative] |
| 23-Dec-2014 13:00 | Aerossurance | Updated [Location, Source, Narrative] |
| 22-Mar-2015 14:30 | TB | Updated [Location] |
| 30-Sep-2016 17:29 | Aerossurance | Updated [Narrative] |
| 21-Dec-2016 19:28 | ASN Update Bot | Updated [Time, Damage, Category, Investigating agency] |
| 27-Nov-2017 20:36 | ASN Update Bot | Updated [Operator, Other fatalities, Nature, Departure airport, Destination airport, Source, Narrative] |
| 10-Dec-2018 21:59 | Aerossurance | Updated [Time, Operator, Other fatalities, Location, Destination airport, Source, Narrative] |
| 13-Feb-2021 17:44 | Aerossurance | Updated [Location, Embed code] |
| 17-Apr-2021 08:14 | Aerossurance | Updated [Embed code] |
Corrections or additions? ... Edit this accident description
The Aviation Safety Network is an exclusive service provided by:
Quick Links:
| ASN Home | Send Correction / Feedback |
| FSF Home | Disclaimer | Copyright |
| Contact Us | Privacy Policy |
| Press / Media |
CONNECT WITH US:
©2024 Flight Safety Foundation