Sorry to bother. I notice the odd additional Oceanic track appear from time to time, but this one is insane.
This one stretches all the way from Ukraine!!!
Anybody know why this is?? Or why they appear in general? Many thanks 
1 Like
Sometimes the oceanic tracks contain waypoints that has the same name as other waypoints, which can confuse the app. 
In this case the waypoint is NALAN, which exists over the Atlantic, and in Ukraine.
4 Likes
I saw this as well and thought it was a bit strange. I’ve seen a few like these which stretch very far over land. I’ve seen loads whilst flight planning that stretch over the US.
1 Like
I’ve seen one start in Idaho 
4 Likes
It does make you wonder why there’s not a check before these routes go up. Maybe there’s something in the code that’s preventing it but from an outsider perspective surely you could just throw all the possible options into a list and then take the ones that are somewhat near the NATL track zone.
I’m no developer, but a maximum distance between fixes could maybe avoid this issue?
I wonder if they only receive one point from upstream, like their provider just sends one point per fix name so it’s either use it or just don’t have a fix there. This has been an issue for multiple years so I’m sure if it was solvable it would’ve been solved or at least acknowledged.
Yeah, I’d definitely think the fix is a lot more difficult than it seems, which I reckon is the norm in software development 
1 Like
I saw this too but didn’t think much of it
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.