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.

Occurrence on 27 December <strong>2008</strong>OverviewOn 27 December <strong>2008</strong>, an Airbus A330-303 aircraft, registered VH-QPG (QPG)and being operated as Qantas <strong>flight</strong> 71, was on a scheduled passenger transportservice from Perth to Singapore. The aircraft departed Perth at 0750 UTC(1550 local time) and reached its cruise altitude <strong>of</strong> FL360 at 0814. At 0829(1729 local time), ADIRU 1 failed.The <strong>flight</strong> crew reported that:• The autopilot (autopilot 1) disconnected and the ECAM started providing aseries <strong>of</strong> caution messages, including a NAV IR 1 FAULT.• They actioned the relevant operational procedure 204 by selecting theIR 1 pushbutton to OFF and the ADR 1 pushbutton to OFF, and both OFF lightsilluminated.• They continued to receive multiple ECAM messages, and those messages wereconstantly scrolling on the display. One <strong>of</strong> the ECAM messages was a NAV IR1 FAULT, and the recommended crew action was to switch the ATT HDGswitch to the CAPT ON 3 position. They completed this action, but it did notstop the ECAM messages.• They returned to Perth and conducted an uneventful landing. At no stage wasthere any effect on the aircraft’s <strong>flight</strong> controls.At the time that the autopilot disconnected, the aircraft was about 480 <strong>km</strong> (260 NM)north-<strong>west</strong> <strong>of</strong> Perth and about 650 <strong>km</strong> (350 NM) south <strong>of</strong> <strong>Learmonth</strong> (Figure 26).The PFR for the 27 December <strong>2008</strong> <strong>flight</strong> contained a series <strong>of</strong> messages associatedwith ADIRU 1 that were very similar to those for the PFR from the 7 <strong>October</strong><strong>2008</strong> occurrence (Table D1). Consistent with there being no in-<strong>flight</strong> <strong>upset</strong>, therewere no PRIM FAULTS or PRIM PITCH FAULTS.Flight recordersThe <strong>flight</strong> data recording system fitted to QPG on 27 December <strong>2008</strong> differed fromthe system fitted to QPA. QPG had a single box system (Teledyne FDIMU partnumber 2234340-02-02) with two separate processors to handle both the FDR andACMS (QAR) functions. However, the source <strong>of</strong> ADIRU parameters for the FDRand QAR was the same as for QPA (section 1.11).The overall pattern <strong>of</strong> ADR and IR data from the recorders was very similar to thatfor the 7 <strong>October</strong> <strong>2008</strong> event. A summary <strong>of</strong> key events from the FDR is presentedin Table D2. The FDR data is presented in Figure D1 and D2, and QAR data ispresented in Figure D3.204This procedure was different to that which applied at the time <strong>of</strong> the 7 <strong>October</strong> <strong>2008</strong> occurrence.The relevant procedure at the time <strong>of</strong> the 27 December <strong>2008</strong> occurrence was based on AirbusOperations Engineering Bulletin (OEB) 74-3 issued in December <strong>2008</strong> in response to the7 <strong>October</strong> <strong>2008</strong> accident (section 7.1.1).- 237 -

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

Saved successfully!

Ooh no, something went wrong!