Descend SPD/ALT restriction

[C2615]

When doing managed descend, I noticed both speed and altitude restriction are not well followed by FMS

speed: Say I have STAR with point WAP1, WAP2, WAP3, on WAP2, there is 210kts speed restriction, the airplane with speed knob in FMS mode will slow to 210 on WAP2, but after WAP2, it will speed up to 240 (or even faster if above FL100),  and even if I also put 210 on WAP3, the airplane will speed up after WAP2, then slow down before WAP3, even when there is less than 10nm between them.

alt: Any "Above" restriction will be treat as "At", say WAP1 and WAP2 both have 8000A and WAP3 have 8000, the airplane will just down to 8000' right at WAP1 and stay there until WAP3.

[pablo636]

I can confirm the speed issues. Everytime there is a speed restriction or if you manually put a speed restriction once the waypoint is passed the plane speed up to 240kts despite the restriction is active for all the consequent waypoints.

For the altitude restrictions, it act sometimes as you described sometime not, I can't really say what is wrong here.

[sebgnoblett@gmail.com]

I have certainly noticed the aircraft treating any altitude restriction that contains an 'above' or 'below' as an 'at' as well, really annoying that it wont follow a good VNAV profile because of this. Seems to be more prevalent on a descent.