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.

The recorded data showed that the failure mode started at 0828:52. <strong>In</strong> terms <strong>of</strong> theADR data, the crew selected ADR 1 OFF 28 seconds after the failure mode started(at 0829:20). Consequently, ADR 1 ceased transmitting data and the FDR switchedits source for the ADR parameters, except angle <strong>of</strong> attack (AOA) 1 and AOA 2,from ADR 1 to ADR 3. 205 When the crew switched the source <strong>of</strong> ADR parametersfor the captain’s displays to ADR 3 (0831:25), the FDR’s source <strong>of</strong> AOA 1 alsoswitched to ADR 3. During the brief period that ADR 1 data was recorded:• There were no spikes in AOA 206 or Mach.• There were two spikes for altitude, and two spikes for static air temperature.There were also four small changes (10 kts) in computed airspeed.ADIRU 1 flagged all <strong>of</strong> these anomalies as valid data.<strong>In</strong> terms <strong>of</strong> the IR data:• Although the crew reported switching IR 1 <strong>of</strong>f, the QAR data showed that theIR 1 parameters continued to be transmitted by the ADIRU until after landing.• From the start <strong>of</strong> the event until after the aircraft landed, the QAR recordednumerous spikes in pitch attitude, drift angle, body lateral acceleration, inertialvertical speed, and magnetic heading. 207• <strong>In</strong> addition to the data spikes, all <strong>of</strong> the IR parameters showed persistentdeviations from their expected values. For most <strong>of</strong> these parameters, thedeviations showed oscillatory behaviour. The groundspeed parameter increasedto 1,000 kts, where it remained for the rest <strong>of</strong> the <strong>flight</strong>, except for a number <strong>of</strong>lower-value data spikes.• With only brief exceptions, ADIRU 1 flagged all <strong>of</strong> the IR 1 data after the start<strong>of</strong> the event (0828:52) as invalid.There were no stall warnings recorded (consistent with no spikes on the captain’sAOA) and no overspeed warnings recorded (consistent with only small changes oncomputed airspeed). However, there were repetitive master cautions recorded afterthe failure mode commenced, consistent with the occurrence <strong>of</strong> ECAM messages.205206207At this time the QAR stopped recording any ADR parameters from ADIRU 1. Computed airspeedwas defined as a switchable parameter, and its source switched to ADIRU 2 at this time.Some oscillations were observed in the recorded data for AOA 1 after the ADR Fail parametercommenced indicating Fail. These oscillations were examined and matched the no computed datacycling behaviour expected when ADR 1 was no longer outputting data, consistent with it beingswitched <strong>of</strong>f (Appendix B).As with the 7 <strong>October</strong> <strong>2008</strong> occurrence, the FDR only recorded a small number <strong>of</strong> spikes at thebeginning <strong>of</strong> the event. For most <strong>of</strong> the IR parameters, the FDR switched its source if the ADIRUflagged its data as invalid. However, the QAR always sourced its data from ADIRU 1.- 240 -

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

Saved successfully!

Ooh no, something went wrong!