DUAT

Steve,
I thought that for /G there still needed to be a vor or other nav fix
in the route. I generally draw a line between the start AP and the
destination and then add a vor in the middle that doesn't increase the
distance by much. Gices me two nav checks for redundancy, too. Are
you saying that /g can be diredt between APs over several hundred miles
with no other fixs?

Chuck

"Chuck" wrote in message
oups.com...

I thought that for /G there still needed to be a vor or other nav fix
in the route. I generally draw a line between the start AP and the
destination and then add a vor in the middle that doesn't increase the
distance by much. Gices me two nav checks for redundancy, too. Are
you saying that /g can be diredt between APs over several hundred miles
with no other fixs?


You don't even have to be /G. IFR flight off-airways and beyond normal
navaid distance/altitude limits just requires radar monitoring by ATC. Now,
if you're going to a rather small airport hundreds of miles away there may
be a flight data processing problem. The NAS computer serving the departure
airport may not know where the destination airport is. You can get around
that by filing a few waypoints based on H-class VORs that fall on your
route, that will also help ATC visualize the route. Or you can just file
the destination coordinates as an intermediate fix.

"Steven P. McNicoll" wrote in message =
link.net...
=20
"Chuck" wrote in message
oups.com...

I thought that for /G there still needed to be a vor or other nav fix
in the route. I generally draw a line between the start AP and the
destination and then add a vor in the middle that doesn't increase =
the
distance by much. Gices me two nav checks for redundancy, too. Are
you saying that /g can be diredt between APs over several hundred =
miles
with no other fixs?

=20
You don't even have to be /G. IFR flight off-airways and beyond =
normal=20
navaid distance/altitude limits just requires radar monitoring by ATC. =
Now,=20
if you're going to a rather small airport hundreds of miles away there =
may=20
be a flight data processing problem. The NAS computer serving the =
departure=20
airport may not know where the destination airport is. You can get =
around=20
that by filing a few waypoints based on H-class VORs that fall on your =

route, that will also help ATC visualize the route. Or you can just =
file=20
the destination coordinates as an intermediate fix.=20


Sometimes, but not always, when I file direct to a distant point,
even an H-class VOR, I'll be cleared first to a nearby fix, then as =
filed.
I usually make a note of that nearby fix, and include it in subsequent =
trips.
I figure the departure controllers prefer that, and it's OK by me.