Originally posted by HN39 ...
The first nine messages follow each other without interruption at an average rate of 6,25 sec/msg, which seems to be the maximum rate allowed by the communication protocol. In other words, these messages may have been generated quasi simultaneously.
I agree, but with regard to the ACARS sequencing, I can only assume that the priority is Flight Controls (auto), Flight Controls(other), Nav, Comms, Maintenance. The F/CTL RUD TRV LIM FAULT has probably been delayed as it is a by-product of the earlier F/CTL ALTN LAW
The AUTO FLT REAC W/S DET FAULT warning seems to be be a little out of place; by that I mean that the windshear predictive function is only available below 1500 feet and windshear below 1300 feet. This maybe a case where warnings regarding its availability should have been inhibited in this phase of the flight. However, it helps with our understanding of the possible causes of this upset.
Three maintenance warnings were not displayed to the crew, and it would appear by the gap between -
2:11:00 WRN/WN0906010210 228300106FLAG ON CAPT PFD FD
2:11:15 WRN/WN0906010210 228301106FLAG ON F/O PFD FD
that there was nothing else sequenced during that period, and that the PF was seated in the left-hand seat - assuming he went looking for the "bird" first.
The
ACARS list has been updated to indicate (using background colors) the relative importance of the various Warnings and Failures. FLAG warnings are in pastel purple except for the warnings that the crew generated when they went looking for the AoA "bird", which are in pastel green. NAV warnings are in pastel orange, F/CTL warnings are in yellow and AUTO FLT warnings are in cyan.
MAINTENANCE messages have a dark grey/gray background and FLR messages are displayed as dark red, while the AUTO FLT REAC W/S DET FAULT is in pink. The final ADVISORY message has a white background.
Clicking on a line will cause the Time of Receipt to be highlighted in yellow. Clicking again will revert the line to normal.
mm43