Since yesterday, after updating to AIRAC 2606 I am no longer able to import Simbrief flightplans into G1000/G3000 or G5000 planes. Everythign worked great until I updated to teh newest AIRAC (20ish flights last week, not 1 problem).
Uninstalling Navigraph and rebuilding the flightplan with MSFS native Data works fine.
Skyward Sovereign+, Cessna Citation Longitude, TBM, C172, Citation X all can’t import flightplans from simbrief anymore
MSFS2024 SU5
KEYW BUFTT1 MATLK Q87 NOWAE DCT BEXGO T398 TAPPA T295 SHLBK T224 ENO V213 BESSI Q22 BAYYS T315 SNIVL DCT HFD DREEM3 KBED
Tried multiple different flightplans from different airports. No joy.
Fenix and PMDG work fine though.
What happens is, that only SID and STAR’s will be imported, all airways and waypoint in between are gone. Manually adding waypoint will show them in the GTC (Sovereign+) but not on the map. Autopilot completely ignores the whole flightplan, including SID/STAR.
Didn’t change anything since the last flight on Friday where everything worked just fine.
Once I updated to the newest AIRAC the problems began. Only other thing that happened was teh new World update by Asobo.
Hi,
Do you have any 3rd party scenery installed? If so, move all these packages out of your community folder, restart the sim, and try the import again.
Your description of seeing no issues with Fenix and PMDG indicates that you have a 3rd-party package installed that is not 100% SU3+ compatible.
Please try this FAQ - in nearly 100% all such reports, it was a 3rd party package and was not related to the navdata.
I have tried your flightplan - no issues:
Thank you
Richard
I uninstalled everything I had installed in terms of 3rd party scenery … in the community folder as well as marketplace … still the same issue. deleted teh streamed paxckages folder contents, even deleted the content.xml file to genererate it new … no joy.
I am going to do a full reinstall at this point and if that doesnb’t fix ikt, it certainly isn’t any scenery or whatnot … it’s mindboggling that an airac update can break soemthing THIS bad …
Please upload your content.xml file here before you make a new installation, so that we can check it.
It has nothing to do with the AIRAC update. As you can see in my screenshot, I have also installed the AIRAC, and the flightplan can be loaded without any issue. Further, when this is really a general issue, you can be sure we would have tons of reports here… but there’s only your report.
The reason for my assumption is your screenshot and the error message:
MATLK does not have the ICAO code WK7; it has K7 … at least in our database, so this data must be coming from somewhere else, but not from our data, because we have only 2-letter codes (the database is limited to 2 letters).
Please send us the content.xml file first. Thank you!
Cheers,
Richard
Thing is, everything worked just fine until friday … didn’t change a thing from friday to saturday other than updating the airac … that’s what I don’t understand.
Anyway, thanks for helping … I truely a appreciate it … it’s just extremely frustrating on ym end at this point. Didn’t mean to offend, apologies!
Here is the content.xml
Content.xml (99.1 KB)
Just found a solution anotehr user told me in WT discord …
Uninstalled ALL of navigraph .. charts, simlink, hub
moved content.xml
reboot pc
install all of navigraph and update
reboot pc
and presto it works … somehow the inconsistent data still came out of some kind of legacy navigraph installation … you might want to look into that. I know several people who have the same problem.
Under certain circumstances it seems that navigraph corrupts itself
Thanks for sharing your solution. Glad that is solved without a re-installation.
Happy flying
Richard
Actually, just a headsup. I found the main culprit.
My solution only worked for a short time before it went haywire again.
For me it was a corrupt Steam cloud save that messed things up.
Once I deleted that, reinitialized MSFS2024 everything is back to normal. All working perfect and for the first time since I bought msfs2024 I can actually use rolling cache .. looks like I’ve been carrying around that corrupt save for a LONG time
No idea why it suddenly decided to go belly up with the newest AIRAC update but hey, had a good side .. finally fixed a problem I didn’t even know I had 
