There are actually two airports here - the airport you have selected is actually Villa Char Mar (1FA9), which is a paved strip about 500’ to the east of the non-paved Jubilee Acres (FD10). The runways are parallel, and both are currently designated 18/36 in official data. So you’re right about the mis-designation (more on that in a minute).
The airports are so close together that despite having different info blocks on the sectional chart, the symbology overlaps and you only see the airport symbol for 1FA9. That said, the sim seems to have placed FD10 in the wrong place, as the graphics you show are overlaying the 1FA9 runway.
As far as it being the wrong runway number, magnetic variation changes. The runways are both aligned at about 180°/360° true, but magnetic variation is currently close to 7°W, which makes their magnetic heading closer to 187°/007°. It’s possible it was re-designated at some point in the last several years, but I can’t currently find evidence of that.
Either way, somewhere along the line, something interpreted that as needing a 1/19 designator. But as airport owners generally don’t change designators until they have to (even moreso for private airports and soft runways), so they remain the same, despite the heading change, until a repaving project or recertification (again, very rare at private fields). Thus, you often run into discrepancies between designation and heading.
Clear as mud, right? I hope that background info helps folks who are looking at issues like this in the future. The sim tries to do its best, but it’s going on several disparate, often incomplete sources of info and gets airport details wrong a lot. It needs human touch and interpretation.
It would be awesome if they added the Verín-Oímbra airfield in Spain, its located right in the south of Verín, almost in the frontline with Portugal, its ICAO is LE419 (Aeródromo de extinción de incendios de Támega)
Identifier - VANM Name - Navi Mumbai International Airport Category - Missing Airport/Helipad Description - The airport is missing entirely from the simulator and is not available as a selectable location.
Just adding to @Speed1994 's link in the previous post by including the list of airports in the drop-down below so that the fix will be found when a user searches this topic by referencing the airport’s ICAO.
Fixes in (AIRAC) cycle 2605
KALW - Fixed runways 7/25 and 17/35 should be closed
KBLM - Fixed wrong taxiway signs placement
KCMR - Fixed missing airport
KCPT - Fixed missing building arount the airport
KDVO - Fixed misplaced beacon tower
KEDW - Fixed missing parking spots near runway
KILM - Fixed missing terminal building
KLAS - Fixed some jetways not connected to terminal
Anyone else seeing elevation issues at KMRY? I just tried it in SU5b.28. No idea if this issue existed prior to the release of beta 5.1. But I’d hate to climb or descent to those runways on an angle like shown below! This is on a perfectly clean version of MSFS2024 (no add-on’s, additional programs running, etc).
Regards
Description: There are some fscking buildings on the taxiway that I learned the hard way has collisions enabled. I am so mad because I keep flying for hours only to discover the mission is uncompletable because of this ish.
The list of issues found at the beginning of this thread has been updated with the fixes from SU5 and latest AIRAC per the release notes except for Gaya’s updates. It doesn’t look like any of Gaya’s fixes were pushed to SU5 despite them listed. Although Gaya’s fixes are listed in the release notes, the first issues I checked remain present in the sim, which suggests those changes may not have been included in SU5, so I did not continue a full verification pass.
As mentioned earlier, until World Hub is released or Asobo / Microsoft make significant updates to their tools to address these en masse, updates to the list will drop off in frequency significantly. They are aware of this thread and monitor it so continue posting new issues you discover.
This thread, thanks to all of you, has been in the top 5 on the Issue Tracker for months. Many of these issues have existed for over 5 years, since the launch of MSFS2020.
The overwhelming majority fall into one of these categories:
Terrain and obstacle issues on runways, helipads, taxiways, or aprons causing damage to aircraft
Missing and/or incorrectly placed taxiway signage or markings
Incorrect taxiway, gate, runway designations
Missing terminal buildings (jetways are visible but the terminal is missing.).
Numerous helipads with only the satellite overlay present (poor image quality), specifically pads on the ground.
Outdated or incorrect airport layout. (runways, taxiways, aprons, windsocks, control towers, aircraft parking spots, etc.)
Numerous missing locations, locations with incorrect identifiers, or locations active in the sim which should be closed.
Overcrowded aprons or incorrectly sized aircraft parking spots
Given recent advances in AI, it would be encouraging to see Microsoft explore tools that could integrate digital data from AMDB providers and other sources into the sim. The potential use cases would likely extend beyond MSFS.
Thanks a lot for your dedication to maintain this thread! I fully support the call for extensive features to maintain the airport database, as its age is becoming more obvious with each report.
