Wirestrike Accident Bell 206L-1 LongRanger II N5734M,
ASN logo
ASN Wikibase Occurrence # 44555
 
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information.

Date:Monday 21 February 2005
Time:13:39
Type:Silhouette image of generic B06 model; specific model in this crash may look slightly different    
Bell 206L-1 LongRanger II
Owner/operator:Air Evac Lifeteam
Registration: N5734M
MSN: 45449
Year of manufacture:1980
Total airframe hrs:23135 hours
Fatalities:Fatalities: 1 / Occupants: 4
Aircraft damage: Substantial
Category:Accident
Location:Gentry, AK -   United States of America
Phase: Take off
Nature:Ambulance
Departure airport:Gentry, AR
Destination airport:Springdale, AR
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
Narrative:
On February 21, 2005, at 1339 central standard time, a single-engine Bell 206-L1 helicopter, N5734M, operated by Air Evac Lifeteam was substantially damaged during a hard landing following a loss of control while hovering out of ground effect near Gentry, Arkansas. The commercial pilot, the flight nurse, and the paramedic were seriously injured and the patient was fatally injured. The helicopter was registered to Air Evac Leasing Corporation, of West Plains, Missouri, d/b/a Air Evac Lifeteam, and was destined for Springdale, Arkansas. No flight plan was filed and visual meteorological conditions prevailed for the air medical transport flight conducted under 14 Code of Federal Regulations Part 135.

The purpose of the air medical flight was to pick up a patient who had been involved in a motor vehicle accident in a rural area, and to transport him to a hospital. The helicopter landed to the north on the front lawn of a private residence. After the patient was boarded, the commercial pilot attempted to determine the wind direction, but found no visual cues. However, he estimated the winds were about 10-15 knots from between 330 and 030 degrees. He stated that he had encountered similar winds while en route to the landing zone. A second EMS pilot who arrived at the scene after the accident stated that the winds were from 030 to 050 at 10 knots. The accident pilot stated that he brought the helicopter to a hover and maneuvered the helicopter to the right to avoid power lines that crossed the residential property. The pilot stated that when he departed, he began a vertical ascent but was trying not to increase the collective above the available torque. He stated that he was concerned about clearing the power lines and losing tail rotor effectiveness. When the helicopter reached an altitude abeam of the power lines, it began an uninitiated spin to the right. The pilot stated that the torque was near 100 percent. He applied full left torque pedal, and attempted to gain forward airspeed. He also used the cyclic to follow the nose of the aircraft in an attempt to fly out of the turn. The pilot was unable to gain airspeed and the helicopter continued to spin to the right and to descend. The pilot initiated an autorotation by lowering the collective and placing the throttle in the idle position, which he stated stopped the spinning. When the helicopter was about 10 to 20 feet above ground, the pilot placed the collective in the full-up position to cushion the landing. However, there was not sufficient main rotor rpm to stop the high rate of descent and the helicopter landed hard in a field adjacent to the private residence. Examination of the helicopter revealed no preimpact structural, system, or other mechanical anomalies. A critical wind azimuth in the Bell 206-L1 flight manual indicated an increased risk of loss of tail rotor effectiveness when winds are encountered between 050 and 210 degrees.

Probable Cause: The pilot’s improper decision to maneuver in an environment conducive to a loss of tail rotor effectiveness.

Accident investigation:
cover
  
Investigating agency: NTSB
Report number: A05F0040
Status: Investigation completed
Duration: 1 year and 7 months
Download report: Final report

Sources:

NTSB: https://www.ntsb.gov/_layouts/ntsb.aviation/brief.aspx?ev_id=20050302X00252&key=1
FAA register: 2. FAA: http://registry.faa.gov/aircraftinquiry/NNum_Results.aspx?omni=Home-N-Number&nNumberTxt=5734M

Location

Images:



Photos: NTSB

Revision history:

Date/timeContributorUpdates
28-Oct-2008 00:45 ASN archive Added
22-Aug-2016 11:47 Dr.John Smith Updated [Time, Operator, Location, Nature, Departure airport, Destination airport, Source, Narrative]
25-Sep-2016 16:32 Aerossurance Updated [Time, Operator, Location, Departure airport, Destination airport, Narrative]
21-Dec-2016 19:24 ASN Update Bot Updated [Time, Damage, Category, Investigating agency]
06-Dec-2017 07:01 ASN Update Bot Updated [Other fatalities, Departure airport, Destination airport, Source, Narrative]

Corrections or additions? ... Edit this accident description

The Aviation Safety Network is an exclusive service provided by:
Quick Links:

CONNECT WITH US: FSF on social media FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2024 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314
www.FlightSafety.org