The U.S. aircraft register, updated daily
Accidents · NTSB WPR20LA228 · Final report

Md Helicopter 600 accident near San Andreas, California, July 20, 2020

On July 20, 2020 at about 4:38 pm local time, a 1998 Md Helicopter 600, registered N745BW, was destroyed in an accident during maneuvering (low-alt flying) near San Andreas, California. It was an aerial observation flight under general aviation rules (Part 91). No one was hurt; 3 people were on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

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.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
July 20, 2020 · about 4:38 pm local time
Place
San Andreas, California · map
Type
Accident
Injuries
No one was hurt; 3 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Md Helicopter 600 N, built 1998
Registration
N745BW · no longer on the register · serial RN045
Damage
Destroyed
Flight
Aerial observation flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

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.

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

  1. Fire/smoke (non-impact) during maneuvering (low-alt flying) defining event
  2. Loss of engine power (total) during emergency descent
  3. Hard landing during landing
  4. Fire/smoke (post-impact) during post (impact)

The NTSB's findings

  • Aircraft › Aircraft propeller/rotor › Main rotor drive › Engine/transmission coupling › Malfunction

Pilot

  • Certificate: commercial pilot
  • Ratings: instructor: helicopter; instrument: helicopter; rotorcraft: helicopter
  • Flight time: 2,788 hours in all; 152 in this make and model; 114 in the last 90 days; 46 in the last 30 days; 2,725 as pilot in command; 108 on instruments
  • Last flight review: February 28, 2020
  • Medical certificate: Class 2 (without waivers/limitations)
  • Seat: left
  • Injury: no injuries

Passenger

  • Seat: rgt
  • Injury: no injuries

Passenger

  • Seat: rgt
  • Injury: no injuries

The aircraft

  • Airframe total time: 7,160.9 hours
  • Last inspection: approved inspection programme, June 25, 2020
  • Maximum gross weight: 4,100 lb
  • Seats: 8
  • Landing gear: fixed
  • Engine: Allison 250-C47 (turboshaft); 7,184 hours total
  • Fire on the ground
  • Operator: Brim Equipment Leasing Inc

The flight

  • Departed from: NA Angels Camp CA at 4:15 pm
  • Destination: NA Angels Camp CA

Weather at the time

  • Light: daylight
  • Sky: clear
  • Temperature: 77°F (25°C), dew point 48°F (9°C)
  • Altimeter: 29.98 inHg
  • Observation at 4:55 pm from CPU, 5 miles away

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers2

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.

Other NTSB records under N745BW the same tail number, which may have belonged to a different aircraft at the time

2016-02-05WPR16LA081 · accident near Ashland, OR · substantial damage · no injuries

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.