Search report text, read a short matching passage, then open the source page.
Exact phrases match first; otherwise all words must occur close together. Six excerpts maximum. Text extraction cannot search image-only charts. Warsaw uses a report transcription with missing figures and appendices.
5 matching PDF pages. Showing 5 short source excerpts. Open the document for full context.
Printed page Front matter. PDF page 18.
systematic errors as well as data spikes, and the ADIRU generated a fault message and flagged the output data as invalid. Once the failure mode started, the ADIRU's abnormal behaviour continued until the unit was shut down. After its powerOpen official document at PDF page 18ATSB AO-2008-070: In-flight upset, VH-QPA, 7 October 2008
Printed page 24. PDF page 44.
receiving system could detect when a source system either stopped providing data, or flagged its output data as invalid (Table 2). If a source system (such as the ADIRUs) provided incorrect data to a receiving system (such as the EFCSOpen official document at PDF page 44ATSB AO-2008-070: In-flight upset, VH-QPA, 7 October 2008
Printed page 35. PDF page 55.
crew selected the switch to the CAPT ON 3 position at 0443:45. In addition, if ADIRU 1 flagged one of its output parameters as ‘invalid' (section 1.6.8), then the FDR recorded that parameter from a different ADIRU. This switching wasOpen official document at PDF page 55ATSB AO-2008-070: In-flight upset, VH-QPA, 7 October 2008
Printed page 39. PDF page 59.
on both the FDR and QAR throughout the flight after 0440:26, indicating that ADIRU 1 flagged most of its ADR output data (including the data spikes) as valid. The presence of spikes for all IR parameters on the QAROpen official document at PDF page 59ATSB AO-2008-070: In-flight upset, VH-QPA, 7 October 2008
Printed page 155. PDF page 175.
3.8.2 Detected failure. Any failure where the ADIRU flagged its output data as invalid, or there was a complete cessation of output data. Undetected failure. ‘Any failure which can result in incorrect data transmission on one or severaOpen official document at PDF page 175ATSB AO-2008-070: In-flight upset, VH-QPA, 7 October 2008