No managed climb and descend anymore (since 1.1.0)

[Matthias0412]

Hey there,

since the latest update, managed modes during all flight phases are not working anymore. The dots indicating managed mode (spd, hdg, alt) on the FCU are missing. The plane follows the spd restrictions in climb and descend, but not the alt restrictions anymore.

Am I the only one experiencing this?

[foliainfx]

1 hour ago, Matthias0412 said:

Hey there,

since the latest update, managed modes during all flight phases are not working anymore. The dots indicating managed mode (spd, hdg, alt) on the FCU are missing. The plane follows the spd restrictions in climb and descend, but not the alt restrictions anymore.

Am I the only one experiencing this?

The ini A350 isn't able to comply with altitude restrictions, on the FCU there are no dots indicating managed mode

[frank_m]

If the flight plan is correct, the A350 will of course observe waypoint constraints in terms of both altitude and speed. I have no problems with this, even with the latest release.

Please provide screenshots. If your glareshield shows no dashed lines for speed or heading, then the MCDU is most likely not programmed correctly. Perhaps the PERF setup is missing?

Edited Friday at 03:21 PM by frank_m

[Matthias0412]

Ok, so the A350 in general doesn't have the dots on the fcu indicating managed modes like the A330? Maybe I was confused, because I had flown the Ini A330 the day before... my bad.

I have no screenshots right now but my experience from yesterdays fight in the A350 was as follow:

during the STAR descend procedure into Doha, I observed that the ALT restrictions in the waypoints (e.g. one waypoint stated above FL100 but under FL150) were not taken into account in the A350 descend profile. The plane had "its own descend profile" to be at the optimum Altitude for catching the ILS in the last STAR waypoint...you know what I mean? 

[frank_m]

On 7/12/2025 at 2:08 PM, Matthias0412 said:

Ok, so the A350 in general doesn't have the dots on the fcu indicating managed modes like the A330?

Yes, it has. And if everything is programmed correct, speed and heading are dashed.

 

On 7/12/2025 at 2:08 PM, Matthias0412 said:

during the STAR descend procedure into Doha, I observed that the ALT restrictions in the waypoints (e.g. one waypoint stated above FL100 but under FL150) were not taken into account in the A350 descend profile. The plane had "its own descend profile" to be at the optimum Altitude for catching the ILS in the last STAR waypoint...you know what I mean?

Of course the A350 calculates the descend path in an optimized way, but it observes for sure all constraints.

If you do not have dashed speed and heading displays and the plane is not observing the constraints of the flightplan, then the MCDU is not programmed correctly.

[Xenon341]

Dot on managed seems to be MSN dependent, not every 350 has them (see the videod below, those 2 exemples don't have the dot on managed alt/speed/heading).

 

 

 

Edited Monday at 10:33 AM by Xenon341

[Matthias0412]

23 hours ago, frank_m said:

Yes, it has. And if everything is programmed correct, speed and heading are dashed.

 

Of course the A350 calculates the descend path in an optimized way, but it observes for sure all constraints.

If you do not have dashed speed and heading displays and the plane is not observing the constraints of the flightplan, then the MCDU is not programmed correctly.

I‘m not talking about the three dashes in spd and heading, but rather the dots beside them indicating managed Mode. See picture.

As Xenon341 states, it seems to be MSN dependent but the Ini A350 doesn‘t have them.

So, when flying the STAR in managed Mode, the descend Profile doesn‘t take the alt restrictions into account. In the specific waypoint, where there was a restriction above FL100 but under FL150, the plane was about 3000ft above indicating an optimum descend (Green dot on the PFD).

Edited Monday at 06:22 PM by Matthias0412

[foliainfx]

31 minutes ago, Matthias0412 said:

I‘m not talking about the three dashes in spd and heading, but rather the dots beside them indicating managed Mode. See picture.

As Xenon341 states, it seems to be MSN dependent but the Ini A350 doesn‘t have them.

So, when flying the STAR in managed Mode, the descend Profile doesn‘t take the alt restrictions into account. In the specific waypoint, where there was a restriction above FL100 but under FL150, the plane was about 3000ft above indicating an optimum descend (Green dot on the PFD).

The A350 doesn't have dots to indicate managed, the ini is just simply unable to reliably comply with altitude constraints (VNAV is a mess).

Edited Monday at 06:52 PM by foliainfx

[frank_m]

51 minutes ago, Matthias0412 said:

I‘m not talking about the three dashes in spd and heading, but rather the dots beside them indicating managed Mode. See picture

You are right, there are no dots, but the dashed lines for spd and heading show the managed mode.

And in managed mode the A350 observes all constraints. I did a flight today, and it worked perfectly. In the MFD you see the upper and lower constraints of each waypoint and the descend path observing it.

[foliainfx]

25 minutes ago, frank_m said:

You are right, there are no dots, but the dashed lines for spd and heading show the managed mode.

And in managed mode the A350 observes all constraints. I did a flight today, and it worked perfectly. In the MFD you see the upper and lower constraints of each waypoint and the descend path observing it.

It shows constraints (except missed on the VD, big nono tbh) but rarely properly complies with them and treats them as if you are not in managed mode

[frank_m]

Please show screenshots. I have never observed missed constraints.