So, Holland's paper is essentially telling us, that the BFO's don't tell us a hell of a lot - not really, so don't get your knickers in a knot over it. Hmmmmmm ...
And why publish it at Cornell ? https://arxiv.org/pdf/1702.02432.pdf Why not through the ATSB (I am choking on that ! - too much Merlot last night - but it was a good drop !)
Then of course there is his UNPUBLISHED "reference 7"
[7] “Internal study regarding SATCOM ground-station logs,” MH370 Flight Path Reconstruction Group - SATCOM Subgroup.
WE NEED that. Mr Greg Hood, for your IMMEDIATE ACTION - thank you.
Moving right along now.
The pesky question of The ATSB's often repeated ASSERTIONS that "an in flight log on by the AES can ONLY be due to POWER INTERRUPTION" raises it's ugly head yet again.
As previously stated, and previously buried, but now "resurfaced" the FACT is, that the way the SYSTEM is designed and specified, REQUIRES the AES to maintain synchronization via CONTINUOUS monitoring of the P channel.
If the P channel is lost for a short time (specified in the literature previously posted way back) synchronization will be lost. Loss of the P channel can occur a number of different ways, and if it does, it will FORCE the AES to initiate a NEW log-on request.
NOTE - NO POWER CYCLING IS REQUIRED, so all the "power loss = second engine flame-out = APU start etc" theories are quite probably "out the window".
Consider the following - from Jeff Wise's Blog
![[Image: attachment.php?aid=249]](http://auntypru.com/forum/attachment.php?aid=249)
And also consider this - From Victor Iannello's Blog
![[Image: attachment.php?aid=250]](http://auntypru.com/forum/attachment.php?aid=250)
The discussion continues at Victor's new blog: http://mh370.radiantphysics.com/2017/02/...h370-data/
And why publish it at Cornell ? https://arxiv.org/pdf/1702.02432.pdf Why not through the ATSB (I am choking on that ! - too much Merlot last night - but it was a good drop !)
Then of course there is his UNPUBLISHED "reference 7"
[7] “Internal study regarding SATCOM ground-station logs,” MH370 Flight Path Reconstruction Group - SATCOM Subgroup.
WE NEED that. Mr Greg Hood, for your IMMEDIATE ACTION - thank you.
Moving right along now.
The pesky question of The ATSB's often repeated ASSERTIONS that "an in flight log on by the AES can ONLY be due to POWER INTERRUPTION" raises it's ugly head yet again.
As previously stated, and previously buried, but now "resurfaced" the FACT is, that the way the SYSTEM is designed and specified, REQUIRES the AES to maintain synchronization via CONTINUOUS monitoring of the P channel.
If the P channel is lost for a short time (specified in the literature previously posted way back) synchronization will be lost. Loss of the P channel can occur a number of different ways, and if it does, it will FORCE the AES to initiate a NEW log-on request.
NOTE - NO POWER CYCLING IS REQUIRED, so all the "power loss = second engine flame-out = APU start etc" theories are quite probably "out the window".
Consider the following - from Jeff Wise's Blog
And also consider this - From Victor Iannello's Blog
The discussion continues at Victor's new blog: http://mh370.radiantphysics.com/2017/02/...h370-data/
