![]() |
If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
|
Thread Tools | Display Modes |
|
#1
|
|||
|
|||
![]()
The ILS 16R (http://tinyurl.com/353gd5) at Reno (KRNO) has the
notation: "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? |
#2
|
|||
|
|||
![]() "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 |
#3
|
|||
|
|||
![]()
Kobra wrote:
"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. If airnav.com is to be believed, it's at the intersection of the 286 radial from HZN, and the 332 radial from FMG, at 22.19 DME, and is charted on enroute-high and enroute-low as well as the IAP. Dave |
#4
|
|||
|
|||
![]() "Dave Butler" wrote in message ... If airnav.com is to be believed, it's at the intersection of the 286 radial from HZN, and the 332 radial from FMG, at 22.19 DME, and is charted on enroute-high and enroute-low as well as the IAP. The low altitude enroute chart shows the intersection of the HZN 286R and FMG 332R to be LIBGE, three miles north of PYRAM. |
#5
|
|||
|
|||
![]()
On Dec 13, 5:41 pm, "Steven P. McNicoll"
wrote: "Dave Butler" wrote in message ... If airnav.com is to be believed, it's at the intersection of the 286 radial from HZN, and the 332 radial from FMG, at 22.19 DME, and is charted on enroute-high and enroute-low as well as the IAP. The low altitude enroute chart shows the intersection of the HZN 286R and FMG 332R to be LIBGE, three miles north of PYRAM. Isn't that interesting. Both on the Jepp approach plate as well as on the Jepp low enrout chart PYRAM shows as FMZ 332R and HZN 286R. LIBGE is FMZ 332R and on the INRO 164 LOC. By measuring the radial from HZN to PYRAM, I get 303 deg T from FliteStar which is actually 286 deg M (HZN Station Declination: 17.0 deg E), so that seems to be correct. Gerd |
#6
|
|||
|
|||
![]()
Dave Butler wrote:
If airnav.com is to be believed, it's at the intersection of the 286 radial from HZN, and the 332 radial from FMG, at 22.19 DME, and is charted on enroute-high and enroute-low as well as the IAP. Dave It's even on the SECTIONAL. |
#7
|
|||
|
|||
![]() "Kobra" wrote in message . .. 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. |
#8
|
|||
|
|||
![]()
On Thu, 13 Dec 2007 12:44:37 -0500, "Kobra" wrote:
No idea, but I would like to know how on an ILS approach without GPS one would identify PYRAM. You use your low altitude chart. PYRAM is defined by the 286.0° radial from HZN (Hazen VOR) at 41.7 NM. It is on V165 a few miles south of LIBGE Ron (EPM) (N5843Q, Mooney M20E) (CP, ASEL, ASES, IA) |
#9
|
|||
|
|||
![]()
On Dec 14, 7:24 am, Ron Rosenfeld wrote:
On Thu, 13 Dec 2007 12:44:37 -0500, "Kobra" wrote: No idea, but I would like to know how on an ILS approach without GPS one would identify PYRAM. You use your low altitude chart. PYRAM is defined by the 286.0° radial from HZN (Hazen VOR) at 41.7 NM. It is on V165 a few miles south of LIBGE Are you looking at a Jeppesen chart? NACO low altitude enroute chart L-9 shows LIBGE to be where the HZN 286R crosses V165. NACO high altitude enroute chart H-3 shows PYRAM to be where the HZN 286R crosses J5. V165 and J5 are defined by the FMG 332R. |
#10
|
|||
|
|||
![]()
On Dec 14, 9:11 am, "Steven P. McNicoll"
wrote: On Dec 14, 7:24 am, Ron Rosenfeld wrote: On Thu, 13 Dec 2007 12:44:37 -0500, "Kobra" wrote: No idea, but I would like to know how on an ILS approach without GPS one would identify PYRAM. You use your low altitude chart. PYRAM is defined by the 286.0° radial from HZN (Hazen VOR) at 41.7 NM. It is on V165 a few miles south of LIBGE Are you looking at a Jeppesen chart? NACO low altitude enroute chart L-9 shows LIBGE to be where the HZN 286R crosses V165. NACO high altitude enroute chart H-3 shows PYRAM to be where the HZN 286R crosses J5. V165 and J5 are defined by the FMG 332R. 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. Gerd |
|
Thread Tools | |
Display Modes | |
|
|