Eddie Posted July 12, 2017 Report Share Posted July 12, 2017 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 Quote Link to comment Share on other sites More sharing options...
mmerelles Posted July 12, 2017 Report Share Posted July 12, 2017 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 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.