MEA oddity near Harrisburg, PA?

I have the current Jepp LO 47 chart and there's something odd around
the SEG (Sellinsgrove) VOR (just north of HAR). The MEAs around the
VOR are in the 4000' range, except for V106 to RASHE, which is 14000'.

I sent a note to Jepp querying this. They claim it's correct, based
on navaid reception. I still find this hard to swallow. 14,000???
C'mon. And if so, why isn't there a MOCA for the segment? There's
a 6000 MEA / 3900T for the next segment.

Anyone have a NOAA chart? Does it have the same MEA? Anyone know
the MVA for the area? Anyone have a topo/sectional map of the area
to explain the mysterious navaid reception issue?

Morris (who cannot be the first person to have noticed this)

Journeyman wrote:
I have the current Jepp LO 47 chart and there's something odd around
the SEG (Sellinsgrove) VOR (just north of HAR). The MEAs around the
VOR are in the 4000' range, except for V106 to RASHE, which is 14000'.

I sent a note to Jepp querying this. They claim it's correct, based
on navaid reception. I still find this hard to swallow. 14,000???
C'mon. And if so, why isn't there a MOCA for the segment? There's
a 6000 MEA / 3900T for the next segment.

Anyone have a NOAA chart? Does it have the same MEA? Anyone know
the MVA for the area? Anyone have a topo/sectional map of the area
to explain the mysterious navaid reception issue?

Morris (who cannot be the first person to have noticed this)
Same on the NOAA chart. Knowing the terrain I would agree it has to be a
mistake.

I've noticed it, and I've flown that segment way below 14K (albeit /G)
so I've no idea what's going on. There is a ridge that might block
reception on the south edge of the airway, so perhaps that's the issue
given how close the VOR is to start of the ridge...

In article .com, Mike Granby wrote:

There is a ridge that might block
reception on the south edge of the airway, so perhaps that's the issue
given how close the VOR is to start of the ridge...

That must be it. Thanks for all the replies.


Morris

Similarly, there's one from Madison, Wisconsin to Chicago with something
like a 10,000 MEA. The best I can tell is that there's one hill in the
flats of Wisconsin that limits the signal, but it's not obvious.

Journeyman wrote:
I have the current Jepp LO 47 chart and there's something odd around
the SEG (Sellinsgrove) VOR (just north of HAR). The MEAs around the
VOR are in the 4000' range, except for V106 to RASHE, which is 14000'.

I sent a note to Jepp querying this. They claim it's correct, based
on navaid reception. I still find this hard to swallow. 14,000???
C'mon. And if so, why isn't there a MOCA for the segment? There's
a 6000 MEA / 3900T for the next segment.

Anyone have a NOAA chart? Does it have the same MEA? Anyone know
the MVA for the area? Anyone have a topo/sectional map of the area
to explain the mysterious navaid reception issue?

Morris (who cannot be the first person to have noticed this)

The sectional chart may help, but you can find the law that
establishes an airway, each one has a public statement. In
that discussion you will find many answers.
If you want to see real odd altitudes, look around Key West
for the safe quadrangle altitude, it is about 14,000 last
time I looked. Why? Because they sometimes have a tethered
balloon and radar up looking at the drug smugglers.



"David Kazdan" wrote in message
. com...
| Similarly, there's one from Madison, Wisconsin to Chicago
with something
| like a 10,000 MEA. The best I can tell is that there's
one hill in the
| flats of Wisconsin that limits the signal, but it's not
obvious.
|
| Journeyman wrote:
| I have the current Jepp LO 47 chart and there's
something odd around
| the SEG (Sellinsgrove) VOR (just north of HAR). The
MEAs around the
| VOR are in the 4000' range, except for V106 to RASHE,
which is 14000'.
|
| I sent a note to Jepp querying this. They claim it's
correct, based
| on navaid reception. I still find this hard to swallow.
14,000???
| C'mon. And if so, why isn't there a MOCA for the
segment? There's
| a 6000 MEA / 3900T for the next segment.
|
| Anyone have a NOAA chart? Does it have the same MEA?
Anyone know
| the MVA for the area? Anyone have a topo/sectional map
of the area
| to explain the mysterious navaid reception issue?
|
| Morris (who cannot be the first person to have noticed
this)

In article f989g.18838$ZW3.12367@dukeread04,
says...


Why? Because they sometimes have a tethered
balloon and radar up looking at the drug smugglers.


Yes, but that's different from reception issues.
I think Mike's answer is probably closer - because the VOR is close to
the ridge, that gives rise to some seemingly wierd MEA's, without
anything untoward inthe MOCA. Puts a kink in your plans though, if you
weren't planning (or cannot do) 14000.

GF

In article ,
Greg Farris wrote:

In article f989g.18838$ZW3.12367@dukeread04,
says...


Why? Because they sometimes have a tethered
balloon and radar up looking at the drug smugglers.


Yes, but that's different from reception issues.
I think Mike's answer is probably closer - because the VOR is close to
the ridge, that gives rise to some seemingly wierd MEA's, without
anything untoward inthe MOCA. Puts a kink in your plans though, if you
weren't planning (or cannot do) 14000.

GF

Take a look at some of the airways in western CT based on the LGA VOR. The
MEA's make no sense based on terrain alone. I'm told the problem is that
the VOR is nestled in among the hangars and other buildings and the signal
suffers.

Journeyman wrote:
I have the current Jepp LO 47 chart and there's something odd around
the SEG (Sellinsgrove) VOR (just north of HAR). The MEAs around the
VOR are in the 4000' range, except for V106 to RASHE, which is 14000'.
/snip/

You wanna see something really wild? Go to
http://idisk.mac.com/scottdb-Public
and look at the "HiMEA" file. Right in the middle, the transitional MEA
for V462 is listed as 88000 between FAGIN and NONDA. This obviously
should be 8800, but I don't think it is just a typo on Jepp's part.
When our company's flight planning software generates a low altitude
route through this area, it actually bypasses that one segment, since
our planes can't climb that high. Makes me think that the data is bad
from the FAA.

Happy Flying!
Scott Skylane

Scott Skylane wrote:

You wanna see something really wild? Go to
http://idisk.mac.com/scottdb-Public

Wish I could, but you don't like my browser.

and look at the "HiMEA" file. Right in the middle, the transitional MEA
for V462 is listed as 88000 between FAGIN and NONDA. This obviously
should be 8800, but I don't think it is just a typo on Jepp's part. When
our company's flight planning software generates a low altitude route
through this area, it actually bypasses that one segment, since our
planes can't climb that high. Makes me think that the data is bad from
the FAA.

That's the Alaska airway V462, not the Federal airway V462, right?

The ATA-100 AWY file effective June 08, 2006 shows a MOCA of 12200 and an MEA of
14000 between FAGIN and NONDA.