Hi guys, just a quick question. Is it normal SID ALT constraint gets active when bring the throttle to CLB? DEP OPKC set cruise ALT to FL390. When bring the throttle back to CLB SID ALT constraint shows up as FL070/7000. Not sure if this a350 behaviour normal. 

 

Comparison with Fenix A320:

In the Fenix A320, the SID altitude constraint is correctly capped at 7,000 ft and is consistently displayed on the altitude tape, navigation display (ND), and FMS, even when the FCU altitude is set to FL370.

In contrast, on the A350, recent builds appear to have a regression. The altitude tape does not display the SID altitude constraint during pre-flight setup. Instead, the constraint only becomes visible after takeoff, once thrust is reduced to CLB.

This behavior was not observed in earlier A350 builds, suggesting a recent issue affecting constraint visualization during initial flight setup.

Hi, this issue has been raised to the team, I will add this to the log for them, thank you.

On 4/30/2026 at 7:54 PM, LineDX said:

Hi guys, just a quick question. Is it normal SID ALT constraint gets active when bring the throttle to CLB? DEP OPKC set cruise ALT to FL390. When bring the throttle back to CLB SID ALT constraint shows up as FL070/7000. Not sure if this a350 behaviour normal. 

Hi,

The magenta altitude constraints on PFD should only show up when the vertical guidance is managed. So it is not a bug that you see them as blue on ground.

However, the magenta constraints should already appear once SRS mode activates (on take-off), since SRS is a managed vertical mode. As you said, the magenta constraints now activate with CLB mode, so this is something that should be fixed.

I'm not familiar with the A320 systems, but it is highly possible, that the logic with the magenta constraints is different than in the A350.