Accident RotorWay Exec 90 N89678, Tuesday 4 January 2000
ASN logo
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 4 January 2000
Time:14:00 LT
Type:Silhouette image of generic EXEC model; specific model in this crash may look slightly different    
RotorWay Exec 90
Owner/operator:Cobb International
Registration: N89678
MSN: RI5026
Total airframe hrs:1537 hours
Engine model:Rotorway 162F
Fatalities:Fatalities: 0 / Occupants: 2
Other fatalities:0
Aircraft damage: Substantial
Location:CHANDLER, Arizona -   United States of America
Phase: Unknown
Departure airport:CHANDLER, AZ (P19)
Destination airport:
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
The flight was a familiarization for the private pilot, who was transitioning into this model of helicopter. An approach was being made to runway 03 when the instructor heard a loud bang from the engine compartment behind his back at an altitude of 100 feet. He stated that it felt like all engine power was lost. When the instructor saw the rotor rpm decreasing, he took control and initiated an autorotation to a soft sandy area. During the touchdown, the main rotor blades contacted the tail boom, and the tail rotor blades contacted the ground. The operator reported that a subsequent inspection determined that the secondary drive shaft fractured. Laboratory examination concluded that the shaft failed from fatigue, originating from galling sites introduced during the manufacturing process. The operator reported that a temperature strip on the bearing was noted to be darkened before the flight, but they were unsure if this information was determined independantly by either the CFI or the student. All other shafts in the operator's fleet were inspected and no additional suspect shafts were found.

Probable Cause: the fatigue fracture and separation of the secondary drive shaft, which resulted from the manufacturer's inadequate quality control process.

Accident investigation:
Investigating agency: NTSB
Report number: LAX00LA071
Status: Investigation completed
Duration: 3 years and 10 months
Download report: Final report



Revision history:

16-Oct-2022 06:16 ASN Update Bot Added

Corrections or additions? ... Edit this accident description

The Aviation Safety Network is an exclusive service provided by:
Quick Links:

CONNECT WITH US: FSF on social media FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2024 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314