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...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Summary <strong>of</strong> IR data for the occurrence <strong>flight</strong> (from the FDR)The FDR only recorded two data spikes for the IR parameters, both for magneticheading (at 0441:38 and 0442:04).From 0440:26 to 0440:31, some <strong>of</strong> the IR parameters showed deviations from theircorrect values. After 0440:31, the IR 1 Fail parameter continuously recorded a failvalue (Figure 20). This result indicated that, after this time, ADIRU 1 flagged all <strong>of</strong>its IR 1 data for at least one <strong>of</strong> its parameters (either pitch attitude or roll attitude) asinvalid, and that the FDR’s source <strong>of</strong> IR data had quickly switched from IR 1 to IR2 for one or more parameters. From 0443:45, when the crew selected the ATT HDGswitch to CAPT ON 3, the IR 3 became the source <strong>of</strong> all the IR parameters recordedby the FDR, and no deviations or spikes were recorded.The FDR did not record any fail values for IR 2 or IR 3.1.11.3 Quick access recorder (QAR)System descriptionThe aircraft’s QAR recorded approximately 250 aircraft <strong>flight</strong> data parameters. 51The data was stored on a removable magneto-optical disk with a capacity <strong>of</strong>230 megabytes.Files stored on the QAR disk were successfully recovered by the ATSB. Theycontained <strong>flight</strong> data from the occurrence <strong>flight</strong> and six previous <strong>flight</strong>s.The QAR and FDR obtained their data via different signal paths (Appendix B).QAR process for recording ADIRU dataThe QAR recorded 16 ADIRU parameters, including the 11 parameters that wererecorded by the FDR (Table 1). As with the FDR, the QAR sampled most <strong>of</strong> theparameters once per second. However, the FDR and QAR were independentsystems and they sampled the parameters at different times. As with the FDR, bothAOA 1 and AOA 2 were recorded, but only one source <strong>of</strong> the other parameters wasrecorded.The QAR received its data from a data management unit (DMU), and the source <strong>of</strong>the ADIRU parameters was configurable when the DMU was programmed. For theoccurrence aircraft, the source <strong>of</strong> most ADIRU parameters was fixed to ADIRU 1.Unlike with the FDR, there was no switching <strong>of</strong> the source recorded by the QAReven if ADIRU 1 flagged a parameter as being invalid. The only exceptions werecomputed airspeed and magnetic heading; if the QAR data for either <strong>of</strong> thoseparameters was flagged as invalid by ADIRU 1, then the QAR’s source switched toADIRU 2.51Unlike the CVR and FDR, the QAR was not required to be installed by regulation. However,operators elected to install the recorder to enable routine and easily accessible monitoring <strong>of</strong>aircraft and <strong>flight</strong> crew performance. As the parameters recorded by the QAR were configurableby an operator, it was described as a Digital ACMS Recorder (DAR) in Airbus terminology. Toavoid confusion, the generic term QAR is used in this report. ACMS is an abbreviation forAircraft Condition Monitoring System.- 38 -

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

Saved successfully!

Ooh no, something went wrong!