S Ramirez wrote:

Wasn't there a big long thread about that very VOR a few weeks ago, when
somebody discovered that his GPS had both locations, and sometimes would
cough up one and sometimes cough up the other and his back and forth with
Garmin about it? Or am I thinking of somewhere else?

Paul, if there was a thread about this, I don't know about it because I
didn't research the archives and I haven't been monitoring this newsgroup
in
a while. I'll go search the archives. Thanks. Simon

It was in rec.aviation.ifr, I believe.

The crux of the problem was what occurs when a DB update moves
a navaid that's in a stored flight plan. In that case, the DB
update didn't work properly with respect to the navaid.

As a software engineer, I found the discussion quite interesting.
Although Garmin "fixed" the problem, I found myself wondering at
the quality of the fix. More, I wasn't sure what the right "fix"
should be.

Should the flight plan move with the navaid? This could result
in an undesired (or at least unexpected) route. Should the flight
plan's waypoint stay fixed in space, even if not connected to the
navaid? To someone (such as myself) that follows the flight plan
with the navaids as well as the GPS, this could quickly become
very disconcerting.

I couldn't see a solution any better than "flagging" the flight
plan as requiring review by the user before the next use.

Here's the start of the followup thread:

http://groups.google.com/groups?hl=e...05%40attbi_s03

- Andrew