Leicester City helicopter smash file exhibits tail rotor controls failed – SkySports

Final Updated: 06/12/18 6:34pm

A file into the helicopter smash which killed 5 of us including Leicester City owner Vichai Srivaddhanaprabha has printed there used to be important ruin to the tail rotor design.

The helicopter crashed rapidly after retract-off following Leicester’s game against West Ham on the King Energy Stadium on October 27.

The Air Accident Investigation Branch (AAIB), who printed the file had already printed they were focusing their investigation on the helicopter’s tail rotor.

Video photos of the helicopter carrying the Leicester owner confirmed the aircraft going real into a whisk moments earlier than it crashed initiating air the stadium.

Consultants already suspected there had been a mechanical failure that affected the tail rotor – within the days following the smash investigators chanced on the levers intended to join the cockpit pedals to the sustain an eye on shaft of the tail rotor weren’t linked.

Also, the pin and one in all the locating bearings were missing from the lever and the locking nut and pin carrier were stumbled on loose within the tail rotator and were bonded together – they needs to be separate.

The file states that “the evidence gathered shows that the lack of sustain an eye on of the helicopter resulted from the tail rotator actuator sustain an eye on shaft turning into disconnected from the actuator lever mechanism.”

The sustain an eye on shaft used to be stumbled on to like a develop-up of dim grease on it, which had been burnt on not by the hearth. The AAIB then scanned a couple of of the components and stumbled on a couple of of them had been friction welded together and one in all the pins had aspects sheared off. There used to be a develop-up of debris, dim dirt and metallic particles – no grease in its customary manufacture used to be present, which in a hydraulic design is necessary.

The investigation is quiet ongoing and no sure reason has been established as but – but the file confirms a severe mechanical fault did happen.

Read More

Leave a Reply