ILS 16R at KRNO

> "8500 to GS intercept 181 (2) and LOC (8.8)"
>
> I don't understand this. It appears this means that GS intercept will
> occur in 2 miles on a 181 heading and that LOC intercept will occur in
> 8.8 miles. Neither appears to be true from the plan view. In fact, it
> looks more like LOC intercept will occur in 2 miles and GS intercept
> in 8.8 (at 8500 feet).
>
> Any insights?

No idea, but I would like to know how on an ILS approach without GPS one
would identify PYRAM.

Kobra

"Kobra" <kobra@yahoo.net> wrote in message
news:n5idnRrIVN4Y8vzanZ2dnUVZ_u2mnZ2d@. ..
>
> No idea, but I would like to know how on an ILS approach without GPS one
> would identify PYRAM.
>

PYRAM is a DME fix on V165.

Three miles north of PYRAM there's another fix, LIBGE, which can be
determined by DME, or a radial intersection from Hazen VOR, or the
intersection with the Reno RWY 16R LOC.

If you were inbound to Reno from the north on V165 you could your determine
your position at LIBGE as you flew through the localizer, continue for
another three miles on V165 and determine your position at the IAF PYRAM by
use of DME or GPS, at which point you'd turn to a heading of 181 to
intercept the localizer.

"gwengler" <gwengler@parkprop.com> wrote in message
news:75cf680d-bf36-4443-bb81-64dde380aa6c@e6g2000prf..com...
>
> You fly to PYRAM (which can be identified by FMG 332 radial and HZN
> 286 radial).
>

What chart are you looking at? Low altitude enroute chart L-9 shows the
intersection of the FMG 332R and HZN 286R to be LIBGE, three miles north of
PYRAM.

On Dec 13, 5:44 pm, "Steven P. McNicoll" <roncach...@>
wrote:
> "gwengler" <gweng...@parkprop.com> wrote in message
>
> news:75cf680d-bf36-4443-bb81-64dde380aa6c@e6g2000prf..com...
>
>
>
> > You fly to PYRAM (which can be identified by FMG 332 radial and HZN
> > 286 radial).
>
> What chart are you looking at? Low altitude enroute chart L-9 shows the
> intersection of the FMG 332R and HZN 286R to be LIBGE, three miles north of
> PYRAM.

I took this information from the Jeppesen approach plate KRNO ILS16R
11-1 24-Aug-07. PYRAM is clearly identified as I said above. It's
22.2D from FMG.
Gerd

"gwengler" <gwengler@parkprop.com> wrote in message
news:30af00e5-bf6c-42aa-80b0-144afd4d8f63@d4g2000prg..com...
>
> Isn't that interesting. On both Jepp approach plate and low enrout
> chart, PYRAM is identified as HZN 286R and FMG 332R. I measured it
> with FliteStar and it's indeed 303T from HZN, which is correct
> (Station Declination: 17.0°E). LIGBE is defined as by the IRNO /
> RW16R Localizer at KRNO at 27.4 NM by Jeppesen, but it's also FMG
> 332R.
>

JO 7350.7B Location Identifiers shows PYRAM to be the intersection of the
HZN 286 and FMG 332 radials as well as the FMG 332R 22 DME fix. The low
altitude enroute chart is in error, I've sent a message to NACO about it.

Steven P. McNicoll wrote:
> "gwengler" <gwengler@parkprop.com> wrote in message
> news:30af00e5-bf6c-42aa-80b0-144afd4d8f63@d4g2000prg..com...
>> Isn't that interesting. On both Jepp approach plate and low enrout
>> chart, PYRAM is identified as HZN 286R and FMG 332R. I measured it
>> with FliteStar and it's indeed 303T from HZN, which is correct
>> (Station Declination: 17.0°E). LIGBE is defined as by the IRNO /
>> RW16R Localizer at KRNO at 27.4 NM by Jeppesen, but it's also FMG
>> 332R.
>>
>
> JO 7350.7B Location Identifiers shows PYRAM to be the intersection of the
> HZN 286 and FMG 332 radials as well as the FMG 332R 22 DME fix. The low
> altitude enroute chart is in error, I've sent a message to NACO about it.
>
>
>
That's odd. I've only got paper Jepps, but the online NACO chart at
aeroplanner shows PYRAM with the 286degree arrow pointing at it.