Narrative:

During taxi and on the runway at zspd all system and indications were normal. Specifically; the map display showed the runway in proper alignment with the aircraft as we taxied out and lined up for takeoff. In addition; the magenta route line was positioned correctly. At liftoff we received a GPWS warning; 'too low; terrain.' at 400 ft and 1000 ft respectively; we engaged LNAV and VNAV; and appeared to track our course normally. After an ATC assigned 90 degree left turn from runway heading we were expecting another left turn on course towards tao. We were then cleared to proceed direct to pinot intersection. According to the FMC; this would be a right turn away from tao. We queried departure control; asking 'verify right turn direct pinot.' ATC did not reply nor change the clearance. We began the right turn as the FMC commanded direct to pinot as displayed on the FMC. We then asked to clarify our routing after pinot because FMC was showing a 180 degree course reversal at pinot to proceed to the next fix (odulo). This did not make sense to us. We were told that odulo was in fact the next fix; so we asked ATC to spell pinot. They did; confirming we had the correct intersection entered in the FMC. At that time ATC saw we were turning right and called and told us to turn left for direct to pinot. We told zspd control we were unable direct pinot; and that we were no longer RNAV equipped; and were given vectors on course. We then discovered that we had a 30+ NM disparity between the FMC position and the GPS position which was displayed on the adsb menu page. It appeared that the GPS position was the more correct position. The 30+ NM disparity continued for the remainder of the flight which we conducted using radar vectors and raw data. We believe that the map shift happened at liftoff; which then activated the GPWS. We did not correlate this to a map shift at that time; it took some extra time to realize that a map shift had occurred; partially because of the language barrier.

Related reports:

Google
 

Original NASA ASRS Text

Title: B757 FLT CREW HAS A TRACK HDG DEV DURING ODULO RWY 17 DEP AT ZSPD AND HAS A GPWS WARNING.

Narrative: DURING TAXI AND ON THE RWY AT ZSPD ALL SYS AND INDICATIONS WERE NORMAL. SPECIFICALLY; THE MAP DISPLAY SHOWED THE RWY IN PROPER ALIGNMENT WITH THE ACFT AS WE TAXIED OUT AND LINED UP FOR TKOF. IN ADDITION; THE MAGENTA RTE LINE WAS POSITIONED CORRECTLY. AT LIFTOFF WE RECEIVED A GPWS WARNING; 'TOO LOW; TERRAIN.' AT 400 FT AND 1000 FT RESPECTIVELY; WE ENGAGED LNAV AND VNAV; AND APPEARED TO TRACK OUR COURSE NORMALLY. AFTER AN ATC ASSIGNED 90 DEG L TURN FROM RWY HDG WE WERE EXPECTING ANOTHER L TURN ON COURSE TOWARDS TAO. WE WERE THEN CLRED TO PROCEED DIRECT TO PINOT INTXN. ACCORDING TO THE FMC; THIS WOULD BE A R TURN AWAY FROM TAO. WE QUERIED DEP CTL; ASKING 'VERIFY R TURN DIRECT PINOT.' ATC DID NOT REPLY NOR CHANGE THE CLRNC. WE BEGAN THE R TURN AS THE FMC COMMANDED DIRECT TO PINOT AS DISPLAYED ON THE FMC. WE THEN ASKED TO CLARIFY OUR ROUTING AFTER PINOT BECAUSE FMC WAS SHOWING A 180 DEG COURSE REVERSAL AT PINOT TO PROCEED TO THE NEXT FIX (ODULO). THIS DID NOT MAKE SENSE TO US. WE WERE TOLD THAT ODULO WAS IN FACT THE NEXT FIX; SO WE ASKED ATC TO SPELL PINOT. THEY DID; CONFIRMING WE HAD THE CORRECT INTXN ENTERED IN THE FMC. AT THAT TIME ATC SAW WE WERE TURNING R AND CALLED AND TOLD US TO TURN L FOR DIRECT TO PINOT. WE TOLD ZSPD CTL WE WERE UNABLE DIRECT PINOT; AND THAT WE WERE NO LONGER RNAV EQUIPPED; AND WERE GIVEN VECTORS ON COURSE. WE THEN DISCOVERED THAT WE HAD A 30+ NM DISPARITY BTWN THE FMC POS AND THE GPS POS WHICH WAS DISPLAYED ON THE ADSB MENU PAGE. IT APPEARED THAT THE GPS POS WAS THE MORE CORRECT POS. THE 30+ NM DISPARITY CONTINUED FOR THE REMAINDER OF THE FLT WHICH WE CONDUCTED USING RADAR VECTORS AND RAW DATA. WE BELIEVE THAT THE MAP SHIFT HAPPENED AT LIFTOFF; WHICH THEN ACTIVATED THE GPWS. WE DID NOT CORRELATE THIS TO A MAP SHIFT AT THAT TIME; IT TOOK SOME EXTRA TIME TO REALIZE THAT A MAP SHIFT HAD OCCURRED; PARTIALLY BECAUSE OF THE LANGUAGE BARRIER.

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