Here I am following a STAR to EDDL 23L. Every single WPT has 220 kt constraint, yet the aircraft doesn't care and places its managed target at 250. Before I got down to FL100, it was even faster than 250.

I have noticed things like this happening when changing approaches or arrivals in the flight plan while enroute. It gets corrupted somehow, like old route data is left, and the aircraft ignores both the lateral and vertical profiles, ignores altitude and speed constraints, and so on.

15 hours ago, Gungnir said:

Here I am following a STAR to EDDL 23L. Every single WPT has 220 kt constraint, yet the aircraft doesn't care and places its managed target at 250. Before I got down to FL100, it was even faster than 250.

I have noticed things like this happening when changing approaches or arrivals in the flight plan while enroute. It gets corrupted somehow, like old route data is left, and the aircraft ignores both the lateral and vertical profiles, ignores altitude and speed constraints, and so on.

Hi,

Thanks for your report. Looking at your MCDU, it looks like the *220 sped restriction is not being applied until the next waypoint.

Are you indicating that it should have also been applied prior to what I'm seeing on the MCDU?

Thanks!