New "Airport ID" (thats what you really request, ICAO and FAA code are just meta tags inside the airport) will need to meet these rules:
Its either a
valid ICAO code (exactly 4 letters, no digits at all, first one NOT being an X)
an X-plane internal code only (starting with the letter X, followed by a valid ICAO region code. IMO that region code would not have to be very stringently verified, as it has no defined function), say it just should be a letter only in position 2 should suffice. Might want to limit to 3 to 7 letters/numbers total, as some tools down the toolchain use limited length strings here.
So anything starting with a digit is just a valid airport ID for grandfathered in existing airports.
You must be logged in to participate in the discussion
Julian Lockwood August 1, 2018 4:53 AM
Not a valid ICAO code.
An unknown user August 1, 2018 4:30 PM
How come this was rejected? The airport does not have an ICAO code, only an FAA identifier.
Michael Minnhaar August 1, 2018 5:35 PM
New "Airport ID" (thats what you really request, ICAO and FAA code are just meta tags inside the airport) will need to meet these rules:
Its either a
So anything starting with a digit is just a valid airport ID for grandfathered in existing airports.