Narrative:

Leaving sdq today we had a bit of a navigation problem. The coordinates were entered at the gate and verified by each pilot. No problems. Taxi, captain in epgws, first officer in map, his leg. Nothing unusual about the flight until we lifted off on runway 17 (immediately over the shore and overwater) when we received a 'terrain terrain' warning. In clear WX we knew something was wrong. I switched over to map mode on climb out and realized the pink line had shifted out to the west of our position. Raw data confirmed that the position the FMC was incorrect and we proceeded to fly via raw data. We told las americas control we were having difficulty with our onboard flight computer and they said 'ok.' when las americas gave us direct to 'retak' position, once we were on a northbound heading, we told them unable and asked them for a heading. We were tuning and xchking every radial and DME as possible, and it confirmed that where we were and where the aircraft thought it was, were 2 different places. Las americas gave us a heading, and verifying the radials, distances on the DME's, and ADF's we approached retak, called port-a-prince and naved through their airspace on the A363 using the pta 301 degree radial. Shortly after we contacted ZMA and told them we were having difficulties and they changed our filed navigation capabilities to the air carrier. They gave us headings. We verified position again using the raw data methods. Fortunately many ADF's were working along the route. At XA53Z miami gave us a latitude/longitude position and we compared what the FMC said, actual N2209 W07435, FMC N2236 WO7433, the 2 position about 30 mi apart. We notified dispatch over ACARS, and per advice tried to remotely tune nearby vors, but didn't help. After landing we left the fmcs on and showed avionics what we had. At the gate, the fix page in the FMC had mia showing 022 degrees/20 KTS with a 9 NM drift rate. Supplemental information from acn 536914: the problem seemed to arise during the takeoff profile, at the point where the fmcs snapshot runway heading at ground break. That was when everything went haywire. During the flight, we tried remote tuning the vors via the VOR control heads and tuning them via the FMC program page to realign the maps per instructions from maintenance and dispatch. This had no effect and the maps never corrected themselves. Callback conversation with the first officer revealed the following information: the first officer reported that maintenance found no definitive problems and would monitor the aircraft.

Google
 

Original NASA ASRS Text

Title: ERRONEOUS FMC POS INFO CAUSES A TERRAIN WARNING AFTER TKOF. THE RAW DATA POS WAS CONFIRMED AND USED FOR NAV WITH THE ASSISTANCE OF ATC FOR A SUCCESSFUL FLT FROM THE DOMINICAN REPUBLIC.

Narrative: LEAVING SDQ TODAY WE HAD A BIT OF A NAV PROB. THE COORDINATES WERE ENTERED AT THE GATE AND VERIFIED BY EACH PLT. NO PROBS. TAXI, CAPT IN EPGWS, FO IN MAP, HIS LEG. NOTHING UNUSUAL ABOUT THE FLT UNTIL WE LIFTED OFF ON RWY 17 (IMMEDIATELY OVER THE SHORE AND OVERWATER) WHEN WE RECEIVED A 'TERRAIN TERRAIN' WARNING. IN CLR WX WE KNEW SOMETHING WAS WRONG. I SWITCHED OVER TO MAP MODE ON CLBOUT AND REALIZED THE PINK LINE HAD SHIFTED OUT TO THE W OF OUR POS. RAW DATA CONFIRMED THAT THE POS THE FMC WAS INCORRECT AND WE PROCEEDED TO FLY VIA RAW DATA. WE TOLD LAS AMERICAS CTL WE WERE HAVING DIFFICULTY WITH OUR ONBOARD FLT COMPUTER AND THEY SAID 'OK.' WHEN LAS AMERICAS GAVE US DIRECT TO 'RETAK' POS, ONCE WE WERE ON A NBOUND HEADING, WE TOLD THEM UNABLE AND ASKED THEM FOR A HEADING. WE WERE TUNING AND XCHKING EVERY RADIAL AND DME AS POSSIBLE, AND IT CONFIRMED THAT WHERE WE WERE AND WHERE THE ACFT THOUGHT IT WAS, WERE 2 DIFFERENT PLACES. LAS AMERICAS GAVE US A HEADING, AND VERIFYING THE RADIALS, DISTANCES ON THE DME'S, AND ADF'S WE APCHED RETAK, CALLED PORT-A-PRINCE AND NAVED THROUGH THEIR AIRSPACE ON THE A363 USING THE PTA 301 DEG RADIAL. SHORTLY AFTER WE CONTACTED ZMA AND TOLD THEM WE WERE HAVING DIFFICULTIES AND THEY CHANGED OUR FILED NAV CAPABILITIES TO THE ACR. THEY GAVE US HEADINGS. WE VERIFIED POS AGAIN USING THE RAW DATA METHODS. FORTUNATELY MANY ADF'S WERE WORKING ALONG THE RTE. AT XA53Z MIAMI GAVE US A LATITUDE/LONGITUDE POS AND WE COMPARED WHAT THE FMC SAID, ACTUAL N2209 W07435, FMC N2236 WO7433, THE 2 POS ABOUT 30 MI APART. WE NOTIFIED DISPATCH OVER ACARS, AND PER ADVICE TRIED TO REMOTELY TUNE NEARBY VORS, BUT DIDN'T HELP. AFTER LNDG WE LEFT THE FMCS ON AND SHOWED AVIONICS WHAT WE HAD. AT THE GATE, THE FIX PAGE IN THE FMC HAD MIA SHOWING 022 DEGS/20 KTS WITH A 9 NM DRIFT RATE. SUPPLEMENTAL INFO FROM ACN 536914: THE PROB SEEMED TO ARISE DURING THE TKOF PROFILE, AT THE POINT WHERE THE FMCS SNAPSHOT RWY HEADING AT GND BREAK. THAT WAS WHEN EVERYTHING WENT HAYWIRE. DURING THE FLT, WE TRIED REMOTE TUNING THE VORS VIA THE VOR CTL HEADS AND TUNING THEM VIA THE FMC PROGRAM PAGE TO REALIGN THE MAPS PER INSTRUCTIONS FROM MAINT AND DISPATCH. THIS HAD NO EFFECT AND THE MAPS NEVER CORRECTED THEMSELVES. CALLBACK CONVERSATION WITH THE FO REVEALED THE FOLLOWING INFO: THE FO RPTED THAT MAINT FOUND NO DEFINITIVE PROBS AND WOULD MONITOR THE ACFT.

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.