In FS2020 SU13, I cannot use airport NM16 (in New Mexico, USA) if I have the Navigraph base AIRAC cycle installed from the Navigraph Hub. I can select it in the World Map and the map will zoom to the location, but it will not allow me to select a runway or click “Fly”.
If I remove Navigraph, I can select NM16 and fly from it as expected.
Background: In SU13, NM16 was moved. It used to be at a different location and called “Chama Land & Cattle Co.” In real life, this version of NM16 was closed and the identifier was freed.
In real life, NM16 was reused for a different airstrip named “Sacaton”. SU13 added this airstrip and labelled it NM16. Unfortunately, they kept the old name of “Chama Land & Cattle Co.”
I suspect that Navigraph is correctly marking the old NM16 closed and removing it from the sim. But this has the effect of removing the new NM16 as well.
The main reason is not the position, the main reason is the runway because in the stock data you have 07/25 but in real it´s 08/26 and seems to be the issue here.
In this case, the only chance is to “exclude” this airport from our database but than, you use an outdated airport. The best would be to report this to MS/ASOBO because it´s clear, that this airport is outdated due the wrong runway-idents.
Thank you for the detailed information. I have already reported (to MS/Asobo) the incorrect name of NM16 in SU13. Hopefully, they will investigate and fix the runway identifiers as well.
Can you explain why the runway identifiers cause a problem with Navigraph?
I am guessing Navigraph removes the 7/25 runway, but why does it not add the 8/26 runway?
Or if it removes the entire NM16 airport, why does it not add the new NM16 airport?
Is there anyone here who knows enough about how Navigraph works to answer my last question?
I’m curious why Navigraph leaves the airport unusable, even if it disagrees with the MS/Asobo data.
We may not overwrite/change existing airports - even they are correct or wrong. You can delete the runway completely but you can´t only change the ident - to delete and re-create the runway with our data completely is a risk due the taxiways or any other airport facilities, which are connected internal/external with the runway/airport.
Therefore, the update contains only airports, which are NOT in the stock data incl. the runways. All other airports will be “untouched” - here we only add the terminal-procedures/terminal waypoints. Additional airways, enroute waypoints and navaids (VORs, NDBs, …) worldwide.
That means in NM16 case, the airport exists in the stock data too, so we may not touch it and we would (when some data are available) only add/change the terminal procedures for this airport. All other things will be taken from the stock data.
Thank you for the reply.
I’m wondering if something was fixed in the latest Navigraph AIRAC cycles (in the last release or two).
I just installed 2310 rev.1, and NM16 is functional. It was not this way when I tried it a few days ago, but I was probably on a 2309 version released before SU13.
I still don’t understand how the airport (or its runways) were deleted by Navigraph, but am glad to see that the latest AIRAC cycle fixes it.
The difference is the SU13 … AIRAC 2309 was build before SU13 was released. That makes the difference, because now you see - the outdated runway-idents 05/27 and also the outdated name. It looks, that ASOBO/MS runs any “re-organization” during the updates, which correct possible internal links - but this is only a assumption. We can´t verify it.
Last, we don´t delete anything - no airport nor runway. We only add airports and runways, if they are not existing in the stock data. What we do is to “disable” the stock terminal procedures, navaids, airways, waypoints, … and add it with our data - but we never, ever delete anything in the sim - not a file nor internal.
Ah, thank you. I was misunderstanding the difference between “delete” and “disable”. You have clarified that for me.
I agree that the MS/Asobo files containing NM16 were never deleted. But if I understand correctly, Navigraph did disable NM16 before in 2309.
This meant, for example, that I couldn’t end a bush trip leg there if Navigraph 2309 was installed. (This is how I and a user of one of my bush trips noticed it.) It also means that if you look for it in Developer Mode, you won’t find it.
Again, thanks for sorting it out in 2310.
