I am experiencing a critical issue with the Fenix A320 in MSFS 2024 since updating to AIRAC Cycle 2605.
I am writing to report a persistent error regarding the SimBrief integration in the Fenix A320 (MSFS 2024). Despite a previously flawless experience, I am now receiving the “INVALID F-PLN UPLINK” message on the MCDU whenever I attempt an INIT REQUEST.
While the SimBrief integration works perfectly on the aircraft’s EFB (Tablet), the MCDU returns an “INVALID F-PLN UPLINK” error when trying to perform an INIT REQUEST. I have already updated all data via the Navigraph Hub, ensuring the Fenix A320 and the simulator are on the latest cycle.
Troubleshooting steps already taken:
Confirmed Pilot ID/Alias matches between SimBrief, the Fenix EFB, and the Fenix App.
The EFB correctly imports the flight plan, weights, and fuel (AOC works on the tablet side).
Verified that the SimBrief Airframe matches the engine variant (tested with both CFM and IAE, as well as Sharklets/Fences).
The flight plan was generated/OFP created immediately before the flight.
Full synchronization of the AIRAC cycle via Navigraph Hub for both MSFS 2024 and the Fenix A320 specifically.
The issue started exactly when AIRAC 2605 was released. It seems the FMS/MCDU is rejecting the uplink data even though the EFB parses it correctly.
Key Observations:
The error only appeared immediately after switching to the 2605 cycle.
The AOC/EFB can read the SimBrief data, but the FMS (MCDU) rejects the uplink, maybe suggesting a possible syntax or waypoint discrepancy in the Fenix-specific navigation database for this cycle?
I have tried multiple airframes and engine variants with the same result.
Could you please investigate if there is a known compatibility issue with the 2605 cycle or is there any known corruption or error in the data export specifically for the Fenix A320 in this cycle?
Hi,
I have checked the database, and it looks ok. I have also made some other tests.
Here are my results:
To enter the route manually - working
To use another flightplan (LOWW - EDDF, LEBL - EDDL, …) - working
To select another flightplan from LEBL - EDDB - not working
So, it looks more like a route issue somewhere, but I can´t debug it deeper; that can only be done by Fenix. What I see from “outside” is that the data are ok, but I can reproduce this Uplink issue, that’s for sure.
I would recommend opening a ticket with Fenix, as they can check this directly in their addon. I´m sorry that I cannot give you a better answer.
Hi again,
We are digging a little bit deeper into this issue, and it could be (no, honestly I´m sure) a Fenix issue. We have found an entry in the System-log:
5/15/2026 2:33:13 PM * Simbrief:Waypoint KLF not found on airway T278
We have checked the database to check if KLF is on the airway T278, and it is.
So, it looks like either a “false alarm” in the log, or Fenix isn’t handling it properly. It seems the database and the IDs are correct. Possible Fenix can look into it further.
Why was this working before? Easy, KLF was not part of T278 with AIRAC 2604; it´s new with AIRAC 2605.
Oh, thank you so much, Richard for your thorough research and dedication in trying to solve this problem. I had already contacted Fenix technical support. While I await their response, and if you don’t mind, I’d like to share your excellent research with them so they can take it into account. I am deeply grateful for your invaluable help. It’s a true honor to be part of your community.
This I believe have nothing with Fenix at all to do. As I wrote issues have accrued before for me also with Ifly and TFDi. What I think could be a idea is to have a selection to skip both SID and STAR from being imported for numerous reasons.
No, Ek, this seems really a Fenix issue, possibly other addons can’t handle that too. Still, in both your examples, they use different datasets that don’t have these relations, and even in iFly, as in TFDi, the KLF is coded as ID, not lat/lon.
So, in these two add-ons, it’s a navdata issue somewhere.
Hi again, Garik,
I want to say thank you very much for these kind words. We are acting as a team, not only internally but also with you, as our users. I´m also proud to be part of this community and, for nearly 20 years, part of the Navigraph team.
It is always a pleasure to get such feedback because it shows us that this is not “only” a business-related connection; it is also a personal connection to you, our user.
Without you, without this great community, we would not be where we are currently.
Thank you very much, Garik - I will forward your feedback to the whole team because it´s special for all of us.
Enjoy your weekend & greetings from Austria,
Richard
