Jump to content

Recommended Posts

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

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

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
  • Recently Browsing   0 members

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