WPR24FA200

NTSB accident investigation · Robinson Helicopter R44 II · Bluestem, WA · June 19, 2024

Accident · FatalClass 3 · FieldFinal report
Date
June 19, 2024, 16:20 local (23:20 UTC)
Place
Bluestem, WA
Injuries
2 fatal
Damage
Destroyed
Phase of flight
Enroute
Aircraft
N323TTRobinson Helicopter R44 II
Defining event
Enroute-cruise: Unknown or undetermined
Weather
Visual (VMC) · Day
Status
Completed · report May 21, 2026
Report
Approved by Office Director
Investigation class
Class 3
NTSB office
Western Pacific Region
Parties
Robinson Helicopters, Lycoming Engines, Federal Aviation Administration
FAA report
20240619009029A
Case key
194501

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.

On this page

Probable cause

The pilot’s failure to manage main rotor rpm during an autorotation, which resulted in a loss of helicopter control. Contributing to the accident was a loss of power for reasons that could not be determined.

Findings · 3

NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.

Engine (reciprocating)Aircraft › Aircraft power plant · Unknown/Not determinedRobinson Helicopter R44 II: 5 casesAll aircraft: 497 casesProbable cause
Performance/control parameters: prop/rotor parametersAircraft › Aircraft oper/perf/capability · Not attained/maintainedRobinson Helicopter R44 II: 17 casesAll aircraft: 182 casesProbable cause

Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.

Analysis

The pilot and pilot-rated passenger were returning the helicopter to its home airport after it had undergone routine maintenance, which included the installation of a fuel flow transducer. While in day visual meteorological conditions (VMC), in cruise flight, and about 745 ft above ground level (agl), the helicopter entered a descent. During the descent, the main rotor blades impacted the tailcone, severing the empennage, while about the same time the main rotor’s pitch horns and control rod ends fractured and separated. The lack of tail rotor and main rotor components resulted in a total loss of helicopter control. The helicopter impacted terrain at a high descent rate in a nose-high attitude as evidenced by the flattening and upward bending of the tailcone and the fracturing of the engine case. A postaccident fire destroyed most of the wreckage. Examination of the wreckage revealed evidence of a total loss of engine power as indicated by the lack of rotational scoring on the upper sheave and the undamaged section of the engine cooling fan. Main rotor blade impact with the tailcone and damage to the main rotor system were indicative of main rotor blade blow back and stall due to low rotor rpm. Examination of the freewheeling unit (sprag clutch) revealed normal operation. Multiple B-nuts on the fuel lines associated with the transducer and fuel servo were found loose; however, due to the thermal exposure, it could not be determined if the loss of torque to the B-nuts was due to heat damage or other factors. The pilot was a highly experienced airplane pilot but had only accumulated about 350 hours of flight experience in helicopters. Based on the helicopter’s altitude and the wreckage signatures, after the loss of total power the pilot likely did not reflexively and simultaneously lower the collective, apply aft cyclic, and trim the helicopter to enter an autorotation while in cruise flight, and/or improperly managed the rotor rpm during the remainder of the autorotation. The lack of timely action allowed the main rotor rpm to reduce to an unrecoverable speed and likely resulted in the main rotor blades stalling, as detailed in the manufacturer’s Safety Notices and FAA guidance documents. The reason for the pilot’s failure to manage rotor rpm during an autorotation could not be determined. According to a Safety Notice published by the manufacturer, pilots with many hours of flight experience in airplanes and fewer hours experience in helicopters may instinctively make flight control inputs that are inappropriate for helicopters, which can result in catastrophic consequences.

Factual narrative

Robinson Safety Notice SN-10, Fatal Accidents Caused by Low RPM Rotor Stall, issued in October 1982, and revised in February 1989 and June 1994, states: A primary cause of fatal accidents in light helicopters is failure to maintain rotor rpm. To avoid this, every pilot must have his reflexes conditioned so he will instantly add throttle and lower collective to maintain rpm in any emergency…Power available from the engine is directly proportional to rpm. If the rpm drops 10%, there is 10% less power. With less power, the helicopter will start to settle, and if the collective is raised to stop it from settling, the rpm will be pulled down even lower, causing the ship to settle even faster. If the pilot not only fails to lower collective, but instead pulls up on the collective to keep the ship from going down, the rotor will stall almost immediately. When it stalls, the blades will either “blow back” and cut off the tailcone or it will just stop flying, allowing the helicopter to fall at an extreme rate. In either case, the resulting crash is likely to be fatal. No matter what causes the low rotor rpm, the pilot must first roll on throttle and lower the collective simultaneously to recover rpm before investigating the problem. It must be a conditioned reflex. In forward flight, applying aft cyclic to bleed off airspeed will also help recover lost rpm. Robinson Safety Notice SN-24 (“Low RPM Rotor Stall Can be Fatal”), issued in September 1986, and revised in June 1994, states: When the rotor stalls, it does not do so symmetrically because any forward airspeed of the helicopter will produce a higher airflow on the advancing blade than on the retreating blade. This causes the retreating blade to stall first, allowing it to dive as it goes aft while the advancing blade is still climbing as it goes forward. The resulting low aft blade and high forward blade become a rapid aft tilting of the rotor disc sometimes referred to as “rotor blow-back.” Also, as the helicopter begins to fall, the upward flow of air under the tail surfaces tends to pitch the aircraft nose-down. These two effects, combined with aft cyclic by the pilot attempting to keep the nose from dropping, will frequently allow the rotor blades to blow back and chop off the tailboom as the stalled helicopter falls. Robinson Safety Notice SN-29 (“Airplane Pilots High Risk When Flying Helicopters”), issued in March 1993, and revised in June 1994, states: There have been a number of fatal accidents involving experienced pilots who have many hours in airplanes but with limited experience flying helicopters. The ingrained reactions of an experienced airplane pilot can be deadly when flying a helicopter. The airplane pilot may fly the helicopter well when doing normal maneuvers under ordinary conditions when there is time to think about the proper control response. But when required to react suddenly under unexpected circumstances, he may revert to his airplane reactions and commit a fatal error…Forexample, in an airplane his reaction to a warning horn (stall) would be to immediately go forward with the stick and add power. In a helicopter, application of forward stick when the pilot hears a horn (low rpm) would drive the rpm even lower and could result in rotor stall, especially if he also “adds power” (up collective). The FAA Helicopter Flying Handbook (FAA-H-8083-21B) states: The pilot should immediately apply simultaneous down collective, aft cyclic and trim the helicopter for entry into an autorotation initiated at cruise airspeed. If rotor rpm has been allowed to decrease, or has inadvertently decreased below acceptable limits, an application of aft cyclic may help rebuild rotor rpm. This application of aft cyclic must be made at least at a moderate rate and may be combined with a turn, either left or right, to increase airflow through the rotor system. This will work to increase rotor rpm. Care should be maintained to not over-speed the rotor system as this is attempted. According to the maintenance facility’s director of maintenance, the helicopter was at their facility for an annual inspection and other maintenance that included replacement of the horizontal stabilizer. The replacement stabilizer had not arrived and was not replaced. A review of the maintenance records revealed that the maintenance included the installation of a left electronic ignition system fixed timing module and a right magneto. A JP Instruments (JPI) fuel flow indicating system and a JPI fuel flow transducer were installed. The fuel flow transducer was mounted between the throttle body and the fuel flow divider. On June 19, 2024, about 1620 Pacific daylight time, a Robinson Helicopters R-44 II, N323TT, was destroyed when it was involved in an accident near Bluestem, Washington. The pilot and pilot-rated passenger were fatally injured. The helicopter was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. According to the owner, the helicopter was at a maintenance facility at Boeing Field/King County International Airport (BFI), Seattle, Washington, where it underwent an annual inspection and other maintenance. The owner asked the accident pilot to travel to BFI and return the helicopter to Coeur d’Alene/Pappy Boyington Field (COE), Coeur d’Alene, Idaho. The owner was also acquainted with the pilot-rated passenger but knew nothing about the details of the flight plan. According to an acquaintance and trainee of the accident pilot, he flew the pilot and the pilot-rated passenger to BFI in his personal airplane. Once at BFI, he observed the pilot conduct a preflight inspection of the helicopter, and he saw a fuel truck top off the helicopter. The acquaintance departed BFI after the helicopter departed. While en route, he saw the helicopter and observed no indication of a problem. The acquaintance did not follow the same flight route as the helicopter and did not stop at Bowers Field (ELN), Ellensburg, Washington. He described the returnflight weather as high clouds and no visibility restrictions, and the temperature was comfortable, but the ride was a little choppy. FAA ADS-B data did not record the helicopter’s departure from BFI. ADS-B data, provided by a commercial source, showed that the helicopter departed BFI around 1338, climbed to a maximum altitude of about 2,000 ft mean sea level (msl), passed eastward over the Snoqualmie Pass, and proceeded directly to ELN. FAA ADS-B data first recorded the helicopter when it was about 10.5 miles northwest of ELN. The helicopter proceeded directly to the parking ramp, where it arrived about 1437. A fuel receipt from the ELN fixed-base operator recorded 14.38 gallons of 100LL fuel purchased for the helicopter. The helicopter departed ELN around 1511, climbed to a maximum altitude of about 3,927 ft msl, and proceeded northeast, consistent with flight toward COE. The helicopter generally maintained about 80 to 100 kts ground speed for most of the flight. The helicopter slowed momentarily when it neared Ephrata Municipal Airport (EPH), Ephrata, Washington, but accelerated back to about 80 to 100 kts after passing the airport. Although there were minor changes in heading and the ground speed varied, there were no indications of notable maneuvering during the 1 hour, 21-minute flight. ADS-B data revealed that, about one quarter mile southwest of the accident site, the helicopter began to decelerate from 85 kts to 55 kts at the last recorded data point, about 3,050 ft msl (745 ft agl) and about 40 ft west of the accident site. No witnesses came forward to provide first-hand accounts of the accident. An autopsy of the pilot was performed by the Spokane County Medical Examiner, Spokane, Washington. The cause of death was blunt force injuries. A weather study revealed that the synoptic conditions indicated no frontal boundaries in the immediate vicinity of the accident site and a weak pressure gradient, which resulted in light and variable winds over eastern Washington. The closest weather observations to the accident site reported low instrument meteorological conditions (IMC) to IMC during the morning hours due to low ceilings and visibilities in fog before 0840, which cleared to VMC around the time of the accident. Conditions were reported as light and variable wind, visibility 10 statute miles or more, clear skies below 12,000 ft, with temperatures near 70°F. A high-resolution rapid refresh (HRRR) numerical model wind profile depicted a near surface wind from 040° at 6 kts with little variation in direction or speed through 5,000 ft. Above 5,000 ft, the wind shifted to the west with slowly increasing wind speed with height. Between 8,600 and 11,200 ft, the sounding depicted a potential for light turbulence due to a change in wind direction and an increase in wind speed. The pilot’s personal logbooks were not available for review. The pilot reported on his last medical examination 21,300 total flight hours and 50 flight hours in the last 6months. According to the owner of Inland Helicopters, Spokane, Washington, the accident pilot was a contract flight instructor for his company. The employer estimated that the accident pilot accrued at least 250 to 350 hours of flight experience in Robinson helicopters and held the Special Federal Aviation Regulations number 73 (SFAR 73) endorsement for the R-44. The company owner reported that the accident pilot initially provided flight instruction training to the helicopter owner as part of the pilot’s employment with the company, but that the training developed into personal flight training that was no longer associated with his company. The helicopter impacted open, hilly terrain and came to rest upright at the first point of impact, on a heading of about 086°, at an elevation of 2,182 ft msl. A postaccident fire destroyed most of the wreckage (see figure 1). Figure 1. Main wreckage (Source: Robinson Helicopters). The empennage, including the tail rotor gearbox, tail rotor assembly, and about two ft of the tailcone, separated from the helicopter and was about 338 ft southwest of the fuselage (see figure 2). Examination of the empennage revealed no indication of smoke or soot deposits. Figure 2. Helicopter empennage, including the tail rotor gearbox and tail rotor assembly. Postaccident examination of the main wreckage revealed the attached section of the tailcone exhibited an overall flattened deformity and an upward “scorpion” bending. Both main rotor blades exhibited a significant downward bending along with chordwise creases. One main rotor blade exhibited a color transfer on the leading edge that matched the color of the paint on the tailcone. The main rotor hub surface, adjacent to the main rotor blades, had small arc-shaped scuff marks through the paint, consistent with upward coning and contact of the blade grips with the hub. Each of the elastomeric teeter stops exhibited deep impact marks. One spindle tusk exhibited bending, consistent with excessive downward movement of the parent spindle and blade. The aft section of one of the main landing gear skids was bent upward to about 45°. The left-seat flight controls were installed. Examination of the engine revealed multiple fractures of the engine case, along with extensive thermal damage. The engine cooling fan exhibited upward crushing with no rotational signatures on the non-impacted top section of the fan. The upper sheave exhibited deep score marks and dents, along with a buildup of material at the end of one deep score mark that showed movement in the direction opposite of normal rotation. Most of the external components of the engine were extensively thermally damaged. Spark plug examination revealed some exhibited normal color when compared with a Champion Check-A-Plug chart, some exhibited impact damage, and at least one exhibited white color and some corrosion. All fuel injectors were unobstructed. The fuel servo was thermally damaged. All lines normally connected to thefuel servo were thermally damaged and separated, except for the line from the fuel flow transducer to the flow divider, which remained attached to the fuel servo. Multiple B-nuts from the fuel lines that were associated with the fuel flow transducer and fuel servo could be turned by hand. Thermal damage precluded further examination.

Aircraft

Registration
N323TT
Reported as
Robinson Helicopter R44 II
Category
Helicopter
Serial number
14626
Built
2023
Airframe hours
60
Engine
Lycoming IO-540-AE1A5, reciprocating
Damage
Destroyed
Fire
On-Ground
Flight
Personal · Part 91
Airworthiness certificate
Standard, Normal
Last inspection
Annual · June 4, 2024
Departed
BFI · Seattle, WA
Destination
COE · Cour d' Alene, ID
Equipment
Electronic primary flight display, Electronic multifunction display, Auto-pilot, ADS-B, Video recording device

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

Flight crew · 2

As NTSB recorded them. NTSB leaves out names.

Role
Pilot
Age
68
Injuries
Fatal
Certificates
Commercial, Airline transport
Airplane ratings
Single-engine sea, Multi-engine land, Single-engine land
Instrument ratings
Helicopter, Airplane
Medical
Class 2, With waivers/limitations
Seat
Right
Restraint
4-point
Toxicology
Performed
Flight hours
21,300 total · 300 in this make and model
Role
Pilot-rated passenger
Age
63
Injuries
Fatal
Certificate
Private
Airplane ratings
Single-engine sea, Single-engine land
Medical
Class 2, With waivers/limitations
Seat
Left
Restraint
4-point
Toxicology
Performed

Weather

Conditions
Visual (VMC) · Day
Wind
30° at 6 knots
Visibility
10 statute miles
Lowest ceiling
None
Temperature
72 °F, dew point 36 °F
Altimeter
30.05 inHg
Observed at
KSKA, 21 nm away
METAR
KSKA 192355Z 03006KT 10SM CLR 22/02 A3005 RMK AO2A SLP170 T02170019 10222 20155 56007 $

Docket · 12

The files NTSB released with the investigation on May 21, 2026, on NTSB’s docket system: statements, records, photos and specialists’ reports. 24.7 MB in all.

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.