Airbus A320/A321/A330 vertical path messed up after importing from EFB in SU5

ISSUE DESCRIPTION

Description of the issue:

After SU5, the vertical path computation of airbus aircraft are messed up if we import the route from EFB. The (DECEL) waypoint will have an altitude of 0, before the final ILS or RNAV waypoints. None of the altitude constraints will be respected, and managed descend will not properly follow the contrained flight height. When we reselect the arrival procedures, the path will be recomputed properly.

FREQUENCY OF ISSUE

How often does this occur for you (Example: Just once, every time on sim load, intermittently)?

Every time

REPRODUCTION STEPS

Please list clear steps you took in order to help our test team reproduce the same issue:

  1. Create flight plan in EFB in free flight or career mode

  2. Send to ATC and Avionics (In career mode, this step can be skipped)

  3. In the MCDU, go to INIT page, see that the CRZ FL is FL1/FL2 (the first digit) with incorrect temperature. Manually correct it

  4. Go to F-PLAN, and switch the ND to PLAN mode, go to the last few way point on the ILS or RNAV path, see that the (DECEL) way point requires an altitude of 0, before the last few way points, and on the ND, there is no vertical constraint.

  5. Now in the MCDU, reselect the arrival procedure, see that the vertical constraints are properly recomputed, and the pink/purple constraints are shown properly on the ND.

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, if relevant:

[PC Only] Are you using Developer Mode or have you made any changes to it?

[PC, MSFS 2020 Only] Are you using DX11 or DX12?

[PC Only] What GPU (Graphics Card) do you use?

[PC Only] What other relevant PC specs can you share?

MEDIA

Please add a screenshot or video of the issue occurring.

Figure 1: after importing the path, the purple height constraint for HEMAN (KSFO-ILS28L ARCHI) is above 3100, but in the MCDU, it is only 1800, because (DECEL) incorrectly requires vertical height 1800.

Figure 2: If I click on send to ATC/AVIONICS on the EFB again. All the constraints are cleared, and the min height for HEMAN/DUYET are now —- and cannot be changed

Figure 3: At the same time, the CRZ FL becomes FL2/-41, which should be instead FL290/-41

Figure 4: another reproduction in career mode, flying to LFML, ILS 31R, see that the altitude constraint at MRM02 should be 2000, but in MCDU, it is changed to 60, and the following (DECEL) is 0

1 Like

(post deleted by author)

Hello please report it here too so we can add it to the bug list of these airplanes

A320neo (v2) - A321neo Family bug list (SU5)

Thanks

1 Like