The beauty of using Navigraph data is that you can also inject it into LNM and most other popular 3rd party tools. That way, your sim and tools are playing with the same Jeppesen data set and all AIRAC cycles are correct, so there are no discrepencies. You don’t plan a flight on Simbrief, only to find that part of it doesn’t work in LNM and most of the waypoints don’t exist in MSFS.
A French company partnering with another French company is what it comes down to.
Now, from what I understand (please someone correct me if I’m wrong), Navblue is owned by Airbus (well known fact) and in the real world they provide data to European airlines for Eurasian routes. All other parts of the world, including airlines flying Airbus planes, use Jeppesen charts, (owned by Boeing). So that would mean they have awesome coverage of their part of the world, but the rest of the world’s data is a bit spotty. And that’s likely why we’re seeing such incomplete or incorrect data in MSFS using the stock nav data.
That’s my rudimentary understanding of it from random stuff I’ve read over the last months. I could be horribly wrong as I’m definitely no expert on this subject. And if I am, please let me know. I don’t want to be propagating incorrect information.
And it’s not just missing approaches, waypoints, etc. The Navblue data is seriously flawed in North America. There’s one nearby airport that if I follow the RNAV down (with stock data), it will land me 1 mile past the end of the runway into Lake Ontario. The database also contains ILS approaches to runways that no longer exist as well. One particular example I’ve encountered is an airport near my place that if you follow the ILS 24 down, it will land you on a taxiway to the left of the runway because 10 years ago they built a new runway 24, turning the old runway into a taxiway. The Navblue data still has the old runway. So that data is a decade out of date.
I started using Navigraph back in October and haven’t encountered any non self-inflicted nav issues since.