thank you so much for your product(navigraph chart) but I have a problem with this.
In spite of having a yearly subscription and buying that, the nav database for some airports which I am flying in my country is not updated and there are a lot of differences between real word charts of jeppesen and your product(navigraph chart). in such a way that when I am flying on msfs2020, the FMS nav data bse is not consistent(matched) with the navigraph chart.
I would like to know why it is not based on the real world!!! and appreciate it if you make it near the real world based on reality. i you want clarification, i can show you differences
Firstly, make sure that you are signing into the correct account. Sign out of Navigraph Hub and sign back in again to make sure you are logged into the correct subscribed account.
For instance in app chart (OIMM) mashhad iran VOR Y 13 L, chart index (13-2), after point MSD there is a point in the name of (D11.0), while in FMS nav data , this point is not published . Another difference is , in the chart there is VOR Y 13L , while in the FMS nav data base there is VDM 13LY (vOR DME 13LY).
There are alot of diffrences like this , in many airports For exmple OIKB,OIBK and …
Hi,
Thanks for the examples, there is no mismatch …
You should not compare the charts 1:1 with the data, as the data are coded according to specific rules and regulations. The result of these rules and regulations is the flight paths and the leg pages in the FMC.
To your examples:
There are two outbound D11 waypoints, one for CAT A&B and one for CAT C&D. Also, you don´t see any idents, like the following D11 [CD13L]. The D11 is part of the approach transition and is internally coded as FD (= track from a fix to a DME distance).
So it is necessary, yes, that is the reason why you see it on the charts too (in case you want/need to fly this manually too). Therefore, some waypoints (in general, without any ident) are only shown on the charts but not directly as their own leg in the FMC. The legs are coded for the flight path …
Your second one it´s nearly the same answer:
The charts show only VOR, NDB, ILS, … approaches, but in the FMC, you must code this more specifically - a VOR approach can be a VOR or a VOR DME approach. You can identify it on the charts, but not in the FMC, when you would have VORxx and VORxx … which one is now the VOR and which one the VORDME approach? Therefore, again, coding rules, how the approaches are “called” to identify the correct one …
So, no mismatch - only another “view” and a few things behind to make all these legs flyable
