ASN Wikibase Occurrence # 182366
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: | Tuesday 15 December 2015 |
| Time: | 17:23 |
| Type: |  Eurocopter AS 350B3 Ecureuil |
| Owner/operator: | Air Methods Corp |
| Registration: | N74317 |
| MSN: | 4317 |
| Year of manufacture: | 2007 |
| Fatalities: | Fatalities: 2 / Occupants: 3 |
| Aircraft damage: | Substantial |
| Category: | Accident |
| Location: | near Sawtooth Ridge, Superstition Mountains, 20mi E of Apache Junction -
 United States of America
|
| Phase: | En route |
| Nature: | Ambulance |
| Departure airport: | Phoenix, AZ (IWA) |
| Globe, AZ (P13) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
The commercial pilot was repositioning the helicopter (with a flight nurse and flight paramedic on board) to its base following an air ambulance flight. The paramedic, who survived the accident, reported that after refueling, they departed and headed east towards mountainous terrain; peak elevations were 5,700 to 6,000 ft. About 10 minutes after takeoff, the helicopter entered the mountainous terrain, and the height of the helicopter above the terrain began to vary as the terrain elevation rose and fell. During the final few minutes of the flight, the helicopter's altitude above the ground varied between 30 ft and 770 ft.
About 30 seconds before impact, the helicopter flew east over a north-south canyon and continued through a saddle on the canyon's east wall, clearing the terrain by about 30 ft. As the helicopter passed over the eastern ridgeline, it banked to the right and reached a ground speed of about 120 knots. After the helicopter cleared the ridge, it started to descend and accelerate. The ground speed reached a maximum of 148 knots, and about 10 seconds later, there was an abrupt increase in the helicopter's pitch and right roll rates, consistent with right and aft cyclic inputs. According to the paramedic, around this time, the pilot said an expletive in a panicked voice. The paramedic looked up and saw a ridgeline immediately in their flight path and terrain filling up the view. The paramedic described the subsequent motions of the helicopter as a violent hard right bank, and he stated that the pilot did not say anything else but was making jerky, fast hand movements. The flight characteristics seconds before impact, as described by the paramedic and shown in flight data, were consistent with a rapid onset of servo transparency. The helicopter impacted terrain on the northwest facing slope of a ridgeline, near a saddle, at an elevation of about 5,035 ft.
Servo Transparency begins when the aerodynamic forces acting to change the pitch of the rotor blades exceed the hydraulic servo actuators' capability to resist those forces and maintain the commanded blade pitch angles. The force deficit is then transmitted back to the pilot's cyclic and collective controls. On clockwise turning main rotor systems such as the AS350B3, the right servo receives the highest load when maneuvering (retreating blade), resulting in an uncommanded right and aft cyclic motion accompanied by down collective movement. The NTSB's Servo Transparency Study for accident No. LAX03MA292 notes that the pilot's control force required to counter this aerodynamically-induced phenomena "tends to be progressive" and is "proportional to the severity of the maneuver," and "may give a pilot who is not aware of this phenomenon an impression that the controls are jammed." If the pilot does not reduce the maneuver, the aircraft will roll right and pitch-up, but the phenomenon normally lasts less than 2 seconds.
The general load on the main rotor increases under the following conditions: high speed, high torque (increase in collective pitch), high g-load, and increase in density altitude. Although the helicopter will self-correct and recover from the servo transparency, the potential exists for a significant flight path deviation. The onset of servo transparency is rapid and could conceivably lead to a helicopter in a right turn exceeding 90º of bank before the pilot was able to recognize what was happening and react accordingly. The associated transition from light and responsive controls to heavy controls that require considerable force to counter the uncommanded maneuver, could cause an unsuspecting pilot to believe that he was experiencing a malfunction, rather than a known characteristic of the helicopter when maneuvered at the published performance limits.
The Operation Control Center mistakenly lost tracking of the helicopter about 2 hours and 10 minutes after the accident occurred. Another company helicopter was then sent to search for the accident helicopter and located the wreckage about 50 minutes later. Due to the mountainous terra
Probable Cause: The pilot's loss of helicopter control in mountainous terrain as the result of operating the helicopter outside the performance envelope of its hydraulic system and encountering the servo transparency phenomenon. Contributing to the accident was the pilot's decision to perform low-level, high-speed maneuvers through mountainous terrain.
Accident investigation:
 |
|
Sources:
NTSB
Location
Images:
Photo: NTSB
Media:
#NTSB Report on #HEMS AS350 N74317 #Helicopter Accidenthttps://t.co/7bXJ6JiU5v#flightsafety pic.twitter.com/xYZqtfVEHQ
— Aerossurance (@Aerossurance) March 20, 2019
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 16-Dec-2015 08:05 | Iceman 29 | Added |
| 16-Dec-2015 08:29 | Geno | Updated [Aircraft type, Location, Destination airport, Source] |
| 16-Dec-2015 08:31 | Aerossurance | Updated [Time, Aircraft type, Operator, Total fatalities, Other fatalities, Location, Destination airport, Source, Damage, Narrative] |
| 16-Dec-2015 09:17 | Aerossurance | Updated [Location] |
| 16-Dec-2015 13:17 | Iceman 29 | Updated [Location, Destination airport, Source] |
| 16-Dec-2015 13:49 | Aerossurance | Updated [Location, Source, Narrative] |
| 16-Dec-2015 15:49 | Aerossurance | Updated [Time, Departure airport, Source, Narrative] |
| 16-Dec-2015 18:09 | Geno | Updated [Registration, Cn, Operator, Departure airport, Source] |
| 16-Dec-2015 22:57 | Aerossurance | Updated [Operator, Location, Source, Narrative] |
| 18-Dec-2015 06:42 | CTYONE | Updated [Aircraft type] |
| 18-Dec-2015 20:37 | Aerossurance | Updated [Source, Narrative] |
| 21-Dec-2016 19:30 | ASN Update Bot | Updated [Time, Damage, Category, Investigating agency] |
| 16-Dec-2018 09:28 | Aerossurance | Updated [Time, Operator, Location, Source, Narrative] |
| 16-Dec-2018 09:30 | Aerossurance | Updated [Operator] |
| 20-Mar-2019 09:40 | Aerossurance | Updated [Damage, Narrative] |
| 20-Mar-2019 10:05 | Aerossurance | Updated [Embed code] |
| 22-Mar-2019 19:07 | ASN Update Bot | Updated [Time, Aircraft type, Operator, Departure airport, Destination airport, Source, Embed code, Damage, Narrative, Accident report, ] |
| 22-Mar-2019 19:55 | harro | Updated [Embed code, Narrative, Photo] |
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