FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR20LA228 · Md Helicopter 600 N

20 Jul 2020 · San Andreas, CA, United States

Brim Equipment Leasing Md Helicopter 600 N · Accident: fire/smoke (non-impact) while maneuvering

From Angels Camp, CA to Angels Camp, CA

Report a problem

Event

NTSB case
WPR20LA228
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
0 · 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
General aviation
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

Md Helicopter 600 N

Aircraft type
MD Helicopters 600
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
N745BW
Onboard fatalities
Unknown
Route
From Angels Camp, CATo Angels Camp, CA
Aircraft age
About 22 years (built 1998)
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 91: General Aviation
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
Maneuvering · low-altitude flying
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
Fire/smoke (non-impact)
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 propeller/rotor

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

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.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR20LA228
Event ID
20200720X84108
Case number
WPR20LA228
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, cause areas. 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: 40d20292ce9c07a5489e09b1bd592eb6ac2d45f1252b7308402c2f64f7bea1bd; retrieved 2026-09-16T12:12:35.836Z.