I’ve noticed there are quite a few arrivals that don’t automatically pin when part of a flight plan. Off the top of my head, I’ve noticed issues with the following:
RJAA - RUTAS G, RUTAS N, LUBLA G, LUBLA N, SUPOK G, SUPOK N, SWAMP G, SWAMP N
VTSP - all arrivals
Am I missing anything, or do I need to just manually pin these each time?
Hello! Welcome to our forum.
This can happen if the procedure (RUTASG for example) cannot be reliably linked to one specific chart.
You can tell if this is the case by looking at the procedure list - is there an associated chart?
In this example, only the LAKESN procedure has an associated chart. Selecting that procedure would automatically pin the related chart to your pinboard.
There could be many reasons why a link cannot be made, but it often comes down to us having insufficient information. We only have the name of the chart to work with, and sometimes the procedure and chart use slightly different naming schemes (RUTASG vs RUTAS G, etc.).
I’ll add this case to our backlog so that we can take a look at possible improvements to this situation in the future. But as of right now, this is expected to happen in some cases, unfortunately!
The VTSP case is a bit more obvious and not possible to work around. There are several procedures, all with different names, but only two arrival charts - and they both have generic names:
It is not possible from a technical standpoint to tell which chart contains a specific procedure in this case since no procedures are referenced by name in the title.
Kind Regards,
Malte
Understood, and thank you for the prompt response!
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.