NTSB CAROL · Event
Event WPR18LA152
Aircraft involved
Probable cause & findings
A vibration of the helicopter for reasons that could not be determined based on the available information, which resulted in a forced landing and the main rotor contacting the tailboom.
Factual narrative
On May 29, 2018, at 1045 mountain standard time, an MD Helicopters 369FF, N975BW, was substantially damaged when it was involved in an accident near Wikieup, Arizona. The pilot and the passenger were not injured. The helicopter was operated as a Title 14 Code of Federal Regulations Part 133 external load flight. The purpose of the flight was to assist power line construction. As the pilot was conducting a slow, left descending turn about 100 ft above ground level, the helicopter started to vibrate. The pilot increased the collective to arrest the rate of descent, but the vibration became more prominent. He then performed a forced landing; the helicopter impacted the ground, and a main rotor blade contacted the tailboom, which separated from the empennage. The pilot did not report any malfunctions with the engine nor any abnormal increase or decrease in main rotor rpm. The helicopter was manufactured in 1994 and had accumulated 6,713.5 hours total time at the time of the accident. Review of maintenance records indicated that the last 100-hour inspection was completed 63.1 hours before the accident flight. The last 300-hour inspection, main rotor damper attachment and weight loading extension check were completed 252.9 hours before the accident flight. The helicopter was equipped with a Rolls-Royce (Allison) 250-C30 turboshaft engine, serial number CAE-900135. The engine had accumulated 6,766.1 hours at the time of the accident. The last 150-hour engine inspection was performed 48.0 hours before the accident. Recovery personnel reported that all main rotor blades were attached to their respective pitch housings/lead-lag links and dampers by main rotor folding pins and attaching hardware. The airframe exhibited a small area of crushed and torn skin on the right side, and the lower fuselage skin was deformed below the left cabin door. The left and right landing gear struts and skid tubes appeared undamaged. The horizontal stabilizer, vertical stabilizers, and stinger exhibited no visible damage. All five main rotor blades exhibited trailing edge bond separation that was more pronounced in the first 3 ft outboard of the root fitting doublers and lessened along the blade span. One rotor blade exhibited blue/green paint transfer marks on the upper and lower surfaces on the leading-edge area near the root fitting and doubler. These paint marks corresponded to the blue/green paint found on the left inlet fairing. At the root end of the same blade, the leading edge and lower surface revealed paint transfer from contacting the upper wire strike arm mounted on the canopy frame. In addition, all laminates (straps) of the same blade strap assembly were fractured. The majority of the straps fractured about 5 inches inboard of the lead-lag bolt. The rotating swashplate scissor link was fractured, and the rotating swashplate was displaced in the lag direction. The upper hub displayed contact marks on the lag side from contact with the five pitch housings. The elastomeric dampers on three blades appeared normal. The fourth blade's elastomeric damper was pulled out of the damper housing. The fifth blade's elastomeric damper was detached from the housing and extended out of the housing about 3.5 inches. Drive continuity from the engine driveshaft to the main and tail rotor driveshaft was verified when the shaft was manually rotated. Tail rotor driveshaft continuity was established from the main transmission outboard to the separation point at the tailboom. Both tail rotor blades were undamaged. The tail rotor control rod was continuous from where it separated in the tail boom to the bellcrank at the tail rotor transmission. Control continuity was established from the cyclic and collective controls to the stationary swashplate. Anti-torque control continuity was verified from the anti-torque pedals to the separation point at the tailboom. Additionally, continuity was confirmed from the separated tailboom section to the tail rotor assembly pitch control. The fractured drive link, fractured strap pack assembly, and parts of engine air inlet fairing were examined at the NTSB Materials Laboratory. The examination revealed that the drive link attachment fitting fractured from overstress in tension, and each element of the tension-torsion strap pack fractured in overstress. There were no indications of other fracture modes, and no pre-existing cracking, corrosion, or other degradation was observed. The engine air inlet fairing sections also exhibited fractures consistent with overstress. Examination of the blue streaks on the outer surface of the fairing exhibited features consistent with paint transfer from the main rotor blade. For additional information, refer to the complete Materials Lab Factual Report contained in the public docket for this accident. The pilot was performing external load operations in the helicopter when he felt a vibration during a left descending turn. The pilot increased the collective to arrest the rate of descent, but the vibration became more prominent. He subsequently performed a forced landing, during which the helicopter impacted the ground and a main rotor blade contacted and severed the tailboom. The pilot did not report any malfunctions with the engine nor any abnormal increase or decrease in main rotor rpm. Postaccident examination revealed a fractured drive link and a fractured strap pack assembly. Examination of the fractured surfaces revealed signatures consistent with tensile overstress, most likely from the blade contacting the left inlet fairing after the helicopter impacted the ground. There was no other evidence of preimpact mechanical malfunctions or failures that would have precluded normal operation, and the reason for the vibration could not be determined based on the available information. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).
- C Not determined-Not determined-(general)-(general)-Unknown/Not determined - C
Verbatim from NTSB's published report. Source file
NTSB_2018_WPR18LA152.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (maintenance). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- Embry-Riddle Scholarly Commons 2026 · Journal article (IJAAA)
From Reactive to Predictive: A hybrid Trust-Mediated Adoption Framework for Data-Driven Maintenance in Distributed-Authority Aviation Environments
Modern aviation maintenance operates within increasingly data-intensive technological environments, yet the operational integration of predictive maintenance into routine decision-making remains incon…
- Semantic Scholar 2025 · Article (Applied Sciences)
Decision-Making Framework for Aviation Safety in Predictive Maintenance Strategies
The implementation of predictive maintenance (PM) in aviation presents unique challenges due to strict safety requirements, complex operational environments, and regulatory constraints.
- Embry-Riddle Scholarly Commons 2024 · Journal article (JAAER)
Low-Resource Automatic Speech Recognition Domain Adaptation – A Case-Study in Aviation Maintenance
With timeliness and efficiency being critical in the aviation maintenance industry, the need has been growing for smart technological solutions that optimize and streamline the different underlying ta…
- Embry-Riddle Scholarly Commons 2024 · Journal article (JAAER)
A New Trajectory in UAV Safety: Leveraging Reinforcement Learning for Distance Maintenance Under Wind Variations
In the field of aviation, safety is a critical cornerstone, and the operation of Unmanned Aerial Vehicle (UAV) systems is deeply connected with this principle.
- Embry-Riddle Scholarly Commons 2024 · Journal article (IJAAA)
Just Culture in Aviation: A Metaphorical Study on Aircraft Maintenance Students
Just Culture, a sub-dimension of safety culture, has been a prominent and debated topic in aviation safety in recent years.
- Embry-Riddle Scholarly Commons 2024 · Journal article (IJAAA)
Performance PRISM: A Comprehensive Framework For Performance Measurement In Aircraft Maintenance
Aircraft maintenance is governed by rigorous safety requirements and high operational complexity, demanding robust performance measurement frameworks to ensure optimal maintenance practices.
Browse the full corpus — academia portal ↗