zlin326m Posted April 6, 2018 Report Posted April 6, 2018 (edited) Hi! During VNAV path descent selecting a new direct to waypoint on the route (simulating a shortcut) has caused my VNAV to go crazy and command a speed of more than 400 kts indicated (460 maybe) and set max thrust during the descent to accelerate to that speed. FMA stayed FMC SPD VNAV PTH The only way for me to reestablish correct function was to revert to another mode and set a CRZ alt in the FMC that is lower than the current altitude. This system behaviour does not match the real aircraft, please have a look into it. Edited April 7, 2018 by Morten Quote
tkyler Posted April 7, 2018 Report Posted April 7, 2018 Thank you for reporting. Changing the route during descents does indeed cause some issues...some of which are due to differences to the way Navigraph and Aerosoft encode some routes differently. We are working on 'normalizing' the data between the two, such that we have a common format to improve the VNAV performance when changing routes mid-flight. We appreciate your patience and sorry for the inconvenience. -tkyler Quote
crisk73 Posted April 7, 2018 Report Posted April 7, 2018 Is it possible to kwow which one of the routing codes between Aerosoft and Navigraph is currently used? I'm asking this because recently I have had some problems with Aerosoft data completely omitting some route waypoints, particularly in the continuous descent procedures newly implemented in the US. Thanks. Quote
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.