Originally posted by Svarin ...
One interpretation is PRIM2 loses connection with ADR1 (part of ADIRU1) through a failed bus. BEA explained it away with "PRIM2 rejects ADR1"... However, this particular failure does not seem to have anything to do with unreliable airspeed and ADR comparison, it is quite obviously an electronics connectivity issue : WRG means wiring, gentlemen. Airbusese for "warning" is WRN.
How strange is it that such an event, electr(on)ical in nature, would be simultaneous with the failed probes, which has external causes (icing) :
02:11:49 PROBE-PITOT 1X2 / 2X3 / 1X3 (9DA), HARD
Thanks for your the analysis of the ACARS messages, and I should point out to others that
Svarin has posted other thoughtful insights into what may have happened, and they are spread throughout the AF447, Air France A330 accident, and AF447 Search to resume threads.
My initial comment is that the WRN messages took precedence and the F/CTL ones that were flagged took overall precedence - as one would expect. Something tells me that the 02:10 FCPC2 (2CE) WRG: ADIRU 1 BUS ADR1-2 TO FCPC2 may have been precipitous to the whole sequence, as a wiring fault manifest itself in turbulence. The unreliable airspeed data could be put down to an unplanned nose-up command to the THS, resulting in the rapid bleed off of airspeed as the A/P and A/THR found themselves in new territory (and beyond their limits) - not to forget the "test" pilots.
What does ADR1-2 mean, i.e. the "-" part?
Why should the BEA dismiss it as PRIM1 rejects ADR1? Possibly because there were other known events that could be linked to the Pitot Probes, and it gave a means of addressing that issue while reserving the right to determine otherwise when the recorders were found and analyzed.
PJ2 has explained that a fault which is declared consolidated is transmitted to the CMC as being a "hard" fault, but in this case it has not been correlated. Perhaps the CMC saw fit to declare this fault once as a Maintenance issue, knowing that on the ground any correlation would be followed up, and the initial ACARS message is all that is required. The most noticeable point, is the 0210 time-stamp, and why would a wiring/connectivity fault suddenly show up in the course of other mayhem. More likely the wiring fault came first and caused the mayhem.
A lightning issue? No, as has been explained previously, none was detected in the area during the course of this event.