EC135P2 N62UP Spatial Disorientation Accident
History of the Flight
The flight, operated as a a Part 91 “personal flight”, originated from Atlantic City International Airport (ACY), New Jersey, 36 minutes earlier so the pilot could practice instrument approaches at New Castle Airport (ILG), Wilmington, Delaware in Instrument Meteorological Conditions (IMC).
…the pilot submitted a flight request form to the company, which documented the weather products he reviewed before the flight and indicated that he was aware of the reported and forecast weather conditions for the route before departure. After reviewing the request, weather, and risk assessment, the company’s operation control center approved and released the helicopter for the flight five minutes after the request was submitted.
The terminal area forecast published earlier that morning and valid for the pilot’s anticipated time of arrival at the destination indicated that the visibility would be 6 statute miles with an overcast ceiling at 1,200 ft agl; though the most recent surface observation report contradicted the forecast, indicating that the visibility was 4 statute miles in rain and the overcast ceiling was at 500 ft.
The helicopter intercepted the localizer course about 1 nautical mile (nm) outside the approach gate. The controller then cleared the pilot for the approach with a restriction to maintain an altitude at or above 2,000 ft mean sea level (msl), which was both the assigned altitude and the intermediate altitude for the approach, until established on the approach and to contact the control tower at the destination airport.
The pilot acknowledged the clearance and contacted the tower controller shortly thereafter. After checking in with the tower controller; the helicopter maintained 2,000 ft msl as it continued through the glideslope and crossed over the locator outer marker, which had a published crossing altitude of 1,842 ft msl.
As the helicopter reached a point about 3 nm inside the outer marker, while flying at an altitude about 2,000 ft msl, the pilot declared a missed approach, telling the controller that he had received “some bad vectors at the very end” and that he wanted to “just line up and come back around again.”
The controller advised the pilot to fly the published missed approach procedure (a straight-ahead climb to 900 ft msl and then a left climbing turn toward the next navigational fix, at an altitude 2,000 ft msl).
The helicopter then climbed straight ahead to an altitude of 2,525 ft msl in 9 seconds, before it turned right and started descending rapidly.
NTSB comment that:
The helicopter’s calculated rate of climb before it began to descend was about 3,000 ft/min, while it’s calculated groundspeed was about 120 knots. This climb rate and speed were not consistent with the pilot using the helicopter’s automatic flight control system go-around mode because they were well above the climb rate and groundspeed that the “go around” mode would have maintained.
Radar contact was lost as the helicopter descended through 1,625 ft msl, and the calculated descent rate between the helicopter’s final two radar-recorded positions was more than 7,000 ft/min.
No further communications were received from the pilot.
One witness reported seeing the helicopter “spinning down…out of the clouds in an upside-down nose dive.” Another witness reported that the helicopter descended “like a rocket”…
The helicopter came to rest in a ditch, fragmented and mostly consumed by post-impact fire, about 3,200 ft before the runway threshold.
NTSB Investigation and Analysis
Several factors indicated that the pilot was task-saturated when the accident sequence occurred:
1) he was performing an instrument approach that he had not previously performed;
2) he was provided radar vectors close to the approach gate, which accelerated the timeline of the approach procedure; and
3) he was likely already planning the return flight to the departure airport, which he previously indicated to the controller that he would conduct following the approach.
That the pilot did not descend the helicopter after intercepting the glideslope or passing the final approach fix and did not fly the published missed approach procedure are indicative that he had likely become task-saturated during the final moments of the flight.
Non-time-correlated but sequentially recorded data recovered from the helicopter’s warning unit revealed that, at some time during the accident flight, the greater-than-106% rotor rpm warning indicator illuminated multiple times, then the greater-than-112% rotor rpm warning illuminated. The rotor rpm warnings cycled between greater than 106% and 112% and less than 95% multiple times.
Given that no discrepancies with the helicopter’s engines or rotor system were discovered during the post-accident examination, it is likely that these rapid, dramatic changes in rotor rpm annunciated and recorded by the warning unit were the result of the pilot’s control inputs as he became task-saturated and began to experience the effects of spatial disorientation.
The helicopter’s subsequent rapid climb, right turn…and its near-vertical descent are consistent with the pilot’s loss of helicopter control due to spatial disorientation.
…under normal flight conditions, when there is a visual reference to the horizon and ground, the sensory system in the inner ear helps to identify the pitch, roll, and yaw movements of the airplane. When visual contact with the horizon is lost, the vestibular system becomes unreliable. Without visual references outside the airplane, there are many situations where combinations of normal motions and forces can create convincing illusions that are difficult to overcome.
The handbook also advises:
…unless a pilot has many hours of training in instrument flight, flight in reduced visibility or at night when the horizon is not visible should be avoided.
NTSB Probable Cause
The pilot’s loss of helicopter control during a missed approach in instrument meteorological conditions due to spatial disorientation and the cumulative effects of task saturation.
Other Safety Resources
- HEMS Black Hole Accident: “Organisational, Regulatory and Oversight Deficiencies” The operator of this S-76C had insufficient resources to effectively manage safety say TSB. The regulator had concerns but its approach did not ensure timely rectification.
- HEMS S-76C Night Approach LOC-I Incident a near accident in Canada
- Life Flight 6 – US HEMS Post Accident Review video and emergency response lessons from a US night accident
- US HEMS “Delays & Oversight Challenges” – IG Report
- US HEMS Accident Rates 2006-2015
- More US Night HEMS Accidents
- Night Offshore Winching CFIT a German HEMS unit attempts night offshore winching
- US Police Helicopter Night CFIT: Is Your Journey Really Necessary?
- That Others May Live – Inadvertent IMC & The Value of Flight Data Monitoring In 2014 Airbus Helicopters released a remarkable 15 minute video that describes the lessons from an Inadvertent IMC incident during a HEMS flight in the US and shows the value of FDM.
- Dim, Negative Transfer Double Flameout a New Zealand HEMS BK117 incident with training and experience lessons
- Misassembled Anti-Torque Pedals Cause EC135 Accident Misassembled anti-torque pedals caused an accident to EC135P1 N911KB, during a post-maintenance check flight by Metro Aviation.
- HEMS A109S Night Loss of Control Inflight
- US HEMS EC135P1 Dual Engine Failure: 7 July 2018
- Accident Report: Fatal Police Helicopter Double Engine Flameout Over City Centre
- AAIB Report on Glasgow Police EC135 Clutha Helicopter Accident
- UPDATE 24 October 2019: EC135P2+ Loss of NR Control During N2 Adjustment Flight