This might be a peculiarity with my (somewhat dated) GNS480 - but it's a stellar unit that I love. When I am crossing our local B to or from my home airport, about 50% of the time I'll get vectors through the B and the other 50% I'll get "proceed direct XXX" with XXX being a DME only fix. The DME is about 1/8 of a mile from the associated airport, so the lazy option is I can select "Nearest", "Airport" and then the associated airport. But to be exact, I should be going right to/from the DME.
If I'm building the flight plan (before takeoff/execute), I can select that DME fix (it shows as a waypoint). But once enroute, there's no way to search for waypoints (at least that I can figure). One option I can do is add it in my flight plans from the beginning and just suspend that leg. It seems dumb to do that. My choices when I select "Nearest" are: airport, VOR, NDB, INT, user, airspace, FSS and ARTCC. It's not in any of those.
This could just be a bit of a bug in the way this GNS categorizes waypoints. Anyone have any workarounds?
If I'm building the flight plan (before takeoff/execute), I can select that DME fix (it shows as a waypoint). But once enroute, there's no way to search for waypoints (at least that I can figure). One option I can do is add it in my flight plans from the beginning and just suspend that leg. It seems dumb to do that. My choices when I select "Nearest" are: airport, VOR, NDB, INT, user, airspace, FSS and ARTCC. It's not in any of those.
This could just be a bit of a bug in the way this GNS categorizes waypoints. Anyone have any workarounds?