Originally Posted by A33Zab
That will raise another question, why was IR V/S not available?
was it related to:
02:13:14 - .1/FLR/FR0906010211 34123406IR2 1,EFCS1X,IR1,IR3,,,,ADIRU2 (1FP2),HARD
and this fault message related to disapperance of FPV?
FPV ECAMs fault are due to their selection and rejection (they were unselected before this point) because airspeed was < 60 kt.
It looks like CONF-iture doesn't read (or believe in) BEA reports; this fault was explained and very understandable considering that pressure altitude, barometric vertical speed and true airspeed were altogether affected by high alpha and unvalid dynamic pressure resulting. In fact, it was a triple IR rejection of ADRs - this fault was reported three times, one by each IR, but consolidated into one single ACARS:
Page 38, report #2.
ADIRU2 (1FP2) (2 h 11)
ATA: 341234
Source: IR2
Identifiers: *EFCS1, IR1, IR3
Class 1, HARD
This message was generated by IR 2. For an ADIRU of this standard, it means that the IR considered that the three ADRs were invalid, that is to say that at least one of the three parameters was invalid (SSM status not NO) amongst pressure altitude, barometric vertical speed and true airspeed. As soon as the third ADR is rejected, the IR generates a message pointing to its ADIRU. If one of the IRs considers the three ADRs as being invalid, this must also be the case for the other IRs. It is therefore logical that, in parallel with this ADIRU 2 message generated by IR 2, an ADIRU 1 message was generated by IR 1 and an ADIRU 3 message by IR 3, which would explain the presence of the latter amongst the identifiers.
The fact that EFCS1 was present amongst the identifiers preceded by an asterisk indicates that EFCS1 had at least generated one class 2 message, perhaps followed by a class 1 message. There are too few elements available to determine precisely what the presence of EFCS1 amongst the identifiers means. Nevertheless, it is possible to state that it concerns a rejection of ADR by at least two PRIMs. It has not been possible at this stage to understand why EFCS2, the clone of EFCS1, is not an identifier.