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.

equipment s<strong>of</strong>tware and aircraft installation. The final assessment contained over2,000 pages <strong>of</strong> documentation, and data from the SSA was included in thecertification dossier that was provided to the certifying authority (that is, theDGAC).2.5 Development <strong>of</strong> the algorithm for processing AOA2.5.1 Preliminary A330/A340 FCPC algorithmThe FCPC algorithm for processing AOA data was a small but important element <strong>of</strong>the overall EFCS. The general safety objectives for the algorithm (and the rest <strong>of</strong>the EFCS) were based on JAR 25.671, JAR 25.1309 and associated guidancematerial, and included the safety objective that no single failure should result in acatastrophic failure condition. The aircraft manufacturer advised that otherrequirements for the algorithm were that the:• AOA values from the three ADIRUs were to be acquired by each channel (COMand MON) <strong>of</strong> each FCPC• aircraft behaviour must be acceptable in the case <strong>of</strong> a runaway <strong>of</strong> one <strong>of</strong> thethree AOA values.Consistent with the aircraft manufacturer’s objective (section 2.4.3), the preliminarydesign <strong>of</strong> the FCPC algorithm was the same as that certified for the A320 in 1988. Itdid not include a memorisation period and had several other differences to thealgorithm that was ultimately used on the production A330/A340 aircraft (describedin sections 2.1.4 and 2.1.5).The preliminary FCPC algorithm for processing AOA data was subject to themanufacturer’s processes for generating requirements, verification and validation,including safety assessment. None <strong>of</strong> these activities, up until <strong>flight</strong> testing,identified any need to change the algorithm’s design.<strong>In</strong> December 1991, during a test <strong>flight</strong> on an A340, a problem was identified withthe operation <strong>of</strong> the preliminary algorithm. The algorithm did not effectivelymanage a specific situation where AOA 2 and AOA 3 on one side <strong>of</strong> the aircraftwere temporarily incorrect and AOA 1 on the other side <strong>of</strong> the aircraft was correct,resulting in ADR 1 being rejected.2.5.2 Redesign <strong>of</strong> the preliminary algorithmAfter reviewing the problem that was identified during <strong>flight</strong> testing, the aircraftmanufacturer redesigned the FCPC algorithm. This led to the final algorithm forprocessing AOA data, which included the 1.2-second memorisation period andseveral other changes (described in sections 2.1.4 and 2.1.5).The manufacturer advised that the 1.2-second duration <strong>of</strong> the memorisation periodwas considered to be the maximum time period that the aircraft could use amemorised AOA value in dynamic manoeuvres. Accordingly, the FCPCs required acurrent AOA value to be obtained at the end <strong>of</strong> the memorisation period, and thefinal algorithm was designed to ensure that a second memorisation period wouldnot be triggered without a new value first being obtained.- 95 -

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

Saved successfully!

Ooh no, something went wrong!