Aircraft displaying incorrect info?

[Fenris]

I think John is talking about other problems as well.

Thing is, near EHAM traffic levels are very high so there are more collisions on the air and strange things can happen, also Holland is very flat so he will hear many signals from a wide area.

He could collect all the port 30003 output to a file and see if he can find evidence of corruption.

[MrT]

But we're not talking about incorrectly decoded Flight IDs here, we're talking about a correctly decoded Flight ID that's being translated to an incorrect route.

But if the Flight ID is incorrectly decoded then the route will be incorrect.  The original poster made no distinction between it being the route or the Flight ID that was wrong.

Sorry,

It's the route that was incorrect. The flight ID was ok.

[Allocator]

Next silly question from me, if you look up the route in DataBase Explorer, is it showing the correct route for that Flight ID, or is is showing what you saw on the screen?

[John Racars]

Next exemples without any comment from my side:

[Fenris]

It looks to me as if some garbled data has caused the registration to be incorrectly received, is this aircraft showing up as a different ModeS hex code?

Since all the other details appear to be correct I think this is the likely explanation. Maybe the demodulation algorithm in the PIC inside the RB hardware box could be improved a bit for marginal cases (probably a 1 bit corruption), but if the data received is like that then it's very difficult to process it differently.

[John Racars]

Some more. No comment. It  speak for it self I think:

[DaveReid]

It looks to me as if some garbled data has caused the registration to be incorrectly received, is this aircraft showing up as a different ModeS hex code?

That was my initial thought too.

But having said that, the flight number is coming from either a 112-bit Extended Squitter packet or a DF20/DF21 (also 112 bits).  It seems very strange that a random bit error would only show up in the 24 bits of the hex code - I would have thought that there was more chance (double, in fact) of the 48-bit Flight ID field being equally corrupted, but from John's examples that doesn't seem to be happening

[jgrloit]

Could it be that just the mode-S is corrupted, by another signal.
This would generate the incorrect registration and aircraft details.
I have this at times, and use the Squawk as a cross-check, as most seem to be allocated to one aircraft at a time!!!

[AirNav Support]

Good point, John if you can add the Mode S column to your list and take a screenshot when you see a duplicate that might help.

[jgrloit]

I have a small problem with aircraft detail displays, but only on the last aircraft in the myflights list, if the aircraft becomes the last due to a timeout of the previous last in list.
I sort by Mode-S, which may help with the explanation.

Screen shot attached

[attachment deleted by admin]

[John Racars]

Good point, John if you can add the Mode S column to your list and take a screenshot when you see a duplicate that might help.

Good afternoon Support,

Immediately at your service!

[AirNav Support]

They do seem close, the message through interference could have been corrupted.

Is it correct in saying when this occurs the second (mystery flight) never has ASD-B and then dissapears when the first flight gets timed out?

[John Racars]

Hi Support,

I don't understand what you mean. I will try to do so and come back later.

Herewith an other exemple of wrong information:

[AirNav Support]

Ok your having two issues here.

One your getting duplicates, your saying this a software issue. We are trying to work out if just corrupted signals, if so its not a software issue but there may be a way to hande it.

Secondly the routes issue. Can you check the aircraft which have the wrong route, whether they landed at EHAM or another airport close to you and then change there Flight ID. As I think I am right in saying RB only checks the route when a new aircraft comes into coverage.

[John Racars]

Secondly the routes issue. Can you check the aircraft which have the wrong route, whether they landed at EHAM or another airport close to you

Support, thank you for your reaction! The aircraft involved (PH-KZH) was, at the moment of making the screenshot, enroute as KLM34K from EKBI to EHAM.