Reinstate appropriated ICAO

[spatialpro]

Did you submit this to Zendesk? If so, what is your ticket #?

132791

Background

This post is strongly related to two others…

Missing Airports Sent to Zendesk

Below is a list of airports I believe are missing from MSFS2020 and submitted to Zendesk. This does not include airports with different identifiers. ICAO Name Lat Long 06TT 6 Mile Airpark 30.8600 -100.2020 0E0 Moriarty Municipal Airport 34.9823 -106.0058 0IL7 Davis Restricted Landing Area 39.7829 -88.5467 0KS5 Oasis Aerodrome 38.4505 -98.7980 18MS Johns Landing 32.4533 -90.3639 19IN* Clark 41.2844 -85.3608 19MT N Bar Ranch 46.8379 -108.9376 19TS KVUE-TV Heliport 27.9296 -…

Please expand ICAO character limitation

Do you have any add-ons in your Community folder? If yes, please remove and retest before posting. No Are you using Developer Mode or made changes in it? YES Brief description of the issue: The airport identifier is limited to 5 characters. This is not enough. 8 characters would allow a more accurate ID For example: CA-0171 Isachsen Airport 78.786517, -103.523051 is not present in the Sim, but does exist in the real world. We should be able to add this airport with it’s correct ID. Many c…

… and countless others pointing out incorrect ICAO for individual or batches of airfields, but this bug report focuses on the core of the issue (i.e. ICAO appropriation) and proposes/reiterates two solutions:

The Bug/Issue

Rather than creating pseudo-ICAO for airfields which have no real ICAO assigned MSFS instead appropriates (in an apparently random way) real ICAO for them. This creates two issues:

1. a user who searches for an airfield with a known [correct] ICAO is taken to the incorrect airfield
2. developers are prohibited from using the correct ICAO when creating/modifying the correct airfield

Solutions

The proposed/reiterated solutions are twofold:

1. re-assign all appropriated ICAO to their original, correct, real airfields (whether or not those airfields still exist)
2. expand the internal pseudo-ICAO beyond just 5 characters (e.g. 8) to permit the use/creation of many more codes (for instance GB-0068 could then be correctly used for Gigha airfield, instead of appropriating EGDA, which actually belongs/belonged to Brawdy… and developers can readily create more random pseudo ICAO for airfields which have never been assigned a real ICAO)

[ClevererElm8055]

Please tag your post with #pc and/or #xbox.
pc and xbox
Are you on Steam or Microsoft Store version?
Microsoft Store Version

Brief description of the issue:
Many airports have their ICAO incorrect or indicate their IATA code, when will they be corrected?

Provide Screenshot(s)/video(s) of the issue encountered:

Build Version # when you first started experiencing this issue:
1.21.13.0

Reinstate appropriated ICAO

Did you submit this to Zendesk? If so, what is your ticket #? 132791 Background This post is strongly related to two others… … and countless others pointing out incorrect ICAO for individual or batches of airfields, but this bug report focuses on the core of the issue (i.e. ICAO appropriation) and proposes/reiterates two solutions: The Bug/Issue Rather than creating pseudo-ICAO for airfields which have no real ICAO assigned MSFS instead appropriates (in an apparently random way) real I…

[AfricanFlyer579]

#PC
Good morning everyone.
As already published in another topic, I reinforce here that in Angola, many ICAOs are incorrect. Some are completely fictitious, others indicate incorrect aerodromes (that is, they are not connected to the real aerodrome) and there are even ICAOs from another country (Namibia) identifying an aerodrome in Angola.

I will be happy to help fix this, if you give me a format or table in which I can send the correct data. (Ex. Name/ICAO/coordinate/Country). Or if you accept a table from us with information from all airports, I can send it. As the solution to send photos of the areas with a description will be very extensive, in the case of Angola, it is not just 1 or 2 aerodromes.

Thank you for your attention and we hope this can be resolved in due course.
Alexandre