Nav data discrepancies in Fenix A320 vs Navigraph

[RejectedCoast8]

I’ve done everything I can find instructions for in terms of making sure my nav data is current in MSFS / Fenix, including having the latest Fenix software, and running Navigraph Hub update (for navdata in and outside of MSFS). But for some reason I keep finding between Navigraph charts (including via Simbrief routes) and nav data in the Fenix A320 MCDU including missing STARs, transition waypoints, or just non existent approaches.

One example is Vail Eagle (KEGE). In Navigraph it lists LDA and RNAV X/YZ approches for runway 25. But in the Fenix A320 MCDU, the options for KEGE approaches include ILS, LOC, and RNAV D/X/Y/Z for runway 25 as well as an RNAV for runway 7. There definitely is no precision approach at KEGE for any runway, and runway 7 isn’t used for landings.

Other aircraft in the sim including the FBW A32NX as well as the Inibuilds A320 Neo V2 match Navigraph, they do not show any such discrepancies.

Anyone run into this recently? It makes it hard to enjoy the Fenix, which is otherwise an incredible product.

[Marklar666]

@RejectedCoast8

But in the Fenix A320 MCDU, the options for KEGE approaches include ILS, LOC, and RNAV D/X/Y/Z for runway 25

I can see ILS and LOC approaches in Navigraph app. Ther are no charts but approaches are on the list.

[Bandit1978SE]

The airport NOTAMs show an issue with the LOC/DME and the runway directional aid. And there is a special ILS approach, but it is limited as to who can use it.

[RejectedCoast8]

Thanks to both of you. Turns out there were some issues with the nav data cycles in my Fenix install (one page in the MCDU showed current cycle, another showed old one), but the bigger problem was obviously me being clueless about charts vs procs in Navigraph, and what LDA abd RNAV D approaches actually mean (ILS with offset and circling, respectively).

Time to do some more learning about IFR procedures in general.