This website uses certain Blogger and Google cookies, including use of Google Analytics and AdSense cookies, and other data collected by Google. By remaining on this site, your consent is implied.

January 16, 2017: Just as I predicted would eventually happen (back on December 16, 2014), the Australian Transport Safety Bureau (ATSB) has ended their search for the MH370 plane crash wreckage in their search area without ever finding MH370 in it: Underwater search of 120,000 square-kilometre area in the southern Indian Ocean completed. Wreckage of Malaysia Airlines flight MH370 not found there. Malaysia, China and Australia announce decision to suspend the underwater search. "Paul Kennedy, the project director of Fugro – the Dutch company leading the search – acknowledged on Thursday [July 21, 2016] that, if the plane was not found there, "it means it's somewhere else"."

Translate

Friday, June 6, 2014

Inmarsat log file message data at 17:07:34 UTC

Hover over image to open it in a larger view.

Originally, I thought I had found an anomaly in the Inmarsat MH370 Data Communication Logs file that was released, at time 17:07:34 UTC.

But upon further examination of the surrounding data, I think I can explain the anomaly and disregard it.

In my Method of calculating MH370's distance from satellite post, I showed a diagram and formulas for how to calculate MH370's distance from the Inmarsat 3F1 satellite.

I extracted only the following message types from the original data file, and only for cases where these messages were one after the other (i.e. no other messages occurred between them):

0x22 - Access Request (R/T-Channel)
0x51 - T-Channel Assignment

At 17:07:34 UTC, the delta time between the messages was 0.020 seconds less than it was for all previous messages of this same type. The delta time was also less than the minimum calculated round trip time.

The minimum calculated round trip time is based on MH370's known Slant Range to the satellite and the Perth GES 305's known Slant Range to the satellite at 17:07:34. But, the 0x62 message before the 0x22 message took 0.020 seconds longer than previous ones, so that might explain this time anomaly.

I was originally going to include all of the data from my calculations in this post, but because I no longer believe there is anything of interest with this data point at 17:07:34 UTC, the anomaly issue is now moot.

I made this blog post for completeness, because I had mentioned this on The Guardian.

No comments:

Post a Comment

I am using comment moderation and word verification to prevent spam. If you want to provide information, but remain anonymous, please state that at the beginning of your comment, and I will not publish it.

If you want to communicate with me, either use the Contact Form or leave your email in a comment and I will contact you but not publish it. I do not use Twitter, Facebook, etc. therefore I am unable to communicate with you using those.

I appreciate any useful information relevant to the disappearance of MH370.