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.

Comparison <strong>of</strong> the three occurrences to other operationsThe three known data-spike occurrences occurred on two aircraft in the sameoperator’s fleet. The investigation examined if there were any unique aspects <strong>of</strong> theoperator’s aircraft, maintenance practices or operational practices that could havebeen related to the ADIRUs’ anomalous behaviour. No related factors were found.More specifically:• Aircraft QPA and QPG were manufactured at different times. The operatoradvised that QPA and QPG did not have any unique configurations or types <strong>of</strong>aircraft systems that made them different to the operator’s other A330-303aircraft.• The aircraft manufacturer advised that the operator’s A330 aircraft did not haveany unique aircraft systems compared with the rest <strong>of</strong> the world A330/A340fleet. That is, each aircraft system used by the operator was also used by at leastone other operator that had LTN-101 ADIRUs fitted to its aircraft.• The aircraft manufacturer, operator and ADIRU manufacturer advised that therewas nothing unique about the operator’s processes for operating or maintainingits ADIRUs. All repairs and s<strong>of</strong>tware upgrades were conducted by the ADIRUmanufacturer. All system tests conducted on the aircraft were conducted inaccordance with the manufacturer’s procedures.The aircraft manufacturer andoperator conducted a detailed examination <strong>of</strong> QPA’s ADIRS installation andconfiguration, focusing on the ADIRU 1 wiring and connections. No problemswere found.• A detailed review <strong>of</strong> the sequence <strong>of</strong> events in the 7 <strong>October</strong> <strong>2008</strong> occurrenceidentified that nothing unique or unusual occurred during the <strong>flight</strong>, either on the<strong>flight</strong> deck or in the cabin. Nothing unique or unusual was reported for either <strong>of</strong>the other two occurrences. The FDR data for both the 7 <strong>October</strong> <strong>2008</strong> and27 December <strong>2008</strong> <strong>flight</strong>s showed nothing unique or unusual prior to the start <strong>of</strong>the anomalous ADIRU behaviour. There was no problematic cargo carried onany <strong>of</strong> the three <strong>flight</strong>s.• The three occurrences happened during cruise; however, with medium or longdistance <strong>flight</strong>s the majority <strong>of</strong> <strong>flight</strong> time involves cruise. All three occurred atdifferent times during each <strong>flight</strong>.• The three occurrences all took place on routes between Perth and Asia (eitherSingapore or Hong Kong), although there were significant distances between theoccurrence locations. The operator advised that about 19% <strong>of</strong> its A330 sectors in<strong>2008</strong> were on <strong>flight</strong>s between Perth and Singapore or Hong Kong and passed inrelatively close proximity to <strong>Learmonth</strong>. <strong>In</strong> addition, about 29% <strong>of</strong> its A330<strong>flight</strong>s passed within 1,500 <strong>km</strong> <strong>of</strong> <strong>Learmonth</strong>. The investigation also identifiedthat other A330/A340 operators, including operators with LTN-101 ADIRUsfitted, conducted regular <strong>flight</strong>s between Asian locations and Perth.1.16.3 Comparison to other A330/A340 occurrencesBetween 1992 and 2009, A330/A340 aircraft conducted over 28 million flyinghours with very few accidents or serious incidents. There have been no otheraccidents on A330/A340 aircraft associated with the <strong>flight</strong> control system providingpitch-down commands in response to incorrect ADIRU data.- 62 -

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

Saved successfully!

Ooh no, something went wrong!