2010-05 · NASA ASRS report 890779
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.
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.
Approximately 2 minutes after passing FOXXE; Gander asked us to verify our routing; since they showed us 40 degrees off course. AVERU was 40 degrees to our left. We asked them what LAT/LON they showed for for AVERU. Their reply 47N 6513W. Gander recleared us from our present position; direct to YCB; direct to MSS; as filed. We proceeded without incident.
More incidents for this aircraft family
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.
Loading the flight search…
Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.
We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.
Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.
Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.