17 Mar 2009: BELL 206 L-1 — Air Evac Lifeteam

17 Mar 2009: BELL 206 L-1 (N595AE) — Air Evac Lifeteam

No fatalities • Springfield, IL, United States

Probable cause

The pilot's failure to maintain clearance from the parked helicopter.

— NTSB Determination

Accident narrative

HISTORY OF FLIGHT

On March 17, 2009, at 0138 central daylight time, a Bell 206L-1, N595AE, operated by Air Evac Lifeteam, struck a parked company Bell 206L-1, N101AE, with its main rotor blade(s) while maneuvering to a fuel pump located next to a company helipad. The maneuvering helicopter sustained minor damage. Night visual meteorological conditions prevailed at the time of the incident. The 14 CFR Part 91 emergency medical service repositioning flight was operating on a company visual flight rules flight plan. The pilot and two medical crewmembers, who were the only occupants, were uninjured. The flight last departed St. Johns Hospital, Springfield, Illinois, at 0131, en route to the company helipad.

On the night of the accident, the pilot arrived to work “a little bit earlier” and took a flight “right away." The incident flight was the second flight that he was scheduled to fly. The accident pilot picked up a patient and flew about 47 minutes to Springfield, Illinois, to drop the patient off, and then flew 7 minutes to the helicopter pad where the accident occurred, to refuel.

The pilot stated that there were two fuel tanks located at the landing pad, a north tank with a hose on the west side of the tank and a south tank. Aircraft “normally park” next to the north tank and obtain fuel. The other helicopter was parked in the northeast end of the pad where they “normally” parked because that’s where transient aircraft fuel from. While the pilot was landing the helicopter, an on-duty pilot on the ground made a radio transmission to tell the pilot that he had to use the south tank because the north tank was empty. According to the on duty pilot on the ground, the pilot had to get closer to the tank for the hose to reach. As the helicopter came into a hover, the accident pilot heard a “pop, pop, pop," which was the sound of the rotor blades striking the parked helicopter. The pilot thought the popping sound was from the skids contacting the pad because he was low. The pilot said that he did not experience any loss of controllability and “could have flown away” if he wanted.

When the pilot was asked if the length of the hose was such that he could have landed further away and unroll the hose, he responded that “in his mind, he was going to get close enough to the fuel.” He stated that he would have to pull the hose out and that it was “1:38 in the morning and second flight.” He didn’t think he was that close to the other helicopter. He reportedly followed the aircraft checklist and didn’t skip any of its procedures.

The pilot stated that it was a “good” night to fly with not much moon light. It was dark with good visibility and there were a lot of lights in the area. There was a hangar east of the pad estimated to be 400 feet away with a light on it that illuminated some of the pad and 2 foot tall amber colored lights on and around the pad. The amber lights are located around four corners of the pad and one on each of the center edges. The on duty pilot stated that he was going outside with a radio to “ground guide” the helicopter for its landing, but he had to go back inside because his radio battery died, at which time the helicopter collided with the parked helicopter. He said he tries to “ground guide” incoming helicopters by either using a radio or hand signals so that arriving pilots do not hit other helicopters while landing for purposes of safety and courtesy. He also said that the reason that he ground guides helicopters is not due to company policies/procedures but a continuance of military practices where a crew member or somebody that was close to the landing site would perform ground guiding. He believed that company personnel at the company’s West Plaines, Missouri, base and maybe some other bases, provide ground guiding.

Both helicopters sustained tip damage to their main rotor blades.

Both fuel tank fuel hoses were of equal length and could reach the opposite side of the helipad.

Contributing factors

  • cause Pilot
  • cause Response/compensation

Conditions

Weather
VMC, wind 190/08kt, 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.