23 Sep 2011: BELL 206 B3 — Pathfinder Aviation

23 Sep 2011: BELL 206 B3 (N204PA) — Pathfinder Aviation

No fatalities • Seward, AK, United States

Probable cause

The pilot's failure to maintain clearance from snow-covered terrain during hover in deteriorating weather and flat light conditions, which resulted in a tail rotor strike.

— NTSB Determination

Accident narrative

On September 23, 2011, about 1330 Alaska daylight time, a high skid-equipped Bell 206B3 helicopter, N204PA, sustained substantial damage during a tail rotor strike while maneuvering to land on the Harding Ice Field, about 10 miles west of Seward, Alaska. The helicopter was owned and operated by Pathfinder Aviation, Homer, Alaska, as a visual flight rules (VFR) public use passenger flight, in conjunction with the National Park Service (NPS), under the provisions of 14 Code of Federal Regulations Part 135, when the accident occurred. The commercial pilot and the two passengers were not injured. Visual meteorological conditions prevailed at the time of departure, and company flight following procedures were in effect. The flight originated about 1320 from a remote site on the Harding Ice Field.

According to the Pilot/Operator Aircraft Accident Report (NTSB Form 6120.1) submitted by the operator, dated October 25, along with subsequent conversations with Pathfinder Aviation’s director of operations, the purpose of flight was to transport two NPS employees to a remote snow-covered site on the Harding Ice Field to collect snow samples. The mission required brief stops at various predetermined sites along a prearranged route. The director of operations noted that when the pilot departed from the previous site, en route to the next predetermined site, weather conditions were “good VFR.” As the flight progressed towards the upper elevations of the ice field, the pilot encountered overcast layers and flat light conditions. According to the director of operations, as the pilot slowed the helicopter to make a precautionary landing, and while on approach, “the aircraft touched down early.” After the initial touchdown, the pilot hovered-taxied the helicopter to an area about 20 or 30 yards beyond the initial touchdown point, then he landed the helicopter in the deep snow. After landing, the helicopter tipped backwards as the aft portion of the skids settled into the deep snow, and the tail rotor blades subsequently struck the snow. There were no preaccident mechanical problems reported with the helicopter.

In a written statement to the NTSB dated September 24, a passenger aboard the accident helicopter reported that while traveling from one landing site on the Harding Ice Field to another, visibility deteriorated rapidly, making it very difficult to discern any topographic features of the snow-covered ice field. He said that as the pilot began slowing the helicopter, he estimated the helicopter’s height above the ice to be 100 feet, and then the helicopter unexpectedly touched down. After the initial touchdown, the helicopter continued to hover momentarily, then the pilot immediately landed the helicopter, and it tipped backwards. Photos of the accident site were provided to the NTSB as part of the passenger’s written statement. The topographical features surrounding the accident site consisted of expansive, smooth, featureless, and snow-covered sloping terrain. According to Pathfinder Aviation’s director of operations, a company maintenance technician was flown by helicopter to the site to inspect the helicopter for damage before it could be ferried back to Seward. Finding no apparent damage, the helicopter was started, ground run, and then hovered. While hovering, a tail rotor driveshaft coupling separated, and the pilot did a hovering autorotation back to the snow-covered ice field. As a result, the helicopter sustained substantial damage to the tail rotor drive shaft assembly.

In the recommendations section of the NTSB 6120.1 form submitted by the operator, the director of operations noted that future pilot training would include formal flat light and whiteout training, as well as added training on judgment and decision making regarding weather.

Contributing factors

  • cause Pilot
  • Contributed to outcome
  • Contributed to outcome
  • Damaged/degraded
  • cause Altitude — Not attained/maintained
  • cause Pilot

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.