Narrative:

Excerpt from filed route: dct foxxe/m080f360 dct averu/n0463f360 dct mss dct jhw during preflight;when the first officer entered route into FMC; averu intersection was found to be not in the database. First officer then manually entered the latitude/longitude coordinates listed for this fix on the computer flight plan: N50300 W068480 the coordinates input; as well as the course and distance to and from this waypoint were cross checked by another pilot and this procedure was observed by a check airman. Note that the fix in question is the third fix in canadian domestic airspace after completing the oceanic portion of this flight. Upon achieving radar contact with gander center; the controller mentioned a 'dogleg' in our route and offered us a shortcut. We informed center that we would rather remain on the flight plan route; in order to achieve our desired arrival time. At this time; I selected the plan mode on the map display and noted a slight right dogleg in our route; and thought that the shortcut would be insignificant. Soon after passing foxxe intersection; the gander center controller expressed his surprise as to the direction we had turned passing that intersection. We stated that we were proceeding direct to averu. The controller then stated that he had expected us to make a turn approximately 40 degrees to the left of our present course. At this point; we realized that there must be some error with the coordinates listed on the flight plan for this intersection; and we obtained an amended clearance to a different fix in order to return to our expected route of flight. Subsequent discussions with the gander center controller revealed that his database contained an averu intersection associated with an approach at a point much further south of our intended route of flight somewhere in moncton center's airspace. It was to this point which he was expecting us to turn towards once we passed foxxe. We communicated the coordinates of the point which we believed to be averu intersection (as listed on our cfp); and he told us that there was no known fix at that location. We later confirmed this by locating the coordinates on a high altitude enroute chart. Indeed; there was no intersection located at these coordinates.

Related reports:

Google
 

Original NASA ASRS Text

Title: B767 Flight Crew reports that waypoint AVERU is not in the FMC data base and use the coordinates from the flight plan to create the fix. Enroute after turning toward AVERU the crew is informed by ATC that the coordinates are not correct.

Narrative: Excerpt from filed route: DCT FOXXE/M080F360 DCT AVERU/N0463F360 DCT MSS DCT JHW During preflight;when the First Officer entered route into FMC; AVERU intersection was found to be not in the database. First Officer then manually entered the Latitude/Longitude coordinates listed for this fix on the Computer Flight Plan: N50300 W068480 The coordinates input; as well as the course and distance to and from this waypoint were cross checked by another pilot and this procedure was observed by a Check Airman. Note that the fix in question is the third fix in Canadian domestic airspace after completing the oceanic portion of this flight. Upon achieving radar contact with Gander Center; the controller mentioned a 'dogleg' in our route and offered us a shortcut. We informed center that we would rather remain on the flight plan route; in order to achieve our desired arrival time. At this time; I selected the Plan mode on the map display and noted a slight right dogleg in our route; and thought that the shortcut would be insignificant. Soon after passing FOXXE intersection; the Gander Center controller expressed his surprise as to the direction we had turned passing that intersection. We stated that we were proceeding direct to AVERU. The controller then stated that he had expected us to make a turn approximately 40 degrees to the left of our present course. At this point; we realized that there must be some error with the coordinates listed on the flight plan for this intersection; and we obtained an amended clearance to a different fix in order to return to our expected route of flight. Subsequent discussions with the Gander Center controller revealed that his database contained an AVERU intersection associated with an approach at a point much further south of our intended route of flight somewhere in Moncton Center's airspace. It was to this point which he was expecting us to turn towards once we passed FOXXE. We communicated the coordinates of the point which we believed to be AVERU intersection (as listed on our CFP); and he told us that there was no known fix at that location. We later confirmed this by locating the coordinates on a High Altitude enroute chart. Indeed; there was no intersection located at these coordinates.

Data retrieved from NASA's ASRS site as of April 2012 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.