[Peetwo]

For and on behalf of Michael John - One of the many long suffering MH370 followers, who are consistently probing, researching, calculating and theorising in the information vacuum that still continues to surround the disappearance of MH370 is Michael John; or MJ on social media...

Anyway MJ has requested that his theory on the riddle of the Inmarsat intercepted MH370 BFO signals be put to public; and/or expert (boffin - ) scrutiny:
 

Michael John
Shared publicly  -  5:56 PM
 
The riddle of the Inmarsat all comes down to the wobble of 3-f1 & possibly in part the issues with the plane.

The errors came with the final 2 ARC positions which I discovered are each out by just 10 degrees & 20 degrees respectively.

This can be checked & I am confident that these checks will confirm my suspicions.

So what else? Well the FMT did exist but this occured at the SDU reboot. For whatever reason Mh370 continued to fly at half velocity than it's previously recorded data track.

I know that the BFO is based on the planes position above the satellite. I also know that when the data was graphed out it was done erroneously (I am not suggesting intentionally either).

I have shown in the attached imagery how the graph should be laid out. Note after 1st turn back the data should have been recorded right to left as shown in my own graph.

Elsewise I have kept true to the data specifics. I plotted up until the 1st data stream was lost & started again at SDU reboot. All I had to do then was link the 2 & that gives us the missing data for the Malacca Strait. This can be corroborated by the military radar.

Next I used the location of my interest which is West of Banda Aceh in Northern Sumatra as a finish point. I noticed looking at the over view that my now graphed data points were a accurate match for a path in this direction.

So what went wrong & why does the data imply a flight into the SIO? It all comes down to the wobble IMO. The difference in the ARC positions is just 10 degrees. That is it. No changing any of the small numbers just adding a compensation of 10 & 20.

Again all this is shown in the attached imagery. I am 100% confident that this entire proposal will stand up to any scrutiny. As I keep painfully pointing out, the BFO (Hz) readings are exactly how they should be. It is the compensation for the wobble that has caused everything to go wrong & even that only occurs at the final 2 ARCS.

The ARC at 22.40pm should be 57.32 & the ARC at 0.10am should be 60.07. Now looking at ARC positions & my plotted map you should find that those 2 slight compensations in ARC positions accurately match the plot perfectly. What that means is that by moving those 2 ARC positions into line but not altering the actual data will make the overall sum more accurate & any discrepancies will disappear.

Couple this with my satellite imagery you have a crash/ ditch location that matches not only the data but the witness sightings & even the Curtin University sound.

Bottom line is that this is indeed the answer to Mh370.

12/04/2016
5 photos

Michael John's photos

PAIN is by nature made up of largely professional aviators/engineers and ATCOs, so we are probably not much help to MJ. However some of our readership/forum membership may be willing and able to review MJs theory...


MTF P2