Aviation Crash Map

Bell 407 N2YN

22 August 2004 · Battle Mountain, Nevada, United States · Fatal

Summary

On 22 August 2004 at about 06:58 local time, a Bell 407 registered N2YN, operated by Jeflyn Aviation, Inc, was involved in an accident near Battle Mountain, Nevada, United States. 5 people were on board and 5 died. The aircraft was destroyed. The NTSB has published a probable cause for this accident; it is quoted in full below.

The record

Date
at 06:58
Classification
Accident
Location
Battle Mountain, Nevada, United States
Coordinates
40.4525, -117.4919
Aircraft
Bell 407
Registration
N2YN
Category
Helicopter
Engines
1
Operator
Jeflyn Aviation, Inc
Operating rule
Part 135: Air Taxi & Commuter
Phase of flight
Not recorded
Route
Battle Mountain → Reno
Aircraft damage
Destroyed
Weather
VMC
Light
Night/Dark
NTSB number
SEA04MA167

People

5 people died.

On board Died Serious Minor Uninjured
5 5 0 0 0

Probable cause

The pilot's failure to maintain clearance from mountainous terrain. Contributing factors were the pilot's improper decision to take the direct route over mountainous terrain, the dark night conditions, and the pressure to complete the mission induced by the pilot as a result of the nature of the EMS mission.

Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.

Read the full NTSB narrative

The emergency medical services (EMS) helicopter departed for a night flight to transport an 11-day-old infant patient from a hospital in Battle Mountain, Nevada, to another in Reno, Nevada. No record was found indicating the pilot obtained a weather briefing before departure. The pilot had a choice of taking either a direct route that crossed a remote area of rugged mountainous terrain with maximum ground elevations of about 9,000 feet or a route that was about 10 minutes longer and followed an interstate highway with maximum ground elevations of about 6,000 feet. After takeoff, the pilot reported his departure to the Elko county dispatch center, stating that his estimated time en route was l hour 20 minutes. There were no further radio communications from the helicopter. Radar data, which show about 4 minutes of the helicopter's flight before coverage was lost due to mountainous terrain, are consistent with the flight following the direct route. A search was initiated about 4 hours after the helicopter did not arrive at the destination hospital, and the wreckage was located the following morning. The accident site was along the direct course line at an elevation of about 8,600 feet. Physical evidence observed at the accident site indicated that the helicopter was in level flight at impact and was consistent with controlled flight into terrain. No evidence was found of any preimpact mechanical discrepancies with the helicopter's airframe or systems that would have prevented normal operation. Rotational damage to the rotor blades and transmission components were consistent with normal engine operation at impact. The two closest aviation weather reporting stations, located 31 and 54 nautical miles (nm) from the accident site, both reported 10 miles visibility, clear skies below 12,000 feet, and no precipitation at the time of the accident. However, satellite images valid approximately 1 hour before the accident indicated cloud cover over the accident site. Additionally, weather radar images valid approximately 1.5 hours before the accident indicated light precipitation was present in the vicinity of the accident site. However, the exact weather conditions and cloud ceiling at the time and location of the accident could not be determined. If the pilot had obtained a weather briefing, he would likely have learned of the cloud cover and light precipitation present along his planned route of flight. Studies conducted by the National Transportation Safety Board and industry have shown that the urgent nature of the EMS mission can result in inaccurate/incomplete preflight planning, as well as poor pilot judgment. The fact that the patient was an infant may well have placed additional pressure on the pilot to take the direct route to arrive at the hospital sooner. The helicopter was not equipped with an enhanced ground proximity warning system (EGPWS), and none as required. If installed, an EGPWS would have alerted the pilot of high terrain ahead at least 35seconds before impact. Although the search for the helicopter was not initiated until about 4 hours after the accident (despite company flight-following procedures that indicated an aircraft should be reported missing as soon as it fails to make a required 15-minute position report), this accident was not survivable and a faster notification would not have changed the outcome.

Quoted verbatim from the NTSB record.

Other Bell 407 accidents

Date Aircraft Location Operator Outcome Died
21 Mar 2004 Bell 407
N502MT
Pyote, Texas, United States - Fatal 4
17 Dec 2004 Bell 407
N976AA
Ship Shoal 130E, United States - Fatal 1
13 Jul 2004 Bell 407
N503MT
Newberry, South Carolina, United States Med-Trans Corp. Fatal 4
13 Aug 2004 Bell 407
XA-CVG
Santa Cruz, Mexico
no coordinates
Golden Aviation S.A. de C.V. Fatal 1
19 Feb 2004 Bell 407
N601MT
Madera, California, United States - No injuries -
27 Apr 2004 Bell 407
N407BP
Hurst, Texas, United States Bell Training Academy No injuries -

All 158 records for this type

Other accidents in this area

Date Aircraft Location Operator Outcome Died
19 Mar 2004 Piper PA-38-112
N2421D
Jean, Nevada, United States - Fatal 1
5 Sep 2004 Robinson R22 BETA
N994RW
North Las Vegas, Nevada, United States Silver State Helicopter Serious injuries -
23 Oct 2004 Ams Flight CARAT A
N418AP
Minden, Nevada, United States - Fatal 1
25 Oct 2004 Bellanca BL17-30
N4894V
Las Vegas, Nevada, United States - Minor injuries -
26 Jan 2004 Piper PA-28-180C
N7922W
Minden, Nevada, United States - No injuries -
24 May 2004 Let BLANIK L-13
N53AS
Sparks, Nevada, United States - No injuries -

All 170,864 records in United States