Can't select LNZ VOR

Charts General
1

There is currently no way to add LNZ VOR to a route, it always adds LNZ NDB.

image
image1920Ă—892 105 KB

2

Hello! Thanks for the feedback.

While we can’t distinguish between the VOR and the NDB in the route string (there is no difference between LNZ J21 SBG and LNZ J21 SBG), it should prioritize the VOR over the NDB.

I am not able to reproduce this issue. Could you copy the full route string so I can try it out?

This is the route I tried with: LOWW/29 SNU2C SNU DCT LNZ J21 SBG DCT LOWS/SBG.I15

image

Kind Regards,
Malte

3

image
image1920Ă—1002 55.2 KB

image
image1920Ă—819 89.6 KB

Clicking “Add to Route” on the LNZ VOR will add the NDB.

image
image1920Ă—734 80.3 KB

image
image1920Ă—879 91.9 KB

The same happens when manually adding LNZ in the route input.

As you are using an airway (J21), it goes to LNZ VOR.
You have to use DCT to trigger the issue.

LOWW/29 SNU2C SNU DCT LNZ DCT SBG DCT LOWS/SBG.I15
4

Thank you for the clarification! I can reproduce the issue and we shall investigate.

1 Like
5

Hello again! This should now be fixed.

Please confirm that you are no longer having this issue!

Kind Regards,
Malte

6

Hello again!

Unfortunately, the changes we made caused new issues, and we have now rolled it back. This means that the issue is back. I’ll let you know once we have a different solution.

Sorry for the inconvenience!

Kind Regards,
Malte

1 Like
7

This should now be fixed again! We’ll see if it works better this time :slight_smile:

Kind Regards,
Malte

8

It’s fixed in a way that by default, LNZ VOR is now selected. But now I am unable to add LNZ NDB to a route, when clicking the “Add to route” button. Same issue with KFT VOR/NDB etc.

To clarify, I do not expect to enter this via the route input, but I would expect to be able to add NDBs with the dedicated navaid button.

9

Hi,

We currently don’t have any option to choose between such closely spaced navaids with the same name. We want to maximize interoperability between systems and apps and therefore we base our app’s flight plan solely on the route string, for example LOWW/29 SNU2C SNU DCT LNZ DCT SBG DCT LOWS/SBG.I15, and in this particular case it isn’t possible to disambiguate LNZ. We might change this sometime in the future but currently we aim to minimize the times it assumes wrong.

Skyvector cannot handle this case either. It always defaults to the NDB and you cannot specify the VOR. Have you tried this in MSFS (if you are using that), and if so, can you export two PLN files and past here, one where you have specified the VOR and one for the NDB?

Regards,

Stephen