"Snowbird" wrote in message
om...
I think two of Don's concerns with lat-longs a
1) they provide ATC with no information about what direction you're
headed, so coordination with other facilities is difficult. In fact,
initial separation is problematic.
Initial separation is never problematic, that's what vectors are for.
2) ATC apparently has no means to verify a lat-long against an
airport identifier or navaid to ensure that the lat-long was entered
correctly. Serious lack of backup or verification redundancy.
I don't care if you entered the lat/lon correctly. Only the last
controller cares.
My suggested solution for filing GPS direct is:
1) provide a VOR radial-distance waypoint which will be recognized --
one w/in the facility's boundry is a good bet. That way ATC knows
which direction you're headed from a waypoint which will be in their
host computer, and coordination is easier for them
Doesn't matter to ATC. File direct, we will figure it out. If we have
to. I have cleared many aircraft to a three letter identifier and never
known the name of the airport. If I need it I will ask for his on
course heading, say resume own nav and there he goes.
2) put a radial-distance from a VOR near your destination into your
flight plan. if you're crossing several centers, make sure there's
one in each center.
I can't even hazard a guess as to how many of these carefully concocted
flight plans I have erased and changed to direct to destination. DUATS
is usually an instigator of these ridiculous plans.
I note that the above does not fulfil the letter of the AIM for
direct flights, which require that a direct flight begin and end
over a ground-based navaid
Not necessary.
(at least as I read it) but I feel
it fulfills the spirit, in that it allows ATC to know which way
I'm headed without guessing and to verify any lat-longs in a
straighforward way.
ATC does not care about lat/lons and your requested altitude will
usually give a heads up of your general direction. If I need to know I
can always look up your destination airport(or any other fix) in our
location ID book.
|