|
|
Post by stealthmanbob on Jan 23, 2020 16:38:20 GMT 1
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. Sorry, I had thought it was changing on the ground before the flight commenced. |
|
philidor
in service - 6 years
Posts: 8,950
|
Post by philidor on Jan 23, 2020 18:07:33 GMT 1
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. I don't know about tracking errors, but I remember many cases in the past in which some posters noticed that a callsign had been changed after take off. |
|
mtrunz
delivered!
Digital Aviation/Meteo Analyst
Posts: 1,956 
|
Post by mtrunz on Jan 23, 2020 21:05:26 GMT 1
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. I don't know about tracking errors, but I remember many cases in the past in which some posters noticed that a callsign had been changed after take off. Yeah, but this has been a daily thing all week for many Airbus and Beluga Flights. Just like its also a thing where FR24 almost always says the flight diverted to the airport its supposed to instead of showing the landing times. |
|
|
|
Post by ca350 on Jan 24, 2020 20:28:21 GMT 1
I don't know about tracking errors, but I remember many cases in the past in which some posters noticed that a callsign had been changed after take off. Yeah, but this has been a daily thing all week for many Airbus and Beluga Flights. Just like its also a thing where FR24 almost always says the flight diverted to the airport its supposed to instead of showing the landing times. So if you look at the previous callsign and updated callsign from yesterday: Initial callsign: www.flightradar24.com/AIB01BO/239ea5e5Updated callsign: fr24.com/AIB02BO/239eb0e8 where the last 8 digit hex code, which I believe is the primary sort key for flights in FR24 database, is different. My not-really-educated guess is that the pilots did change the callsign either in taxi or in flight which resulted in a flight code (last 8 digit) change and then FR24 was able to pick up the updated callsign. If this was a caching issue, I would think the flight hex code stays the same but only callsign updated in flight. |
|
|
|
Post by a380admirer on Jan 29, 2020 10:08:28 GMT 1
|
|
|
|
Post by pa380scal on Jan 29, 2020 13:40:38 GMT 1
|
|
|
|
Post by ca350 on Jan 29, 2020 18:35:36 GMT 1
|
|
|
|
Post by ca350 on Feb 1, 2020 9:09:14 GMT 1
|
|
|
|
Post by Ravi1925 on Feb 1, 2020 11:07:22 GMT 1
|
|
|
|
Post by fanairbus on Feb 3, 2020 10:04:15 GMT 1
Indonesia’s Batik Air enters the A320neo club By Greg Waldron3 February 2020 www.flightglobal.com/fleets/indonesias-batik-air-enters-the-a320neo-club/136494.articleIndonesian carrier Batik Air has taken delivery of its first Airbus A320neo, the 46th Airbus aircraft in its fleet. The aircraft is equipped with 12 business and 144 economy class seats, according to Airbus. It was handed over at Jakarta’s Soekarno-Hatta International Airport. |
|
