Hopefully I can finally get some info on this. The manual is silent. Sometimes the speed rest I enter 240/10000 on the descent page(and sometimes climb page) dissapears and is unable to be restored as invalid entry or just simply dissapears after I hit enter. Seems to be legs constraints but I cannot figure out how they conflict because sometimes this works but most of the time it does not. N one has been able to figure it out and so I always have to use speed intervene. No biggie I just want to find out what I am doing wrong or if it is a bug. This was not happening before sp1.Thanks

On the CLB page you mean. When you cross 10000 (or whatever the restriction altitude is) it clears. You cannot enter another altitude after this until the FMC resets upon landing. That's the way it works.

No, 90% of the time when I try to input this after setting up my route it will not let me, and it is blank to begin with. Whenever it is blank to begin with I cannot make the input. Either it says invalid entry or as soon as I line select it to the entry it goes away. On the rare event lately when I get to the climb or descent page and the default 250/10000 is showing then I can input anything I want like 230/10000 for example. It is that it mysteriously dissapears more often than not and when it does it will not let me put anything there in the way of speed/altitude. This was not happening before and I was flying the same STARS/transitions and approaches. Very peculiar.All the other methods for entering speed and altitude restrictions like in the LEGS page work fine. This is just the CLM and DES pages since, it seems, SP1.Thanks

Marc !Why not just enter it on the legs page ?That is normally where you add/delete/change speed and altitude restrictions.Fred.

Because the legs page is for a speed restriction at a point and the descent page is for a speed restriction at an altitude irrespective of a point. To comply with 250 below 10000 is the objective and not 250 at a waypoint in this case. I guess I am just anal. I can allways use speed intervene or level change but the fact that this worked before and does not now is bugging me. It is also sometimes nice and very helpfull to use this feature to automate this deceleration during one of the highest workload times of the flight where this usually comes in between any legs waypoint.

I understand you now.The speed restriction you are talking about 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/15000 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.

Yes, but it does not work. This is my problemma. I think I am doing everything right. And it worked before SP1 allways.

Yes, but it does not work. This is my problemma. I think I am doing everything right. And it worked before SP1 allways.

Hi Marc.I have just tried it now and was able to change both the Climb and Descent page restrictions no problem.I am using SP1 too.Fred.

I noticed in your very first post that you said about hitting the enter key ?Do you mean the enter key on the keyboard or the execute key on the CDU ?Fred.

Is this it? FCOMv2 pp 11.41.8

Note:If the FMC default speed restriction is overwritten, it will be deleted and not return after the overwrite condition passes (e.g. the default of 250/10000 is overwritten to 230/3000, after 3000 feet is passed there will be no speed restriction and VNAV will accelerate to the unrestricted climb speed).

I mean the execute key, sorry. I read that section in the FCOM thank you. This is not what I meant though. I all ways go into the VNAV pages after I am done with the route and before SP1 it used to be that I would all ways see the default 250/10000 and 240/10000 for descent respectively. Lately during some pre-flights I either go into those pages and either see it missing (usually) or there. If it is there already there usually is no need to change it and it works. If I am flying outside the US then I change it and this is when it will not take. Either "invalid entry" upon execute or just a strait up blank to ---/-----. Most of the time I first get to these pages this area will be ---/----- or blank. This is very strange because it was not doing this before. In this case I try putting a restriction in there like 250/10000 and get what I was refering to above, either an "invalid entry" or it will take and the execute light will illuminate and upon hitting the execute key the restriction goes immediately back to ---/-----. I think there is something wrong.

I would do a complete uninstall/Reinstall.Just to be certain.Fred.

Nothing to do with the transition altitude being lower outside US and the FMC thinks you enter a FL instead of an alt? I know, normally the FMC will pick that up automatically.Just a thought.Bert Van Bulck

No, because it does not work in the US either with the entry 3000 or 10000 vs. 030 or 100. Nothing will actually go into that area anymore.I know allot of people will uninstall/reinstall at the drop of a hat but this is usually the last thing I do following the KISS principal. It is almost always something more simple like pilot error. I am open to it being pilot error, I just do not think it is because my procedures are the same as before. Unless they made this procedure more realistic and I am doing something wrong. I am at a loss for what it could be as I gaze into the legs page constraints. Even if all those altitudes and speeds are FMS created based on a VNAV path being drawn from cruise altitude to the TDZ and not pilot or database hard speeds/altitudes I still cannot get the climb/descent page constraints to work. However, one of my flights from Zurich to the Azores had no sids or stars or any en route way points and both pages worked this one time. I had set the FMS up with the departure runway and the ILS 18 at LPAZ and had it going direct the IAF. I had hard constraints in the legs page for this ILS but no other waypoints in between and all worked well.

Just right now I am enroute from KLGA to KSFO with the Mod3.mod.oal STAR and the ILS 28L from Divac and 7000A at Divak as my initial constraint. As I try to put 250/10000 into the blank Descent page it will take it and the Exec light will illuminate but when I push it it dissapears.