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!

2 hours ago, iniKyle said:

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!

Hi, thanks for looking at this.

If you look at the ND, the waypoint I just overflew, DL426, also has 220 kts in magenta. That means the aircraft should have slowed well before passing DL426. The FMS PERF page on the MCDU (left) also says, if I am interpreting it correctly, that it's in managed speed mode with a 220 kt constraint. Also, while I can't 100% swear it now, I am pretty sure previous waypoints also had this restriction.

The main point is this: There is a general issue with updating the flightplan with new runways/approaches/arrivals where the aircraft will plot crazy courses, fly off course, ignore vertical profiles and restrictions. I think anyone who flies this aircraft regularly enough would attest to that. It has happened to me at least 10 times.

2 minutes ago, Gungnir said:

Hi, thanks for looking at this.

If you look at the ND, the waypoint I just overflew, DL426, also has 220 kts in magenta. That means the aircraft should have slowed well before passing DL426. The FMS PERF page on the MCDU (left) also says, if I am interpreting it correctly, that it's in managed speed mode with a 220 kt constraint. Also, while I can't 100% swear it now, I am pretty sure previous waypoints also had this restriction.

The main point is this: There is a general issue with updating the flightplan with new runways/approaches/arrivals where the aircraft will plot crazy courses, fly off course, ignore vertical profiles and restrictions. I think anyone who flies this aircraft regularly enough would attest to that. It has happened to me at least 10 times.

Thanks for the clarification. Will forward this to the team for further review!

Appreciate your time 🙂