Godlike Productions - Discussion Forum
Users Online Now: 1,657 (Who's On?)Visitors Today: 589,543
Pageviews Today: 1,262,632Threads Today: 552Posts Today: 10,422
05:18 PM


Rate this Thread

Absolute BS Crap Reasonable Nice Amazing
 

Inmarsat Data MH370 shows SEVEN/ EIGHT planes

 
redhouserebel
Offer Upgrade

User ID: 67869536
United Kingdom
02/20/2015 11:08 PM
Report Abusive Post
Report Copyright Violation
Inmarsat Data MH370 shows SEVEN/ EIGHT planes
If you follow this link and enclosed links - you will find planes for MH370 all over the place.

I previously took the P-Channel data to be the planes - no - the P-Channels x3 are the IOR ground satellite stations in the Indian ocean region.

These three ground earth satellite stations all picked up what they believed was the plane.


Later Inmarsat Ground station in Perth was also said to have picked up two pieces of data - these pieces are not included in the published reports but are the data which was used to say the plame MH370 was in the southern ocean.


Listed are EIGHT R-Channel IDs.

The R-Channel is the data FROM the plane - it is the R-Channel that identifies the plane.


Scroll down to this post:


Ok - just when you thought things couldn't get any crazier... I have found some info I have been looking for - and it is totes cray cray - like seriously - but it matches with what I felt was happening and confirms a conspiracy - and also shows I have made some errors:


Noting the 3 P-Channel IDs - I put these down to being plane identities - they are not - they are ground based IDs - so these are ground based stations in contact with "the plane" - so for example - this could be KL ATC Cambodia and MAS OPS - that is for example.

Then there are the 4 different T-Channel numbers which kept getting swapped about


And the EIGHT different R-Channel IDs - I previously made the assumption that these were R for radar and thus the ground based stations: this is incorrect - these are EIGHT planes.


I will post info and links shortly while you get your head round that.


You will see from the info that P-Channel is info TO the plane and R-Channel is FROM the plane


The thing is this: the ground station won't acknowledge data from two planes with the same Q number at the same time - only from one - and also if a plane does not respond - then it interrogates - so if you wanted to keep a plane grounded or land it - you would then need to reassign its Q number to another plane - if you wanted to maintain the appearance the plane was still flying.

So for example - if you asked a plane on the east coast of Vietnam to assume the Q number of the flight - the tail number - then to prioritise this data you would have to unsign the other planes so this data would be recorded - then - if that plane was going to be landing in say nanning shortly but was the wrong flight - and you are doing something with the grounded plane and passengers - then you need to reassign another plane so that data keeps responding to the P-Channel automatic requests etc.


EIGHT PLANES.


EIGHT.


x
 Quoting: redhouserebel


on this page:


Thread: INMARSAT SATELLITE DATA FOR MH370 SHOWS DATA FOR THREE PLANES UPDATE PAGE 5: EIGHT PLANES IN INMARSAT DATA EIGHT PLANES (Page 5)



and continue for explanations links and updates.



xx

Last Edited by redhouserebel on 02/21/2015 12:01 PM
A MILF Mortgage - coming soon ;)
redhouserebel  (OP)

User ID: 67869536
United Kingdom
02/20/2015 11:18 PM
Report Abusive Post
Report Copyright Violation
Re: Inmarsat Data MH370 shows SEVEN/ EIGHT planes
Is it seven or eight? I know my first count was wrong - as I later found another one - I will have to count again and double check - if anyone is actually counting anymore....so its back to the drawing board again.




This link tells you who uses inmarsat:


[link to www.satcomdirect.com]




US Government
– Military
• USA, USAF, USN, USMC, USCG
– Federal
• State Dept, FBI, DHS, USCBP, DIA, CIA, ???


2 more pages about P-channel

[link to books.google.co.uk (secure)]


[link to books.google.co.uk (secure)]
A MILF Mortgage - coming soon ;)
plus
User ID: 68119718
Hong Kong
02/20/2015 11:20 PM
Report Abusive Post
Report Copyright Violation
Re: Inmarsat Data MH370 shows SEVEN/ EIGHT planes
You might enjoy this, it seems right up your alley. hf

I'm not really sure but it sounds like just the kind of thing you could come up with so you might appreciate the sleuthing, if nothing else.

March 10, 2002 -- Eureka! One of my readers, who calls himself "Snake Plissken," has put it together. He tells us why the passenger lists of the four September 11 "suicide" jets were so small, how remote control was used, why the transponders were turned off, why the radar tracks of the four planes were confused, why there was no Boeing 757 debris at the Pentagon.

By George, I think he's got it!

My e-mail exchanges with Snake took place over a series of days. With Snake's agreement, I have consolidated the exchanges, inserted some reference URLs, and made minor edits. My comments and additions will be bracketed thus [ ]. As you read what Snake has to say, keep the following in mind:

Magic is the pretended performance of those things which cannot be done. The success of a magician's simulation of doing the impossible depends upon misleading the minds of his audiences. This, in the main, is done by adding, to a performance, details of which the spectators are unaware, and leaving out others which they believe you have not left out. In short a performance of magic is largely a demonstration of the universal reliability of certain facts of psychology.
(John Mulholland, The Art of Illusion, Charles Scribner & Sons, 1944.)
In what follows, Snake unravels the illusions of the 9-11 magicians.
[link to www.public-action.com]
redhouserebel  (OP)

User ID: 67869536
United Kingdom
02/20/2015 11:23 PM
Report Abusive Post
Report Copyright Violation
Re: Inmarsat Data MH370 shows SEVEN/ EIGHT planes
How and why a GES ground sat station cannot receive from more than one plane with the same ID at the same time follows - but remember - a different GES ground station can still pick up a plane with the same ID and will not put it into a queue - so this is why at the end of the flight - we have three sets of coordinates - from three different GES ground stations picking up 3 planes at those times: this allows one plane to land and switch off - while another takes on its role so as not to interrupt the communications - which would then be noted:



1.2.4 C channel. Circuit-mode single channel per carrier (SCPC) channel, used in both to-aircraft
and from-aircraft directions. This channel is time division multiplexed to provide a primary channel for voice
or data traffic and a sub-band channel for signalling, supervision, and data messages. The use of the channel
is controlled by assignment and release signalling at the start and end of each transaction.



Simultaneous transmission on the R channel and the T channel shall not be required. Simultaneous
reception on more than one P channel shall not be required.



Simultaneous operation of the C channel with either the R channel or the T channel shall not be required


Note.! An AES with Level 4 capability provides digitized voice capability on a C channel simultaneously
with packet mode data capability on the R channel or the T channel. Two receive channels and two
transmit channels are required.
1.3.5.2 Recommendation.- A Level 4 AES should be capable of simultaneous R and T channel
transmissions whenever the C channel is not in use.

[link to www.icao.int]
[link to www.icao.int]




5.1 GENERAL
5.1.1 The P and R channels are used for signalling and data communications in the to-aircraft and
from-aircraft directions, respectively. Data transmission on the R channel is restricted to short messages (less
than 33 octet link service data units (LSDUs)).

[link to www.icao.int]

5.4 P CHANNEL PROTOCOL
5.4.1 The P channel link layer protocol is used in the to-aircraft direction for processing the
transmission of 1) the LIDUs received from the GES management, 2) the LIDUs received from the
circuit-mode services with routing parameters indicating transmission on the P channel, and 3) all LIDUs5-2
received from the subnetwork layer. The P channel protocol reliable link service (RLS) is used for processing
the transmission of the LIDUs received from the subnetwork layer only. The transmission of all other LIDUs
is processed according to the P channel protocol direct link service (DLS). The P channel is also used for the
transmission of the following link layer signalling SUs:
a) T channel reservation (RES) and reservation forthcoming (RFC) SUs associated with
the T channel reservation protocol [Part I, 6];
b) T channel acknowledgement (TACK) SU; and
c) R channel acknowledgement (RACK) SU.
The above SUs are transmitted in accordance with the P channel protocol DLS service.
5.4.2 At a given time, the P channel protocol may be processing the transmission of several LSDUs
(a reference number has been assigned and an SU set has been generated from each LIDU to transmit the
LSDU). However, for RLS, at each Q number only one LSDU of the LSDUs destined to the same AES is
permitted to be in process for transmission at one time. The other RLS LSDUs with the same Q number and
destined to the same AES will be stored until the transmission of the current LSDU at that Q number is over,
either successfully or unsuccessfully. Thus, at the AES, only one RLS SU set per Q number could be in the
reassembly process at a given time and the AES will discard an incomplete RLS SU set if it starts receiving
another RLS SU set with the same Q number and a different reference number. After either a successful or
an unsuccessful transmission of an SU set, the GES link layer releases all link layer resources associated with
that SU set, i.e. the assigned reference number, activated timers, memory allocation, etc.

[link to www.icao.int]

Failure to receive an acknowledgement from the an AES would
cause the GES to solicit such acknowledgement by sending a request for acknowledgement (RQA) SU to that
AES. The AES keeps track of the status of the RLS SU set that the AES is currently processing at a given Q
number in order to correctly respond to an RQA.
5.4.4 In an SU set, original or retransmitted, only the ISU, or the RTX SU, identifies the
destination AES ID. In order to avoid erroneous processing due to the broadcast nature of the P channel, the
AES discards an SSU if received without previously receiving the corresponding (same reference number and
Q-number) ISU, or RTX SU.

The R channel is also used for the transmission of the following link layer signalling SUs:
a) P channel acknowledgements (PACKs);
b) T channel request for acknowledgement (RQA); and
c) T channel request for reservation (REQ).


5.5.3 At a given time, the R channel protocol at the AES may be processing the transmission of
several LSDUs (reference number is assigned and an SU set is generated from each LIDU to transmit the
LSDU). However, for RLS, at each Q number only one LSDU is permitted to be in process for transmission
to the GES at one time. Other RLS LSDUs with the same Q number will be stored in the AES until the
transmission of the current RLS LSDU at that Q number is over, either successfully or unsuccessfully. Thus,
at the GES, only one RLS SU set per Q number per AES could be in the reassembly process at a given time
and the GES will discard an incomplete RLS SU set if it starts receiving another RLS SU set with the same
Q number from the same AES. After either a successful or an unsuccessful transmission of an SU set, the
AES link layer releases all link layer resources associated with that SU set, i.e. the assigned reference number,
activated timers, memory allocation, etc.


5.5.4 For RLS, the R channel protocol implements a selective-repeat-ARQ scheme for error
control. Accordingly, upon transmitting an SU set, the AES expects to receive an R channel
acknowledgement (RACK) SU from the GES. The RACK SU may indicate either complete or incomplete
reception using its acknowledgement control field. In the later case the RACK SU also indicates the missing
SUs of the SU set by identifying their sequence indicators. The AES transmits the indicated missing SUs
without any alterations to their contents. The largest SU set on the R channel contains three SUs, thus, the
GES may identify at the most two missing SUs in a RACK SU, one SU of the set must be correctly received
at the GES in order to detect an attempt of an SU set transmission.
5.5.5 The R channel is a multiple access channel, therefore, the GES concurrently receives SUs
from all AES assigned to one set of R channel frequencies. Each received SU contains the source AES ID.
Thus, the received SUs are first sorted out according to their AES IDs and then independently processed.
[Part I, 5.8.3] contains the R channel protocol requirements corresponding to the processing of SUs from a
given AES.
A MILF Mortgage - coming soon ;)
redhouserebel  (OP)

User ID: 67869536
United Kingdom
02/20/2015 11:29 PM
Report Abusive Post
Report Copyright Violation
Re: Inmarsat Data MH370 shows SEVEN/ EIGHT planes
You might enjoy this, it seems right up your alley. hf

I'm not really sure but it sounds like just the kind of thing you could come up with so you might appreciate the sleuthing, if nothing else.

March 10, 2002 -- Eureka! One of my readers, who calls himself "Snake Plissken," has put it together. He tells us why the passenger lists of the four September 11 "suicide" jets were so small, how remote control was used, why the transponders were turned off, why the radar tracks of the four planes were confused, why there was no Boeing 757 debris at the Pentagon.

By George, I think he's got it!

My e-mail exchanges with Snake took place over a series of days. With Snake's agreement, I have consolidated the exchanges, inserted some reference URLs, and made minor edits. My comments and additions will be bracketed thus [ ]. As you read what Snake has to say, keep the following in mind:

Magic is the pretended performance of those things which cannot be done. The success of a magician's simulation of doing the impossible depends upon misleading the minds of his audiences. This, in the main, is done by adding, to a performance, details of which the spectators are unaware, and leaving out others which they believe you have not left out. In short a performance of magic is largely a demonstration of the universal reliability of certain facts of psychology.
(John Mulholland, The Art of Illusion, Charles Scribner & Sons, 1944.)
In what follows, Snake unravels the illusions of the 9-11 magicians.
[link to www.public-action.com]
 Quoting: plus 68119718




I will definitely look at your link - and I understand the magic deception analogy - as with MH17 I referred to the ball and the cups - which cup is the ball under kind of thing.


If they wanted something bad enough - they would have used many planes - all they had to do was fly about - so people seeing planes land at Butterworth U-Tapao - crashing in this sea that sea - off Vietnam up in Cambodia - pinging in Australia etc unidentified plane here there everywhere - so long as they kept the satellite pings going - very well thought out really.


Inmarsat tech is amazing to have recorded all of this shenanigans - I hope they take care of my new mobile phone when it arrives on Monday - my old one hasn't worked since last October - I am such a dill. chuckle


xx
A MILF Mortgage - coming soon ;)
redhouserebel  (OP)

User ID: 67869536
United Kingdom
02/21/2015 12:02 AM
Report Abusive Post
Report Copyright Violation
Re: Inmarsat Data MH370 shows SEVEN/ EIGHT planes
hey Hong Kong dude - just read this link you gave me

[link to www.public-action.com]


very interesting.


Great thing about this case - MH370 is that Inmarsat have given us data - even if we do only have the published portions - it means this is not just speculation - but based on fact; reliable fact/s.



This must surely provide some sort of case for the families involved.



For anyone affected - we all have been - terrorised - and even more so now.
A MILF Mortgage - coming soon ;)
redhouserebel  (OP)

User ID: 17654831
United Kingdom
02/21/2015 11:29 AM
Report Abusive Post
Report Copyright Violation
Re: Inmarsat Data MH370 shows SEVEN/ EIGHT planes
Right - going back through my notes - I have the following R-Channel list - I know at some point I found an extra R-Channel which i didn't originally find and so I don't know yet if I added it this list - so either 7 planes if I did add it - or 8 if I didn't:


IOR-R1200-0-36E3 - 12 OCCURRENCES FROM 00.07 TO 00.29.17


IOR-R1200-0-36D3 40 OCCURRENCES STARTING FROM 00.00.13 TO 00.29.41


the next one seems to follow the last one:
IOR-R1200-0-36ED 37 occurrences CHANNEL 4
00.29.49.907 BFO/BTO 87/14940 - goes to 01.07.48.907 BFO 131 / BTO 15620


R CHANNEL - IOR-R600-0-36F8 (appears once)
02.25.27.421 ID 8 LOG ON REQUEST - FLIGHT INFORMATION PING 17120


R-CHANNEL - IOR-R600-0-36FC (appears once)
08.19.29.416 ID 10 LOG ON REQUEST - FLIGHT INFORMATION PING 23000

This is at the final ping times - Gulf of Thailand



R-CHANNEL IOR R1200-0-36F6 (appears once)
08.19.37.443 id 10 LOG ON LOG OFF ACKNOWLEDGE -2/49660

This is at the final ping time - Belitung Island Java Sea area


R-Channel IOR R600-0-36E1 - appears once - the East Vietnam ping data
2.25.27.471

This ping looks like I added it after - meaning 7 planes - this matches the data downloaded by MAS OPS for the bearing 14.5N 109E - I previously took this and other R-Channels as meaning - the radar station picking up the ping - obviously this is incorrect as the satellite data does not register which radar the pinging plane was near - it registers the ground satellite station which is P-Channel which I previously took as the plane terminal.

The R-Channel is the plane terminal.

I will check more details and explain more shortly.

xx

Also I have not added anything to this list from the data not published by Malaysia but published elsewhere on the web - so more cross-referencing to do there as well - from the github info.

xx

Last Edited by redhouserebel on 02/21/2015 11:30 AM
A MILF Mortgage - coming soon ;)
Anonymous Coward
User ID: 45483046
United Kingdom
02/21/2015 11:30 AM
Report Abusive Post
Report Copyright Violation
Re: Inmarsat Data MH370 shows SEVEN/ EIGHT planes
Inmarsat is part of the UKUSA cover up
redhouserebel  (OP)

User ID: 17654831
United Kingdom
02/21/2015 11:41 AM
Report Abusive Post
Report Copyright Violation
Re: Inmarsat Data MH370 shows SEVEN/ EIGHT planes
How I just explained this to my daughter is like this:


I have three mobile phones registered in my name - one for me and one each for my daughters.

If these phones were tracked by my name - I would appear in three different places at once - IF we were not all being picked up by the same ground station.

If we were all by the SAME ground satellite station, then only one would acknowledge and two would be said to be anomylous readings re location (this is how it works for P-Channel ground satellite for planes - I will explain more in a bit)

but if we were all greater distances apart - then DIFFERENT ground satellite stations WOULD register all the phones - and you would not know where i was UNLESS you bothered to check the unique data for each phone i.e. the phone number - in this case - the plane number - which is the R-Channel.


Further:

Each plane is given a "time slot" or tail number - this is assigned - in the same way a phone can be registered to a name - or given a name - you can give your phone a name like: "Donut eating FBI agent in the van at the end of your street" of "GCHQ agent 001.5" etc - but the number is the number.


The geo sat ground station will expect to keep hearing from a plane given a time slot - so if more than one has the time slot - and one of these stops or lands or does not take off or obeys a CANCEL SID request - so long as another plane assigned that time slot is still flying - the satellite will continue to pick it up as the same flight. It will not pick up more than one - the others are put into a queue - but if one goes - the others in the queue step forward and so there is no missed interrogation ping.


If all the planes cancel their time slot - or tail number assignment - they will no longer be picked up by the satellite - so by changing the time slot allotted - you can hide the plane from the satellite; however - if any matching R-Channel data is still available - this should be somewhere - unless the satellite will only pick up info when a plane is allotted a time slot - thereby asking the geo sat ground station to communicate.



xx
A MILF Mortgage - coming soon ;)
redhouserebel  (OP)

User ID: 17654831
United Kingdom
02/21/2015 11:50 AM
Report Abusive Post
Report Copyright Violation
Re: Inmarsat Data MH370 shows SEVEN/ EIGHT planes
Inmarsat is part of the UKUSA cover up
 Quoting: Anonymous Coward 45483046



I am trying to get my head round that: if it were true - why release the data?

Response: as they said - no one had ever tried to read this sort of data before.

I still think no - not at that time most certainly.


If however, at some time since then - they have been asked to not release any further data and were awarded a massive contract since then - then that would only be speculation; it all depends on if they are prepared to publicly release all and any possible relevant data.

It was previously released to Malaysia - who selected what they would publish from it; as we have seen github published ping data prior to midnight Malaysia time. We also have the 301/305 anomaly not yet explained - plus the potential for more data - which is hidden - when tail numbers/ time slots change - and any additional data relating to the R-Channel numbers.


xx


It is quite possible that Inmarsat are independent of Intel agencies on personal levels - but dependent on them for contracts/ money. I don't think they would risk themselves to be complicit to extreme criminal activity: you would need to follow who the stock holders are - and if or when the stock holders decide to refuse to release data in instances such as this - we need full transparency.

We need planes to ping regardless of time slot assignments - to ping their registration - and with all the dodgy double dealing going on - who knows who will fight for or against that.


??
A MILF Mortgage - coming soon ;)
redhouserebel  (OP)

User ID: 17654831
United Kingdom
02/21/2015 05:38 PM
Report Abusive Post
Report Copyright Violation
Re: Inmarsat Data MH370 shows SEVEN/ EIGHT planes
The following includes data from the Github charts and is not cross-referenced with the Malaysia Gov data - I was initially looking for T-Channel access requests - but diverged later: check it out:







7/03/2014 15.41:52907 IOR—R1200—O—36ED IOR 305 4 R—Channel RX 0x22 — Access Request (R/T—Channel) 141 14940

7/03/2014 15.41:53405 IOR—P10500—O—3859 IOR 305 10 P—Channel TX 0x51 — T—Channel Assignment

7/03/2014 15.41:57248 IOR—T1200—O—36FA IOR 305 10 T—Channel RX 0x71 — User Data (ISU) — RLS 142 9920

7/03/2014 15.41:57728 IOR—T1200—O—36FA IOR 305 10 T—Channel RX 0x22 — Access Request (R/T—Channel) 140 9920

7/03/2014 15.41:58528 IOR—T1200—O—36FA IOR 305 10 T—Channel RX Subsequent Signalling Unit 141 9920


7/03/2014 15.42:02058 IOR—T1200—O—36D7 IOR 305 8 T—Channel RX 0x71 — User Data (ISU) — RLS 147 9980

7/03/2014 15.42:02553 IOR—T1200—O—36D7 IOR 305 8 T—Channel RX Subsequent Signalling Unit 147 9980

7/03/2014 15.42:02708 IOR—T1200—O—36D7 IOR 305 8 T—Channel RX Subsequent Signalling Unit 148 9980



7/03/2014 15.42:17405 IOR—R1200—O—36ED IOR 305 4 R—Channel RX 0x22 — Access Request (R/T—Channel) 160 14960

7/03/2014 15.42:17905 IOR—P10500—O—3859 IOR 305 10 P—Channel TX 0x51 — T—Channel Assignment

7/03/2014 15.42:21748 IOR—T1200—O—36D7 IOR 305 8 T—Channel RX 0x71 — User Data (ISU) — RLS 157 9940




7/03/2014 15.42:31905 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x62 — Acknowledge User Data (R—channel) 125 14900

7/03/2014 15.42:32905 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x22 — Access Request (R/T—Channel) 127 14900

7/03/2014 15.42:33405 IOR—P10500—0—3859 IOR 305 10 P—Channel TX 0x51 — T—Channel Assignment

7/03/2014 15.42:37248 IOR—T1200—0—36D8 IOR 305 8 T—Channel RX 0x71 — User Data (ISU) — RLS 121 9940

7/03/2014 15.42:37408 IOR—T1200—0—36D8 IOR 305 8 T—Channel RX Subsequent Signalling Unit 121 9940


7/03/2014 15.42:44405 IOR—P10500—0—3859 IOR 305 10 P—Channel TX 0x62 — Acknowledge User Data

7/03/2014 15.42:45905 IOR—P10500—0—3859 IOR 305 10 P—Channel TX 0x71 — User Data (ISU) — RLS



7/03/2014 15.42:47907 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x62 — Acknowledge User Data (R—channel) 123 14920

7/03/2014 15.42:48405 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x22 — Access Request (R/T—Channel) 123 14900

7/03/2014 15.42:48905 IOR—P10500—0—3859 IOR 305 10 P—Channel TX 0x51 — T—Channel Assignment

7/03/2014 15.42:52748 IOR—T1200—0—36D7 IOR 305 8 T—Channel RX 0x71 — User Data (ISU) — RLS 131 9960

7/03/2014 15.42:52909 IOR—T1200—0—36D7 IOR 305 8 T—Channel RX Subsequent Signalling Unit 131 9960



7/03/2014 15.43:12407 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x62 — Acknowledge User Data (R—channel) 126 14920

7/03/2014 155523907 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x22 — Access Request (R/T—Channel) 156 15200

7/03/2014 15.55:24405 IOR—P10500—0—3859 IOR 305 10 P—Channel TX 0x51 — T—Channel Assignment

7/03/2014 15.55:28290 IOR—T1200—0—3718 IOR 305 12 T—Channel RX 0x71 — User Data (ISU) — RLS 157 10220



7/03/2014 155538407 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x22 — Access Request (R/T—Channel) 155 15220

7/03/2014 155538905 IOR—P10500—0—3859 IOR 305 10 P—Channel TX 0x51 — T—Channel Assignment

7/03/2014 15.55:42748 IOR—T1200—0—36D7 IOR 305 8 T—Channel RX 0x71 — User Data (ISU) — RLS 161 10240



7/03/2014 15.55:43ng IOR—T1200—0—36D7 IOR 305 8 T—Channel RX Subsequent Signalling Unit 164 10200

7/03/2014 15.55:43988 IOR—T1200—0—36D7 IOR 305 8 T—Channel RX Subsequent Signalling Unit 163 10200


7/03/2014 15.55:51907 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x62 — Acknowledge User Data (R—channel) 159 15200

7/03/2014 15.55:53407 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x22 — Access Request (R/T—Channel) 159 15240

7/03/2014 155553905 IOR—P10500—0—3859 IOR 305 10 P—Channel TX 0x51 — T—Channel Assignment

7/03/2014 15.55:57748 IOR—T1200—0—36D7 IOR 305 8 T—Channel RX 0x71 — User Data (ISU) — RLS 163 10240


7/03/2014 15.55:07905 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x62 — Acknowledge User Data (R—channel) 158 15220

7/03/2014 15.55:03407 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x22 — Access Request (R/T—Channel) 158 15200

7/03/2014 15.55:03905 IOR—P10500—0—3859 IOR 305 10 P—Channel TX 0x51 — T—Channel Assignment

7/03/2014 15.55:11748 IOR—T1200—0—36FA IOR 305 10 T—Channel RX 0x71 — User Data (ISU) — RLS 156 10260

7/03/2014 15.55:17407 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x62 — Acknowledge User Data (R—channel) 156 15240


In the above data - notice the times and also the R-Channel: IOR—R1200—0—36ED - this plane is the one coming down from the Gulf of Thailand before the flight of MH370 - an hour before.

5 minutes later we have a new R-Channel:


7/03/2014 16.00:13.406 IOR—R1200—0—36D3 IOR 305 8 R—Channel RX 0x15 — Log—on/Log—off Acknowledge 103 14820

7/03/2014 16.00:13.906 IOR—P10500—0—3859 IOR 305 10 P—Channel​ TX 0x15 — Log—on/Log—off Acknowledge


7/03/2014 16.00:23.407 IOR—R1200—0—36D3 IOR 305 8 R—Channel RX 0x22 — Access Request (R/T—Channel) 103 14820

7/03/2014 16.00:23.905 IOR—P10500—0—3859 IOR 305 10 P—Channel​ TX 0x51 — T—Channel Assignment

7/03/2014 16.00:27.741 IOR—T1200—0—36D7 IOR 305 8 T—Channel RX 0x71 — User Data (ISU) — RLS 86 9820



7/03/2014 16.01:19.906 IOR—R1200—0—36D3 IOR 305 8 R—Channel RX 0x22 — Access Request (R/T—Channel) 87 14780

7/03/2014 16.01:20.405 IOR—P10500—0—3859 IOR 305 10 P—Channel​ TX 0x51 — T—Channel Assignment

7/03/2014 16.01:20.906 IOR—R1200—0—36D3 IOR 305 8 R—Channel RX 0x62 — Acknowledge User Data (R—channel) 87 14800

7/03/2014 16.01:24.241 IOR—T1200—0—36D8 IOR 305 8 T—Channel RX 0x71 — User Data (ISU) — RLS 88 9800


Now we go back to the first R-Channel:


7/03/2014 16.09:37.407 IOR—R1200—0—36E3 IOR 305 11 R—Channel RX 0x22 — Access Request (R/T—Channel) 84 14840

7/03/2014 16.09:37.905 IOR—P10500—0—3859 IOR 305 10 P—Channel​ TX 0x51 — T—Channel Assignment

7/03/2014 16.09:41.749 IOR—T1200—0—36D8 IOR 305 8 T—Channel RX 0X71 — User Data (ISU) — RLS 88 9900



7/03/2014 16.11:03.907 IOR—R1200—0—36E3 IOR 305 11 R—Channel RX 0x22 — Access Request (R/T—Channel) 84 14840

7/03/2014 16.11:04.405 IOR—P10500—0—3859 IOR 305 10 P—Channel​ TX 0x51 — T—Channel Assignment

7/03/2014 16.11:08.306 IOR—TIZOO—O—36D7 IOR 305 8 T—Channel RX 0X71 — User Data (ISU) — RLS 89 9820

7/03/2014 16.11:08.409 IOR—T1200—0—36D7 IOR 305 8 T—Channel RX Subsequent Signalling Unit 89 9820



7/03/2014 16.11:13.408 IOR—R1200—0—36E3 IOR 305 11 R—Channel RX 0x62 — Acknowledge User Data (R—channel) 84 14860



7/03/2014 16.27:59.407 IOR—R1200—0—36E3 IOR 305 11 R—Channel RX 0x22 — Access Request (R/T—Channel) 88 14920

7/03/2014 16.27:59.905 IOR—P10500—0—3859 IOR 305 10 P—Channel​ TX 0x53 — Reservation Forthcoming (RFC)

7/03/2014 16.28:01.905 IOR—P10500—0—3859 IOR 305 10 P—Channel​ TX 0x51 — T—Channel Assignment

7/03/2014 16.28:10.641 IOR—T1200—0—36FA IOR 305 10 T—Channel RX 0x71 — User Data (ISU) — RLS 87 9920



7/03/2014 16.28:15.909 IOR—R1200—0—36E3 IOR 305 11 R—Channel RX 0x62 — Acknowledge User Data (R—channel) 85 14860

7/03/2014 16.29:17.407 IOR—R1200—0—36E3 IOR 305 11 R—Channel RX 0x22 — Access Request (R/T—Channel) 95 14860

7/03/2014 16.29:17.905 IOR—P10500—0—3859 IOR 305 10 P—Channel​ TX 0x51 — T—Channel Assignment

7/03/2014 16.29:21.748 IOR—T1200—0—36D7 IOR 305 8 T—Channel RX 0x71 — User Data (ISU) — RLS 99 9940

7/03/2014 16.29:38.905 IOR—P10500—0—3859 IOR 305 10 P—Channel​ TX 0x61 — Request for Acknowledge (RQA) User Data



Now we go back to the 2nd R-Channel:


7/03/2014 16.29:41.907 IOR—R1200—0—36D3 IOR 305 8 R—Channel RX 0x22 — Access Request (R/T—Channel) 96 14920

7/03/2014 16.29:42.405 IOR—P10500—0—3859 IOR 305 10 P—Channel​ TX 0x51 — T—Channel Assignment

7/03/2014 16.29:46.242 IOR—T1200—0—3718 IOR 305 12 T—Channel RX 0x71 — User Data (ISU) — RLS 93 9900


Here at 1.05am we have another R-Channel:


7/03/2014 17.05:49405 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x22 — Access Request (R/T—Channel) 129 15600

7/03/2014 17.05;49_905 IOR—P10500—0—3859 IOR 305 10 P—Channel​ TX 0x51 — T—Channel Assignment

7/03/2014 17.05:53749 IOR—T1200—0—3718 IOR 305 12 T—Channel RX 0x71 — User Data (ISU) — RLS 135 10600

7/03/2014 17.07:04405 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x22 — Access Request (R/T—Channel) 131 15620


7/03/2014 17.07;04_905 IOR—P10500—0—3859 IOR 305 10 P—Channel​ TX 0x51 — T—Channel Assignment



7/03/2014 17.07:03749 IOR—T1200—0—36D8 IOR 305 8 T—Channel RX 0x71 — User Data (ISU) — RLS 133 10600



7/03/2014 17.07:18905 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x62 — Acknowledge User Data (R—channel) 132 15600

7/03/2014 17.07:19407 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x22 — Access Request (R/T—Channel) 132 15660

7/03/2014 17.07:19905 IOR—P10500—0—3859 IOR 305 10 P—Channel TX 0x51 — T—Channel Assignment


7/03/2014 17.07:23755 IOR—T1200—0—36D7 IOR 305 8 T—Channel RX 0x71 — User Data (ISU) — RLS 137 10640



7/03/2014 17.07:33907 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x62 — Acknowledge User Data (R—channel) 130 15620

7/03/2014 17.07:34427 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x22 — Access Request (R/T—Channel) 132 15620

7/03/2014 17.07;34_905 IOR—P10500—0—3859 IOR 305 10 P—Channel​ TX 0x51 — T—Channel Assignment

7/03/2014 17.07:33749 IOR—T1200—0—3718 IOR 305 12 T—Channel RX 0x71 — User Data (ISU) — RLS 136 10620


here at 2.25am we have another R-Channel:

7/03/2014 18.25:27.421 IOR—R600—0—36E1 IOR 305 8 R—Channel RX 23:38)" Log'on Request (ISU)/Logo” Flight Information 142 17120

skip P36FC at 273 51700


7/03/2014 18.25:35408 IOR—P10500—0—386B IOR 305 10 P—Channel TX 0x15 — Log—on/Log—off Acknowledge


2 minutes later: here we are back to the first R-Channel - the plane which flew in from the Gulf of Thailand:


7/03/2014 18.27:03905 IOR—R1200—0—36ED IOR 305 4 R—Channel RX Eleven Octet User Data 176 12560

7/03/2014 18.27:04405 IOR—R1200—0—36ED IOR 305 4 R—Channel RX Four Octet User Data 175 12520


7/03/2014 18.28:05904 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x22 — Access Request (R/T—Channel) 144 12500


Note that here we have a different PChannel - a different ground station picking up pings:


7/03/2014 18.28:05407 IOR—P10500—0—386B IOR 305 10 P—Channel TX 0x51 — T—Channel Assignment
7/03/2014 18.28:10250 IOR—T1200—0—36D7 IOR 305 8 T—Channel RX 0x71 — User Data (ISU) — RLS 148 7540


time jump: here at 3.41am and at 4.41am and at 5.41am and at 6.41am we have the first plane which flew down from the Gulf of Thailand being interrogated by our original IOR P-Channel and responding every time with response and location - flying north from Malaysia mainland in to Gulf of Thailand:


7/03/2014 19.41:00910 IOR—P10500—0—386B IOR 305 10 P—Channel TX 0x14 — Log Control — Log—on Interrogation

7/03/2014 19.41:02905 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x15 — Log—on/Log—off Acknowledge 111 11500

7/03/2014 20.41:02907 IOR—P10500—0—386B IOR 305 10 P—Channel TX 0x14 — Log Control — Log—on Interrogation

7/03/2014 20.41:04904 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x15 — Log—on/Log—off Acknowledge 141 11740

7/03/2014 21.41:24907 IOR—P10500—0—386B IOR 305 10 P—Channel TX 0x14 — Log Control — Log—on Interrogation

7/03/2014 21.41:25905 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x15 — Log—on/Log—off Acknowledge 168 12780

7/03/2014 22.41:19907 IOR—P10500—0—386B IOR 305 10 P—Channel TX 0x14 — Log Control — Log—on Interrogation

7/03/2014 22.41:21905 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x15 — Log—on/Log—off Acknowledge 204 14540



7/03/2014 23.13:53407 IOR—P10500—0—386B IOR 305 10 P—Channel TX 0x20 — Access Request/Call Announcement Telephone/Circuit—Mode Data

7/03/2014 23.13:53407 IOR—P10500—0—386B IOR 305 10 P—Channel TX 0X33 — C—Channel Assignment (Regularity)

7/03/2014 23.14:00904 IOR—3737—21000 IOR 305 5 C—Channel RX 0x30 — Call Progress — Test 216

7/03/2014 23.15:01ng IOR—3737—21000 IOR 305 6 C—Channel RX 0x30 — CaII Progress — Channel Release 219

8/03/2014 00.10:53000 IOR—P10500—0—386B IOR 305 10 P—Channel TX 0x14 — Log Control — Log—on Interrogation

8/03/2014 00.10:59928 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x15 — Log—on/Log—off Acknowledge 252 18040


In this piece of R-Channel data above - we have the final co-ordinate for this plane from its R-Channel at 8.10am it is over Thai mainland - not over the sea.

At 8.19am we get a ping from another R-Channel: this one is over the sea in the Gulf of Thailand:

8/03/2014 00.19:29.416 IOR—R600—0—36F8 IOR 305 10 R—Channel RX 23:3)" Log'O” Request (ISU)/Logo“ Flight Information 182 23000


Then note here: note the change of P-Channel - this means the following data is from a different Geo sat ground station:

8/03/2014 00.19:31572 IOR—P600—0—36FC IOR 305 10 P—Channel TX 0x11 — Log—on Confirm

8/03/2014 00.19:31le IOR—P600—0—36FC IOR 305 10 P—Channel TX 0x40 — P—/R—Channe| Control (ISU)

8/03/2014 00.19:31le IOR—P600—0—36FC IOR 305 10 P—Channel TX Subsequent Signalling Unit

8/03/2014 00.19:32352 IOR—P600—0—36FC IOR 305 10 P—Channel TX 0x41 — T—Channel Control (ISU)

8/03/2014 00.19:32352 IOR—P600—0—36FC IOR 305 10 P—Channel TX Subsequent Signalling Unit

This other ground station is picking up a plane with a different R-Channel again which has logged on near Belitung java sea area:

8/03/2014 00.19:37443 IOR—R1200—0—36F6 IOR 305 10 R—Channel RX 0x15 — Log—on/Log—off Acknowledge —2 49660


these last few interrogations are speaking from the first geo sat ground station and do not correspond to the Belitung Plane and are interrogating a plane whose T-assignment has been logged off cancelled or changed:


8/03/2014 00.19:33407 IOR—P10500—0—386B IOR 305 10 P—Channel TX 0x15 — Log—on/Log—off Acknowledge

8/03/2014 01.15:55000 IOR—P10500—0—386B IOR 305 10 P—Channel TX 0x14 — Log Control — Log—on Interrogation

8/03/2014 01.15:05000 IOR—P10500—0—386B IOR 305 10 P—Channel TX 0x14 — Log Control — Log—on Interrogation

8/03/2014 01.15:15000 IOR—P10500—0—386B IOR 305 10 P—Channel TX 0x14 — Log Control — Log—on Interrogation

So of course the plane does not respond.

You will see typographical errors above - these are not mine but from the data so i left them so you can see the work was manually done by someone - i may have to replace some colons in the times as this forum acknowledges double colons as smilies and does not allow so many.
A MILF Mortgage - coming soon ;)
redhouserebel  (OP)

User ID: 17654831
United Kingdom
02/21/2015 05:44 PM
Report Abusive Post
Report Copyright Violation
Re: Inmarsat Data MH370 shows SEVEN/ EIGHT planes
This new info does not mean the bearings and maps were wrong before - the bearings have not changed - just it is all falling into place and making more sense now - we can finally pinpoint the location of planes by their R-Channel; account for anomalies - and what some referred to as errors in the data; we can see more clearly what happened - why a pilot of Malaysia looked at the data and said MH370 9M-MRO never left - according to the data - this is not to say it did not leave under another guise - perhaps registered in other data.

We can clearly see that the ping from the east of Vietnam at 2.25am reported at 2.36am was not an estimate by MAS OPS but it came from a plane logged into the MH370 time slot for a minute or two for the purpose of deception.


Also - I now understand the 301/305 anomaly


when it says IOR 301/ IOR 305 - this is talking about the Indian Ocean region - where the signals are being picked up - if anyone has a map of these regions - that would be awesomeness.


xx
A MILF Mortgage - coming soon ;)
redhouserebel  (OP)

User ID: 17654831
United Kingdom
02/21/2015 06:05 PM
Report Abusive Post
Report Copyright Violation
Re: Inmarsat Data MH370 shows SEVEN/ EIGHT planes
the post above now with bolded highlights:



The following includes data from the Github charts and is not cross-referenced with the Malaysia Gov data - I was initially looking for T-Channel access requests - but diverged later: check it out:







7/03/2014 15.41:52907 IOR—R1200—O—36ED IOR 305 4 R—Channel RX 0x22 — Access Request (R/T—Channel) 141 14940

7/03/2014 15.41:53405 IOR—P10500—O—3859 IOR 305 10 P—Channel TX 0x51 — T—Channel Assignment

7/03/2014 15.41:57248 IOR—T1200—O—36FA IOR 305 10 T—Channel RX 0x71 — User Data (ISU) — RLS 142 9920

7/03/2014 15.41:57728 IOR—T1200—O—36FA IOR 305 10 T—Channel RX 0x22 — Access Request (R/T—Channel) 140 9920

7/03/2014 15.41:58528 IOR—T1200—O—36FA IOR 305 10 T—Channel RX Subsequent Signalling Unit 141 9920


7/03/2014 15.42:02058 IOR—T1200—O—36D7 IOR 305 8 T—Channel RX 0x71 — User Data (ISU) — RLS 147 9980

7/03/2014 15.42:02553 IOR—T1200—O—36D7 IOR 305 8 T—Channel RX Subsequent Signalling Unit 147 9980

7/03/2014 15.42:02708 IOR—T1200—O—36D7 IOR 305 8 T—Channel RX Subsequent Signalling Unit 148 9980



7/03/2014 15.42:17405 IOR—R1200—O—36ED IOR 305 4 R—Channel RX 0x22 — Access Request (R/T—Channel) 160 14960

7/03/2014 15.42:17905 IOR—P10500—O—3859 IOR 305 10 P—Channel TX 0x51 — T—Channel Assignment

7/03/2014 15.42:21748 IOR—T1200—O—36D7 IOR 305 8 T—Channel RX 0x71 — User Data (ISU) — RLS 157 9940




7/03/2014 15.42:31905 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x62 — Acknowledge User Data (R—channel) 125 14900

7/03/2014 15.42:32905 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x22 — Access Request (R/T—Channel) 127 14900

7/03/2014 15.42:33405 IOR—P10500—0—3859 IOR 305 10 P—Channel TX 0x51 — T—Channel Assignment

7/03/2014 15.42:37248 IOR—T1200—0—36D8 IOR 305 8 T—Channel RX 0x71 — User Data (ISU) — RLS 121 9940

7/03/2014 15.42:37408 IOR—T1200—0—36D8 IOR 305 8 T—Channel RX Subsequent Signalling Unit 121 9940


7/03/2014 15.42:44405 IOR—P10500—0—3859 IOR 305 10 P—Channel TX 0x62 — Acknowledge User Data

7/03/2014 15.42:45905 IOR—P10500—0—3859 IOR 305 10 P—Channel TX 0x71 — User Data (ISU) — RLS



7/03/2014 15.42:47907 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x62 — Acknowledge User Data (R—channel) 123 14920

7/03/2014 15.42:48405 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x22 — Access Request (R/T—Channel) 123 14900

7/03/2014 15.42:48905 IOR—P10500—0—3859 IOR 305 10 P—Channel TX 0x51 — T—Channel Assignment

7/03/2014 15.42:52748 IOR—T1200—0—36D7 IOR 305 8 T—Channel RX 0x71 — User Data (ISU) — RLS 131 9960

7/03/2014 15.42:52909 IOR—T1200—0—36D7 IOR 305 8 T—Channel RX Subsequent Signalling Unit 131 9960



7/03/2014 15.43:12407 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x62 — Acknowledge User Data (R—channel) 126 14920

7/03/2014 155523907 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x22 — Access Request (R/T—Channel) 156 15200

7/03/2014 15.55:24405 IOR—P10500—0—3859 IOR 305 10 P—Channel TX 0x51 — T—Channel Assignment

7/03/2014 15.55:28290 IOR—T1200—0—3718 IOR 305 12 T—Channel RX 0x71 — User Data (ISU) — RLS 157 10220



7/03/2014 155538407 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x22 — Access Request (R/T—Channel) 155 15220

7/03/2014 155538905 IOR—P10500—0—3859 IOR 305 10 P—Channel TX 0x51 — T—Channel Assignment

7/03/2014 15.55:42748 IOR—T1200—0—36D7 IOR 305 8 T—Channel RX 0x71 — User Data (ISU) — RLS 161 10240



7/03/2014 15.55:43ng IOR—T1200—0—36D7 IOR 305 8 T—Channel RX Subsequent Signalling Unit 164 10200

7/03/2014 15.55:43988 IOR—T1200—0—36D7 IOR 305 8 T—Channel RX Subsequent Signalling Unit 163 10200


7/03/2014 15.55:51907 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x62 — Acknowledge User Data (R—channel) 159 15200

7/03/2014 15.55:53407 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x22 — Access Request (R/T—Channel) 159 15240

7/03/2014 155553905 IOR—P10500—0—3859 IOR 305 10 P—Channel TX 0x51 — T—Channel Assignment

7/03/2014 15.55:57748 IOR—T1200—0—36D7 IOR 305 8 T—Channel RX 0x71 — User Data (ISU) — RLS 163 10240


7/03/2014 15.55:07905 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x62 — Acknowledge User Data (R—channel) 158 15220

7/03/2014 15.55:03407 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x22 — Access Request (R/T—Channel) 158 15200

7/03/2014 15.55:03905 IOR—P10500—0—3859 IOR 305 10 P—Channel TX 0x51 — T—Channel Assignment

7/03/2014 15.55:11748 IOR—T1200—0—36FA IOR 305 10 T—Channel RX 0x71 — User Data (ISU) — RLS 156 10260

7/03/2014 15.55:17407 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x62 — Acknowledge User Data (R—channel) 156 15240


In the above data - notice the times and also the R-Channel: IOR—R1200—0—36ED - this plane is the one coming down from the Gulf of Thailand before the flight of MH370 - an hour before.

5 minutes later we have a new R-Channel:


7/03/2014 16.00:13.406 IOR—R1200—0—36D3 IOR 305 8 R—Channel RX 0x15 — Log—on/Log—off Acknowledge 103 14820

7/03/2014 16.00:13.906 IOR—P10500—0—3859 IOR 305 10 P—Channel​ TX 0x15 — Log—on/Log—off Acknowledge


7/03/2014 16.00:23.407 IOR—R1200—0—36D3 IOR 305 8 R—Channel RX 0x22 — Access Request (R/T—Channel) 103 14820

7/03/2014 16.00:23.905 IOR—P10500—0—3859 IOR 305 10 P—Channel​ TX 0x51 — T—Channel Assignment

7/03/2014 16.00:27.741 IOR—T1200—0—36D7 IOR 305 8 T—Channel RX 0x71 — User Data (ISU) — RLS 86 9820



7/03/2014 16.01:19.906 IOR—R1200—0—36D3 IOR 305 8 R—Channel RX 0x22 — Access Request (R/T—Channel) 87 14780

7/03/2014 16.01:20.405 IOR—P10500—0—3859 IOR 305 10 P—Channel​ TX 0x51 — T—Channel Assignment

7/03/2014 16.01:20.906 IOR—R1200—0—36D3 IOR 305 8 R—Channel RX 0x62 — Acknowledge User Data (R—channel) 87 14800

7/03/2014 16.01:24.241 IOR—T1200—0—36D8 IOR 305 8 T—Channel RX 0x71 — User Data (ISU) — RLS 88 9800


Now we go back to the first R-Channel:


7/03/2014 16.09:37.407 IOR—R1200—0—36E3 IOR 305 11 R—Channel RX 0x22 — Access Request (R/T—Channel) 84 14840

7/03/2014 16.09:37.905 IOR—P10500—0—3859 IOR 305 10 P—Channel​ TX 0x51 — T—Channel Assignment

7/03/2014 16.09:41.749 IOR—T1200—0—36D8 IOR 305 8 T—Channel RX 0X71 — User Data (ISU) — RLS 88 9900



7/03/2014 16.11:03.907 IOR—R1200—0—36E3 IOR 305 11 R—Channel RX 0x22 — Access Request (R/T—Channel) 84 14840

7/03/2014 16.11:04.405 IOR—P10500—0—3859 IOR 305 10 P—Channel​ TX 0x51 — T—Channel Assignment

7/03/2014 16.11:08.306 IOR—TIZOO—O—36D7 IOR 305 8 T—Channel RX 0X71 — User Data (ISU) — RLS 89 9820

7/03/2014 16.11:08.409 IOR—T1200—0—36D7 IOR 305 8 T—Channel RX Subsequent Signalling Unit 89 9820



7/03/2014 16.11:13.408 IOR—R1200—0—36E3 IOR 305 11 R—Channel RX 0x62 — Acknowledge User Data (R—channel) 84 14860



7/03/2014 16.27:59.407 IOR—R1200—0—36E3 IOR 305 11 R—Channel RX 0x22 — Access Request (R/T—Channel) 88 14920

7/03/2014 16.27:59.905 IOR—P10500—0—3859 IOR 305 10 P—Channel​ TX 0x53 — Reservation Forthcoming (RFC)

7/03/2014 16.28:01.905 IOR—P10500—0—3859 IOR 305 10 P—Channel​ TX 0x51 — T—Channel Assignment

7/03/2014 16.28:10.641 IOR—T1200—0—36FA IOR 305 10 T—Channel RX 0x71 — User Data (ISU) — RLS 87 9920



7/03/2014 16.28:15.909 IOR—R1200—0—36E3 IOR 305 11 R—Channel RX 0x62 — Acknowledge User Data (R—channel) 85 14860

7/03/2014 16.29:17.407 IOR—R1200—0—36E3 IOR 305 11 R—Channel RX 0x22 — Access Request (R/T—Channel) 95 14860

7/03/2014 16.29:17.905 IOR—P10500—0—3859 IOR 305 10 P—Channel​ TX 0x51 — T—Channel Assignment

7/03/2014 16.29:21.748 IOR—T1200—0—36D7 IOR 305 8 T—Channel RX 0x71 — User Data (ISU) — RLS 99 9940

7/03/2014 16.29:38.905 IOR—P10500—0—3859 IOR 305 10 P—Channel​ TX 0x61 — Request for Acknowledge (RQA) User Data




Now we go back to the 2nd R-Channel: I think this one is 9M-MRO


7/03/2014 16.29:41.907 IOR—R1200—0—36D3 IOR 305 8 R—Channel RX 0x22 — Access Request (R/T—Channel) 96 14920

7/03/2014 16.29:42.405 IOR—P10500—0—3859 IOR 305 10 P—Channel​ TX 0x51 — T—Channel Assignment

7/03/2014 16.29:46.242 IOR—T1200—0—3718 IOR 305 12 T—Channel RX 0x71 — User Data (ISU) — RLS 93 9900


Here at 1.05am we haveEDIT FROM ABOVE POST the first R-Channel again:


7/03/2014 17.05:49405 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x22 — Access Request (R/T—Channel) 129 15600

7/03/2014 17.05;49_905 IOR—P10500—0—3859 IOR 305 10 P—Channel​ TX 0x51 — T—Channel Assignment

7/03/2014 17.05:53749 IOR—T1200—0—3718 IOR 305 12 T—Channel RX 0x71 — User Data (ISU) — RLS 135 10600

7/03/2014 17.07:04405 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x22 — Access Request (R/T—Channel) 131 15620


7/03/2014 17.07;04_905 IOR—P10500—0—3859 IOR 305 10 P—Channel​ TX 0x51 — T—Channel Assignment



7/03/2014 17.07:03749 IOR—T1200—0—36D8 IOR 305 8 T—Channel RX 0x71 — User Data (ISU) — RLS 133 10600



7/03/2014 17.07:18905 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x62 — Acknowledge User Data (R—channel) 132 15600

7/03/2014 17.07:19407 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x22 — Access Request (R/T—Channel) 132 15660

7/03/2014 17.07:19905 IOR—P10500—0—3859 IOR 305 10 P—Channel TX 0x51 — T—Channel Assignment


7/03/2014 17.07:23755 IOR—T1200—0—36D7 IOR 305 8 T—Channel RX 0x71 — User Data (ISU) — RLS 137 10640



7/03/2014 17.07:33907 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x62 — Acknowledge User Data (R—channel) 130 15620

7/03/2014 17.07:34427 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x22 — Access Request (R/T—Channel) 132 15620

7/03/2014 17.07;34_905 IOR—P10500—0—3859 IOR 305 10 P—Channel​ TX 0x51 — T—Channel Assignment

7/03/2014 17.07:33749 IOR—T1200—0—3718 IOR 305 12 T—Channel RX 0x71 — User Data (ISU) — RLS 136 10620


here at 2.25am we have another R-Channel:

7/03/2014 18.25:27.421 IOR—R600—0—36E1 IOR 305 8 R—Channel RX 23:38)" Log'on Request (ISU)/Logo” Flight Information 142 17120

skip P36FC at 273 51700 - EAST COAST OF VIETNAM GROUND SAT AND LOG IN FOR DECEPTION PURPOSES




7/03/2014 18.25:35408 IOR—P10500—0—386B IOR 305 10 P—Channe​l TX 0x15 — Log—on/Log—off Acknowledge


2 minutes later: here we are back to the first R-Channel - the plane which flew in from the Gulf of Thailand:


7/03/2014 18.27:03905 IOR—R1200—0—36ED IOR 305 4 R—Channel RX Eleven Octet User Data 176 12560

7/03/2014 18.27:04405 IOR—R1200—0—36ED IOR 305 4 R—Channel RX Four Octet User Data 175 12520


7/03/2014 18.28:05904 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x22 — Access Request (R/T—Channel) 144 12500


Note that here we have a different PChannel - a different ground station picking up pings:


7/03/2014 18.28:05407 IOR—P10500—0—386B IOR 305 10 P—Channe​l TX 0x51 — T—Channel Assignment
7/03/2014 18.28:10250 IOR—T1200—0—36D7 IOR 305 8 T—Channel RX 0x71 — User Data (ISU) — RLS 148 7540


time jump: here at 3.41am and at 4.41am and at 5.41am and at 6.41am we have the first plane which flew down from the Gulf of Thailand being interrogated by our original IOR P-Channel and responding every time with response and location - flying north from Malaysia mainland in to Gulf of Thailand:


7/03/2014 19.41:00910 IOR—P10500—0—386B IOR 305 10 P—Channel TX 0x14 — Log Control — Log—on Interrogation

7/03/2014 19.41:02905 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x15 — Log—on/Log—off Acknowledge 111 11500

7/03/2014 20.41:02907 IOR—P10500—0—386B IOR 305 10 P—Channel TX 0x14 — Log Control — Log—on Interrogation

7/03/2014 20.41:04904 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x15 — Log—on/Log—off Acknowledge 141 11740

7/03/2014 21.41:24907 IOR—P10500—0—386B IOR 305 10 P—Channel TX 0x14 — Log Control — Log—on Interrogation

7/03/2014 21.41:25905 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x15 — Log—on/Log—off Acknowledge 168 12780

7/03/2014 22.41:19907 IOR—P10500—0—386B IOR 305 10 P—Channel TX 0x14 — Log Control — Log—on Interrogation

7/03/2014 22.41:21905 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x15 — Log—on/Log—off Acknowledge 204 14540



7/03/2014 23.13:53407 IOR—P10500—0—386B IOR 305 10 P—Channel TX 0x20 — Access Request/Call Announcement Telephone/Circuit—Mode Data

7/03/2014 23.13:53407 IOR—P10500—0—386B IOR 305 10 P—Channel TX 0X33 — C—Channel Assignment (Regularity)

7/03/2014 23.14:00904 IOR—3737—21000 IOR 305 5 C—Channel RX 0x30 — Call Progress — Test 216

7/03/2014 23.15:01ng IOR—3737—21000 IOR 305 6 C—Channel RX 0x30 — CaII Progress — Channel Release 219

8/03/2014 00.10:53000 IOR—P10500—0—386B IOR 305 10 P—Channel TX 0x14 — Log Control — Log—on Interrogation

8/03/2014 00.10:59928 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x15 — Log—on/Log—off Acknowledge 252 18040


In this piece of R-Channel data above - we have the final co-ordinate for this plane from its R-Channel at 8.10am it is over Thai mainland - not over the sea.

At 8.19am we get a ping from another R-Channel: this one is over the sea in the Gulf of Thailand:

8/03/2014 00.19:29.416 IOR—R600—0—36F8 IOR 305 10 R—Channel​ RX 23:3)" Log'O” Request (ISU)/Logo“ Flight Information 182 23000


Then note here: note the change of P-Channel - this means the following data is from a different Geo sat ground station:

8/03/2014 00.19:31572 IOR—P600—0—36FC IOR 305 10 P—Channel TX 0x11 — Log—on Confirm

8/03/2014 00.19:31le IOR—P600—0—36FC IOR 305 10 P—Channel TX 0x40 — P—/R—Channe| Control (ISU)

8/03/2014 00.19:31le IOR—P600—0—36FC IOR 305 10 P—Channel TX Subsequent Signalling Unit

8/03/2014 00.19:32352 IOR—P600—0—36FC IOR 305 10 P—Channel TX 0x41 — T—Channel Control (ISU)

8/03/2014 00.19:32352 IOR—P600—0—36FC IOR 305 10 P—Channel TX Subsequent Signalling Unit

This other ground station is picking up a plane with a different R-Channel again which has logged on near Belitung java sea area:

8/03/2014 00.19:37443 IOR—R1200—0—36F6 IOR 305 10 R—Channel RX 0x15 — Log—on/Log—off Acknowledge —2 49660


these last few interrogations are speaking from the first EDIT: SECOND - geo sat ground station and do not correspond to the Belitung Plane and are interrogating a plane whose T-assignment has been logged off cancelled or changed:


8/03/2014 00.19:33407 IOR—P10500—0—386B IOR 305 10 P—Channel TX 0x15 — Log—on/Log—off Acknowledge

8/03/2014 01.15:55000 IOR—P10500—0—386B IOR 305 10 P—Channel TX 0x14 — Log Control — Log—on Interrogation

8/03/2014 01.15:05000 IOR—P10500—0—386B IOR 305 10 P—Channel TX 0x14 — Log Control — Log—on Interrogation

8/03/2014 01.15:15000 IOR—P10500—0—386B IOR 305 10 P—Channel TX 0x14 — Log Control — Log—on Interrogation

So of course the plane does not respond.

You will see typographical errors above - these are not mine but from the data so i left them so you can see the work was manually done by someone - i may have to replace some colons in the times as this forum acknowledges double colons as smilies and does not allow so many.
A MILF Mortgage - coming soon ;)
redhouserebel  (OP)

User ID: 17654831
United Kingdom
02/21/2015 06:22 PM
Report Abusive Post
Report Copyright Violation
Re: Inmarsat Data MH370 shows SEVEN/ EIGHT planes
and again with added bold - tried to edit but meh


the post above now with bolded highlights:



The following includes data from the Github charts and is not cross-referenced with the Malaysia Gov data - I was initially looking for T-Channel access requests - but diverged later: check it out:







7/03/2014 15.41:52907 IOR—R1200—O—36ED IOR 305 4 R—Channel RX 0x22 — Access Request (R/T—Channel) 141 14940

7/03/2014 15.41:53405 IOR—P10500—O—3859 IOR 305 10 P—Channel TX 0x51 — T—Channel Assignment

7/03/2014 15.41:57248 IOR—T1200—O—36FA IOR 305 10 T—Channel RX 0x71 — User Data (ISU) — RLS 142 9920

7/03/2014 15.41:57728 IOR—T1200—O—36FA IOR 305 10 T—Channel RX 0x22 — Access Request (R/T—Channel) 140 9920

7/03/2014 15.41:58528 IOR—T1200—O—36FA IOR 305 10 T—Channel RX Subsequent Signalling Unit 141 9920


7/03/2014 15.42:02058 IOR—T1200—O—36D7 IOR 305 8 T—Channel RX 0x71 — User Data (ISU) — RLS 147 9980

7/03/2014 15.42:02553 IOR—T1200—O—36D7 IOR 305 8 T—Channel RX Subsequent Signalling Unit 147 9980

7/03/2014 15.42:02708 IOR—T1200—O—36D7 IOR 305 8 T—Channel RX Subsequent Signalling Unit 148 9980



7/03/2014 15.42:17405 IOR—R1200—O—36ED IOR 305 4 R—Channel RX 0x22 — Access Request (R/T—Channel) 160 14960

7/03/2014 15.42:17905 IOR—P10500—O—3859 IOR 305 10 P—Channel TX 0x51 — T—Channel Assignment

7/03/2014 15.42:21748 IOR—T1200—O—36D7 IOR 305 8 T—Channel RX 0x71 — User Data (ISU) — RLS 157 9940




7/03/2014 15.42:31905 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x62 — Acknowledge User Data (R—channel) 125 14900

7/03/2014 15.42:32905 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x22 — Access Request (R/T—Channel) 127 14900

7/03/2014 15.42:33405 IOR—P10500—0—3859 IOR 305 10 P—Channel TX 0x51 — T—Channel Assignment

7/03/2014 15.42:37248 IOR—T1200—0—36D8 IOR 305 8 T—Channel RX 0x71 — User Data (ISU) — RLS 121 9940

7/03/2014 15.42:37408 IOR—T1200—0—36D8 IOR 305 8 T—Channel RX Subsequent Signalling Unit 121 9940


7/03/2014 15.42:44405 IOR—P10500—0—3859 IOR 305 10 P—Channel TX 0x62 — Acknowledge User Data

7/03/2014 15.42:45905 IOR—P10500—0—3859 IOR 305 10 P—Channel TX 0x71 — User Data (ISU) — RLS



7/03/2014 15.42:47907 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x62 — Acknowledge User Data (R—channel) 123 14920

7/03/2014 15.42:48405 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x22 — Access Request (R/T—Channel) 123 14900

7/03/2014 15.42:48905 IOR—P10500—0—3859 IOR 305 10 P—Channel TX 0x51 — T—Channel Assignment

7/03/2014 15.42:52748 IOR—T1200—0—36D7 IOR 305 8 T—Channel RX 0x71 — User Data (ISU) — RLS 131 9960

7/03/2014 15.42:52909 IOR—T1200—0—36D7 IOR 305 8 T—Channel RX Subsequent Signalling Unit 131 9960



7/03/2014 15.43:12407 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x62 — Acknowledge User Data (R—channel) 126 14920

7/03/2014 155523907 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x22 — Access Request (R/T—Channel) 156 15200

7/03/2014 15.55:24405 IOR—P10500—0—3859 IOR 305 10 P—Channel TX 0x51 — T—Channel Assignment

7/03/2014 15.55:28290 IOR—T1200—0—3718 IOR 305 12 T—Channel RX 0x71 — User Data (ISU) — RLS 157 10220



7/03/2014 155538407 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x22 — Access Request (R/T—Channel) 155 15220

7/03/2014 155538905 IOR—P10500—0—3859 IOR 305 10 P—Channel TX 0x51 — T—Channel Assignment

7/03/2014 15.55:42748 IOR—T1200—0—36D7 IOR 305 8 T—Channel RX 0x71 — User Data (ISU) — RLS 161 10240



7/03/2014 15.55:43ng IOR—T1200—0—36D7 IOR 305 8 T—Channel RX Subsequent Signalling Unit 164 10200

7/03/2014 15.55:43988 IOR—T1200—0—36D7 IOR 305 8 T—Channel RX Subsequent Signalling Unit 163 10200


7/03/2014 15.55:51907 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x62 — Acknowledge User Data (R—channel) 159 15200

7/03/2014 15.55:53407 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x22 — Access Request (R/T—Channel) 159 15240

7/03/2014 155553905 IOR—P10500—0—3859 IOR 305 10 P—Channel TX 0x51 — T—Channel Assignment

7/03/2014 15.55:57748 IOR—T1200—0—36D7 IOR 305 8 T—Channel RX 0x71 — User Data (ISU) — RLS 163 10240


7/03/2014 15.55:07905 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x62 — Acknowledge User Data (R—channel) 158 15220

7/03/2014 15.55:03407 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x22 — Access Request (R/T—Channel) 158 15200

7/03/2014 15.55:03905 IOR—P10500—0—3859 IOR 305 10 P—Channel TX 0x51 — T—Channel Assignment

7/03/2014 15.55:11748 IOR—T1200—0—36FA IOR 305 10 T—Channel RX 0x71 — User Data (ISU) — RLS 156 10260

7/03/2014 15.55:17407 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x62 — Acknowledge User Data (R—channel) 156 15240


In the above data - notice the times and also the R-Channel: IOR—R1200—0—36ED - this plane is the one coming down from the Gulf of Thailand before the flight of MH370 - an hour before.

5 minutes later we have a new R-Channel:



7/03/2014 16.00:13.406 IOR—R1200—0—36D3 IOR 305 8 R—Channel RX 0x15 — Log—on/Log—off Acknowledge 103 14820

7/03/2014 16.00:13.906 IOR—P10500—0—3859 IOR 305 10 P—Channel​ TX 0x15 — Log—on/Log—off Acknowledge


7/03/2014 16.00:23.407 IOR—R1200—0—36D3 IOR 305 8 R—Channel RX 0x22 — Access Request (R/T—Channel) 103 14820

7/03/2014 16.00:23.905 IOR—P10500—0—3859 IOR 305 10 P—Channel​ TX 0x51 — T—Channel Assignment

7/03/2014 16.00:27.741 IOR—T1200—0—36D7 IOR 305 8 T—Channel RX 0x71 — User Data (ISU) — RLS 86 9820



7/03/2014 16.01:19.906 IOR—R1200—0—36D3 IOR 305 8 R—Channel RX 0x22 — Access Request (R/T—Channel) 87 14780

7/03/2014 16.01:20.405 IOR—P10500—0—3859 IOR 305 10 P—Channel​ TX 0x51 — T—Channel Assignment

7/03/2014 16.01:20.906 IOR—R1200—0—36D3 IOR 305 8 R—Channel RX 0x62 — Acknowledge User Data (R—channel) 87 14800

7/03/2014 16.01:24.241 IOR—T1200—0—36D8 IOR 305 8 T—Channel RX 0x71 — User Data (ISU) — RLS 88 9800


Now we go back to the first R-Channel:


7/03/2014 16.09:37.407 IOR—R1200—0—36E3 IOR 305 11 R—Channel RX 0x22 — Access Request (R/T—Channel) 84 14840

7/03/2014 16.09:37.905 IOR—P10500—0—3859 IOR 305 10 P—Channel​ TX 0x51 — T—Channel Assignment

7/03/2014 16.09:41.749 IOR—T1200—0—36D8 IOR 305 8 T—Channel RX 0X71 — User Data (ISU) — RLS 88 9900



7/03/2014 16.11:03.907 IOR—R1200—0—36E3 IOR 305 11 R—Channel RX 0x22 — Access Request (R/T—Channel) 84 14840

7/03/2014 16.11:04.405 IOR—P10500—0—3859 IOR 305 10 P—Channel​ TX 0x51 — T—Channel Assignment

7/03/2014 16.11:08.306 IOR—TIZOO—O—36D7 IOR 305 8 T—Channel RX 0X71 — User Data (ISU) — RLS 89 9820

7/03/2014 16.11:08.409 IOR—T1200—0—36D7 IOR 305 8 T—Channel RX Subsequent Signalling Unit 89 9820



7/03/2014 16.11:13.408 IOR—R1200—0—36E3 IOR 305 11 R—Channel RX 0x62 — Acknowledge User Data (R—channel) 84 14860



7/03/2014 16.27:59.407 IOR—R1200—0—36E3 IOR 305 11 R—Channel RX 0x22 — Access Request (R/T—Channel) 88 14920

7/03/2014 16.27:59.905 IOR—P10500—0—3859 IOR 305 10 P—Channel​ TX 0x53 — Reservation Forthcoming (RFC)

7/03/2014 16.28:01.905 IOR—P10500—0—3859 IOR 305 10 P—Channel​ TX 0x51 — T—Channel Assignment

7/03/2014 16.28:10.641 IOR—T1200—0—36FA IOR 305 10 T—Channel RX 0x71 — User Data (ISU) — RLS 87 9920



7/03/2014 16.28:15.909 IOR—R1200—0—36E3 IOR 305 11 R—Channel RX 0x62 — Acknowledge User Data (R—channel) 85 14860

7/03/2014 16.29:17.407 IOR—R1200—0—36E3 IOR 305 11 R—Channel RX 0x22 — Access Request (R/T—Channel) 95 14860

7/03/2014 16.29:17.905 IOR—P10500—0—3859 IOR 305 10 P—Channel​ TX 0x51 — T—Channel Assignment

7/03/2014 16.29:21.748 IOR—T1200—0—36D7 IOR 305 8 T—Channel RX 0x71 — User Data (ISU) — RLS 99 9940

7/03/2014 16.29:38.905 IOR—P10500—0—3859 IOR 305 10 P—Channel​ TX 0x61 — Request for Acknowledge (RQA) User Data




Now we go back to the 2nd R-Channel: I think this one is 9M-MRO


7/03/2014 16.29:41.907 IOR—R1200—0—36D3 IOR 305 8 R—Channel RX 0x22 — Access Request (R/T—Channel) 96 14920

7/03/2014 16.29:42.405 IOR—P10500—0—3859 IOR 305 10 P—Channel​ TX 0x51 — T—Channel Assignment

7/03/2014 16.29:46.242 IOR—T1200—0—3718 IOR 305 12 T—Channel RX 0x71 — User Data (ISU) — RLS 93 9900


Here at 1.05am we have EDIT FROM ABOVE POST the first R-Channel again:


7/03/2014 17.05:49405 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x22 — Access Request (R/T—Channel) 129 15600

7/03/2014 17.05;49_905 IOR—P10500—0—3859 IOR 305 10 P—Channel​ TX 0x51 — T—Channel Assignment

7/03/2014 17.05:53749 IOR—T1200—0—3718 IOR 305 12 T—Channel RX 0x71 — User Data (ISU) — RLS 135 10600

7/03/2014 17.07:04405 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x22 — Access Request (R/T—Channel) 131 15620


7/03/2014 17.07;04_905 IOR—P10500—0—3859 IOR 305 10 P—Channel​ TX 0x51 — T—Channel Assignment



7/03/2014 17.07:03749 IOR—T1200—0—36D8 IOR 305 8 T—Channel RX 0x71 — User Data (ISU) — RLS 133 10600



7/03/2014 17.07:18905 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x62 — Acknowledge User Data (R—channel) 132 15600

7/03/2014 17.07:19407 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x22 — Access Request (R/T—Channel) 132 15660

7/03/2014 17.07:19905 IOR—P10500—0—3859 IOR 305 10 P—Channel TX 0x51 — T—Channel Assignment


7/03/2014 17.07:23755 IOR—T1200—0—36D7 IOR 305 8 T—Channel RX 0x71 — User Data (ISU) — RLS 137 10640



7/03/2014 17.07:33907 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x62 — Acknowledge User Data (R—channel) 130 15620

7/03/2014 17.07:34427 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x22 — Access Request (R/T—Channel) 132 15620

7/03/2014 17.07;34_905 IOR—P10500—0—3859 IOR 305 10 P—Channel​ TX 0x51 — T—Channel Assignment

7/03/2014 17.07:33749 IOR—T1200—0—3718 IOR 305 12 T—Channel RX 0x71 — User Data (ISU) — RLS 136 10620


here at 2.25am we have another R-Channel:

7/03/2014 18.25:27.421 IOR—R600—0—36E1 IOR 305 8 R—Channel RX 23:38)" Log'on Request (ISU)/Logo” Flight Information 142 17120

skip P36FC at 273 51700 - EAST COAST OF VIETNAM GROUND SAT AND LOG IN FOR DECEPTION PURPOSES




7/03/2014 18.25:35408 IOR—P10500—0—386B IOR 305 10 P—Channe​l TX 0x15 — Log—on/Log—off Acknowledge


2 minutes later: here we are back to the first R-Channel - the plane which flew in from the Gulf of Thailand:


7/03/2014 18.27:03905 IOR—R1200—0—36ED IOR 305 4 R—Channel RX Eleven Octet User Data 176 12560

7/03/2014 18.27:04405 IOR—R1200—0—36ED IOR 305 4 R—Channel RX Four Octet User Data 175 12520


7/03/2014 18.28:05904 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x22 — Access Request (R/T—Channel) 144 12500


Note that here we have a different P-Channel - a different ground station picking up pings:


7/03/2014 18.28:05407 IOR—P10500—0—386B IOR 305 10 P—Channe​l TX 0x51 — T—Channel Assignment
7/03/2014 18.28:10250 IOR—T1200—0—36D7 IOR 305 8 T—Channel RX 0x71 — User Data (ISU) — RLS 148 7540


time jump: here at 3.41am and at 4.41am and at 5.41am and at 6.41am we have the first plane which flew down from the Gulf of Thailand being interrogated by our original IOR P-Channel and responding every time with response and location - flying north from Malaysia mainland in to Gulf of Thailand:


7/03/2014 19.41:00910 IOR—P10500—0—386B IOR 305 10 P—Channel TX 0x14 — Log Control — Log—on Interrogation

7/03/2014 19.41:02905 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x15 — Log—on/Log—off Acknowledge 111 11500

7/03/2014 20.41:02907 IOR—P10500—0—386B IOR 305 10 P—Channel TX 0x14 — Log Control — Log—on Interrogation

7/03/2014 20.41:04904 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x15 — Log—on/Log—off Acknowledge 141 11740

7/03/2014 21.41:24907 IOR—P10500—0—386B IOR 305 10 P—Channel TX 0x14 — Log Control — Log—on Interrogation

7/03/2014 21.41:25905 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x15 — Log—on/Log—off Acknowledge 168 12780

7/03/2014 22.41:19907 IOR—P10500—0—386B IOR 305 10 P—Channel TX 0x14 — Log Control — Log—on Interrogation

7/03/2014 22.41:21905 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x15 — Log—on/Log—off Acknowledge 204 14540



7/03/2014 23.13:53407 IOR—P10500—0—386B IOR 305 10 P—Channel TX 0x20 — Access Request/Call Announcement Telephone/Circuit—Mode Data

7/03/2014 23.13:53407 IOR—P10500—0—386B IOR 305 10 P—Channel TX 0X33 — C—Channel Assignment (Regularity)

7/03/2014 23.14:00904 IOR—3737—21000 IOR 305 5 C—Channel RX 0x30 — Call Progress — Test 216

7/03/2014 23.15:01ng IOR—3737—21000 IOR 305 6 C—Channel RX 0x30 — CaII Progress — Channel Release 219

8/03/2014 00.10:53000 IOR—P10500—0—386B IOR 305 10 P—Channel TX 0x14 — Log Control — Log—on Interrogation

8/03/2014 00.10:59928 IOR—R1200—0—36ED IOR 305 4 R—Channel RX 0x15 — Log—on/Log—off Acknowledge 252 18040


In this piece of R-Channel data above - we have the final co-ordinate for this plane from its R-Channel at 8.10am it is over Thai mainland - not over the sea.

At 8.19am we get a ping from another R-Channel: this one is over the sea in the Gulf of Thailand:

8/03/2014 00.19:29.416 IOR—R600—0—36F8 IOR 305 10 R—Channel​ RX 23:3)" Log'O” Request (ISU)/Logo“ Flight Information 182 23000


Then note here: note the change of P-Channel - this means the following data is from a different Geo sat ground station:

8/03/2014 00.19:31572 IOR—P600—0—36FC IOR 305 10 P—Channel TX 0x11 — Log—on Confirm

8/03/2014 00.19:31le IOR—P600—0—36FC IOR 305 10 P—Channel TX 0x40 — P—/R—Channe| Control (ISU)

8/03/2014 00.19:31le IOR—P600—0—36FC IOR 305 10 P—Channel TX Subsequent Signalling Unit

8/03/2014 00.19:32352 IOR—P600—0—36FC IOR 305 10 P—Channel TX 0x41 — T—Channel Control (ISU)

8/03/2014 00.19:32352 IOR—P600—0—36FC IOR 305 10 P—Channel TX Subsequent Signalling Unit

This other ground station is picking up a plane with a different R-Channel again which has logged on near Belitung java sea area:

8/03/2014 00.19:37443 IOR—R1200—0—36F6 IOR 305 10 R—Channel RX 0x15 — Log—on/Log—off Acknowledge —2 49660


these last few interrogations are speaking from the first EDIT: SECOND - geo sat ground station and do not correspond to the Belitung Plane and are interrogating a plane whose T-assignment has been logged off cancelled or changed:


8/03/2014 00.19:33407 IOR—P10500—0—386B IOR 305 10 P—Channel TX 0x15 — Log—on/Log—off Acknowledge

8/03/2014 01.15:55000 IOR—P10500—0—386B IOR 305 10 P—Channel TX 0x14 — Log Control — Log—on Interrogation

8/03/2014 01.15:05000 IOR—P10500—0—386B IOR 305 10 P—Channel TX 0x14 — Log Control — Log—on Interrogation

8/03/2014 01.15:15000 IOR—P10500—0—386B IOR 305 10 P—Channel TX 0x14 — Log Control — Log—on Interrogation

So of course the plane does not respond.

You will see typographical errors above - these are not mine but from the data so i left them so you can see the work was manually done by someone - i may have to replace some colons in the times as this forum acknowledges double colons as smilies and does not allow so many.

Last Edited by redhouserebel on 02/21/2015 06:25 PM
A MILF Mortgage - coming soon ;)
redhouserebel  (OP)

User ID: 17654831
United Kingdom
02/21/2015 08:11 PM
Report Abusive Post
Report Copyright Violation
Re: Inmarsat Data MH370 shows SEVEN/ EIGHT planes
If anything, Inmarsat are proven to have no hidden agenda in any of this: they released the info to Malaysia.


Going by the US expert and the Malaysian pilot who examined data and said 9M-MRO did not leave Malaysia - it seems that Malaysia knew what they were doing when they published the data that they did - they wanted it to be understood and indeed later came out and said the US had shot down the plane. I feel they knew the plane was going to be decoyed, but were not aware of what was designed to happen next. I believe they were misled over cargo - not passengers - at the ATC level at least.


What gets me is why the IATA code for the plane is nowhere to be found - according to the linked data - the satellite records the 24 digit identity code for the plane and this is nowhere to be seen - and I can't find any history of it.

I believe there would be a number of IATA codes for a number of planes if the full data documentation were to be released - this is what we need to finally confirm the identities of some of these planes involved.


xx
A MILF Mortgage - coming soon ;)
redhouserebel  (OP)

User ID: 63793915
United Kingdom
02/22/2015 06:26 PM
Report Abusive Post
Report Copyright Violation
Re: Inmarsat Data MH370 shows SEVEN/ EIGHT planes
[link to www.afceaboston.com]


[link to www.afceaboston.com]


[link to wikimapia.org]


[link to wikimapia.org]


The C Channel calls were picked up by the EIK Ground station in Norway

[link to i.imgur.com]


[link to i.imgur.com]


cntrl F - 301 - GES ID - / C-Channel/ voice/ satellite calls?

[link to www.dca.gov.my]
A MILF Mortgage - coming soon ;)
redhouserebel  (OP)

User ID: 63793915
United Kingdom
02/22/2015 06:31 PM
Report Abusive Post
Report Copyright Violation
Re: Inmarsat Data MH370 shows SEVEN/ EIGHT planes
Is this the location of the Primary Ground station that picked up the satellite call to/ from the plane/ a plane - re MH370?


[link to www.google.co.uk (secure)]



Is that normal?
A MILF Mortgage - coming soon ;)
redhouserebel  (OP)

User ID: 63793915
United Kingdom
02/22/2015 06:36 PM
Report Abusive Post
Report Copyright Violation
Re: Inmarsat Data MH370 shows SEVEN/ EIGHT planes
In English:


obviously i don't understand all the terms and data - but we have 3 P-Channels - and these are to do with data sent TO a plane FROM a ground station.

However we have a consistency throughout the data of GES ID 305 - which would be a Perth ground station - picking up in the IOR Indian Ocean region (nothing on there for southern ocean region) - EXCEPT where C- Channel data is relayed via GES ID 301 - which according to Inmarsat sister company SITA who Inmarsat passed the data to - and who gave it to Malaysia - 301 is Ground Station EIK - in Norway.



???
A MILF Mortgage - coming soon ;)
redhouserebel  (OP)

User ID: 20763890
United Kingdom
02/22/2015 08:25 PM
Report Abusive Post
Report Copyright Violation
Re: Inmarsat Data MH370 shows SEVEN/ EIGHT planes
Satellite-aided Air Traffic Control (ATC) Communications

When an aircraft is out of range of VHF/UHF radio, such as in oceanic airspace, Inmarsat enables air traffic controllers to stay in touch with the aircraft. The ability to have reliable communications with ground-based controllers at all times, on all major oceanic routes, is an important safety feature.

Automatic dependent surveillance (ADS)

Inmarsat facilitates the automatic reporting of an aircraft’s real-time position to ATC centres, including altitude, speed and heading, via satellite to air traffic control centres, helping controllers know where an aircraft is at all times.


How does Inmarsat identify one aircraft from another?
All aircraft are given a unique code confirming its identity, linked to the tail number of the aircraft. The signal sent from an aircraft carries this unique code and cannot get confused with another aircraft.


[link to www.inmarsat.com]


Where is the unique code on the data?


Ships hooked up with Inmarsat have distress panic buttons

[link to www.inmarsat.com]


... their use triggers search and rescue - can't find the plane equivalent - unless it is also the C-Channel???


xx
A MILF Mortgage - coming soon ;)
redhouserebel  (OP)

User ID: 20763890
United Kingdom
02/22/2015 08:30 PM
Report Abusive Post
Report Copyright Violation
Re: Inmarsat Data MH370 shows SEVEN/ EIGHT planes
Inmarsat achievements are amazing

[link to www.inmarsat.com]


they promote safety

[link to www.inmarsat.com]


and employ the best


[link to www.inmarsat.com]


xx


I am trying to think why there are 3 P-Channel listings indicating 3 GES ground - land earth stations - but only the numbers 301 and 305


also the C-Channel listings have some variation and I wonder what this means: 3737/3730/ 373E


?
A MILF Mortgage - coming soon ;)
redhouserebel  (OP)

User ID: 46114875
United Kingdom
02/22/2015 11:08 PM
Report Abusive Post
Report Copyright Violation
Re: Inmarsat Data MH370 shows SEVEN/ EIGHT planes
Inmarsat achievements are amazing

[link to www.inmarsat.com]


they promote safety

[link to www.inmarsat.com]



and employ the best


[link to www.inmarsat.com]


xx


I am trying to think why there are 3 P-Channel listings indicating 3 GES ground - land earth stations - but only the numbers 301 and 305


also the C-Channel listings have some variation and I wonder what this means: 3737/3730/ 373E


?
 Quoting: redhouserebel




Its a shame they had to give that award for safety 10 days after two people - navy seals - died on one of their ships:


[link to edition.cnn.com]


talk about bad timing... and then to think... the cargo from that ship was headed for MH370...

[link to www.google.co.uk (secure)]


at least Inmarsat came through with the data.



clappa
A MILF Mortgage - coming soon ;)
Intz

User ID: 52422236
Australia
02/23/2015 10:01 PM
Report Abusive Post
Report Copyright Violation
Re: Inmarsat Data MH370 shows SEVEN/ EIGHT planes
What you make of this?
[link to www.dailymail.co.uk]
plus
User ID: 68330296
Singapore
02/23/2015 10:43 PM
Report Abusive Post
Report Copyright Violation
Re: Inmarsat Data MH370 shows SEVEN/ EIGHT planes
hey Hong Kong dude - just read this link you gave me

[link to www.public-action.com]


very interesting.
 Quoting: redhouserebel


I find that article to be one of the most fascinating I've ever read anywhere. I'm glad you enjoyed it and it apparently helped you out somehow.

But, I'm not "Hong Kong dude" if you don't mind (I only appear to be that because I use HK IPs a lot. I'm using a US IP now because a HK IP I was using was just banned in fact.), I'm "plus" the one you once said you "loved."

I know you probably forgot, I knew the "love" you were expressing was ephemeral and unimportant but I think we should respect the concept. chuckle

Thread: FINDING LOVE ON GLP - I NEVER THOUGHT IT WOULD HAPPEN TO ME <3

Of course I'm being sarcastic but under the circumstances I think you could be a little more considerate. hf
redhouserebel  (OP)

User ID: 68337256
United Kingdom
02/24/2015 05:44 AM
Report Abusive Post
Report Copyright Violation
Re: Inmarsat Data MH370 shows SEVEN/ EIGHT planes
What you make of this?
[link to www.dailymail.co.uk]
 Quoting: Intz



There is no data or factual evidence included so I can't really comment. There is another link at the bottom which says we have to wait for March 8th this year to see what have they reached a conclusion synonymous with a penguin migration. I also notice they say that it was originally thought MH370 was in the Gulf of Thailand or South China

[link to www.news.com.au]



but no search was ever done in the Gulf.


Does anyone know what the difference is between a primary ground station and a secondary ground station? Is this like primary and secondary radar or not?

EIK in Norway is operated by ARINC owned by Carlisle Group up to December 2013 then sold to Rockwell Collins.



What does it mean when a ground or land station picks up a signal?

I thought that ground stations picked up signals from nearby - then rebounded them up to the satellite, so this has got me confused - unless it means that someone; someone near Norway made a call to MH370 or one of the planes pretending to be MH370 and if so - then you was that?


xx

Last Edited by redhouserebel on 02/24/2015 05:49 AM
A MILF Mortgage - coming soon ;)
redhouserebel  (OP)

User ID: 68337256
United Kingdom
02/24/2015 06:10 AM
Report Abusive Post
Report Copyright Violation
Re: Inmarsat Data MH370 shows SEVEN/ EIGHT planes
Just to be clear about my confusion over the ground station which picked up the satellite phone calls TO the plane - if that is what is represented by the C-Channel data: why would a GROUND station in Norway pick up the call?

Now if the call had been made near Denmark of the Netherlands for example - I could understand that -

[link to i.imgur.com]


map for example - but why a ground station in Norway for a call from Malaysia?

This is not the location of the Inmarsat satellite up in the air/space which is 36000 metres high or whatever it is, which picks up satellite pings from all over.


xx
A MILF Mortgage - coming soon ;)
redhouserebel  (OP)

User ID: 68337256
United Kingdom
02/24/2015 06:17 AM
Report Abusive Post
Report Copyright Violation
Re: Inmarsat Data MH370 shows SEVEN/ EIGHT planes
Just to be clear about my confusion over the ground station which picked up the satellite phone calls TO the plane - if that is what is represented by the C-Channel data: why would a GROUND station in Norway pick up the call?

Now if the call had been made near Denmark of the Netherlands for example - I could understand that -

[link to i.imgur.com]


map for example - but why a ground station in Norway for a call from Malaysia?

This is not the location of the Inmarsat satellite up in the air/space which is 36000 metres high or whatever it is, which picks up satellite pings from all over.


xx
 Quoting: redhouserebel




Here is an example picture showing the distance from the satellite to Kuala Lumpur:


[link to i.imgur.com]



And then the GROUND station picking up all the other pings was allegedly PERTH even though I read that this ground station covers a different area not included in any of the ping results covered by the data.

It seems ground earth stations are not like primary radar stations and work in an entirely different manner - or else - something is wrong.


??
A MILF Mortgage - coming soon ;)
Comperio

User ID: 65690366
Denmark
02/24/2015 06:25 AM
Report Abusive Post
Report Copyright Violation
Re: Inmarsat Data MH370 shows SEVEN/ EIGHT planes
Another excellent analysis - very important information. Thank you very much, your work is highly appreciated - please go on. 5*
"The important thing is not to stop questioning. Curiosity has its own reason for existing. Never lose a holy curiosity. Condemnation without investigation is the height of ignorance." Albert Einstein
redhouserebel  (OP)

User ID: 68337256
United Kingdom
02/24/2015 06:45 AM
Report Abusive Post
Report Copyright Violation
Re: Inmarsat Data MH370 shows SEVEN/ EIGHT planes
Page 166 here

[link to books.google.co.uk (secure)]


says that ground station EIK services the Atlantic region alongside Aussaguel in France and Goonhilly in UK using the Inmarsat 3-F2 satelllite at 15.5W - - not the 64E satellite which we are told the readings are from.


I read elsewhere that EIK could be a back-up for Beijing - but nowhere that it could be a back up for southern ocean region.


Page 170 there is good to see the Channels - and we still have to determine if a call actually went through and is returned in the data - the data does not imply that a call was not successful.


xx
A MILF Mortgage - coming soon ;)
redhouserebel  (OP)

User ID: 68337256
United Kingdom
02/24/2015 06:50 AM
Report Abusive Post
Report Copyright Violation
Re: Inmarsat Data MH370 shows SEVEN/ EIGHT planes
EIK is owned by ARINC


[link to en.wikipedia.org]


[link to en.wikipedia.org]


Just some background reading if anyone is interested.


xx
A MILF Mortgage - coming soon ;)
redhouserebel  (OP)

User ID: 68337256
United Kingdom
02/24/2015 08:53 AM
Report Abusive Post
Report Copyright Violation
Re: Inmarsat Data MH370 shows SEVEN/ EIGHT planes
Articles like this:

[link to www.therakyatpost.com]


show us that everyday people aren't meant to understand the Inmarsat data - and this article includes some data which is an example given in the Inmarsat data Page 1:


7/03/2014 16:42:04.408, 35200217,SITADP(3047),IOR-R1200-0-36ED,IOR,305,Rx Primary,4,R-Channel RX,12184,,5,,0×62 – Acknowledge User Data (R-channel),62,1F D0 62 75 00 8F C5 7A 4E 00 00 00 00 00 00 00 00 7F 89,D,0,E,S31,Yes,No,No,-57.29,40.09,146,0,14920.




Here is a screenshot of that same info from the data released by Malaysia from the Inmarsat data:


[link to i.imgur.com]


That screenshot is from here:


[link to www.dca.gov.my]



On that screenshot I have underlined some things.


Please note the "Field Headings" and the "Example message".

The example message is from R-Channel R1200-0-36ED at time of take off 00.42.04 and some microseconds on the 8th Malaysia time, which is listed as the 7th of March UTC time 16.42.04 etc


Please note - this is the flight which came down from the Gulf of Thailand according tot he data not given in this document but given in data on Github:

[link to github.com (secure)]


7/03/2014 15:41:52907 IOR—R1200—O—36ED IOR 305 4 R—Channel RX 0x22 — Access Request (R/T—Channel) 141 14940

and again:


7/03/2014 15:41:52907 IOR—R1200—O—36ED IOR 305 4 R—Channe​l RX 0x22 — Access Request (R/T—Channel) 141 14940



Please look at this link to github and all the data there - it is for an R-Channel coming down from the Gulf to KL - it flies over and picks up the flightpath of 9MMRO which has a CANCEL SID instruction to cancel its flightpath and to not take off.


More in a minute so post is not so long.

x

Last Edited by redhouserebel on 02/24/2015 09:03 AM
A MILF Mortgage - coming soon ;)
redhouserebel  (OP)

User ID: 68337256
United Kingdom
02/24/2015 09:02 AM
Report Abusive Post
Report Copyright Violation
Re: Inmarsat Data MH370 shows SEVEN/ EIGHT planes
OK, so we know that GES means a ground station which pings with the aircraft and the satellite and this is the P-Channel which pings a flight which has a registered time slot such that the satellite will register it.


The AES is the antenna on the plane: this is also a ground station - but it is a mobile ground station - such as the antenna on a plane:


[link to www.cept.org]


It is the earth station on a plane.


The antennas are owned and operated by companies such as those that have ground stations like ARINC and SITA - SITA are the ones who gave the Inmarsat data to Malaysia for example.


Now on the screenshot:


[link to i.imgur.com]


of the released data page 1 - in the field headings we have Time (which includes date) then we have AES ID - and in the example given below we have the AES ID 35200217


This is the identity of the antenna on the plane in the example R1200-0-36ED


The AES - antennas - have to be registered for use and this antenna is therefore registered to this plane and we can see it is owned by SITA.


Now when you compare the Field Headings and Example message on page 1 and compare this with all the data - you will see that nowhere else is the AES ID given - except in this one example message - so we have no way to compare the AES IDs of the other R-Channel info given in the data - it has been removed from what has been published.

If we had all the data - we could then ascertain whether or not it was indeed 9M-MRO which flew down from the gulf, circled without time to pick up passengers - and then left again - or if in fact it was a different plane.


xx
A MILF Mortgage - coming soon ;)





GLP