WPR24FA200 · Robinson Helicopter Company R44 II
Robinson Helicopter Company R44 II · Accident en route
From King County International Airport - Boeing Field (BFI) to Coeur D'Alene Airport - Pappy Boyington Field (COE)
Event
- NTSB case
- WPR24FA200
- 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
- 2 · 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
Robinson Helicopter Company R44 II
- Aircraft type
- Robinson R44
- 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
- N323TT
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From King County International Airport - Boeing Field (BFI), Seattle, WATo Coeur D'Alene Airport - Pappy Boyington Field (COE), Cour d' Alene, ID
- Aircraft age
- About 1 year (built 2023)
- 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
- En route · cruise
- 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
- Unknown or undetermined
- 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 oper/perf/capability
- Aircraft › Aircraft power plant
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
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.
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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR24FA200
- Event ID
- 20240620194501
- Case number
- WPR24FA200
- 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, coordinates, 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: bdefef3800f9d72730347bfb91a9320172748a1f666b7145aafffc216e9fcd4e; retrieved 2026-09-15T08:19:15.524Z.