View Single Post
  #65  
Old January 21st 04, 03:00 PM
Steven P. McNicoll
external usenet poster
 
Posts: n/a
Default


"John R Weiss" wrote in message
news:vHfPb.91560$5V2.229832@attbi_s53...

I was under the impression you were an instrument-rated pilot as
well as an ATC controller...


I am.



Direct, using the time/heading/distance from your preflight planning.


Ah, via dead-reckoning. I see. Are you an instrument-rated pilot? Are you
a pilot at all?


[From the question, I assume MKE doesn't have a VOR at the field.
I'm in Seattle, and don't have charts or other pubs for the MKE area,
so I'll fast-forward you to WA.]


Online versions are available, MKE is on the NACO IFR Area Chart
Chicago/Milwaukee.



If I was enroute to BFI (Boeing Field, WA, which does not have a
co-located VOR), I would know to look up the nearby NAVAIDS
in the Airport/Facility Directory, and find that BFI is at the SEA

341/5.7.
I would plot the course and distance from my previous waypoint (e.g.,
TAGOR, on V 120, SEA 069/16) on a Sectional, and transfer it
(approx 291/17) to my kneeboard Nav card.

In the airplane, if I lost comm prior to TAGOR, all I have to do is fly
direct from TAGOR to the SEA 341/5.7 (cross-checking with the
PARKK NDB at the field, if I don't have DME -- I could do this as
an NDB hold, too, but I am assuming that isn't an option at MKE),
using the preplanned heading and time, adjusted for any wind
corrections I'd been using enroute to TAGOR.


Nope, not an option at MKE. Given that you can navigate enroute and hold
using just dead-reckoning, why do you bother with navaids while enroute at
all?