Hi MatsThe VNKT SIDSTAR file is now available for download from the Navdata site (http://www.navdata.at/php/sidstar/sidstar.php). There is some text at the beginning of the file that should be read!Feel free to try it. Problem still remains.CheersNick Kidd:)

NickJust tried a departure from VNKT RWY20 with your SID/STAR file. Very interesting procedures to say the least. However I never managed to replicate what you have described. It is a bumpy ride down the runway but it rotates fine. And keeps N1 up at the desired level and keeps the speed to 175 knots, later 190. Started with the default Cessna 172 with engines running. Changed to 737-800 default paint and loaded fuel as per your post. Also loaded cargo and pax, but with the fuel load and cargo/pax I get a gross weight of 62 tonnes not 42 as you write.All in all. Did you install the latest patch? Have you done a torough pre-flight check to cross check all settings? Everyting entered in the FMC?Looks like something else than the thinng you suspect I'm afraid...Cheers,

Thanks MatsI still get the problem and I will discover what is happening here.I have noticed that the problem NEVER occurs on the first take off from VNKT (Not yet sure if the location is significant) which suggests that perhaps something is not being reset from a previous departure (bearing in mind the problem occurs when repeatedly resetting to fly a SID).One thing I have been mulling is that the wether loaded is the same each time - and I haven't been setting QNH before flying the procedures which is giving a 200 ft error. It may be significant but too early to say at this time. I don't know the mode change parameters of the FMC but if pressure altitude is a factor in the algorithm .....I will of course let you knowNick:)

"and I haven't been setting QNH before flying the procedures which is giving a 200 ft error. It may be significant but too early to say at this time. I don't know the mode change parameters of the FMC but if pressure altitude is a factor in the algorithm ....."Some FMC/APFD logic is based on Radio Altitude, but other logic is based on baro altitude. Things like thrust reduction height is, as I understand it, based on a pressure-altitude a certain height above a pressure-altitude value sampled during the takeoff roll (i.e. it is independent of pilot baro settings). It is basically the equivalent of Radio Altitude. However, things like altitude restrictions will be based on altitudes affected by pilot baro settings.Hope this makes sense.Cheers.Ian.(Edit) E.g. If your altimeter is reading 200' below what it should be (because of your error), and you've set your thrust reduction height at 3000' and an altitude restriction at 3000', the aircraft will reduce thrust at 2800' (according to your PFD) and level off at 3000' (according to your PFD).

MatsFurther info on this. It isn't anything to do with QNH or airport or altitude or hardware etcThis only occurs following "resetting" of the flight. It never happens on the first flight. If I exit FS9 and start a new flight/load a previous flight, the problem never occurs.It's something that isn't reset by FS9 or NG. Exactly the same today - if I reset flight, twice MCP SPD was commanded before any rotation had occurred. Rapid switching off of Autothrottle and application of full throttle gets us away just about.In this way, it isn't a problem - except when I'm trying to refine SIDS when it's a bit of a pain to restart FS9 each time.Quite often following a restart, the warning klaxon sounds at rotation also - yet there is no annunication of a problem anywhere (including the master warning lamp). It lasts for a couple of seconds and then stops. All engine and OHP indications are normal. I can't help but wonder if this is related somehow to the MCP SPD. Once again, this will never happen on a new/loaded flight - only following reset.More info to follow as I discover it :)Thanks