Hi and Merry Christmas,I installed sp1b and it worked for 2 flights. That is my 240/10000 on my climb and descent page for constraints. But now such is my luck on my 3rd flight on climbout the aircraft tried to break the speed limit below 100 and sure enough the constraint is gone again. I tried to put it back in there and when I do I get an Exec prompt but when I press Execute it goes away. This is happening on the descent page as well. I can just as easiliy put in a constraint at a fix in the legs page but this is driving me nuts as to why this is happening and I really want to get it figured out. Unless anyone smarter than I can figure this out I am going to assume it is a bug that hopefully will be fixed in the next sp. So far this is my 2nd post on the issue and no ideas. There are no conflicting legs constraints either.Any help much appreciated.

are you always starting from the same panel config? anything else different between the first two flights and the third? without knowing more about exactly what the plane is doing when the restriction disappears it's hard to do anything but speculate. you're basically saying that the speed bug resets before you reach 10,000 feet, while you are in vnav? what altitude does it reset at, what do the autopilot modes say they are doing...?sorry to say i don't really have much of an idea, i've never had any issues with the alt/spd restriction... in fact i don't think i've ever had to touch it since the default entry is usually fine and she always seems to fly it right...? unfortunately that may be why you aren't gettin many replies i would guess a lot of other people not seeing any issue here either.. good luck!cheers,-andy crosby

Are you getting your route from an external program ?Fred.

Are you getting your route from an external program ?Fred.

Hi.I use FS Commander and I found sometimes I have same issue. What is the relation between external program and such issues? Constraint is entered in FMC and it should follow in any way. I am just trying to find a solution as well.Thx

I have seen this bug, and I believe it's related to entering a step climb altitude in the FMC. Whenever I enter an altitude into the step climb page, I instantly lose the 10,000ft speed restrictions on climb and descent pages, easily reproducible.I remember in the past the autopilot blasting past the 250kt speed limit below 10,000 feet on climb, very annoying. Until PMDG acknowledges this glitch, I refuse to use the step climb prediction facility in the FMC, instead I use it during preflight to make a note of when I can expect to climb to the higher altitude, but that is it.

Hi.I use FS Commander and I found sometimes I have same issue. What is the relation between external program and such issues? Constraint is entered in FMC and it should follow in any way. I am just trying to find a solution as well.Thx

Hi Ed.RSR posted this at the top of the forum. It's part of the SP1 update info.*****************************************************************************************************************************************************************I want to direct everyone's attention to the first item listed here, as this is extremely important. Most all the applications that have been created to export .RTE files for use with the PMDG line of products produce RTE files that include your runway/SID and STAR selections. After hundreds and hundreds of hours of research, we have discovered that saving files in this manner is not only highly unrealistic, but creates problems for the FMS when it comes to correctly parsing/computing/interpolating performance along the flight path. For this reason, beginning with SP1b, the FMS will disregard any runway or SID/STAR information contained in a RTE file *unless that RTE file was created by the FMS itself.*This should eliminate a significant number of FMS and LNAV/VNAV performance issues that we have been investigating since August.******************************************************************************************************************************************************************Fred.

Hi Ed.RSR posted this at the top of the forum. It's part of the SP1 update info.*****************************************************************************************************************************************************************I want to direct everyone's attention to the first item listed here, as this is extremely important. Most all the applications that have been created to export .RTE files for use with the PMDG line of products produce RTE files that include your runway/SID and STAR selections. After hundreds and hundreds of hours of research, we have discovered that saving files in this manner is not only highly unrealistic, but creates problems for the FMS when it comes to correctly parsing/computing/interpolating performance along the flight path. For this reason, beginning with SP1b, the FMS will disregard any runway or SID/STAR information contained in a RTE file *unless that RTE file was created by the FMS itself.*This should eliminate a significant number of FMS and LNAV/VNAV performance issues that we have been investigating since August.******************************************************************************************************************************************************************Fred.

Hi again. Thanks for the response.I saw that topic and that is why I save just the rouite without SID/STARs and then I ship it to FMC, and I pick SID/STARs inside of FMC, not in FS Commander. Will have to take a look again what's wrong. FS commander really save time transfering route to FMC. :(

Hi again. Thanks for the response.I saw that topic and that is why I save just the rouite without SID/STARs and then I ship it to FMC, and I pick SID/STARs inside of FMC, not in FS Commander. Will have to take a look again what's wrong. FS commander really save time transfering route to FMC. :(

No problem. Always glad if I can be of help.The speed restriction comes from the airport database. It will be entered when you select a sid or star.If none is found, the FMC automatically enters 250/10000 in the climb page.You could of course change this to lets say 240/12000 or use the delete key to remove it completely.( don't forget to execute the modification !!! )The Climb, Cruise and Descent pages are only used with VNAV.Fred.