Hello Folks!
I’m sorta new to posting so I hope I picked the right category.
I’ve been learning to fly the Longitude for the last month or so, and doing short flights from KMSP to my hometown airport of CYWG. I’ve noticed that enroute waypoints included in the World Map flight plan are not showing up in the G5000 (either runway or cold-and-dark start), and this has resulted in ATC getting out of whack because they are expecting me to hit a waypoint that is now missing, and then they don’t like when I start descending because I haven’t passed through the missing waypoint.
Here’s my flight plan setup from the World Map:
- Takeoff runway: KMSP (4)
- Landing runway: CYWG (36)
- SID = KBREW1 ALL
- STAR = PEPNO03 36
- IFR High-Altitude
- World Map: KMSP-GEP-HRBEK-HOMUR-KBREW-FAR-LITNA-KENBI-PEPNO-IPSIV-NOXAM-VITIL-CYWG
In the G5000, I consistently get this on a handful of repro attempts: KMSP-GEP-HRBEK-HOMUR-KBREW-FAR-PEPNO-NOXAM-IPSIV-NOXAM-VITIL-CYWG
So, not only am I missing two enroute waypoints (LITNA & KENBI), I have NOXAM in both my approach and arrival, resulting in what I think is an unnecessary loop?
What I’ve started to do is add those two missing enroute waypoints, and remove the first NOXAM listed. After that, I have no issues with ATC the whole way through.
I understand that there are quite a few criticisms toward World Map flight planning, as well as ATC. Those two things seem to be in-sync in this scenario though. It’s the G5000 that gets… de-sync’d somehow?
Anywho, just wondering if I’m maybe doing something incorrectly that is causing this, or if this is a known ‘quirk’ that sometimes occurs. I’ll note that I’ve flown into quite a few other airports (some with Longitude and many more with TBM 930), and it’s sorta rare that I run into ATC/Flight Plan issues. This was the first occasion though that I finally spent the time to try and figure out what was happening.
Cheers.
