I believe the default AIRAC for MSFS 2024 is missing some waypoints around KTEB. I was trying to do a route in a bizjet that uses the default data rather than an addon specific one. The only flight plans Simbrief will generate for my selected route won’t load in them. This is for current AIRAC 2607, and one of the routes in question is this:
KTEB**/24 N0432F430 DCT LANNA J48 CSN/N0447F400 J48 MOL/N0433F430 DCT FLASK DCT COREX DCT BURGG DCT IRQ DCT CYNTA SHFTY6 KMKY/**35
See attached screenshots. The Garmin can’t find LANNA. There is also another route that uses the COL VOR and waypoint WHITE after that, and the Garmin can’t find them either. I also attached a screenshot of the TEB4 SID that shows those waypoints. I’ve tried uninstalling and reinstalling the AIRAC to no avail. Also of note is these routes load fine in the Fenix A320 and the PMDG 737. I assume this is because those use addon specific data rather than the default.
Hi,
Thanks for your report. It seems there’s something wrong with your MSFS system, as I can´t reproduce it. I have checked our source as well as the MSFS2024 database, and all three example waypoints are included:
The waypoints are included and available (you confirmed this with PMDG and Fenix, too). So something seems not 100% correct with your MSFS2024 installation. Sorry about that.
Odd, I tried it with 3 different planes, one being a default plane (Cessna Citation) that have the style GPS in my screenshots and they all did that. I did load into the Pilatus PC-12 with the WT GNS 530 and LANNA did come up there so now I’m even more confused as to why it’s just this particular GPS having the issue. Any thoughts as to what my next steps would be since it seems localized to that specific style GPS? Can you test in the Cessna Citation and see if it’s broken for you too? I noticed you used different Garmins to test with.
I’m having this same problem but Navigraph just say delete everything in your community folder and it’ll be fine because they apparently have never used scenery before…
Your comment, “they apparently have never used scenery before,” is neither helpful nor accurate.
If you look through the forum, you will find a large number of issues caused by add-on sceneries that have not been updated for the latest MSFS versions.
This can manifest with weird errors not obvious to users and support staff. Often removing these sceneries in bulk resolves the issue, and adding them back one by one helps determine the scenery causing the error. Yes, it is time-consuming, but the issue is not of Navigraph’s making.
