Unable to import SimBrief flight plan into MCDU/FMC - AIRAC 2511 rev. 3

SimBrief Dispatch
1

Hello,

I am having issues importing my SimBrief flight plan into ANY FMC/MCDU of any aircraft in MSFS2024. I have had this problem on all aircraft, including the Fenix A320 and IniBuilds A350. Keep in mind that this problem does not affect the EFB in any aircraft, just the FMC/MCDU. Also, this only started to happen after I updated Navagraph Hub to AIRAC Cycle 2511 rev. 3.

Thanks in advance,

Malcolm

2

What is your flight plan that you are unable to import? Like departure airport, arrival airport and route?

Regards,

Tim

3

Hi Tim,

The route is going to be: FENIX A320-200; KSEA-CYUL; KSEA**/16L N0456F330 MONTN2 SEA DCT ZADON DCT ZELAK DCT ZIRAN DCT ZAXBY DCT BLOWS DCT ISN DCT MOT DCT DLH/N0457F350 DCT SSM DCT BEMOG LFLER7 CYUL/**24R; (I have made different variations, but with the same DEP/ARR airports).

Best,

Malcolm

4

What if you manually remove the SID and plan e.g. the following route:

DCT SEA DCT ZADON DCT ZELAK DCT ZIRAN DCT ZAXBY DCT BLOWS DCT ISN DCT MOT DCT DLH DCT SSM DCT BEMOG LFLER7

MONTN2 is a “vector” SID that doesn’t explicitly end at the SEA VOR, any many aircraft addons (including the Fenix, put probably others as well) have trouble making this construct work (same applies to ISBRG1, JEFPO1, OZWLD1 and SEA9 departures as well).

Regards,

Tim

1 Like
5

Alright, that helps.

Thank you much,

Malcolm

6

So this means import was successful after manually removing the SID, correct?

Regards,

Tim

7

Correct,

Thank you much.

8

You’re welcome :slight_smile:

Regards,

Tim

9

@SimBrief now sure what the Fenix and other tools use as the source for the route during import, but I wonder if for cases like this adding a DCT between the SID and the first waypoint of the route could be a feasible workaround?

Unfortunately I cannot test it as manually adding it (e.g. MONTN2 DCT SEA) the DCT gets filtered out in the generated briefing.

Regards,

Tim

10

Yes, I think that that should work. I have played around with the routing system and it appears that it works. Thanks!

11

In all fairness, I do not think this should fall on SimBrief to fix.

Fenix aren’t the only ones using the SimBrief API, and changing the output for one add-on has a very real risk of breaking other add-ons in the process.

This bug should be extremely trivial for Fenix to fix on their own end. It should be as simple as:

  • Check if the SID transition exists.
  • If yes, use it.
  • If not, insert the “no transition” or “default” variant of the SID, then direct to the first route waypoint. So “MONTN2 SEA” should be inserted as MONTN2 with no transition, then a discontinuity, then direct SEA.

Or just don’t import the SID at all if the transition is unrecognized, but I think the above logic should work just fine.

Best regards,

1 Like
12

Hi, I believe that it should be under SimBrief to fix this problem because their whole idea is flight planning, if there’s a mistake with a flight planning, they have to fix it.

The problem has been solved, so it is all good.

Best,

Malcolm

13

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.