17 Sep 2010: ROBINSON HELICOPTER COMPANY R44 II — Lake Superior Helicopters

17 Sep 2010: ROBINSON HELICOPTER COMPANY R44 II (N145DM) — Lake Superior Helicopters

No fatalities • Duluth, MN, United States

Probable cause

The pilot's failure to identify and arrest the helicopter's descent due to spatial disorientation.

— NTSB Determination

Accident narrative

On September 17, 2010, about 0023 central daylight time, a Robinson R44 II helicopter, N145DM, piloted by a commercial pilot, was destroyed during an in-flight collision with the waters of Island Lake near Duluth, Minnesota. The flight was being conducted under 14 Code of Federal Regulations Part 91 without a flight plan. Night visual meteorological conditions prevailed. The pilot sustained minor injuries. The flight departed from a beach on Island Lake and was on the initial climbout at the time of the accident. The intended destination was Duluth International Airport (DLH), Duluth, Minnesota, which was located about 10 miles south of the accident site.

The pilot reported that he had flown from DLH to the beach site on Island Lake in order to show the helicopter to some prospective clients. After spending several hours, he decided to return to DLH. The pilot stated that he lifted off into a hover, and subsequently established a 600 foot-per-minute rate of climb at 60 knots airspeed to depart the area. As he climbed out, he reported a "sinking feeling in the seat all of a sudden," and noticed that the vertical speed indicator "started to dip down indicating a descent." His flight instruments indicated that the helicopter was at 60 knots airspeed and in level flight; "everything checked out." He increased engine power, but was still descending. The pilot referenced the flight instruments a second time and noted that "all indications showed level and 60 [knots]." He recalled thinking that the helicopter might have encountered a "microburst of some type." He added that he could not tell the helicopter's exact height above the water because of the night lighting conditions. The helicopter hit the water at about 60 knots. The pilot commented that he thought the helicopter was still higher off the water and, as a result, did not flare prior to impact.

A witness reported that the start and warm up were unremarkable. In addition, the liftoff and initial climb also appeared normal. He stated, "If the entire event took 10 seconds, only the last 2, showed concern as we could see the distance between the [helicopter's navigation] lights and the reflection in the water markedly become closer, ultimately converging." He noted that the helicopter appeared to be level and remain in controlled flight the entire time.

A post accident examination of the helicopter did not reveal any anomalies consistent with a pre impact failure or malfunction.

Weather conditions recorded at DLH, located about 10 miles south of the accident site, at 2355, included: Scattered clouds at 11,000 feet above ground level (agl), 10 miles visibility, and winds from 180 degrees at 4 knots. At 0055, conditions included: Broken clouds at 10,000 feet agl, 10 miles visibility, and wind from 240 degrees at 7 knots. The moon set at 0058, about 35 minutes after the accident. It was in a waxing gibbous phase, with 73 percent of the visible disk illuminated.

The witness commented that the "night was dark, but there was a distinguishable horizon." He did not feel that the conditions were "adverse" for the pilot's return flight.

The pilot informed Federal Aviation Administration (FAA) inspectors that he had executed a similar type of night departure in June; although, the night of the accident was darker. The pilot did not hold an instrument rating. However, he was reportedly working toward the rating and he had accumulated about 30 hours of instrument flight time.

Contributing factors

  • cause Pilot
  • cause Pilot
  • Effect on operation

Conditions

Weather
VMC, wind 240/07kt, 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.