37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1409256 |
Time | |
Date | 201612 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | FRG.Airport |
State Reference | NY |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Small Aircraft Low Wing 2 Eng Retractable Gear |
Operating Under FAR Part | Part 91 |
Flight Phase | Parked |
Flight Plan | IFR |
Component | |
Aircraft Component | Navigation Database |
Person 1 | |
Function | Pilot Flying Single Pilot |
Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Multiengine Flight Crew Instrument Flight Crew Flight Instructor |
Experience | Flight Crew Last 90 Days 30 Flight Crew Total 2800 Flight Crew Type 1600 |
Events | |
Anomaly | Aircraft Equipment Problem Less Severe Deviation - Procedural Published Material / Policy |
Narrative:
I purchase an annual database subscription from jeppesen that covers the eastern and central us; but not the canadian navigation database (more on this later). In attempting to input my clearance into the GPS the following intersections were not found: colts; borek; and lopvo. I spend close to an hour on the ground with both engines running to attempt to resolve this with ATC. We finally got a revised routing that I was able to enter. It appears that certain canadian fixes are included in the us database and many are not. This was quite surprising since there is no publication or notice to airman from jeppesen to advise the database consumer of which fixes are in or out. While this occurred on the ground and created a process issue for me and ATC if this had been airborne it could have been far worse.aircraft frequently transit canadian airspace from the east coast us to points west and are given ATC routes that they do not have advance notice on. In my case I discovered that certain canadian navigational points were not in my data base but others were. This created issues for me and ATC and expended a significant amount of fuel during the problem resolution period. I believe that this lack of clarity in the jeppesen provided databases is creating uncertainty and questions about the integrity of the databases provided by jeppesen. This in my mind is a safety of flight issue! They need to do one of the following:1) in any database that does not include canadian coverage eliminate all references to any canadian navigation points.2) publish a notice to airman with each database update the canadian fixes that will be included in the us data base stipulating that no other fixes are included from canadian airspace.3) include those canadian fixes within a 200 mile lateral northern zone into canada to provide consistent coverage to avoid confusion.
Original NASA ASRS Text
Title: A general aviation pilot reported his Garmin 530W database provided by Jeppesen did not include several Canadian waypoints which were part of his IFR flight plan between two domestic U.S. airports. Reporter stated some Canadian waypoints are available; but others are not.
Narrative: I purchase an annual database subscription from Jeppesen that covers the Eastern and Central U.S.; but not the Canadian navigation database (more on this later). In attempting to input my clearance into the GPS the following intersections were not found: COLTS; BOREK; and LOPVO. I spend close to an hour on the ground with both engines running to attempt to resolve this with ATC. We finally got a revised routing that I was able to enter. It appears that certain Canadian fixes are included in the U.S. database and many are not. This was quite surprising since there is no publication or notice to airman from Jeppesen to advise the database consumer of which fixes are in or out. While this occurred on the ground and created a process issue for me and ATC if this had been airborne it could have been far worse.Aircraft frequently transit Canadian airspace from the east coast U.S. to points west and are given ATC routes that they do not have advance notice on. In my case I discovered that certain Canadian navigational points were not in my data base but others were. This created issues for me and ATC and expended a significant amount of fuel during the problem resolution period. I believe that this lack of clarity in the Jeppesen provided databases is creating uncertainty and questions about the integrity of the databases provided by Jeppesen. This in my mind is a safety of flight issue! They need to do one of the following:1) In any database that does not include Canadian coverage eliminate ALL references to any Canadian navigation points.2) Publish a notice to airman with each database update the Canadian fixes that will be included in the U.S. data base stipulating that no other fixes are included from Canadian airspace.3) Include those Canadian fixes within a 200 mile lateral northern zone into Canada to provide consistent coverage to avoid confusion.
Data retrieved from NASA's ASRS site and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.