13.07.2015 Views

In-flight upset - 154 km west of Learmonth, WA, 7 October 2008,

In-flight upset - 154 km west of Learmonth, WA, 7 October 2008,

In-flight upset - 154 km west of Learmonth, WA, 7 October 2008,

SHOW MORE
SHOW LESS
  • No tags were found...

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Following the second in-<strong>flight</strong> <strong>upset</strong>, the crew continued to review the ECAMmessages and other indications. The first ECAM message they noticed was F/CTLALTN LAW (PROT LOST). 14 The next messages were recurrences <strong>of</strong> the NAVIR 1 FAULT and F/CTL PRIM 3 FAULT messages. The crew reported that the IR1FAULT light and the PRIM 3 FAULT light on the overhead panel wereilluminated. No other fault lights were illuminated.The crew reported that by this time ECAM messages were frequently scrolling,with each new caution message being placed at the top <strong>of</strong> the list. The NAV IR 1FAULT message kept recurring, together with several other messages, such asNAV GPS FAULT, and they could not effectively interact with the ECAM toaction and/or clear the messages. Master caution chimes associated with the ECAMmessages were frequently occurring, together with aural stall warnings andoverspeed warnings. The crew stated that these constant aural alerts, and theinability to silence them, were a significant source <strong>of</strong> distraction.1.1.5 Diversion to <strong>Learmonth</strong>At 0446:10, the captain made a public announcement to the cabin, advising that thecrew were dealing with <strong>flight</strong> control problems, and telling everyone to remainseated with their seat belts fastened. The second <strong>of</strong>ficer contacted the cabin againby interphone to ask a <strong>flight</strong> attendant to send the first <strong>of</strong>ficer to the <strong>flight</strong> deck.The captain reported that, after the second <strong>upset</strong> event, he observed that theautomatic pitch trim (autotrim) was not functioning 15 and he began trimming theaircraft manually. The crew advised that, because the autotrim was not working,they thought the <strong>flight</strong> control system was in direct law. 16With the exception <strong>of</strong> the loss <strong>of</strong> autotrim, the captain reported that the aircraft wasflying normally. At 0447:25, he disconnected the autothrust to minimise anypotential problems associated with the erroneous air data information affecting theelectronic engine control units. He then flew the aircraft without the autopilot orautothrust engaged, and using the standby instruments, for the remainder <strong>of</strong> the<strong>flight</strong>.The first <strong>of</strong>ficer returned to the <strong>flight</strong> deck at 0447:40, taking over from the second<strong>of</strong>ficer in the right control seat while the second <strong>of</strong>ficer moved to the third occupantseat. The crew discussed the situation, and the captain stated that he would continueflying the aircraft.141516The crew reported that they did not recall seeing amber crosses on the PFDs, which were meant tobe displayed if the <strong>flight</strong> control system was in alternate law or direct law. The aircraftmanufacturer advised that there was no technical reason why these amber crosses would not havebeen displayed on the occurrence <strong>flight</strong>.A ‘USE MAN PITCH TRIM’ message was not displayed to the crew on their PFDs as, at the time<strong>of</strong> the occurrence, this message was only displayed if the <strong>flight</strong> control system was in direct law.The aircraft manufacturer advised that this problem was being addressed with a new designstandard, which was certified in 2011.The <strong>flight</strong> control system was in alternate law from 0445:11 until the end <strong>of</strong> the <strong>flight</strong>. Autotrimwas generally available in alternate law, but it was lost in this case due to the sequence <strong>of</strong> faultmessages associated with the FCPCs (PRIMs) (section 2.2.2).- 5 -

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!