Support overload. We are currently seeing 65% more demand for support then we normally see. We can only assume this is because more people are at home due to the corona crises. Our complete support staff is online and they are working flat out, but it will take some days before we can scale up resources. Please be patient.

Jump to content
Sign in to follow this  
indianbhaji

Altitude Restriction on Descent isn't changing

Recommended Posts

Hi there, I've noticed something a bit odd with the FMS.

Here, I am on the REDFA1A arrival into Schiphol. At present, there is a restriction at SUGOL; at SUGOL you must be between FL100 and FL70.

1384727490_DesktopScreenshot2018_07.17-14_59_28_23.thumb.png.5c610539e1f6e3a1c96a5859dcaeb84e.png

 

I've decided that I want to be FL70 level at SUGOL, so I type '7000' into the scratchpad. I click on the RSK3 to replace the current restriction which is already in there. Here's the aftermath; the ALT CSTR still displays FL070-FL100, despite the fact that I replaced the ALT CSTR with 7000.

1125777576_DesktopScreenshot2018_07.17-14_59_35_04.thumb.png.3d612f9e1715d1a506aca5433cb8880b.png

 

The bug here is that the ALT CSTR hasn't visually changed - if I go to the F-PLN page, I can see that FL070 at SUGOL is confirmed/predicted, and the VNAV is descending accordingly to be FL070 at SUGOL.

604144858_DesktopScreenshot2018_07.17-15_07_10_32.thumb.png.cd418b8cfc174a432a4d108b923cfd29.png

 

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×
×
  • Create New...