Island Express Helicopters Aerospatiale AS-350-D accident
Aerospatiale AS-350-D · Accident: loss of engine power (total) on approach
From Long Beach, CA to Avalon, CA
Event
- NTSB case
- SEA08MA136
- 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
- 3 · all aircraft and ground
- Ground fatalities
- Unknown
- 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
- Charter & commuter
- 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
Aerospatiale AS-350-D
- Aircraft type
- Aerospatiale AS-350
- 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
- N67GE
- Operator
- Island Express Helicopters
- Onboard fatalities
- Unknown
- Route
- From Long Beach, CATo Avalon, CA
- 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 135: Air Taxi & Commuter
- 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
- Approach
- Defining eventThe 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
- Loss of engine power (total)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Aircraft › Aircraft power plant
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
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.\
Following the accident, Honeywell Aerospace issued Service Bulletins; LT 101-71-00-0252 and LTS101-71-00-0253. The Service Bulletins require the removal and inspection of the turbine assemblies, "To address a service related difficulty with Power Turbine Rotor Blade Part No. 4-141-084-06 cracking at the mid span of the airfoil that can lead to a blade separation and subsequent inability to maintain powered flight resulting in potential injuries and damage to the aircraft."
Additionally, two FAA Airworthiness Directives pertaining to this issue are pending.
Probable cause
Loss of engine power during approach for landing due to a fatigue fracture of a power turbine blade.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA08MA136
- Event ID
- 20080529X00746
- Case number
- SEA08MA136
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, coordinates. 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: 3df2cfd64880aed68b5fa97deeef299a644623274ff277145f617da40b0a0cd7; retrieved 2026-09-13T19:05:34.161Z.