Narrative:

On preflight, I turned to moscow parking spot page in chart to load position into inertials. I inadvertently loaded the spot for a different moscow airport 20 mi away. Complying with company procedures I showed the coordinates to the captain for verification. He did not notice they were at the incorrect airport. There was no indication of a mistake until takeoff. The computer generated map disappeared on takeoff. We manually flew the departure after several seconds of confusion. About 1/2 hour later we determined the cause but had no way to update IRS position and were concerned about having to land before crossing the atlantic. Approximately 200 mi out of former ussr airspace, VOR DME updated FMC to a position well within tolerance for an atlantic crossing.

Google
 

Original NASA ASRS Text

Title: WRONG COORDINATES ENTERED INTO INS, DIFFERENT ARPT.

Narrative: ON PREFLT, I TURNED TO MOSCOW PARKING SPOT PAGE IN CHART TO LOAD POS INTO INERTIALS. I INADVERTENTLY LOADED THE SPOT FOR A DIFFERENT MOSCOW ARPT 20 MI AWAY. COMPLYING WITH COMPANY PROCS I SHOWED THE COORDINATES TO THE CAPT FOR VERIFICATION. HE DID NOT NOTICE THEY WERE AT THE INCORRECT ARPT. THERE WAS NO INDICATION OF A MISTAKE UNTIL TKOF. THE COMPUTER GENERATED MAP DISAPPEARED ON TKOF. WE MANUALLY FLEW THE DEP AFTER SEVERAL SECONDS OF CONFUSION. ABOUT 1/2 HR LATER WE DETERMINED THE CAUSE BUT HAD NO WAY TO UPDATE IRS POS AND WERE CONCERNED ABOUT HAVING TO LAND BEFORE XING THE ATLANTIC. APPROX 200 MI OUT OF FORMER USSR AIRSPACE, VOR DME UPDATED FMC TO A POS WELL WITHIN TOLERANCE FOR AN ATLANTIC XING.

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