Problems addressed with GPS databases

COPA has become involved with finding solutions to questions on GPS databases raised by COPA member Trevor Lyons. (See, “Little orphan avionics,” page C-6, Canadian Flight, March 2002.) Lyons identified deficiencies in the database of his Garmin 90 GPS related to the Ottawa area.
Question 1: Some Non-direction Beacon transmitters were missing such as the “Oscar” Beacon at Ottawa.
Garmin answer: Single letter NDB identifiers will only exist in units with the approach in the database and may not be included if there are two such named points in the same region. If there are two “O” NDBs in eastern Canada, there is no means to discriminate which one you should be navigating to unless you have the full approach loaded. This is a case of naming policy being incompatible with new technology.” Matthew Harrah, Product Support Supervisor, Garmin International
COPA input: “I appreciate the difficulties with the single identifier NDBs. We have taken this issue up with Nav Canada and Transport Canada. It is a safety issue that can only be resolved by renaming the beacons using a naming convention that is compatible with electronic databases. Although we view this as a relatively minor issue, it can be easily resolved for little cost.” Kevin Psutka.
Question 2: No control zone circle depicted around Ottawa International Airport or Gatineau, Que.
Garmin answer: “Jeppesen (database supplier) has dropped what I believe you are referring to the Class C Control Zone. Our speculation is that the inner-most airspace ring had the same altitude attributes of a 1,500-ft MSL floor and 12,500-ft MSL ceiling as the adjoining airspace. Having a surface to 3,000 ft when all other airspace is up to 12,500 ft is odd at the least. This would apply across the board and not just effect Garmin units.” Matthew Harrah.
COPA input: “I am confused by your answer. It appears that the issue is with airspace that does not go up to 12,500 feet, or at least to the top of the surrounding airspace. Even if that is the issue, why is, for example, the Toronto International (CYYZ) control zone, which goes from the ground up to 2,500 feet, shown in your database? There appears to be an inconsistency in the database that applies in some area but not in others. I view this safety issue as a major one. It appears that information that was previously included has been systematically taken away. A safety trap for sure!
“I will ask that Transport Canada work with Jeppesen and Nav Canada to resolve this issue and, in the meantime, put a warning out to Canadians, as well as communicating this to the FAA for pilots who may visit Canada.” Kevin Psutka.
Question 3: Some restricted areas such as around the parliament buildings, are not depicted.
Garmin answer: “In the case of the Class F restricted airspace, are these classified as Temporary Flight Restrictions or are they going on the books permanently? Jeppesen has not added any TFR type data to the database and has taken the stance to not add them until they reach permanent inclusion in the National (U.S.) and Canadian Airspace Plans. If they have gone permanent, it typically takes a cycle or two to be verified and published.”