Incorrect Callsign Data


I'm not sure if this is a bug, but I've noticed that the call sign on the database is different from the callsign that is actually used by the flight. An example is on the below link. You'll notice the table states the callsign is RYR6MN but when the live flight is tracked, or a recent flight using the playback feature, the actual callsign used is RYR8KT.

Is there a reason they are different? Is this something that is fixable?
Last edited:

Mark Daniels

Staff member
Hi Matthew,
This is happening because we aren't showing changes in the database side when a different callsign is used for the same flight number.
The live display should be correct.
We will look into improving this.
Thanks for raising it.