[JoeDColeman1981]

@Curtis
Re P channel issues - it was in one of the Satcom System Specification Manuals, referenced way back, can't find it just now.  Go over to Victor's blog, they have mentioned it again.

Also note this....

Thanks much, Ventus45

As for P channel: Pardon, bad worded: I saw the specifications, which tells us that a disturbed connection would result in renewing of the  log on, which of course is huge different to log on after power outage. My question was meant like: "How can it happen that the P-channel signal is disturbed?" What can we deduce from that if anything.

I agree about the odd behavior of Inmarsat, which makes it suspicious, of course even more since the resulting search came up blank, and some other possible leads were discarded mainly because of this very data interpretation. This "we gave it to the authorities, go ask them" and the authorities`"investigation ongoing, no publication", "the radar details are too sensitive", "wait for final report" and so on, may be usual for a certain time - but now for almost 3 years?

And WOW! Inmarsat first said, the ca 1830 UTC pings were the closest to satellite?? Will try to find something about it.

It is similar odd,  in my humble view,  like the "later found 0019 ping"; which i cannot understand, when working with a data base - and when the log off MUST be visible in GES logs immediately and giving a good estimate of the last connection before that.

Another point IMO could be, if the ACARS transmission from 1707 was last satcom activity, shouldn´t be there a GES interrogation at  ca. 1807 + max 4 minutes = 1811 with a resulting log off at GES after some attempts?  

And; if the 1721 events would have triggered an ACARS transmission, we would come up at 1825? The latter must be coincidence, because as per data log, there were no further ACARS.

Which would lead to the question who is getting nervous if ACARS is missing? Nobody?

Who took care about the 1737 and 1807 missing ACARS?

And why did the confidential RMP report did not contain - as far as we know - any reports from witnesses, whereas there are several reports about witnesses that have filed some. Witness reports that do not corroborate the official story. And so on.

Well, may be I am mistaking it all - I am no way expert in these matters - but it looks strange; and, it does not help me to believe in ping data´s virginity. (probity).

P7 my edit - Nice post Curtis; "V" is your man, bet he's thinking on it all - right now.

I'm thinking that after sometime after 17:07:48.907 the ACARS may have been turned off because of this a handshake request (1hr) would have been just after 18:07, but didn't happen because MAS tried to get ACARS info (5 requests) at 18:03:41 after ATC contacted (where's your plane) them at 18:02. If the sat comm had never came on at 18:25 and 18:28 then the next handshake because of the 18:03 (5 requests) activity would have been just after 19:04. Then MAS make at call at 18:39 (unanswered) which would make the next handshake request be 19:41 then no other interrupting requests. 20:41 then 21:41 22:41. Then a call at 23:13 would reset the send out request again due for approx an hour later that did happen 00:10:59. Then sat comm comes back on 00:1929 for a partial handshake.

The RMP report once investigated at the time perhaps didn't fully understand what happened with hourly ping interruptions and since seems to have not been corrected or updated.

P7 Edit - Coincidence, happenstance or' enemy action ?