Description of the issue: When flight plans are sent to avionics from the Flight Planner EFB app (either using the Send to Avionics button or simply by creating the flight plan prior to starting the flight) the resulting flight plan in the MCDU contains numerous flight-breaking errors. The most common issues demonstrated in this report include:
mishandling/complete omission of any portion of the enroute flight plan which contains an airway
incorrect selection of waypoints/navaids with duplicate names potentially thousands of nautical miles apart
FREQUENCY OF ISSUE
How often does this occur for you (Example: Just once, every time on sim load, intermittently)?
Every time with default iniBuilds Airbus airliners (note, this was tested on and not observed with default Boeing airliners or any other avionics platforms in the base simulator).
REPRODUCTION STEPS
Please list clear steps you took in order to help our test team reproduce the same issue:
Start a flight with the iniBuilds A320neo and the following route built in the Flight Planner EFB app [ENGM/01L EVTO5A EVTOG Z418 DOPUX DCT SOBDU Z263 IPTON DCT H6203 DCT H6207 DCT 6310N DCT H6314 DCT ING DCT NASBU NASB4K BIKF/19]
Observe that on the F-PLN page of the MCDU the route goes EVTOG DCT SOBDU DCT H6203 completely omitting two (2) different segments of the enroute flight plan that should have used airways
Observe that the distance between EVTOG and SOBDU is 3,680nm (it should be approximately 81nm with missing waypoint DOPUX in between)
Observe that the distance between SOBDU and H6203 is 3,754nm (it should be approximately 310nm with missing waypoint IPTON via missing airway Z263 in between)
Observe that the distance between H6203 and H6207 is 3,754nm (it should be precisely 110nm)
Observe that the distance between H6207 and 6310N is 3,809nm (it should be precisely 87nm)
Observe that the total route distance is calculated as 15,278nm (it should be precisely 1,011nm)
YOUR SETTINGS
If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the User Support Hub.
What peripherals are you using: n/a
[PC Only] Are you using Developer Mode or have you made any changes to it? No
[PC Only] What GPU (Graphics Card) do you use? AMD Radeon RX 7900 GRE
[PC Only] What other relevant PC specs can you share? n/a
This is still present on 1.6.23.0 - anytime the imported route includes an airway, the MCDU skips over it and all subsequent waypoints and procedures and goes direct to the arrival airport.
Possibly? Skimming through it, it sounds like their flight plan is imported zero en route waypoints, though in my experience it’s importing everything up until a jetway is used, then it skips to arrival. Very similar at best, but possibly the exact same.
Hi, Ihavent tested it with the A320neo v2 but I’m mainly having this issue with the A330 variants and I’ve had it on the A350 variants. I haven’t really looked at the Boeings in too much depth except the 737 Max 8 and I’ve different issues to moan about with that.
In my case, the issues I have are the same as the OP’s. I’ll create a flightplan in Simbrief assign it to the correct variant airframe and generate. When I get into the game I’ll import the flightplan either from the world map or from the gate and this is where the problem seems to stem from.
For example I’ll create a flight from Paris LFPG to Saint Martin TNCM but a chunk of the waypoints will be missing. Namely the ones made up of numbers over the Atlantic called 3630N etc. When my aircraft finished the SID it would then deviate from the flightplan to track a waypoint over 2500 miles away.
Instead of importing the Simbrief flightplan from the efb, I tried importing from the MCDU instead and this seems to work. However, doing it this way prevents you from filing the IFR with ATC. There’s also no way to erase or overwrite the flightplan once it’s in there except via the efb import method. The only work around is to import from the efb as normal to get the “file IFR clearence” prompt in the ATC window but then to use the “secondary f-plan” button to clean import a fresh full flightplan and then activate it.
*I specifically tested the A330-300 GE but as all variants are combined into one package, it’s assumed that defects of systems shared by all variants would be universal among them. Also of note is that I continue to get frequent-but-not-100%-consistent CTDs when selecting the A330. This typically happens during on the aircraft configuration menu but can and has happened at any time prior to the flight beginning. I will open a new bug report for this soon, but just strange that I’ve seen no one else mention it and it’s occurring with a totally empty community folder.
We have created an internal ticket to see if our team already has this logged, and if not they will attempt to reproduce the issue and create a new bug report. This item is now marked as feedback-logged. If there is an existing bug report or one is created, we will move this thread to bug-logged.
Any update on this bug? I have just come across this exact issue whereby by imported a flight plan that i created via on the FS flight planner and then imported into EFB. This misses out most if not all way-points in between a departure procedure and rival.
