Airbus Helicopters AS350 accident near Superior, Arizona, December 16, 2015
On December 16, 2015, a 2007 Airbus Helicopters AS350, registered N74317, was substantially damaged in an accident during maneuvering (low-alt flying) near Superior, Arizona. It was flown under charter and air-taxi rules (Part 135). 2 people were killed and 1 person was seriously injured. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
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.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- December 16, 2015
- Place
- Superior, Arizona · map
- Type
- Accident
- Injuries
- 2 people were killed and 1 person was seriously injured.
- Weather
- visual conditions (good weather)
- Aircraft
- Airbus Helicopters AS350 B3, built 2007 · all AS350s on the register
- Registration
- N74317 · no longer on the register · serial 4317
- Damage
- Substantial damage
- Flight
- Flight · charter and air-taxi rules (Part 135)
The NTSB's narrative final · quoted from the NTSB record
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 terrain and limited access to the accident site, another helicopter responded to the area about 4 hours after the accident and was capable of hoisting medics to the accident site. The emergency locator transmitter (ELT) did not activate during the accident sequence, resulting in the delayed response of the search and rescue teams. Examination of the ELT revealed that the G-switches in the unit failed to activate due to a powdery residue from internal wear. The pilot's autopsy identified a lesion in his brain consistent with a cavernous hemangioma. No bleeding or other acute finding around the cavernous hemangioma was described by the autopsy report, and no other natural disease was identified. Given the paramedic's description of the flight indicating that the pilot was actively flying, it is unlikely that the cavernous hemangioma contributed to the accident. According to the paramedic, the flight nurse survived the impact and was initially awake and alert, but over time, he became increasingly short of breath and eventually stopped talking and breathing. An injury study was completed on the flight nurse to evaluate whether improved communication regarding the timing and location of the crash, such as through a functioning ELT, could have allowed him to survive. Given the flight nurse's injury severity, particularly to the chest, the amount of internal bleeding, and the fact that he was wet and exposed with minimal clothing in 20°F temperature, it is unlikely that he would have survived until help arrived even if the initial notification of the crash had occurred more rapidly. No evidence was found of any preimpact mechanical malfunctions or failures of the airframe or engine that would have precluded normal operation. Examination of the accident site and wreckage revealed that the helicopter impacted terrain in a right bank and level attitude.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Low altitude operation/event during maneuvering (low-alt flying) defining event
- Collision with terrain or object (not controlled flight into terrain) during maneuvering (low-alt flying)
The NTSB's findings
- cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
- cause Personnel issues › Action/decision › Action › Incorrect action performance › Pilot
- cause Aircraft › Aircraft systems › Hydraulic power system › (general) › Capability exceeded
- cause Aircraft › Aircraft oper/perf/capability › Aircraft capability › Climb capability › Attain/maintain not possible
- factor Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
- factor Environmental issues › Physical environment › Terrain › Mountainous/hilly terrain › Decision related to condition
- factor Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Airspeed › Incorrect use/operation
- factor Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Altitude › Incorrect use/operation
Pilot
- Certificate: flight instructor, commercial pilot
- Ratings: instructor: helicopter; instrument: helicopter; rotorcraft: helicopter
- Flight time: 2,117 in this make and model
- Medical certificate: Class 2 (with waivers/limitations)
- Seat: rgt
- Injury: fatal
The aircraft
- Last inspection: condition inspection
- Seats: 4
- Landing gear: fixed
- Engine 1: (turboshaft); 0 hours total
- Engine 2: (turboshaft); 0 hours total
- Operator: Air Methods CORP
The flight
- Departed from: IWA Phoenix AZ
- Destination: P13 Globe AZ
Weather at the time
- Light: daylight
- Wind: from 310° at 5 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 48°F (9°C), dew point 25°F (-4°C)
- Altimeter: 29.98 inHg
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 2 | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.
Other NTSB records under N74317 the same tail number, which may have belonged to a different aircraft at the time
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
