vnav pro3 versus aircraft fmc
2 posters
Page 1 of 1
vnav pro3 versus aircraft fmc
hello, this is my first post. i have had a look at your explanatory video and the processes therein, and i am curious as to why there should be differences in the vnav pro and the data in the aircraft fmc. surely these differences must be minimal as both items are using the same airac with TPs as per navigraph. hope you understand my query. gigabyte.
gigabyte- Posts : 2
Join date : 2009-07-06
vnav pro3 versus aircraft fmc
There are 2 type of differences that may appear:
1. Caused by using different months of AIRAC cycles on the plane and in TuneVNAV.
2. Some missing waypoint names in TuneVNAV compared with the one from the plane's FMC.
Here is the explanation for this second issue:
This issue is caused by the fact that TuneVNAV Pro3 considers for its calculations ONLY the waypoints with restrictions (altitude or speed restrictions). The other waypoints are "buffer" waypoints (where the speed and the altitude can freely change) so they are only important for the LNAV part of the flight. Therefore there is no need to make any changes to these waypoints in the FMC.
Hope this answer helps.
Regards,
Valerian E Partenie
TuneVNAV Author
1. Caused by using different months of AIRAC cycles on the plane and in TuneVNAV.
2. Some missing waypoint names in TuneVNAV compared with the one from the plane's FMC.
Here is the explanation for this second issue:
This issue is caused by the fact that TuneVNAV Pro3 considers for its calculations ONLY the waypoints with restrictions (altitude or speed restrictions). The other waypoints are "buffer" waypoints (where the speed and the altitude can freely change) so they are only important for the LNAV part of the flight. Therefore there is no need to make any changes to these waypoints in the FMC.
Hope this answer helps.
Regards,
Valerian E Partenie
TuneVNAV Author
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum
|
|