Using 'Travel To' feature - buggy

I have found that the 'Travel To' to a later flight segment function on the toolbar e.g. Cruise, Descent, Approach etc really messes up the waypoints and autopilot system. I was able to test and retest this several times using the Schipol to London route. If I flew the whole route either in real time or using the change sim speed feature then the whole flight would work perfectly and the plane would use ILS and fly down the glide scope perfectly.

If on the same flight plan I 'Travel to' the Descent phase then the plane would sort of pick up the ILS but start overcorrecting as it came down the glide scope - >3000 ft descent speed, fly past the purple triangle level and then >3000ft ascent speed. I also had similar issues flying to Entebbe where the plane would ignore half the waypoints and fly straight to the one just before landing. When I change to not using 'Travel to' then all operated absoloutely perfectly, This was using the A320 Flybywire. 'Travel To' also had the nasty feature of setting the plane in a mode way out of line with what it would be in at the point you had 'Travel To' in the flight. e.g. 'Travel To' Descent and the plane is at about 1/3 throttle not in autopilot, auto throttle off, flying at 170 but with the altitude knob at 5000ft. So it was normally a mad dash to get the plane stable at 170 before continuing the descent. This element did not seem to effect the complete mess it made of final approach.

I tried both ways of speeding up the flight a few times and the 'Travel To' option always messed up the subsequent phases and the 'Increase sim speed; temporarily always worked perfectly. My advice is to keep away from 'Travel To'.

CJ