Question with those experienced in the FBW a32nx and loading flight plans, and apologies for any mistaken terms below as I am a noob at both. In this example (vid attached), I have a flight from KLAX->KSAN and I am using the LAXX1 to SLI with the MZB transition. After loading from Simbrief, I attempt to load that approach and I get a discontinuity that I can’t clear. When I select that departure, it seems to give me a vector and a straight path out, so what is the proper action here in terms of telling the MCDU how it is to connect the route? And is there a reason I seem to run into these issues with KLAX especially when heading down to KSAN as opposed to other departure/arrival locations? Thanks for the feedback/help in advance.
For that SID, you can’t.
Every path on that SID has radar vectors to join the departure.
As you can see here, for each runway, there’s a spot where it says “vectors” That means that on departure, you typically fly the assigned heading (a second turn to 221 for 25L/R departures) and then wait for departure to tell you where to go.
If you are flying without ATC (or ATC offline on Vatsim) then once stabilized, you would select Direct To SLI in the FMS. You’d also do that once ATC tells you either “proceed on course” or “proceed direct to SLI”
2 Likes
Okay, great. That’s effectively what I ended up doing (flying and vectoring to SLI). So I should just not worry about being a completist in terms of the graphical representation and be okay with a discontinuity. Thanks for the thorough response.
That’s exactly correct. The discontinuity has the same functionality as the MANSEQ on the garmin units that people are talking about. The FMS has no way to know how that section is going to be maneuvered. Once you are on the departure routing, that discontinuity is a thing of the past.
1 Like
