In MSFS2024 a lot of SID/STARS are unflyable since GPS coordinates for fixes are inserted in the MCDU as N0/E0. This makes waypoint to be thousand miles away. I started this topic as the same one was close with no resolution but I have the exact same issues on FS24 and only with Inibuilds planes. MCDU All okay until I enter a SID or STAR than goes 6000 nm away and show 0 for the lat long coordinate. Pictures sre from the A330 but the same happen on all mu flight with the A321N.

I tried removing all airac and reinstall them and it did not fix it.

I have this same problem in the A330 300. Everything is ok until I select a Star and it calculates various points on the flight plan as thousands of miles away. I tried a flight from Bangkok to Singapore and it had one leg at 7700 miles when you try to delete it, it simply moves the incorrect distance down the flight plan, making It impossible to fly the route. It doesn't occur on all routes that I have tried only random ones. Many thanks.

It happens on Sids as well, forgot to say, I have not ever had the problem with the new A50.

Same here I reported it a while back but no answer ...

Edited April 10, 20251 yr by alex6463

SIDs in HKG are all unusable. More than 10k miles on every SID. First thought it would be a Navigraph problem, but they confirmed its a inibuilds issue.

Hi there,

I am currently experiencing the same issue, meaning that it hasn't been solved in the meantime. I checked the Navigraph forum and it seems that the issue was reported there as well:
https://forum.navigraph.com/t/navdata-problem-in-defult-airplane-in-msfs2024/20002

As it seems, the guys at Navigraph have concluded that the problem relates to the A320neo V2 using the "old WT framework" - I am not sure whether the other default aircraft such as A310, A321 and A330 are also affected by this.

Since the FMC is messing up almost every SID or STAR I load in, needing painstaking manuel editing which then again seems to destroy things like T/D calculation, I would really appreciate a fix for this. Is there any effort underway?

The A330 is affected, as someone mentioned above SID/STARS/Approaches into VHHH are totally unusable. I'm surprised this hasn't got more attention, but many airports are unflyable in the A330. 

I have the same issue. I tried to fly from LTFM and SID/START were broken. Team, please fix it. Thx

Can we get any answer for this please? This effects all your default Ini planes using Asobo AIRAC.  When will default aircraft be updated using the latest WT framework?

Edited July 27, 2025Jul 27 by VBHB

i am still experiencing this issue, did anyone find a potential fix or workaround? Or will the team be rolling out a fix for this at some point?

After hours of troubleshooting, I found a fix to this problem, but it only works if you have Navigraph subscription.

The cause:
This problem is actually not specific to just iniBuilds default A320/A330, it's applicable to all Asobo-distributed aircraft, such as ATR. It's caused by combination of factors, among them how MSFS2024 handles package priorities and how some 3rd party airports are able to override any other navdata. Apparently, some 3rd party airports somehow override MSFS default or Navigraph data, but they don't have airport-related fixpoints and other things properly defined in them, so this causes those fixpoints in airport's SIDs and STARs to have 0,0 coordinates. This is a reason why this problem never occurs for default airports. Many custom airports are also working fine. It's just those custom airports that have their own navigation layer are causing this problem. In my case, I specifically had it occur on freeware airports developed by x-flight team.

The fix:
If you are using Navigraph, you can fix this by setting priority of Navigraph data higher, so it takes over navdata in airport scenery. Open your Content.xml (located in [your_windows_username]\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalCache\[your_MSFS_username]. In the file, find following entries:

<Package name="communityfs24-navigraph-nav-base" active="Activated"/>
<Package name="communityfs24-navigraph-nav-jepp" active="Activated"/>

Now give highest priority to this data:

<Package name="communityfs24-navigraph-nav-base" active="Activated" priority="100"/>
<Package name="communityfs24-navigraph-nav-jepp" active="Activated" priority="100"/>

After I did this, all my SIDs and STARs started to load correct for both iniBuilds default Airbuses and ATR.

Sorry, I don't know if it's possible to fix this if you are not using Navigraph.

Edited 12 hours ago12 hr by j.14