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

Robinson Helicopter Company R44 II accident near Mt. Baldy, California, December 29, 2016

On December 29, 2016 at about 7:31 pm local time, a 2003 Robinson Helicopter Company R44 II, registered N324RS, was substantially damaged in an accident during approach near Mt. Baldy, California. It was a personal flight under general aviation rules (Part 91). 1 person was seriously injured and 3 people had minor injuries. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot's failure to maintain main rotor speed during a low orbiting approach over a confined mountainous area. Contributing to the accident was the pilot's decision to attempt to land in an area that did not allow for a safe exit path under conditions near the limit of the helicopter’s performance capability.

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

What the record shows

Date
December 29, 2016 · about 7:31 pm local time
Place
Mt. Baldy, California · map
Type
Accident
Injuries
1 person was seriously injured and 3 people had minor injuries.
Weather
visual conditions (good weather)
Aircraft
Robinson Helicopter Company R44 II II, built 2003
Registration
N324RS · no longer on the register · serial 10067
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

The commercial pilot planned to land the helicopter at the top of a high mountain peak. Three passengers were onboard, and the helicopter was loaded just below its maximum gross weight. The enroute climb was uneventful, and after reaching the peak, the pilot performed an orbit over the landing site. While surveying his landing options, the helicopter's low rotor rpm warning horn sounded, and he corrected by lowering the collective and increasing engine power. The horn stopped, and he continued to circle the area while reviewing an engine limit manifold pressure chart and determining that he had enough engine power available to proceed. Hikers were close to his intended landing area, so he initiated an approach with a tailwind toward the lower face of a ridgeline with the intention of turning back to land into the wind. As he approached the landing spot, the low rotor rpm horn sounded again, and he lowered the collective. The helicopter descended rapidly, and due to terrain, there was no escape path, so he warned the passengers to brace for impact. The helicopter landed hard and sustained substantial damage. The helicopter was operating at the upper limit of its performance capabilities at the reported gross weight and calculated density altitude. Performance charts indicated that the helicopter would not have been able to hover at that altitude, and as such, a successful landing, while not impossible, would have been challenging. The activation of the warning horn during the initial orbit would have been another indication to the pilot that there was limited engine power available for landing. The pilot reported no preimpact mechanical malfunctions or failures with the airframe or engine that would have precluded normal operation, and the accident is consistent with the pilot's failure to maintain rotor rpm while operating near the helicopter's performance limits.

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. Loss of lift during approach defining event
  2. Attempted remediation/recovery during approach
  3. Loss of control in flight during approach
  4. Collision with terrain or object (not controlled flight into terrain) during uncontrolled descent

The NTSB's findings

  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Prop/rotor parameters › Not attained/maintained
  • cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • factor Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
  • factor Aircraft › Aircraft oper/perf/capability › Aircraft capability › (general) › Capability exceeded

Pilot

  • Certificate: flight instructor, commercial pilot
  • Ratings: instructor: instrument helicopter; instrument: helicopter; rotorcraft: helicopter
  • Flight time: 487 hours in all; 300 in this make and model; 2.5 in the last 90 days; 0.5 in the last 30 days; 461 as pilot in command
  • Last flight review: April 9, 2016
  • Medical certificate: Class 1 (with waivers/limitations)
  • Seat: left
  • Injury: serious injuries

The aircraft

  • Airframe total time: 789.4 hours
  • Last inspection: 100-hour inspection, December 10, 2016; 28 hours since
  • Maximum gross weight: 2,500 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming IO-540-AE1A5 (piston); 789 hours total

The flight

  • Departed from: FUL Fullerton CA at 7:00 pm
  • Destination: Mt. Baldy CA
  • Flight plan: none
  • A second pilot was aboard

Weather at the time

  • Light: daylight
  • Visibility: 10 statute miles
  • Sky: a few clouds at 18,000 ft
  • Temperature: 72°F (22°C), dew point 32°F (0°C)
  • Altimeter: 30.11 inHg
  • Observation at 7:53 pm from KONT, 13 miles away

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers3

Documents from the investigation the NTSB's docket: the evidence folder behind the report

8 documents, released by the NTSB on July 5, 2018. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

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.