ASN Wikibase Occurrence # 19946
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: | Saturday 24 May 2008 |
| Time: | 09:20 |
| Type: |  Aérospatiale AS 350D Ecureuil |
| Owner/operator: | Island Express Helicopters |
| Registration: | N67GE |
| MSN: | 1604 |
| Year of manufacture: | 1984 |
| Total airframe hrs: | 9687 hours |
| Engine model: | Lycoming LTS - 101 |
| Fatalities: | Fatalities: 3 / Occupants: 6 |
| Aircraft damage: | Destroyed |
| Category: | Accident |
| Location: | Two Harbors, Santa Catalina Island, CA -
 United States of America
|
| Phase: | Approach |
| Nature: | Passenger - Non-Scheduled/charter/Air Taxi |
| Departure airport: | Long Beach, CA |
| Avalon, CA | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
The helicopter was descending to the planned destination during the on-demand air taxi flight when witnesses reported hearing a loud pop, followed by flames emitting from the back of the engine. The helicopter subsequently collided with the ground.
A surviving passenger reported that just after the loud pop, the pilot told passengers that he was going to autorotate. The helicopter entered a descent at an altitude witnesses on the ground estimated at 200 to 400 feet above ground level. During the descent, the pilot had to clear numerous obstacles, including buildings and power lines, to reach an open field located beyond the obstacles but short of the normal landing area. The ground witnesses stated that the helicopter was in an area near the shoreline when they witnessed the flames and heard the loud pop; however, the exact location in reference to the shoreline could not be determined.
Since the pilot stated to passengers that he was going to autorotate, it is likely that the helicopter experienced a loss of power after the loud pop. In the event of a loss of engine power, the pilot must enter an autorotation by immediately reducing the collective pitch to maintain main rotor speed to avoid a main rotor stall. The collective pitch must be reduced to the point required to maintain, or regain a safe main rotor speed. This would allow the pilot to maintain sufficient rotor speed while maneuvering to a suitable landing area, and to arrest the descent when needed. If the main rotor blades stall, this will ultimately result in a loss of control and uncontrolled descent.
Because of the relatively low altitude at which the loss of power occurred, it is likely that the accident pilot had to trade rotor rpm to maintain the altitude needed to clear the obstacles and reach the open field. This would have resulted in a lack of sufficient rotor rpm to arrest the helicopter’s descent rate as it approached the ground. Further, examination of the main rotor blades at the accident scene did not show evidence of high rotational energy at impact.
Postaccident inspection of the turbine engine revealed localized damage to four consecutive power turbine blades. Two of the blades were fractured transversely across the airfoil above the blade root platform and two were fractured higher up their respective airfoils near the blade tips. Generalized damage was observed to the remaining power turbine blades; however, all blades were in place and remained secured to the power turbine wheel. A Safety Board materials engineer's examination of the fractured blades revealed striation features typical of fatigue cracking on the pressure (concave) side of the airfoil. The fatigue crack features emanated from the boundary area between the base material and a casting pin. Further analysis disclosed that the fracture was the result of fatigue cracking that emanated from two platinum casting pins on the pressure side of the blade adjacent to the platform. The fracture face of the blade contained isolated regions of fatigue cracking that were separated by fracture regions and showed oxidation damage consistent with fatigue. Additional testing of the fractured blade(s) indicated that the microstructure in the airfoil portions showed no evidence of operation above a temperature profile expected for this stage of the engine. The fracture features of the remaining turbine blades were consistent with overstress separation.
Review of maintenance records indicated that, the engine's cycle counting process, inspection requirements, and compliance with airworthiness directives and service bulletins were all satisfactory. More specifically, due to the power turbine blade failures, the life and maintenance history of the power turbine rotor, including the power turbine blades, were assessed. The information contained in the maintenance records, as well as the information provided by the manufacturer on the history and inspection requirements of the power turbine blades showed that they were operated in accordance with the requirements set forth by the manufacturer.
Probable Cause: Loss of engine power during approach for landing due to a fatigue fracture of a power turbine blade [of the Honeywell LTS101-600A engine].
Accident investigation:
 |
|
Sources:
NTSB
FAA register: 2. FAA: http://registry.faa.gov/aircraftinquiry/NNum_Results.aspx?omni=Home-N-Number&nNumberTxt=67GE
Location
Images:
(c) NTSB
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 25-May-2008 07:40 | plane freak | Added |
| 25-May-2008 07:44 | harro | Updated |
| 25-May-2008 07:45 | harro | Updated |
| 27-May-2008 11:19 | harro | Updated |
| 13-Jul-2009 11:53 | harro | Updated |
| 18-Jul-2014 18:11 | Dr. John Smith | Updated [Time, Location, Departure airport, Destination airport, Source, Narrative] |
| 08-Sep-2014 19:21 | Aerossurance | Updated [Phase, Nature, Source, Narrative] |
| 21-Dec-2016 19:14 | ASN Update Bot | Updated [Time, Damage, Category, Investigating agency] |
| 21-Dec-2016 19:16 | ASN Update Bot | Updated [Time, Damage, Category, Investigating agency] |
| 21-Dec-2016 19:20 | ASN Update Bot | Updated [Time, Damage, Category, Investigating agency] |
| 03-Dec-2017 10:48 | ASN Update Bot | Updated [Cn, Operator, Other fatalities, Departure airport, Destination airport, Source, Narrative] |
| 13-Feb-2021 17:24 | Aerossurance | Updated [Other fatalities, Location, Source, Narrative] |
| 28-Jan-2022 21:31 | BEAVERSPOTTER | Updated [Aircraft type, Cn, Country, Source] |
| 15-Jun-2022 15:31 | Ron Averes | Updated [Country] |
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