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.

Up until 2009, the A330 had not been associated with any accidents resulting infatalities. On 1 June 2009, an Airbus 330-200, operated as <strong>flight</strong> AF447, impactedthe Atlantic Ocean on a <strong>flight</strong> from Rio de Janeiro, Brazil to Paris, France. Aninvestigation by the French Bureau d’Enquêtes et d’Analyses pour la sécurité del’aviation civile (BEA) is ongoing, and all the factors contributing to the accidenthave yet to be determined. 73The AF447 accident and the 7 <strong>October</strong> <strong>2008</strong> accident on <strong>flight</strong> QF72 involved avery different set <strong>of</strong> events and conditions. More specifically:• On the AF447 <strong>flight</strong>, there were a series <strong>of</strong> fault messages that showedinconsistencies between the measured airspeeds calculated by the threeADIRUs, as well as consequences on other aircraft systems. Such messageshave occurred on several <strong>flight</strong>s near large cumulous cloud build-ups, and theyhave been associated with pitot probe obstruction due to icing. During the QF72<strong>flight</strong> on 7 <strong>October</strong> <strong>2008</strong>, the aircraft did not encounter weather conditionsassociated with pitot probe icing, there was no problem with the performance <strong>of</strong>the pitot probes, and there were no fault messages that showed airspeedinconsistencies. Although ADIRU 1 provided some incorrect airspeed data,there was no problem with the data provided by the other two ADIRUs.• <strong>In</strong> contrast to the QF72 event, the AF447 event did not involve an ADIRUfailure. The ADIRUs on the two aircraft were different models made bydifferent manufacturers, and the model fitted to the A330 that was involved inAF447 has not been associated with any ADIRU data-spike occurrences.• During both <strong>flight</strong>s, stall warnings occurred. However, during the QF72 <strong>flight</strong>,the stall warnings were brief, nuisance warnings associated with incorrect AOAdata from an ADIRU, and the aircraft did not approach or enter an aerodynamicstall during the <strong>flight</strong>.1.17 Organisational and management information1.17.1 A330 operationsThe operator commenced A330 operations in late 2002. At the time <strong>of</strong> the7 <strong>October</strong> <strong>2008</strong> occurrence, the operator’s A330 fleet included 10 A330-303aircraft and six A330-202 aircraft. An associated Australian operator (Jetstar) hadfive A330-202 aircraft, with a sixth joining its fleet in late <strong>2008</strong>. The operator <strong>of</strong>QPA controlled the maintenance for all 22 A330 aircraft. All the aircraft wereobtained new from the manufacturer, and all were fitted with the same types <strong>of</strong>ADIRUs and FCPCs as fitted to QPA.Throughout the period from 2003 to <strong>2008</strong>, the Qantas/Jetstar A330 fleet conducted60,973 sectors and accumulated 312,834 <strong>flight</strong> hours. <strong>In</strong> <strong>2008</strong>, the fleet conducted9,149 sectors and accumulated 93,406 <strong>flight</strong> hours.73The BEA has released three <strong>In</strong>terim Reports on the accident which are available atwww.bea.aero/en.- 63 -

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

Saved successfully!

Ooh no, something went wrong!