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

Bell 407 accident near Mount Baldy, California, September 4, 2022

On September 4, 2022 at about 2:57 pm local time, a 2001 Bell 407 (helicopter), registered N687AM, was substantially damaged in an accident during approach near Mount Baldy, California. It was an other work-use flight under general aviation rules (Part 91). 1 person was seriously injured. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot’s failure to ensure the throttle was properly positioned before commencing an approach to land, which resulted in a low rotor rpm condition and impact with terrain. Contributing to the accident was a worn throttle detent.

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

What the record shows

Date
September 4, 2022 · about 2:57 pm local time
Place
Mount Baldy, California · map
Type
Accident
Injuries
1 person was seriously injured.
Weather
visual conditions (good weather)
Aircraft
Bell 407, built 2001 · all 407s on the register
Registration
N687AM · registry record · serial 53497
Damage
Substantial damage
Flight
Other work-use flight · general aviation rules (Part 91)

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

The pilot was conducting flights to transport supplies and people about 4 miles between a lower altitude landing zone (LZ) and a high-altitude LZ. He was flying down-canyon to lose altitude and set up for a steep approach to the lower LZ. As he was maneuvering and slowing the helicopter to land, a low rotor rpm warning occurred. He saw the rotor rpm was about 95% and aborted the landing. He radioed ground personnel that he had a partial engine failure and was looking for a place to land. As he continued to fly down the canyon, he raised the collective and the low rotor rpm warning occurred again. He attempted to land in a clearing but overshot it and landed in trees. He said he did not check the throttle position during the event sequence, but he had maintained 100% main rotor rpm during each offload at the upper LZ. The engine control unit captured data consistent with main rotor impact. The data showed that during the 12 seconds before the fault, the power lever angle (PLA) readings were between 48° and 50° and the engine was operating consistent with those settings. The normal PLA reading when the throttle is in the FLY position is 70°, and full engine governing is available down to 62° PLA. The pilot’s operating handbook states that the throttle should be in the FLY position for takeoffs and landings. It also cautions that failure to position and maintain the throttle in the FLY detent position during normal flight operations can limit available engine power. There is a detent in the throttle that is engaged by a ball plunger when the throttle is rolled to the FLY position from either the Idle or Max Ng positions. The throttle was manipulated by hand during postaccident examination and, when the throttle was rolled down from the FLY position towards Idle, there was perceivably less tactile resistance than when the throttle was rolled from FLY to Max Ng. Testing of the throttle determined the ball plunger would disengage from the FLY position detent when 4 lb of the force was applied to turn the throttle. The helicopter maintenance manual states 14 to 15 lb of force should be required to move the throttle through the FLY detent position. Disassembly of the collective assembly revealed the detent where the ball plunger in the throttle engages at the FLY position was worn, which likely reduced the force required to move the throttle out of the FLY position towards IDLE. No other preimpact anomalies were found with the engine or airframe systems. Maintenance records indicted the throttle friction should have been verified in accordance with the manufacturer’s recommended inspection schedule and maintenance procedures. The procedures directed maintenance personnel to set throttle friction to the appropriate amount by adjusting the ball plunger on the throttle. Although the ball plunger disengaged from the FLY position detent in postaccident testing with less force than specified by the manufacturer, it could not be determined if maintenance personnel did not properly adjust the ball plunger in accordance with the manufacturer’s specified procedures, or if the worn detent reduced the ability of the ball plunger to maintain the correct torque after being set properly. Although the maintenance procedures did not require inspection of the throttle detent, if the specified throttle friction forces were unable to be achieved during the inspection, this should have provided the opportunity necessary for maintenance personnel to identify and correct the worn throttle detent. The accident is consistent with the pilot not ensuring the throttle was in the FLY detent position as the helicopter made an approach to land which resulted in reduced engine power, a low main rotor RPM condition, and subsequent impact with terrain. The worn throttle detent bracket likely contributed to the pilot unknowingly rolling the throttle towards idle prior to commencing the approach to land and subsequently not recognizing that the throttle had moved.

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. Aircraft inspection event during prior to flight
  2. Loss of control in flight during approach defining event

The NTSB's findings

  • Personnel issues › Task performance › Use of equip/info › Use of checklist › Pilot
  • Aircraft › Aircraft power plant › Engine controls › Power lever › Fatigue/wear/corrosion
  • Personnel issues › Task performance › Maintenance › Scheduled/routine maintenance › Maintenance personnel
  • Aircraft › Aircraft power plant › Engine controls › Power lever › Incorrect service/maintenance
  • Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot

Pilot

  • Certificate: flight instructor, commercial pilot, private
  • Ratings: single-engine sea; instructor: helicopter; instrument: helicopter; rotorcraft: helicopter
  • Flight time: 3,447 hours in all; 264 in this make and model; 28.3 in the last 90 days; 8 in the last 30 days; 3,309 as pilot in command
  • Last flight review: October 11, 2021
  • Medical certificate: Class 2 (with waivers/limitations)
  • Seat: rgt
  • Injury: serious injuries

The aircraft

  • Airframe total time: 6,943 hours
  • Last inspection: approved inspection programme, August 30, 2022; 42 hours since
  • Maximum gross weight: 5,250 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Allison M250-C47B (turboshaft); 2,815 hours total
  • Operator: Air Methods CORP

Weather at the time

  • Light: daylight
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 88°F (31°C), dew point 61°F (16°C)
  • Altimeter: 29.95 inHg
  • Observation at 8:15 am from KCCB, 8 miles away

Weather report (METAR): KCCB 041515Z AUTO 00000KT 10SM CLR 31/16 A2995 RMK AO2

Injuries

FatalSeriousMinorNone
Flight crew1

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

17 documents, released by the NTSB on August 21, 2024. 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.