Not sure where to post this, but I’ve been having a problem after importing a Simbrief flight plan into the Flypad on the FBW A32NX. When I try to import the Simbrief flight plan via the INIT REQUEST option on the MCDU, I get an invalid data uplink error. Rather common if you don’t follow all the procedures recommended by FBW (which I have correctly done).
The interesting part is on the Flypad of the FBW aircraft one is able to see an error pop up explaining why the uplink was unsuccessful. In my case it’s specifically because of a waypoint TOVAR, see screenshot.
This might have originated from a flight I did up the east coast from Miami to Charleston.
If I create and import a flight in Europe, no problems at all.
If I return to the east coast USA, even staying up North, the error shows up again, and unable to load the flight from the Simbrief import in the Flypad into the MCDU.
I first thought it was because I had an outdated AIRAC cycle. So I subscribed to Navigraph for a month, updated all necessary elements (even the sim) to the latest AIRAC, (2607 as of 5 August 2026). I cleared the rolling cache of the sim, restarted everything more than once. It actually fixed the problem for ONE uplink, but then came back the second time I tried.
Why is this waypoint TOVAR giving me such a headache? Is this something in the Navigraph database?
—Interesting observation: not long ago (April?) the US government created a no fly zone and altered the flight paths around YOU_KNOW_WHO’s house down there near West Palm Beach, very close to this TOVAR waypoint. Maybe it has something to do with that?
Thanks for any insight you might give me to my problem. I’m stumped!
Here’s the flight plan if it helps:
KCHS/33 N0443F370 PLMTO3 CRE DCT RAPZZ Q135 RREGG Q117 SAWED Q97 ZJAAY JIIMS4 KPHL/09L
Are you 100% sure this is the exact flight plan throwing the error when importing? The southernmost waypoint of that route (airport KCHS) is 381 nautical miles north of waypoint TOVAR, which doesn’t make a whole lot of sense.
Regards,
Tim
Oh I know, and YES this is the flight plan that gives the error. As well as any other plan I try to import that goes up the east coast, even far north. The day before, I flew from Miami to Charleston, with no problem. I can paste that flight plan as well. It’s almost like that’s where I picked up the TOVAR waypoint. But that said TOVAR wasn’t even on that flight plan from KMIA to KJZI (regional Charleston, an error I made…)
When you enter TOVAR manually (i.e., in the EFB or in the WorldMap), does this work?
Here from my MSFS 2024 - AIRAC 2608 installed:
It seems you have installed 3rd-party scenery, which is causing this issue because TOVAR is included in MSFS.
Cheers
Richard
Thanks Richard for your reply. No 3rd party scenery is installed. I will look later to see if TOVAR is available via the EFB and Worldmap. I just want to clarify that the flight plans I’m creating (with Simbrief) that throw the error in the MCDU of the fbw320 go nowhere near TOVAR, other than being on the east coast. European flight plans are accepted without any problem. So basically, I don’t even need TOVAR!
But it’s causing an error. This all could be a Flybywire issue, not sure.
This morning I downloaded the latest AIRAC (2608) that just came out overnight. I updated EVERYTHING that depends on it. I went back to the stable version of the fbw320 just in case. I’ll be testing later today to see if this resolves the problem. I’ll update when I can.
Possibly a silly question:
The flightplan was created with the current AIRAC 2608 or with any previous cycle?
I have recreated it on my system, and I get the same output as you:
KCHS/33 PLMTO3 CRE DCT RAPZZ Q135 RREGG Q117 SAWED Q97 ZJAAY JIIMS4 KPHL/09L
I have tested this in the latest stable FBW A320 version:
So, I can´t identify any issue here - with TOVAR or without TOVAR.
Cheers & thanks for testing and the additional information
Richard
Thanks Richard for putting in the effort to help me. The first time I was having this problem several days ago I was running an old outdated AIRAC from last year. To search for solutions I renewed my Navigraph sub and updated the AIRAC to the latest version, which a few days ago was 2607? Though it was still current. I also updated the Sim with simhub, cleared the rolling cache and retested. I still had the problem with TOVAR.
As noted above, this morning with the new AIRAC out, 2608, I updated everything related to the sim and changed back to the FBW stable version.
I just recreated the flight fresh in simbrief, started in a parked space on the tarmac in KCHS, imported the flight plan into the flypad. Clicked the INIT REQ button: (held breath): this time it indicated INVALID UPLINK as before, but actually imported the flight plan correctly. I was able to clear the error on the MCDU, and took a look at the flypad and no new error appeared! (with regard to TOVAR).
SO, for the moment all is well. But I have been able to successfully import once before only to have it throw the error on a second try. I did not compete the flight as it was for testing, but later I will run through the process again to make sure.
Thanks again for taking the time to help me trouble shoot.
You are welcome, thanks for your feedback - may I ask, which FBW version you use? The stable or the dev version? I ask because I use the latest stable version …
Cheers
Richard
1st failure/error: stable, 2nd failure/error: dev, 3rd reset and retry: stable version. I’m currently flying the route. Everything went perfectly for the set up, import, no errors. There was definitely a gremlin in the machine, probably on my end because of using outdated AIRAC, then updating, then changing versions, who knows. But the release of a new AIRAC was timely and I think it helped resolve the issue. Really still unclear if this was of origin from Navigraph, or my installation. Just happy it’s resolved and I’m on my way to Philly at FL390 with no errors. Thanks again for your help.
