ASN Wikibase Occurrence # 161332
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: | Wednesday 9 October 2013 |
Time: | 07:20 |
Type: | Bell 206L-3 LongRanger III |
Owner/operator: | Panther Helicopters Inc |
Registration: | N54LP |
MSN: | 51466 |
Year of manufacture: | 1991 |
Total airframe hrs: | 11238 hours |
Engine model: | Allison 250-C30 SER |
Fatalities: | Fatalities: 1 / Occupants: 4 |
Aircraft damage: | Substantial |
Category: | Accident |
Location: | 30 miles NE of Venice, LA in Block 108, Gulf of Mexico -
United States of America
|
Phase: | Take off |
Nature: | Offshore |
Departure airport: | MP107D, GM |
Destination airport: | Belle Chasse, LA (06LA) |
Investigating agency: | NTSB |
Confidence Rating: | Accident investigation report completed and information captured |
Narrative:As the helicopter departed from the oil platform’s helipad, witnesses heard a “pop” followed by a high-pitch screeching noise coming from the back of the engine. The helicopter nosed-over and dove into the water with the emergency floats extended. Examination of the engine revealed that one of the second-stage turbine disk blades had liberated due to a high-cycle fatigue (HCF) crack. The crack propagated until the blade separated due to material overload, which resulted in extensive damage to all of the third-stage turbine disk blades and most of the fourth-stage turbine disk blades. Metallurgical analysis of the liberated blade revealed no material anomalies.
According to the engine manufacturer, there was no history of second-stage turbine blade failure due to HCF at the same spanwise position as the accident blade. A dynamics analysis of the second-stage turbine wheel revealed no mode crossing within or above the normal engine operating range that would be consistent with HCF initiation at the point where the blade failed. Several potential failure scenarios were also evaluated; however, none yielded any evidence to support the blade failing as it did. The engine was not equipped with an engine-monitoring system that could have identified any anomalies that may have initiated the HCF crack or contributed to the failure of the second-stage turbine blade. Although the surviving passengers stated that the platform was not venting methane at the time of the accident and an eyewitness said he did not see methane being vented, platform operating records revealed that methane was being vented continuously on the day of the accident. However, the actual volume of methane released at the time of the accident and whether it was ingested into the engine on takeoff could not be determined. The HCF crack was a pre-existing condition and was not the result of a sudden ingestion of methane on the day of the accident.
A low-level of diphenhydramine, a sedating antihistamine, was detected in the pilot’s blood and urine, but it could not be determined if it impaired the pilot’s ability to operate the helicopter.
Probable Cause: A total loss of engine power due to the liberation of a second stage turbine blade near the blade root due to a high-cycle fatigue crack and subsequent overload. Although extensive testing and materials analysis was performed, the reason for crack initiation could not be determined.
Accident investigation:
|
| |
Investigating agency: | NTSB |
Report number: | CEN14FA004 |
Status: | Investigation completed |
Duration: | |
Download report: | Final report |
|
Sources:
NTSB
Location
Revision history:
Date/time | Contributor | Updates |
09-Oct-2013 17:28 |
gerard57 |
Added |
09-Oct-2013 17:29 |
harro |
Updated [Aircraft type, Location] |
09-Oct-2013 19:55 |
Geno |
Updated [Source] |
10-Oct-2013 06:19 |
gerard57 |
Updated [Aircraft type] |
11-Oct-2013 18:16 |
Geno |
Updated [Time, Aircraft type, Registration, Cn, Phase, Nature, Departure airport, Destination airport, Source] |
20-Jan-2016 17:29 |
Aerossurance |
Updated [Time, Nature, Destination airport, Source, Narrative] |
20-Jan-2016 17:32 |
Aerossurance |
Updated [Source] |
27-Sep-2016 13:28 |
Aerossurance |
Updated [Narrative] |
21-Dec-2016 19:28 |
ASN Update Bot |
Updated [Time, Damage, Category, Investigating agency] |
29-Nov-2017 09:17 |
ASN Update Bot |
Updated [Operator, Other fatalities, Departure airport, Destination airport, Source, Narrative] |
The Aviation Safety Network is an exclusive service provided by:
CONNECT WITH US:
©2024 Flight Safety Foundation