20200503010149I

Incident · No damage

FAA incident report · Airbus Helicopters AS 350B3 · Clewiston, FL · May 3, 2020

Date
May 3, 2020 · 10:45 local
Place
Clewiston, FL
Phase of flight
Cruise/Level Flight
Operating rules
General operating rules (Part 91)
Damage
No damage
Aircraft
N1WT
NTSB investigation
NTSBENG20LA031
Reported as
Airbus Helicopters AS 350B3
Reported engine
SAFRAN ARRIEL-2D
People aboard
1
Fatal injuries
0
Other injuries
0

From the FAA’s Accident/Incident Data System (AIDS), through its Aviation Safety Information Portal, as reported. The NTSB investigates accidents separately, and its record of an accident is the fuller one. The aircraft is matched to the registry by N-number and event date, checked against the reported make and model; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

What happened

The FAA’s narrative, in sentence case. The FAA writes it in capitals and removes private details.

Upon entering the left downwind for runway 13 at 2IS, the pedals went rock hard, along with the hyd 2 and servo lights illuminating themselves on the cwp. There was some light smoke in the cockpit and a significant burning smell. Pilot knew he had a hydraulic failure due to the lights and the severely increased load in the pedals. He immediately opened my window to clear some of the smoke/smell. Came on the radio and announced my emergency. He then slowed down the helicopter gradually, remembering the training that his instructor taught him for this situation as they had practiced a hyd 2 failure in training. He extended the downwind to give himself enough room to execute a shallow approach to a run on landing, then made a nice gentle left base turn to final, continuously decelerating the helicopter. He crossed the threshold of the runway at approximately 25-30KTS and approximately 30FT. Pilot states he made the heading as straight as he could, and then made an extremely smooth run on landing and steered the helicopter to the best of his ability to the center of the runway. He stopped and came on the radio and announced what had just happened, and that he was stuck on the runway. There was no one around the airport and did not get a response from anyone on the radio. He then shut down the helicopter; called hi instructor to tell him what had just happened. Then called the airport manager and notified her that the airport needed to be closed.

As the FAA filed it

UPON ENTERING THE LEFT DOWNWIND FOR RUNWAY 13 AT 2IS, THE PEDALS WENT ROCK HARD, ALONG WITH THE HYD 2 AND SERVO LIGHTS ILLUMINATING THEMSELVES ON THE CWP. THERE WAS SOME LIGHT SMOKE IN THE COCKPIT AND A SIGNIFICANT BURNING SMELL. PILOT KNEW HE HAD A HYDRAULIC FAILURE DUE TO THE LIGHTS AND THE SEVERELY INCREASED LOAD IN THE PEDALS. HE IMMEDIATELY OPENED MY WINDOW TO CLEAR SOME OF THE SMOKE/SMELL. CAME ON THE RADIO AND ANNOUNCED MY EMERGENCY. HE THEN SLOWED DOWN THE HELICOPTER GRADUALLY, REMEMBERING THE TRAINING THAT HIS INSTRUCTOR TAUGHT HIM FOR THIS SITUATION AS THEY HAD PRACTICED A HYD 2 FAILURE IN TRAINING. HE EXTENDED THE DOWNWIND TO GIVE HIMSELF ENOUGH ROOM TO EXECUTE A SHALLOW APPROACH TO A RUN ON LANDING, THEN MADE A NICE GENTLE LEFT BASE TURN TO FINAL, CONTINUOUSLY DECELERATING THE HELICOPTER. HE CROSSED THE THRESHOLD OF THE RUNWAY AT APPROXIMATELY 25-30KTS AND APPROXIMATELY 30FT. PILOT STATES HE MADE THE HEADING AS STRAIGHT AS HE COULD, AND THEN MADE AN EXTREMELY SMOOTH RUN ON LANDING AND STEERED THE HELICOPTER TO THE BEST OF HIS ABILITY TO THE CENTER OF THE RUNWAY. HE STOPPED AND CAME ON THE RADIO AND ANNOUNCED WHAT HAD JUST HAPPENED, AND THAT HE WAS STUCK ON THE RUNWAY. THERE WAS NO ONE AROUND THE AIRPORT AND DID NOT GET A RESPONSE FROM ANYONE ON THE RADIO. HE THEN SHUT DOWN THE HELICOPTER; CALLED HI INSTRUCTOR TO TELL HIM WHAT HAD JUST HAPPENED. THEN CALLED THE AIRPORT MANAGER AND NOTIFIED HER THAT THE AIRPORT NEEDED TO BE CLOSED.

NTSB investigation

The NTSB’s investigation of this event, with its probable cause and findings. Matched to this report by N-number and date.