Narrative:

Flight plan loaded [prior to departure]. All class ii procedures followed; route and waypoints all checked by sops. One nat X waypoint was N48 W050. On check in with gander domestic; cleared direct 48 north 50 west. PF [pilot flying] selected; and made nicso; the only intermediate waypoint; an abeam. Confirmed 50W time and next waypoint with gander. Passing abeam nicso; did a class ii waypoint check. Next waypoint; n48w050; estimated XA11; howgozit time was XA09. Course was close; not expected to match because we were abeam nicso; not overhead. Distance matched within a few miles. Followed all normal class ii sops; checked in with gander oceanic; etc. Approaching 50W; began waypoint sops; got cpdlc to call gander domestic on VHF. Controller advised we were 12nm north of 48/50. Checked waypoint; still read n48w050. All GPS on position page dead on. Passed 50W waypoint; and position report page switched. Instead of reporting pos shown as N48 W050; it showed N4812.3 W5006.3. All other oceanic waypoints checked by bringing shorthand (N50 W040) down to scratchpad to expand to lat /long. All were correct.gander domestic turned us back to yyt to troubleshoot; but did say that radar showed our course to 50n40w looked accurate. Captain brought back from break; contacted maintenance control and dispatch. Examined all possibilities; consensus was that N4812.3 W5006.3 was loaded into FMS by sabre uplink; but shorthand showed n48w050. None of the class ii sops will detect this type of error. Captain / dispatcher made decision to continue; but fuel stop was required; as arrival fuel now projected at 6.0.

Google
 

Original NASA ASRS Text

Title: B767 flight crew experiences a track deviation while attempting to navigate direct to 48N50W. While the FMC showed 48N50W; the actual position reported to CZQX was N4812.3 W5006.3. CZQX will not allow the flight to continue and the flight turns back while troubleshooting and discussing with Maintenance Control. Eventually; with no navigational anomaly detected the flight is allowed to continue on NAT X with a fuel stop.

Narrative: Flight plan loaded [prior to departure]. All class II procedures followed; route and waypoints all checked by SOPs. One NAT X waypoint was N48 W050. On check in with Gander Domestic; cleared direct 48 N 50 W. PF [Pilot Flying] selected; and made NICSO; the only intermediate waypoint; an abeam. Confirmed 50W time and next waypoint with Gander. Passing abeam NICSO; did a class II waypoint check. Next waypoint; N48W050; estimated XA11; howgozit time was XA09. Course was close; not expected to match because we were abeam NICSO; not overhead. Distance matched within a few miles. Followed all normal class II SOPs; checked in with Gander Oceanic; etc. Approaching 50W; began waypoint SOPs; got CPDLC to call Gander domestic on VHF. Controller advised we were 12nm north of 48/50. Checked waypoint; still read N48W050. All GPS on position page dead on. Passed 50W waypoint; and position report page switched. Instead of reporting pos shown as N48 W050; it showed N4812.3 W5006.3. All other oceanic waypoints checked by bringing shorthand (N50 W040) down to scratchpad to expand to lat /long. All were correct.Gander domestic turned us back to YYT to troubleshoot; but did say that radar showed our course to 50N40W looked accurate. Captain brought back from break; contacted Maintenance control and Dispatch. Examined all possibilities; consensus was that N4812.3 W5006.3 was loaded into FMS by Sabre uplink; but shorthand showed N48W050. None of the class II SOPs will detect this type of error. Captain / Dispatcher made decision to continue; but fuel stop was required; as arrival fuel now projected at 6.0.

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.