Aerospatiale AS-350-D accident near Avalon, California, May 24, 2008
On May 24, 2008 at about 4:20 pm local time, a Aerospatiale AS-350-D (helicopter), registered N67GE, was destroyed in an accident during approach near Avalon, California. It was flown under charter and air-taxi rules (Part 135). 3 people were killed and 3 people were seriously injured. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
Loss of engine power during approach for landing due to a fatigue fracture of a power turbine blade.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- May 24, 2008 · about 4:20 pm local time
- Place
- Avalon, California · map
- Type
- Accident
- Injuries
- 3 people were killed and 3 people were seriously injured.
- Weather
- visual conditions (good weather)
- Aircraft
- Aerospatiale AS-350-D · all AS-350-Ds on the register
- Registration
- N67GE · no longer on the register · serial 1640
- Damage
- Destroyed
- Flight
- Flight · charter and air-taxi rules (Part 135)
The NTSB's narrative final · quoted from the NTSB record
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.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Loss of engine power (total) during approach defining event
- Off-field or emergency landing during emergency descent
- Autorotation Collision with terrain or object (not controlled flight into terrain)
The NTSB's findings
- cause Aircraft › Aircraft power plant › Engine (turbine/turboprop) › Turbine section › Failure
- cause Aircraft › Aircraft power plant › Engine (turbine/turboprop) › Turbine section › Fatigue/wear/corrosion
Pilot
- Certificate: commercial pilot
- Ratings: single-engine land; instructor: helicopter; instrument: helicopter; rotorcraft: helicopter
- Flight time: 5,692 hours in all; 3,942 in this make and model
- Last flight review: April 29, 2008
- Medical certificate: Class 2 (without waivers/limitations)
- Seat: rgt
- Injury: fatal
The aircraft
- Airframe total time: 9,687 hours
- Last inspection: 100-hour inspection, May 20, 2008; 7 hours since
- Maximum gross weight: 4,300 lb
- Seats: 7
- Landing gear: fixed
- Engine: Lycoming LTS - 101 (turboshaft); 0 hours total
- Fire on the ground
The flight
- Departed from: Long Beach CA at 4:07 pm
- Destination: Avalon CA
Weather at the time
- Light: daylight
- Wind: from 080° at 3 knots
- Visibility: 10 statute miles
- Sky: broken clouds at 1,500 ft
- Temperature: 48°F (9°C), dew point 46°F (8°C)
- Altimeter: 29.95 inHg
- Observation at 4:28 pm from AVX, 5 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 2 | 3 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
