Jump to content

Issues with "below X, above Y" altitude constraints

Eddie

By Eddie
in Bug Reports

 Share

Recommended Posts

Eddie Newbie

Eddie

Posted
Posted

Observed with version 1.2 of the 737-300, Navigraph AIRAC 1706, and X-Plane 11.02rc1. The FMC will interpret a "below X, above Y" altitude constraint as "above X", which will lead to a violation if not manually corrected. I observed this on the HYDRR1 arrival into Phoenix Sky Harbour (KPHX), and have attached both the procedure chart and the FMC's interpretation of the arrival on the CDU.

00322HYDRR_C.PDF

ixegbug.PNG

mmerelles Newbie

mmerelles

Posted
Posted

yes, this is a known limitation of current vnav implementation.

anytime you see a waypoint on a SID/STAR having double altitude constrain you need to go to the legs page and adjust the constrain altitude manually.

 

vnav will be reworked entirely as said by the developers

  • Upvote 1

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
 Share
Go to topic listing

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...