Hello.
After updating AIRAC 2025 Rev2 (after fix from today), when I want to import a Flight Plan from Simbrief in the FBW A32NX, I have a error message " INVALID F-PLN UPLINK" in the MCDU and cannot import the Flight Plan.
All my parameters, Simbrief ID, … are OK.
If I remove the AIRAC and re-launch the SIM, I have no problem.
Thank you for your help.
1 Like
Hello!
Can you provide the flightplan that you are trying to load?
Kind Regards,
Malte
1 Like
LGAV - UNNT : KRO2E KRO UN604 AMANI UG8 SUDES UN604 BIG UG8 IST UM603 BKZ UW702 PAZAR UT310 INB UM853 GAKSU UN743 ODIRA G487 ROKMO R710 ZG G487 OBATA L988 ATR N60 NINBU A357 LENTA N60 BARKI A357 OMONA B234 SZ W1 GOLIM GOLI1K
I have retried with another flghtplan, it’s the same (LGAV-LFPG : KOR1E KOR UL53 OLGAT NUTRO CERVI MOLUS UNKIR UM982 TINIL TINI9W)
My Simbrief is well in AIRAC 2503.
The import in the EFB is OK.
I have retried without the Navigraph AIRAC 2503 rev 2 in the SIM (2020), it’s OK.
The problem is when this package is loaded.
Cheers,
Alain
Same here, any FPL. The A20N is also not finding any airways while hand-typing the plan.
E.g. EVRA/36 N0440F380 VALE2H VALED M869 LEP M864 ADAXA DCT NINTA DCT DIPEB DCT ANFEV DCT PENOR DCT BODLA DCT KOSIX DCT NIMAB T171 LASTO T178 KERAX KERA5D EDDF/07L
1 Like
Good morning.
Any idea ? It’s the same this morning…
Thank you.
Hi,
Thanks for your report. We will check this …
Cheers
Richard
Hello Richard.
I’ve retried this morning with this flightplan :
LGAV/03R N0451F370 KRO2E KRO UN604 SUDES UG8 BIG UN604 BKZ UW702 GUMRU UT310 HAKAN UW702 MIMTO UT310 INB UW90 SIN UW96 ODIRA/K0824F370 G487 OBATA L988 ALABA/K0820F390 T586 DAKIN B944 GOLIM GOLI1N UNNT/16
Same error message “INVALID F-PLN UPLINK”.
I have the development version of the FBW A32NX as always.
I switch to the stable version of the plane : this time, clicking on the INIT REQUEST freeze the sim, and whe have to brutally shutdown the sim…
If that details help you to investigate…
Can’t we return back to the AIRAC 2503 REV 1 temporarily ?
Thanks,
Cheers,
Alain
Hi Alain,
No, that’s not possible. We are analyzing the issue but don’t see any navdata issue somewhere. We will continue tomorrow and/or on Monday.
Possibly we find something …
I appreciate your understanding,
Richard
1 Like
Thanks Richard.
For now, I’m going to fly by removing the latest AIRAC package (files from April 3, 6:23 PM).
I saw two other posts that mentioned the same problem.
I’ll try asking FBW… but I haven’t seing any report in the Discord.
Cheers,
Alain
EDIT : the problem has been reported in the FBW discord : INVALID F-PLN UPLINK or
AWY/WPT MISMATCH with the latest update of AIRAC.
No response yet…
I can Confirm this is occurring in my setup as well.
Same issue here. Cannot load from SimBrief to FBW A320 MCDU (Stable) without the sim crashing/freezing (MSFS 2020). Tried multiple routes and only 1 out of 4 worked for me and I was able to fly. Up until now all has been flawless with this great mod. Seems like a bug with the latest AIRAC package.
1 Like
Again, we are still analyzing those reports.
Thank you very much
Richard
1 Like
Just an update to this:
We have seen a minor bug in the airway file; I’m unsure if this is the reason, but it could be.
We will fix it and release a new revision as soon as possible.
Cheers, and thanks for your patience
Richard
3 Likes
Thank you for your efforts! Just FYI…I rolled back SimBrief AIRAC to 2502 and I encountered the same issue as I had with the current AIRAC 2503. Freeze/CTD in MSFS 2020 when INIT loading into the MCDU, FBW A32NX (Stable version). I don’t know if this is helpful at all, just sharing my experience.
Follow-up Edit / FYI…I just tried the identical flight plan as above (GCTS → EGLL) using SimBrief AIRAC 2502 with the ASOBO 787, Working Title airframe, and there were no issues with the sim, all OFP and route data loaded perfectly, so perhaps the issue is with FBW???
Hi guys,
Just a short update - we have identified the issue and are working on a fix. As soon as we are ready, we will release a new version for both sims MSFS2020 and 2024. Is in both the same. We have “optimized” the airways a little bit too much; it looks like 
Sorry for that, and thanks for all your examples - they were very helpful! We do our best
Cheers,
Richard
2 Likes
Thanks a lot Richard 
It seems to go beyond that, I tried to manually punch in my route EDDM-EDDK without airways, it does not find waypoint ASKIK, then I tried to manually define it via the nearby FFM VOR, not possible, it does not know about that VOR. Probably because there are many dublicates to that VOR as if almost always the case, and it has just stored one in the USA, but the RAD NAV page (without asking) gives the correct one with the right frequency of 114.2, so very strange.
No, that has nothing to do with it and the FBW A32NX. I have tried both of your examples (ASKIK and FFM), and both were found in the MSFS2020. So, it seems you have another issue—properly with a third-party scenery and the loading order—but that has nothing to do with this topic.
… back to the initial topic now.
Thank you,
Richard
2 Likes
Guys, I´m still working on it - need a little bit more time, special for testing …
Thank you,
Richard