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.