#2182 AI Trafic not landing at their destination

[Merca]

Sometimes AI Trafic reports wrong destination airports. As shown in the attached image, 3 traffics are reported as going to EGSS while they are hundreds of miles past that airport. I tried to follow them to check if they were to land anywhere to no avail. They'll probably go around the globe forever. It's not the first time I noticed this behaviour.
I'm using flightgear 2019.1.1 on Ubuntu 18.04

[James Turner]

Thanks for the report, that's quite strange. With only the information available here, it's hard to to debug this unforutnately. It would help to know if it's specific routes which are wrong, or specific destination / origin airports, or any other pattern to the fligths which go off-course.

[Merca]

Something new: I was using an artificial time setting, Noon. By chance I decided to change to Clock-time and all 3 planes turned around and, I presume, are going towards their destination airport. I'll let you know what they do.

[James Turner]

Ah that's interesrting. All AI traffic is scheduled based on the 'sim world time' which you (the user) can adjsut easily. This is on purpose so if you're starting at EGLL at night it's quieter than daytime, etc. But when you change the time during the simulation, I'm not sure how the traffic system handles this, since we have many flights in the air which are now landing at the 'wrong' time.

Maybe it's just like being really, really delayed? I have forgotten for sure what the code does with this,

[Merca]

No, they won't land at EGSS. I've tried changing the time to every other preset a couple of times but they kept their current bearing south past the airport. I nearly reached the north pole tracking these rebels! :-D
Something else you're probably aware of: speed and altitude of AI traffic reported in the map is not very accurate, but I understand it may not be too important or doable for it to be that accurate.
Ok, I give up before I reach South Africa. Cheers.