NTSB CAROL · Event
Event CEN16LA294
Registry · N975BH
FAA Aircraft Registry record.
Make / Model
BELL 47G-2
Seats / Engines
3 seats · 1 engine
Last airworthiness date
19841108
ADS-B equipped
Yes — Mode-S AD9659
Registrant of record
ANDERSON CHRISTOPHER T
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
The loosening and separation of the throttle linkage nut, which resulted in a loss of throttle control and subsequent hard landing after autorotation.
Factual narrative
On July 30, 2016, about 1500 central daylight time (CDT), a Bell 47 G2, N975BH, experienced a loss of engine power control during descent into Whittman Regional Airport (KOSH), Oshkosh, Wisconsin. The helicopter sustained substantial damage to the main rotor blades and tail. The airline transport-rated pilot and two passengers on-board were not injured. The helicopter was privately registered and operated by the Experimental Aircraft Association (EAA) under the provisions of 14 Code of Federal Regulations Part 136 as a commercial air tour flight. Visual meteorological conditions prevailed for the flight, and no flight plan was filed. The local flight originated at Pioneer Airport (WS17), Oshkosh, Wisconsin. The pilot explained that tour flights departed from Pioneer Airport (WS17), part of the Oshkosh Airport Complex, and flew over the EAA AirVenture Fly-In grounds then returned to the airport. Upon return to the airport, the pilot entered the downwind leg of the pattern and attempted to reduce power for landing. The power would only decrease to 3100rpm. The throttle was moved 'full travel' with no power change. The pilot explained that he wanted to maintain the collective to avoid over speeding the engine, but was unable to slow or descend. He switched to the right magneto and applied full carburetor heat to reduce the engine power; however, the power did not reduce enough to descend. After flying the traffic pattern "several times" attempting to descend, the pilot described putting the helicopter into a slip with the right pedal. He stated it was the only way to descend because when the pedals were in a neutral position the helicopter would climb with the engine still producing full power. He circled at the end of runway 9 to descend in altitude, getting to approximately 100 feet agl before shutting off the ignition and conducting a low altitude auto rotation. The helicopter impacted the ground "hard" on the back side of the skids, the main rotor blade struck the tail and the tail rotor assembly separated from the tail boom. The helicopter skidded to the left side of the runway and came to rest in the grass. The pilot stated there were no indications of a flight control problem in prior flights the day of the accident, or during the accident flight until returning to the airport at the completion of the tour. The pilot indicated a complete overhaul of the helicopter was completed 37.6 hours before the accident flight. An on-scene inspection of the helicopter by the FAA and NTSB personnel revealed the throttle linkage nut had loosened and separated from its fitting, this separation would result in complete loss of throttle control. The maintenance manual for the Bell 47 G-2 did not specify a torque value for this nut given there were no maintenance procedures requiring the nut to be loosened or removed. The airline transport pilot maneuvered the helicopter on the downwind leg of the airport traffic pattern and attempted to reduce power for landing; however, the engine power remained excessively high. The pilot attempted to further reduce the engine power by turning off one magneto and applying carburetor heat, but the power remained too high to safely descend. The pilot then entered a sideslip, which allowed the helicopter to descend to about 100 ft above the runway. He turned the engine power off and autorotated to the ground. The helicopter landed hard in a tail-low attitude. The main rotor struck the tail and the tail rotor assembly separated from the helicopter. A postaccident examination found that the throttle linkage nut had loosened and separated from its fitting, causing the throttle to remain open. The helicopter's maintenance manual did not specify a torque value for the throttle linkage nut, and there were no maintenance procedures requiring the nut to be loosened or removed during overhaul. The pilot indicated that a complete overhaul of the helicopter was completed about 37 hours before the accident flight. 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 Aircraft-Aircraft power plant-Engine controls-Power lever-Inoperative - C
Verbatim from NTSB's published report. Source file
NTSB_2016_CEN16LA294.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 ↗