Airac 2410 VTBS Bangkok problem

[NAVData]

Hi,
There are several postings on this topic (outdated scenery in MSFS or any third-party scenery). Here are a few ones, where I have tried to explain the main reason:

EDDB with AIRAC 2410 doesn’t work

Hi again, No, no. I have understood you correctly. When you look at my reference link, you will see that the report is equal to yours but at an airport in the US area. In AIRAC 2409, the runway idents were 07LR/25LR, but with AIRAC 2410, they were changed to 06LR/24LR. That is correct because our data reflects the real world. The main point is the scenery in the MSFS—this scenery still has the old runways (it seems the third-party scenery, too), and therefore, the MSFS can´t assign the termin…

KBWI has no SIDS or STARS

Hi, the MSFS stock scenery for KBWI is outdated - there is a missing runway 15R/33L Here the current airport diagram from the FAA: [image] The data are all included for KBWI but the logic in the MSFS disables it, when terminal procedures can´t be assigned to a runway - in this case, there are some terminal procedures for 15R/33L but the runway doesn´t exist in the MSFS scenery - and therefore no SIDs, no STARs. Here the runways from the MSFS scenery - 15R/33L is missing: [image] Please …

Also, we have added this limitation to our release notes since day one after the release of MSFS 2020. We hope that 2024 brings any improvements here because we have all this data and could change the runway idents when possible and allowed.

@pattayapete

PS Is it usual to leave the old designations (01, 19 etc) in the data?

No, this is impossible, and honestly, it makes no sense. You can´t expect real-world data, and then we offer outdated data to fit with an outdated scenery. That is not our philosophy, I´m sorry.

Cheers,
Richard