Hi Mats, Just tried the approach again. Here goes: I preflighted completely and took off with everything done according to the manuals and check lists. Five miles before reaching the TOD, I got the RESET MCP ALT message and reset the MCP ALT to 15000 (this was done on purpose to see if that could be the culprit as you hinted at). Upon reaching TOD, the a/c started the decend nicely, and I noted the FMA indications: FMC SPD|LNAV|VNAV PTH, altough the thrust mode flipped a bit between FMC SPD and ARM. As I crossed LOGAN (at FL250 as required), the FMA was indicating FMC SPD|LNAV|VNAV PTH but it seemed that it spent most effort on bringing up the speed and as before, the plane kept deviating from the decend path (that is, after LOGAN the a/c only decended at a few hundred feet per minute). When I recycled the VNAV button, the a/c started to race to catch up on the deviation and consequently I got an overspeed disconnect. I checked my settings and I do indeed have VNAV ALT checked (not that it really matters as I had the MCP set lower than the hard alt constraint). Can this be caused by the STAR that I am using?Thanks in advance, :-waveBoazEKCH

LOL I did the same today as you and got the same thing!! :D

>Can this be caused by the STAR that I am using?Probably not. But you can never be sure. Can you attach or mail me the file and I'll check it out. Another thing that hit me as being a cause. Are you running the 600/700 v1.3 or have you upgraded with the 800/900?My try was with the 800/900. And I didn't enter the FL250 restriction at LOGAN. Will try it immediately with the 600/700 v1.3 only.Cheers,

Hi Mats, I am running the -800 version. Not sure if I have updated to v1.3... What is the easiest way to check?PS. Edit: Attached the EGLL SIDs and STARs I was using. I flew the LAM3A ILS27R.BoazEKCH

Version 1.3 is the latest revision for 600/700. The 800/900 is version 1.0 but have the interrim patch that could be applied. SHouldn't make a difference here though.I don't think the 800/900 will install if you didn't have 600/700 v1.3 already.Something is fishy with your -800! ;-) I'll try the LOGAN restriction as well immediately.

Aye, I wouldn't be surprised. I also have problems with the flaps starting to drop as soon as I cut the electrical hydraulic system as part of the shut down and secure check list... Anyway, I now installed the interim update and will fly again to see if that makes a difference.Thanks,BoazEKCH

GentsAfter some testing I have managed to get the same behaviour as you have reported. After passing a waypoint with a hard altitude restriction the aircraft reverts to a shallow dive set to 500 fpm. The aircraft will thus get way above the path. All announciations look normal though. This will need further investigations and a report will be filed to the dev team. Thanks for bringing it up. We'll look into this one! :-wave

Hi Mats, Thanks go to you too for the patient explanations. Besides, it is always nice to know that I not insane :-)Thanks :-waveBoazEKCHEdit: Just forgot to mention, but I did run the interim update just to be sure. It still exhibits the same behaviour.