27 Sep 2011: BELL 47D1 — Lee Haley

27 Sep 2011: BELL 47D1 (N9158R) — Lee Haley

No fatalities • Ahwahnee, CA, United States

Probable cause

The pilot’s failure to maintain adequate main rotor rpm during the landing approach, which resulted in a loss of control.

— NTSB Determination

Accident narrative

On September 27, 2011, at 1030 Pacific daylight time, a Bell 47D1, N9158R, collided with trees while descending near Ahwahnee, California. The helicopter was being operated under the provisions of Title 14 Code of Federal Regulations Part 91. The helicopter was substantially damaged. The private pilot sustained serious injuries, and the passenger sustained minor injuries. Visual meteorological conditions prevailed and no flight plan was filed. The pilot departed about 1020 for the local area flight.

The Federal Aviation Administration (FAA) accident coordinator responded to the accident site. The helicopter had impacted terrain in a nose down attitude and the tail and tail rotor systems were resting upright against a tree.

The pilot submitted a written statement on May 14, 2012. He reported that he was conducting a run on landing and the rotor revolutions per minute (RPM) decreased. He turned away from the trees hoping to recover the RPM. The helicopter then settled into a tree. He said that there were no mechanical malfunctions or failures.

In an interview with the NTSB investigator, the passenger said that he had been maintaining the helicopter for about 5 years. The owner had reported what he surmised to be a problem with the number one bearing being loose on the tail rotor drive shaft. Additionally, they had previously installed an oil filter and they were going to change the oil lines. The pilot and mechanic completed the pre-flight inspection and review and noted no problems with the tail rotor drive shaft. They decided to take the helicopter on a short flight to warm the oil. The mechanic had flown with the pilot previously and had no concerns about his operation of the helicopter.

They departed from the private landing pad which was located at the pilot's residence. They flew for about 15 minutes with no problems noted. They returned to the area of the landing pad which was surrounded by trees and terrain. The helicopter gradually descended and the mechanic told the pilot that he did not think they were going to maintain clearance from a large tree to the west of their position. About 10 yards from the tree, they were below treetop level and the power [rotor RPM] continued to decrease while the helicopter descended. The pilot attempted to pull out of the landing to avoid the tree and turned the helicopter to the right while increasing collective. The helicopter then collided with the tree. The mechanic had flown in and out of the area with the pilot multiple times. He felt on this occasion, due to the confined area there were no options to recover the helicopter prior to impact with the tree. The mechanic indicated that no mechanical malfunctions occurred.

A witness was working as a fire lookout in Miami Mountain Fire Lookout Tower, which was located about 1 mile from the accident site. She heard the helicopter and saw a cloud of dust appear. The helicopter ascended out of the dust cloud and flew approximately 500 feet above ground level down a valley. The helicopter then turned and appeared to be returning to the landing pad. The landing pad was surrounded by trees and houses. As the helicopter approached the landing pad, it made a gradual descent while almost coming to a stop. She then saw the tail move from left to right, and the helicopter quickly descended and impacted a tree. The wind was calm at the time. There was no postimpact fire. She immediately called emergency response personnel.

Contributing factors

  • cause Prop/rotor parameters — Not attained/maintained
  • cause Pilot
  • Contributed to outcome

Conditions

Weather
VMC, vis 10sm

Loading the flight search…

What you can do on Flight Finder

  • Search flights between any two airports with live fares.
  • By aircraft — pick a plane model (e.g. Boeing 787, Airbus A350) and see every route it flies from your origin.
  • Route map — click any airport worldwide to explore its destinations, or draw a radius to find nearby airports.
  • Global aviation safety — aviation accident database, 5,200+ records since 1980, with map and rankings by aircraft and operator.
  • NTSB safety feed — recent U.S. aviation accidents and incidents from the official NTSB CAROL database, updated daily.

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.