|
|
Post by ca350 on Jan 12, 2020 20:07:57 GMT 1
|
|
|
|
Post by ca350 on Jan 12, 2020 20:08:27 GMT 1
|
|
|
|
Post by Ravi1925 on Jan 20, 2020 14:38:21 GMT 1
|
|
|
|
Post by Ravi1925 on Jan 20, 2020 15:21:25 GMT 1
|
|
|
|
Post by a380admirer on Jan 23, 2020 9:58:14 GMT 1
|
|
|
|
Post by Ravi1925 on Jan 23, 2020 10:38:32 GMT 1
|
|
|
|
Post by a380admirer on Jan 23, 2020 10:40:25 GMT 1
You are right, 1st flight was on 20th Jan, sorry for my mistake! |
|
mtrunz
delivered!
Digital Aviation/Meteo Analyst
Posts: 1,956 
|
Post by mtrunz on Jan 23, 2020 15:01:37 GMT 1
I think its a bug in FR24. Seems to happen a lot lately. |
|
|
|
Post by stealthmanbob on Jan 23, 2020 15:13:06 GMT 1
I think its a bug in FR24. Seems to happen a lot lately. I think it's due to the fact that when Airbus test pilots "turn the aircraft on" the Callsign from the previous flight is still stored in the computer, so it will start transmitting with that, until they reprogram in today's call sign. |
|
mtrunz
delivered!
Digital Aviation/Meteo Analyst
Posts: 1,956
|
Post by mtrunz on Jan 23, 2020 15:25:11 GMT 1
I think its a bug in FR24. Seems to happen a lot lately. I think it's due to the fact that when Airbus test pilots "turn the aircraft on" the Callsign from the previous flight is still stored in the computer, so it will start transmitting with that, until they reprogram in today's call sign. Yeah but it would happen right away. They wont be changing the callsign while in the air. Its probably more of a caching issue on FR24, since other Flight Tackers don't seem to have that issue. |
|
