ASN Wikibase Occurrence # 238441
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: | Monday 20 July 2020 |
| Time: | 09:38 LT |
| Type: |  MD Helicopters MD 600N |
| Owner/operator: | Brim Equipment Leasing Inc |
| Registration: | N745BW |
| MSN: | RN045 |
| Year of manufacture: | 1998 |
| Total airframe hrs: | 7160 hours |
| Engine model: | Allison 250-C47 |
| Fatalities: | Fatalities: 0 / Occupants: 3 |
| Aircraft damage: | Destroyed |
| Category: | Accident |
| Location: | near San Andreas, Calaveras County, CA -
 United States of America
|
| Phase: | Landing |
| Nature: | Survey |
| Departure airport: | Angels Camp, CA |
| Angels Camp, CA | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
During low-altitude operations to visually assess power lines, the pilot and front seat passenger detected smoke in the cockpit when the helicopter was about 250 ft above ground level. The pilot elected to make a precautionary landing and rapidly lowered the collective. When the helicopter descended to an altitude of about 30 ft above ground level, the engine lost power. The helicopter then yawed to the left and landed hard, which caused the right landing gear to fail. A postaccident fire ensued and consumed most of the fuselage and tailboom.
Postaccident examination of the airframe revealed that most of the fuselage, tailboom, and cabin interior was destroyed due to extensive thermal damage. Flight control continuity could not be confirmed due to the thermal damage to the fuselage.
Examination of the engine revealed no mechanical malfunctions or failures that would have precluded normal operation. Data recovered from the engine control unit revealed primary exceedance messages for a main rotor droop, which was followed almost immediately by an engine surge then a flameout. Immediately after the main rotor droop, the torque and fuel flow dropped to zero, which was consistent with a complete loss of load. Additionally, the engine control unit data showed that the rotational speed of the engine rose above the rotational speed of the main rotor, which was consistent with a break in the main rotor drive system.
Examination of the main rotor drive system revealed the overrunning clutch subassembly remained attached to the power takeoff gear shaft on one end but had separated from the interconnecting driveshaft at the inner race output shaft. The output shaft of the overrunning clutch inner race fractured at the output bearing, which resulted in a loss of torque to the transmission and the main rotor system and a loss of load to the engine.
The output shaft deformed and fractured due to high-temperature overstress at the output bearing. The highest heat, which was localized to the area around the output bearing inner race, was not from the postaccident fire because the overall pattern of heating, scoring, and deformation was consistent with frictional heating from a failure of the output bearing. That failure caused the output bearing to seize and spin on the clutch inner race. The flakes of stainless steel found between the balls, cage, and outer race were likely remnants of the stainless-steel insert that was part of the grease seal, and the accumulation of the flakes between the balls indicated the seal failed before the bearing seized.
A review of maintenance documents revealed that the bearing was inspected and repacked with grease as required by the manufacturer.
Probable Cause: The failure of the output shaft of the overrunning clutch inner race due to frictional overheating of the shaft, which resulted from the failure of the output bearing's stainless-steel grease seal.
Accident investigation:
 |
|
Sources:
NTSB WPR20LA228
History of this aircraft
Other occurrences involving this aircraft
| 12 October 2009 | N613BP | U.S. Department of Homeland Security | 0 | San Diego, CA | |
sub |
| Heavy landing | ||||||
| 5 February 2016 | N745BW | Private | 0 | Ashland, OR | |
sub |
Location
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 21-Jul-2020 01:25 | Geno | Added |
| 21-Jul-2020 02:55 | RobertMB | Updated [Aircraft type, Operator, Location, Source, Narrative] |
| 21-Jul-2020 13:33 | RobertMB | Updated [Registration, Cn, Operator, Source, Narrative] |
| 21-Jul-2020 22:42 | Captain Adam | Updated [Location, Narrative] |
| 03-Mar-2021 21:06 | rudy | Updated [Nature] |
| 21-Aug-2022 19:15 | ASN Update Bot | Updated [Time, Operator, Other fatalities, Nature, Departure airport, Destination airport, Source, Narrative, Category, Accident report] |
| 21-Aug-2022 19:28 | harro | Updated [Other fatalities, Departure airport, Destination airport, Source, Narrative] |
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