Re: R4808N Airspace NAVAIDS & Fixes


Message posted by Joerg (Webmaster) on January 02, 2007 at 1:42:49 PST:

After a little research, here is what I came up with. Comments and corrections welcome, especially from our resident pilots like Frank.

The typical current flight plan is:

LAS -> Groom
FIDOE SHOWW BTY060030

Groom -> LAS
BTY060030 SHOWW FIDOE BLD260033 BLD

LAS -> TTR
MCCRN3 BTY J92 LIDAT TPH206010 TPH

TTR -> LAS
TPH TPH206010 LIDAT J92 BTY FUZZY6
(sometimes the FUZZY7 approach to LAS is used instead of FUZZY6)

In older flight plans, the fix "FIDOE" was LAS290020 (near Angel Peak), and the fix SHOWW was LAS294052 (near Mercury). So unless the route has changed we can assume that LAS290020 is the vector for FIDOE, and LAS294052 is the vector for SHOWW.

Doing the math (and it is entirely possible that I did it wrong), I get:

FIDOE (=LAS290020)
Lat/Long: 36-15-33.6N / 115-30-22.6W

SHOWW (=LAS294052)
Lat/Long: 36-35-41.8N / 116-01-21.0W

The waypoint LIDAT in the TTR flight plan is:

LIDAT
Lat/Long: 37-25-48.670N / 117-16-41.000W

TPH (Tonopah), BLD (Boulder City), BTY (Beatty), MCY (Mercury) and LAS (Vegas McCarran) are well documented beacons.

The vectors are given as degrees magnetic heading and distance in nautical miles off a beacon. So, BLD260033 is 33 nautical miles from the Boulder City VOR, at 260 degrees magnetic.

No joy on ABBEY or TEDDY. They are both registered as fixes, but in different states. No joy on PYD or Pyramid (either).

I really never paid much attention to the flight plans, but since there seems to be an interest, I will put this all together into a map, which can be amended/corrected as needed. I think a map says more that a thousand words...

Any input on this is welcome. Thanks!


In Reply to: R4808N Airspace NAVAIDS & Fixes posted by Les Parson on December 31, 2006 at 6:28:13 PST:

Replies:



[ Discussion Forum Index ] [ FAQ ]