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.

<strong>In</strong> summary, the source <strong>of</strong> most <strong>of</strong> the ADR and IR data recorded by the FDR couldvary. Table 8 provides a summary <strong>of</strong> the sources for the occurrence <strong>flight</strong>, based onthe actual FDR data (discussed below).Table 8: FDR’s source <strong>of</strong> ADR and IR parameters (except AOA)TimeAIR DATAswitchpositionSource <strong>of</strong>ADR dataATT HDGswitchpositionSource <strong>of</strong> IRdataTake<strong>of</strong>f to 0440:28 NORM ADR 1 NORM IR 10440:28 to 0441:37 NORM ADR 1/ADR 2 NORM IR 20441:37 to 0443:45 NORM ADR 1 NORM IR 20443:45 to 0506:48 NORM ADR 1 CAPT ON 3 IR 30506:48 to landing NORM ADR 1/ADR 2 CAPT ON 3 IR 3Summary <strong>of</strong> ADR data for the occurrence <strong>flight</strong> (from the FDR)Soon after 0440:26, spikes became evident on all <strong>of</strong> the recorded ADR parametersfrom ADIRU 1 (Figure 19). The recorded spikes occurred at different times foreach parameter, and the spikes for many <strong>of</strong> the parameters contained repetitions <strong>of</strong> asmall number <strong>of</strong> values. As the data output rate <strong>of</strong> the ADIRUs was much higherthan the recording rate <strong>of</strong> the FDR 50 , the data available to the investigation wasincomplete, and it was not possible to determine the full nature, magnitude andfrequency <strong>of</strong> the data spikes. Further discussion <strong>of</strong> the data-spike characteristics isprovided in section 3.3.From 0440:41 to 0441:37, the ADR 1 Fail parameter intermittently recorded a failvalue (Figure 20), which indicated that at least one <strong>of</strong> the ADR 1 parameters (eitherstandard altitude or computed airspeed) was flagged as invalid during this period.From 0441:38 to 0506:48, the ADR 1 Fail parameter did not record any failindications; however, the FDR recorded many spikes in all recorded ADRparameters (including standard altitude and computed airspeed) during that time.Consequently, because no source switching had occurred, it was evident thatADIRU 1 had transmitted data spikes to other systems as valid data.The FDR did not record any fail values for ADR 2 or ADR 3.50As examples, the ADIRU outputted Mach eight times per second and the FDR recorded it onceper second, and the ADIRU outputted pitch attitude 50 times per second and the FDR recorded itfour times per second.- 36 -

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

Saved successfully!

Ooh no, something went wrong!