NTSB CAROL · Event
Event WPR11GA431
Registry · N205WW
FAA Aircraft Registry record.
Make / Model
BELL 205A-1
Year of manufacture
1980 · 31 years old at event
TCDS
H1SW · BELL TEXTRON INC
Engine
HONEYWELL T5317B (1500 hp)
Seats / Engines
15 seats · 1 engine
Last airworthiness date
20140529
ADS-B equipped
Yes — Mode-S A1A69F
Registrant of record
BLADES LLC
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
The pilot's inability to adequately execute an emergency autorotation due to the flight's low altitude during external load operations, which resulted in a hard landing. Contributing to the accident was a torsionally overstressed tachometer shaft, which sent erroneous engine rpm readings to the cockpit.
Factual narrative
On September 4, 2011, about 1500 Pacific daylight time, a Bell 205 A1, N205WW, landed hard during an off field emergency autorotation near Tehachapi, California. The Kern County Fire Department was operating the helicopter as a public-use fire suppression flight under the provisions of 14 Code of Federal Regulations (CFR) Part 133. The commercial rated pilot sustained minor injuries; the helicopter sustained substantial damage to the tail boom from impact forces. A company visual flight rules (VFR) flight plan had been filed for the local flight.The helicopter had a water bucket as an external load, and the pilot was preparing to drop a load on the leading edge of the fire. The helicopter was about 100 feet above ground level (agl) at 10 knots, when the engine revolutions per minute (rpm) light illuminated, and the low rotor rpm horn sounded. The pilot released the water, and made a left pedal turn to exit the canyon and move away from the fire. He checked his engine rotor rpm gauge and saw that the needles had split. The rotor rpm needle was at the 4-5 o'clock position, and the engine rpm needle was at the 6-o'clock position, which he stated indicated maximum rpm. The helicopter was now about 400 feet agl, and the pilot spotted a landing zone for a landing. He perceived that the helicopter had a high side fuel control failure. He rolled off the throttle, and lowered the collective. After he placed the governor switch into manual mode, he rolled the throttle on while raising the collective. He felt the rotor rpm decrease as he pulled the collective, and saw that the gauge was at 90 percent. He was 250-300 feet agl, and felt that he was running out of altitude and rpm, so he lowered the collective to regain rpm, and established an autorotation into the landing zone. After landing hard, which collapsed the landing skids, the pilot closed the throttle, turned off the fuel switches, and checked for fire/warning lights. He exited the helicopter to stop approaching civilians. Once he felt the area was secure, he checked for fire and assessed the damage. The helicopter sustained substantial damage to the airframe and tail boom. He reentered the cockpit, and reset the switches to post flight mode out of habit, and assessed the interior damage. The helicopter was recovered to the operator's facility in Renton, Washington. An investigator from the engine manufacturer examined the engine under the supervision of the FAA. He confirmed both N1 and N2 control continuity from the pilot's seat to the engine, and observed that both controls traveled from stop to stop. The only anomaly discovered was a sheared N2 tachometer drive shaft. A specialist from the National Transportation Safety Board's Materials Laboratory examined the N2 shaft. He determined that the shaft failed as a result of torsional overstress. The N2 tachometer drive delivers engine rpm readings to the cockpit engine tachometer; failure of the N2 tachometer drive would send erroneous engine rpm readings to the cockpit. The pilot's instruments indicated that there was an engine overspeed, but the warning lights and audio were indicating a low power condition. The emergency procedures section of the flight manual states that in the event of an engine failure or low rotor rpm, a red light will illuminate and an audio signal will sound when the audio switch is in the AUDIO position. The flight manual instructs the pilot to immediately execute an autorotative descent. During an external load operation to drop water on a fire, the helicopter was about 100 feet above ground level at 10 knots when the engine rpm light illuminated and the low rotor rpm horn sounded. The emergency procedures section of the flight manual states that in the event of an engine failure or low rpm, a red light will illuminate and an audio signal will sound when the audio switch is in the AUDIO position. The flight manual instructs the pilot to immediately execute an autorotative descent. The pilot released the water, and made a left-pedal turn to exit the canyon and move away from the fire. He checked his engine rotor rpm gauge and saw that the needles had split: the rotor needle was at the 4-5 o'clock position, and the engine needle was at the 6-o'clock position, which he stated indicated maximum rpm. He maneuvered to establish an autorotation into a landing zone. The helicopter sustained substantial damage to the airframe and tail boom as the result of a hard landing, which collapsed the landing skid. Postaccident examination discovered that the N2 tachometer drive shaft was sheered as a result of torsional overstress. The N2 tachometer drive delivers engine rpm readings to the cockpit engine tachometer; failure of the N2 tachometer drive would send erroneous engine rpm readings to the cockpit. Accordingly, the pilot's instruments indicated that there was an engine overspeed, but the warning lights and audio were indicating a low power condition. The pilot elected to perform an autorotative landing in accordance with the flight manual instructions for a low rotor rpm. 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).
- F Aircraft-Aircraft power plant-Engine indicating system-Power indicating system-Malfunction - F
- C Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Landing flare-Incorrect use/operation - C
- C Personnel issues-Task performance-Use of equip/info-Aircraft control-Pilot - C
Verbatim from NTSB's published report. Source file
NTSB_2011_WPR11GA431.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 (engine failure). 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 2015 · Conference paper
International Air Transport Association Vision 2050 Report Assessment
The International Air Transport Associations report Vision 2050 report addresses how the aviation industry members participating in the Vision 2050 will work towards meeting combined established goals…
- Embry-Riddle Scholarly Commons 2002 · Journal article (JAAER)
A Fanciful Look at Air Carrier Operations in the Year 2050
Captain Lance Boyle smiled as he felt the smooth rippling thunk of the landing gear tires meeting the runway. Now that was how aircraft should land, not this vertical takeoff and landing nonsense empl…
- arXiv 2022 · arXiv preprint
Multi-level Adaptation for Automatic Landing with Engine Failure under Turbulent Weather
This paper addresses efficient feasibility evaluation of possible emergency landing sites, online navigation, and path following for automatic landing under engine-out failure subject to turbulent wea…
- NASA NTRS 2019 · Conference Paper
Simulation of Liquid Rocket Engine Failure Propagation Using Self-Evolving Scenarios
Traditional probabilistic risk assessment approaches often require failure scenarios to be explicitly defined through event sequences that are then quantified as part of the integrated analysis.
- NASA NTRS 2019 · Conference Paper
Rocket engine failure detection using system identification techiques
The theoretical foundation and application of two univariate failure detection algorithms to Space Shuttle Main Engine (SSME) test firing data is presented.
- NASA NTRS 2019 · Conference Paper
Rocket engine failure detection using system identification techniques
The theoretical foundation and application of two univariate failure detection algorithms to Space Shuttle Main Engine (SSME) test firing data is presented.
Browse the full corpus — academia portal ↗