Rather than assign fictitious airport codes to US airports that have an FAA code but no ICAO, it is a better idea to use the FAA code, the reason being that non-gateway custom sceneries for those airports almost always use the FAA code and if the gateway version does not it is not suppressed.
In their case, using 43IG would insure that there is no conflict between the custom scenery and the default. As it is, I needed to edit the custom apt.dat to use XK000V to achieve that; I do not think that was intended by the the use of the fictitious airport ID.
You must be logged in to participate in the discussion
daemotron October 30, 2018 5:35 PM
FAA Code: 43IG
Cf. https://nfdc.faa.gov/nfdcApps/services/ajv5/airportDisplay.jsp?airportId=43IG
Rather than assign fictitious airport codes to US airports that have an FAA code but no ICAO, it is a better idea to use the FAA code, the reason being that non-gateway custom sceneries for those airports almost always use the FAA code and if the gateway version does not it is not suppressed.
In their case, using 43IG would insure that there is no conflict between the custom scenery and the default. As it is, I needed to edit the custom apt.dat to use XK000V to achieve that; I do not think that was intended by the the use of the fictitious airport ID.