You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Entering a route as follows: KPWK JVL ODI KFCM. Avare correctly identifies JVL as a navaid waypoint, but it is using the JVL NDB (located at the field) instead of the JVL VOR (about 5 nm SW of the field).
Similar problem occurs when using the "Find" function and searching for JVL. The airport, the VOR, and the NDB come up, but even if the VOR is selected the NDB winds up being the selected waypoint. This is confirmed by pulling up the "Find" function again, which shows the most recent search results - the JVL NDB is at the top of the list.
I'm sure there are other locations in the system where an airport, VOR, and NDB share the same identifier and the NDB is off-field - maybe this is a problem in other places as well.
This is on 5.4.1 on a Nexus 4 with 4.4.2 Kitkat.
The text was updated successfully, but these errors were encountered:
Entering a route as follows: KPWK JVL ODI KFCM. Avare correctly identifies JVL as a navaid waypoint, but it is using the JVL NDB (located at the field) instead of the JVL VOR (about 5 nm SW of the field).
Similar problem occurs when using the "Find" function and searching for JVL. The airport, the VOR, and the NDB come up, but even if the VOR is selected the NDB winds up being the selected waypoint. This is confirmed by pulling up the "Find" function again, which shows the most recent search results - the JVL NDB is at the top of the list.
I'm sure there are other locations in the system where an airport, VOR, and NDB share the same identifier and the NDB is off-field - maybe this is a problem in other places as well.
This is on 5.4.1 on a Nexus 4 with 4.4.2 Kitkat.
The text was updated successfully, but these errors were encountered: