(If you mark the flight as public, everyone can see the route). Anyhow, what you're seeing is an artifact of the fact that I get my data from a wide variety of (free) sources. Sometimes that data has small inconsistencies. In this case, if you map the flight from JKV to KJSO, you'll see that the codes are both in the database, but are...oh, I'd guess 50ft apart? So if you're on the north side of the airport, autodetection will pick up JKV, and if you're on the south side, you pick up KJSO.
There are two fixes for this (both on my end):
- Reconcile the positions, so JKV and KJSO are at the same location. (JSO too, actually, since that's also in the database). Done.
- Designate KJSO as "preferred" in the case of a tie. This was in fact already the case, so if you were on the south you'd be closest to both JSO and KJSO, and it already picked KJSO as the "preferred" nearest (always a good idea to use ICAO codes). But alas, since JKV had a different location, if you were on the north, it picks up the closest.
So the locations are reconciled on the server; the mobile apps only periodically have their databases updated, so it will be until the next update where I include a database update before the mobile apps pick it up.