PPRuNe Forums - View Single Post - AF 447 Thread No. 5
View Single Post
Old 23rd Jul 2011, 00:55
  #587 (permalink)  
A33Zab
 
Join Date: Jun 2009
Location: somewhere
Posts: 451
Likes: 0
Received 0 Likes on 0 Posts
@Takata:

Quite simply if, at any point, you've got 3 valid ADRs and a failure makes those 3 ADRs to be rejected by all PRIMs and Autoflight System (AFS)... it will certainly be called a triple ADR fault. That is what happened starting at 0210:05, in all certaincy (this is also stated as a fact from the 1st BEA report).


I will disagree with the statement "a failure makes those 3 ADRs to be rejected"
Out of 3 sources FCPC can reject only 1 outlier ADR, but the other 2 remain because FCPC is not able to determine which one or even both are delivering wrong information.
If both keep on delivering different information for more than 10s the NAV ADR DISAGREE message is triggerd. This message was not present @ 02:10:16 or subsequent seconds but ca. 2 minutes later.
The first UAS was only transient, ADR 1 lasted only few seconds, ISIS (ADR 3) was absent for nearly 1 minute.

The NAV IAS DISCREPANCY message, triggered when there is a difference in ADR1 (LH PFD) & ADR 2 (RH PFD) was not present.
ADR 2 therefore must have been (+ or - 30Kts) with ADR 1 at that time and was - like ADR 1 - only absent for few seconds (9s or less).

As said the NAV ADR DISAGREE message is presented because crew has to make a decision to elaborate the ADR in error by switching off this (or multiple ADRs) so it will not be available for the FCPC also.

This relevant fault was: PROBE-PITOT 1X2 / 2X3 / 1X3 (9DA)
Its meaning is quite clear: total pressure was out of boundaries and different at each probe-pitot source (9DA1, 9DA2, 9DA3) and the following consequences are well known on ADRs output channels as well as with other systems (A/FLT, F/CTL, NAV) using those values.

Same for this failure message, in fact you should read: PROBE-PITOT 1+2 or 2+3 or 1+3 (9DA?).
Meaning there are 2 or more PITOT-PROBES affected but BITE/CMC can't determine which 2 (or more) are faulted.
This fault is indeed correlated with the first UAS event but same message would have been correlated to the second UAS event @ 02:12 however only the first occurance will be recorded en transmitted to CMC/CFR/PFR.
A33Zab is offline