ASN Wikibase Occurrence # 44734
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: | Saturday 21 August 2004 |
| Time: | 23:58 |
| Type: |  Bell 407 |
| Owner/operator: | Jeflyn Aviation Inc dba Access Air |
| Registration: | N2YN |
| MSN: | 53239 |
| Year of manufacture: | 1998 |
| Total airframe hrs: | 2361 hours |
| Fatalities: | Fatalities: 5 / Occupants: 5 |
| Aircraft damage: | Destroyed |
| Category: | Accident |
| Location: | Battle Mountain, NV -
 United States of America
|
| Phase: | En route |
| Nature: | Ambulance |
| Departure airport: | Battle Mountain Hospital, NV |
| Washoe Medical Center, NV | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
On August 21, 2004, approximately 2358 Pacific daylight time, a Bell 407 helicopter, N2YN, operating as an air ambulance flight, impacted mountainous terrain in cruise flight and was destroyed about 27 nautical miles (NM) southwest of Battle Mountain, Nevada. The airline transport pilot, the two medical crewmembers, the infant patient being transported and the patient's mother, were fatally injured. The helicopter was operated by Jeflyn Aviation, Inc., of Boise, Idaho, dba Access Air. The purpose of the Title 14 CFR Part 135 flight was to transport the infant patient from Battle Mountain Hospital to Washoe Medical Center in Reno, Nevada. Dark night visual meteorological conditions prevailed for the 2338 departure from Battle Mountain Hospital. A company flight plan was filed.
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.
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.
Accident investigation:
 |
|
Sources:
NTSB: https://www.ntsb.gov/_layouts/ntsb.aviation/brief.aspx?ev_id=20040831X01336&key=1
Location
Images:
Photos: NTSB
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 28-Oct-2008 00:45 | ASN archive | Added |
| 07-Feb-2009 10:21 | harro | Updated |
| 21-Dec-2016 19:24 | ASN Update Bot | Updated [Time, Damage, Category, Investigating agency] |
| 07-Dec-2017 18:19 | ASN Update Bot | Updated [Source, Narrative] |
Corrections or additions? ... Edit this accident description
The Aviation Safety Network is an exclusive service provided by:
Quick Links:
| ASN Home | Send Correction / Feedback |
| FSF Home | Disclaimer | Copyright |
| Contact Us | Privacy Policy |
| Press / Media |
CONNECT WITH US:
©2024 Flight Safety Foundation