Originally Posted by bearfoil
Everything never happens at once. If that were so, there would be no time. What happened prior to 2h10m05s to cause "..all disconnected at 2h10m05s?"
Bold doesn't make you bolder.
Nothing before 0210:05.
And yes, at 0210:05, the speed function was simply invalidated by the PRIMs after a 1 second check out of its limit range... that's all!
It is all you need to have the following sequence of ACARS (and more).
- First dispatched: those are the cockpit effects (warnings) without failure.
- Root system failures are at the end of the ACARS list for the whole sequence: Pitots fault and this ADIRU faults.
CMC needed to crosscheck what systems caused the failures (internal, external, etc.) before dispatching the failure ACARS while cockpit effects are immediatly processed once they occured. The following time sequence is due to the protocole as the messages are queued and dispatched one by one. It will be clear from the DFDR tracks that all those warnings were basically simultaneous and that any delay in warning would be caused by priority order functions.
For example, there is a small delay between AP OFF and ATHR OFF because the later is retardated for not confusing both cockpit alarms sounding.