MSFS 2024 Airport / Helipad Issue Tracker

Thank you, Thesevenflyer, for your feedback. I wasn’t aware of the existence of World Hub until now — this is completely new to me. However, if you tell me that it is not active, then it becomes a useless tool.

At the beginning, I thought that bugs and errors should be reported directly here on the MSFS2024 forum, and that’s exactly what I did.

I would like to remind those who develop airports and minor airfields, including airstrips and ultralight fields, that — at least for Italy — in addition to ENAC and Avioportolano, there is also this website:

It is a paid service, but it provides real and official information with very detailed technical data.

Yes, Asobo has corrected a few, but to the best of my knowledge, there have been no internal Bug Reports submitted to them from these.
They have just used this a resource.

It is not active at the moment, as Asobo has been concentrating on the sim’s performance.
That is not to say it isn’t going to be.
The last statements I have heard is that the new version of it is still in the works.

I would like to point out to SpotterSim not to confuse the ICAO code (which is recognized worldwide and is used on Jeppesen charts and Garmin navigators) with a local identifier code. These are two completely different things.

The identifier code can refer to different types of airfields, such as airstrips, ultralight fields, or small aerodromes. Unlike the ICAO code, which is always made up of 4 letters, an identifier code can vary in format and length.

Therefore, when you indicate SEGU, it is not a local identifier code, but an ICAO code.

Spottersim is following the requested reporting format from my first post. Identifier covers any designation with ICAO being the primary if present followed by any other designation.

Ah, I overlooked the distinction. Thanks for the clarification!

It’s simply the ID that the sim uses. It might be an LID, an ICAO, or something made up entirely when neither exists.

CharlieFox The LID (Local Identifier) is not something invented.
It is a real and commonly used identifier, especially in general aviation.

Unlike ICAO codes, which are standardized worldwide and always consist of 4 letters, a Local Identifier (LID) can have a variable length and is assigned at a national or local level.

It is often used for smaller airfields, private strips, or ultralight fields that may not have an official ICAO code.

So, calling it “invented” is incorrect — it is simply not part of the global ICAO standard, but it is still a legitimate and widely used system.

Chaliefox The LID (Local Identifier) is not invented, and it is not random either.
It follows a practical naming convention, even if it is not standardized globally like ICAO codes.

In many countries (for example Italy), local identifiers are assigned using a logical structure:

  • A regional or provincial prefix (e.g. “BA” for Bari)
  • Followed by a number or a short name related to the airfield

For example:

  • BA05 → Bari area + progressive number
  • BAALT → Bari + Altamura (location-based abbreviation)

So while there is no single international algorithm like ICAO, there is still a clear and consistent logic behind how these identifiers are created and used locally.

They are officially used in local aviation databases, flight planning tools, and national publications, especially for small airfields and ultralight operations.

You don’t have to explain it to me, I’m well aware. The point I was making is that in the context of the reports in this thread, “identifier” means whatever the sim uses for that airport (no matter the “correctness”), so that scenery developers can find that airport in the sim as such and fix the problem that’s reported.

If the ID itself is incorrect, that can also be a category of report.

I plan to make another update after SU5 is released. Beyond that, updates won’t pick up until World Hub is released or MS/Asobo make drastic changes to address the numerous issues with airports and helipads. With that said, I strongly encourage you all to continue posting issues in this thread as we know MS/Asobo frequently view it.

Identifier - VOHS
Name - Rajiv Gandhi International Airport
Category - Grounds and Facilities
Description - Cargo stands are missing in the simulator, and the main apron layout is completely outdated compared to current aeronautical charts and satellite imagery. The cargo area and apron have undergone real‑world redevelopment that is not reflected in the default autogenerated airport.

Identifier - FCPP
Name - Maya-Maya Airport
Category - Grounds and Facilities
Description - The airport layout is outdated in the simulator, and multiple gates are missing

Identifier - FOOL
Name - Libreville Leon M’ba International Airport
Category - Grounds and Facilities
Description - Multiple gates and stands are missing in the simulator. Existing stand characteristics are incorrect, and several stands are misaligned or incorrectly positioned compared to real-world aeronautical charts and satellite imagery.

New terminals at these airports

KMSY New Orleans

KMCO Orlando

KMCI Kansas City

KSLC Salt Lake City

KEWR Newark

KSAN San Diego (I think this new terminal is not open or newly opened. I saw it on navigraph charts)

Identifier - VCBI
Name - Bandaranaike International Airport
Category - Grounds and Facilities
Description - Many gates and stands are missing in the simulator compared to real‑world aeronautical charts and satellite imagery.

Identifier - KLAX
Name - Los Angeles International Airport
Category - Grounds and Facilities
Description - The Midfield Satellite Concourse (MSC) is positioned too far south in the simulator, and several gates are misaligned compared to real‑world airport data. Taxiway N2 is missing entirely, and Taxiway M is outdated in layout and alignment.

Identifier - OAKB
Name - Hamid Karzai International Airport
Category - Grounds and Facilities
Description - Several gates at this airport are misaligned in the simulator, and multiple jetways are missing compared to real‑world airport infrastructure.

FYI, fixes listed in the in SU5 v1.7.16.0 Release Notes:

Identifier - LEBL
Name - Barcelona–El Prat Josep Tarradellas Airport
Category - Grounds and Facilities
Description - Stand designations are incorrect in the simulator and do not match current real‑world airport documentation and aeronautical charts.

Identifier - MGGT
Name - La Aurora International Airport
Category - Grounds and Facilities
Description - Stand numbering and stand positioning are incorrect in the simulator and do not match current real‑world airport layouts, aeronautical charts, or satellite imagery.