"Ben Jackson" wrote in message
news:%6kOb.89954$na.49173@attbi_s04...
In article ,
Andrew Sarangan wrote:
For example, the NDB 19 approach at CYO has a current approach chart.
There are no NOTAMs against it. But the NDB is no longer functioning.
It has been decommisioned. I don't know of any way a pilot could get
this information without a current AF/D.

The notion that you can just document a problem and that's as good as
fixing it is bunk. It happens all the time on software projects. The
FAA seems to have bought into it in a big way. Permanent TFRs are a
perfect example.

There is a story behind that:

You see, there once was an airliner, so safe that none had crashed in 18
years. Long ago an error had been made in validation rules and a waypoint
identifier was removed from it's FMS database. (remove all doubles) Many
years later, the problem was corrected in the data base and a decision was
made to "fix the problem". Software was delivered, a service bulletin was
released and there was much rejoycing. Six months later, the foreign NOTAM
for the missing identifier was removed and the runway VOR was commissioned
by AA 965. Unfortunately, the service bulletin was never applied to the
airplane.

So you see, from the perspective of the system, fixing a problem is not
always a good plan.