Originally Posted by
sensor_validation
I think you need to revise your timings a bit though to fit in with the detailed ACARS timings - presented in colour here
Yes, the exact timings of the real events related to the ACARS messages that's where I was a bit unsure indeed.
The only thing which seemed reasonable to me was the sequence
Icing -> A/THR /AP lost -> Alt2.
The exact timing may well have been closer together.
so that close to 2:10:05 they were already in Alt2.
Couldn't all the 02:10 messages have been generated early in 02:10, just output in priority order over the next 2 minutes - interrupted only by high priority position report?
Yes, agreed, see above.
The BEA identified one missing ACARS that should have been transmitted before 2:15:15, but impact could have been at 2:14:30. A shorter time of fall seems to fit in better with a single stall/ fall rate.
Agreed that is the second area of uncertainty: It could reasonably have crashed between 2:14:30 and 2:15:15.
I was just on the conservative side, admitting that an earlier impact fits better with the RoD's that can be expected in such a scenario.
I will include the updated timings based on your remarks in my original post.