MSFS2024
FBW A320neo
KIAH RWY 15L to KAUS RWY 18R
BNDTO6 MNURE WLEEE7
AIRAC 2603 rev.3
NO ADD-ON AIRPORT SCENERY
NO ADD-ON AIRCRAFT LIVERIES
The problem is FBW A320 MCDU is not loading Navigraph Nav data. What is loaded is MSFS26030001 and it is not in sync with Navigraph AIRAC Cycle 2603 rev.3. Simbrief has given me RWY 15L BNDTO5 for departure, but I can’t insert it into MCDU. My only SID options for 15L are GRIFFA1, INDIE8, LCH5, LFK4 and MYLSN8. I have uninstalled FBW A320 and Navigraph AIRAC Cycle 2603 rev.3 two times, but MCDU still loads MSFS2603001. Don’t understand why Navigraph AIRAC is not overriding the default AIRAC values. Following image shows SIDs from MSFS2603001.
Ian, Thanks for investigating this, so I am now stuck on finding out why my configuration is not working. I don’t have much in my Community folder, but I’ll start removing SayIntentions or Hanger Control. These apps have not caused problems in the past, but I will start there. Once again thank you for ruling out Navigraph.
Robert
Hi Robert,
One additional input besides Ian´s answer:
Before you delete/remove anything, the FBW A320 uses in-game data, so I recommend testing it in another MSFS stock aircraft first. My personal recommendation is always the C172 equipped with the Garmin G1000, because it uses the latest WT navigation framework and is a good reference for whether the data is working/complete.
When you see the terminal procedures here, you know that this is an FBW A320 issue and not a general issue on your system:
Here from the G1000 with the latest AIRAC installed:
I have now flown have the FWB A320 from KONT to KSAN with no problem with departure SIDS appearing in MCDU. Still working on solving problems with SID issues from KIAH to KAUS. It is a mystery to me. I did fly Cessna 172 SP from KIAH to KAUS and SID, route and STAR loaded just fine.
The attached Simbrief screenshot shows the selected route as ILEXY4 ILEXY GUSHR3. When I use Find SIDS/STAR it only lists one SID - CWK8. Why does BNDIA3 not show in the list? BNDIA3 appears two times as Suggested Route options. Any suggestions?
Robert
Because BNDIA3 only connects with BNDIA, not ILEXY (the first – and here, only – enroute waypoint). The CWK8 departure, on the other hand, does have an ILEXY transition.
That being said, at first glance, it does seem weird that ILEXY4 (which also ends at, and therefore connects to, ILEXY) is not shown above in the SID/STAR selection panel.
