An updated STAR now requires an altitude between 16000 and 14000 at a particular waypoint. Is it possible to enforce this (as written) in the FMC or a way of using /16000B and /14000A together?

 

In this descent, using only the "above" would work most of the time but an ATC "hold" or manual intervention prior to the waypoint could change the descent profile.

 

Thanks in advance for any help :-)

As I think the FMC can handle such a restriction if it is part of the SID/STAR (and also in the database) however as a pilot you can't enter such a restriction.

If you see that you won't be within the restriction take over and manually controll the descent with VS or LVL change. :wink:

Thanks John .. I think you're right. I've tried to be creative but nothing works. I think I do remember seeing it on the FMC from a published SID/STAR so maybe you're right. okay if in the database, but not pilot-enterable.

 

I found one in the FMC database. KMEM 18C arrival, MASHH1 STAR, VUZ transition .. waypoint FLOND is 210/9000 11000.

We just had a discussion on this in another thread, Ryan has said that he believes this is not possible in the real plane, however I've discovered that in the NGX it is possible to manually enter it.

 

Enter 14000A16000B just like that, no spaces. Then line select it where you need it on the right column.

Thanks for the heads-up on this one Steve. Useful to know.

Enter 14000A16000B just like that, no spaces. Then line select it where you need it on the right column.

 

Nice find, Steven. Thanks for this.