Please suggest an identifier. The NOTAMs guidelines are:
The format for designing these codes should be: X (for fictitious code) + country ICAO prefix + IATA or local aviation authority code. An example of this would be Foya Airport in Liberia: currently it only has an IATA code of FOY. So, a “New Airport Code Request” should list XGLFOY in the ICAO field.
If the airport has no code at all, you can make something up that resembles the guidelines.
Jennifer Roberts September 20, 2017 2:06 PM
Please suggest an identifier. The NOTAMs guidelines are:
The format for designing these codes should be: X (for fictitious code) + country ICAO prefix + IATA or local aviation authority code. An example of this would be Foya Airport in Liberia: currently it only has an IATA code of FOY. So, a “New Airport Code Request” should list XGLFOY in the ICAO field.
If the airport has no code at all, you can make something up that resembles the guidelines.
USER123 September 30, 2017 1:16 PM
So XEDD1 would be good?
Jennifer Roberts October 5, 2017 2:20 PM
That is the basic format, yes, but we already have that used on the Gateway for Lindlar.
USER123 October 5, 2017 2:31 PM
Oh sorry, didn't search right, XEDD10 then?
This scenery pack contains accurately drawn surrounding trees and forests. Those forests should be helpful for flying a VFR circuit.
In my latest version I removed those forests because of beeing issued as "scenery far outside the airport boundary". Good idea to remove?
I don't find the solution for this issue: Hangar object and parking space incursions on road network Could you please give me a hint?
Cheers! Flusifritz