Narrative:

Conditions: scattered clouds; visibility 7 mi (by ATIS). Phase of flight: visual approach to runway 1R iad. (ILS off air.) problem: FMC map shift. Were southeast of airport on barin 1 STAR; when approach cleared us direct to tille (OM runway 1R). Shortly after that; was cleared to visual for runway 1R. (ILS was off and runway in use was runway 19L and runway 19R; south operation.) FMC was; at this point in flight; showing runway 1R and tille in their correct position. As we descended and got in closer to tille (about 20 mi from tille) we received a significant map shift of what I estimate was 5-7 mi to east of actual tille position; and autoflt; flight director commanded a right turn to about a 030 degree heading to maintain direct track to tille and comply with our ATC clearance of 'direct tille.' I maintained old course as I was looking at runway 1R directly ahead. But was aware that there was a possibility that we could be tracking to runway 1L instead of runway 1R. There was this doubt only because FMC was showing tille and runway 1R well to right of aircraft course. At this point we were low enough (OM altitude of about 1700 ft) where we were unable to see other runways. Also; runway lights and approach lights; VASI were all off; or were set for runway 19L; not runway 1R. After a brief discussion with my crew and tower; elected to abort approach and request an ILS. Tower reclred us to left downwind for runway 19L (which had the ILS and lights on; at that time of morning). We proceeded northeast heading on a left downwind leg to runway 19L. The whole time the FMC was showing airport well to our east when in fact it was well to our west. After positively identing runway 19L; we were cleared to a visual runway 19L and landed. Shortly before landing; below 1000 ft; we received intermittent GPWS warnings. And continued receiving these warnings after exiting runway until terrain switch was disarmed. After stopping on taxiway; we determined that FMC was still showing a 6 mi error/disagreement in the position page. Runway 1R was still showing 6 mi to east of aircraft position. Even though we were correctly proceeding to runway 1R in visual conditions; the FMC created a significant element of doubt as to which runway we were really looking at; runway 1L or runway 1R. Since I did not want to descend below 1700 ft without knowing for sure that we were looking at correct runway; I elected to abort approach and request another approach. I further believe we got an erroneous GPWS warning because the airplane thought we were landing off airport; and did not know where we were. As it turns out; FMC was in error. The airplane has a history of FMC problems. Also received several 'error' codes: 'purge updates on FMC' from left FMC; after on ground in iad. FMC and map shift was written up. Had we been in anything less than visual conditions; this could have been a serious problem. Even while receiving ILS to runway 19L; FMC continued to show runway course 6 mi east of actual localizer. Callback conversation with reporter revealed the following information: the reporter has received no feedback from maintenance regarding the anomaly. He stated there was some NOTAM regarding ecg VOR that had escaped their notice which may have affected the IRU updating upon arriving overland. The problem; however; was that the position appeared accurate initially and the map shift resulted in a significant error; rather than a more precise position as would be expected from an IRU update. The egpws warnings would have been a significant issue had they not had visual contact with the ground. Even more potentially distressing was that they had little reserve fuel to allow for troubleshooting had they been forced to perform a go around due to the terrain warnings as is required when IMC.

Google
 

Original NASA ASRS Text

Title: B767-300 EXPERIENCES MAP SHIFT ON ARRIVAL.

Narrative: CONDITIONS: SCATTERED CLOUDS; VISIBILITY 7 MI (BY ATIS). PHASE OF FLT: VISUAL APCH TO RWY 1R IAD. (ILS OFF AIR.) PROB: FMC MAP SHIFT. WERE SE OF ARPT ON BARIN 1 STAR; WHEN APCH CLRED US DIRECT TO TILLE (OM RWY 1R). SHORTLY AFTER THAT; WAS CLRED TO VISUAL FOR RWY 1R. (ILS WAS OFF AND RWY IN USE WAS RWY 19L AND RWY 19R; S OP.) FMC WAS; AT THIS POINT IN FLT; SHOWING RWY 1R AND TILLE IN THEIR CORRECT POS. AS WE DSNDED AND GOT IN CLOSER TO TILLE (ABOUT 20 MI FROM TILLE) WE RECEIVED A SIGNIFICANT MAP SHIFT OF WHAT I ESTIMATE WAS 5-7 MI TO E OF ACTUAL TILLE POS; AND AUTOFLT; FLT DIRECTOR COMMANDED A R TURN TO ABOUT A 030 DEG HDG TO MAINTAIN DIRECT TRACK TO TILLE AND COMPLY WITH OUR ATC CLRNC OF 'DIRECT TILLE.' I MAINTAINED OLD COURSE AS I WAS LOOKING AT RWY 1R DIRECTLY AHEAD. BUT WAS AWARE THAT THERE WAS A POSSIBILITY THAT WE COULD BE TRACKING TO RWY 1L INSTEAD OF RWY 1R. THERE WAS THIS DOUBT ONLY BECAUSE FMC WAS SHOWING TILLE AND RWY 1R WELL TO R OF ACFT COURSE. AT THIS POINT WE WERE LOW ENOUGH (OM ALT OF ABOUT 1700 FT) WHERE WE WERE UNABLE TO SEE OTHER RWYS. ALSO; RWY LIGHTS AND APCH LIGHTS; VASI WERE ALL OFF; OR WERE SET FOR RWY 19L; NOT RWY 1R. AFTER A BRIEF DISCUSSION WITH MY CREW AND TWR; ELECTED TO ABORT APCH AND REQUEST AN ILS. TWR RECLRED US TO L DOWNWIND FOR RWY 19L (WHICH HAD THE ILS AND LIGHTS ON; AT THAT TIME OF MORNING). WE PROCEEDED NE HDG ON A L DOWNWIND LEG TO RWY 19L. THE WHOLE TIME THE FMC WAS SHOWING ARPT WELL TO OUR E WHEN IN FACT IT WAS WELL TO OUR W. AFTER POSITIVELY IDENTING RWY 19L; WE WERE CLRED TO A VISUAL RWY 19L AND LANDED. SHORTLY BEFORE LNDG; BELOW 1000 FT; WE RECEIVED INTERMITTENT GPWS WARNINGS. AND CONTINUED RECEIVING THESE WARNINGS AFTER EXITING RWY UNTIL TERRAIN SWITCH WAS DISARMED. AFTER STOPPING ON TXWY; WE DETERMINED THAT FMC WAS STILL SHOWING A 6 MI ERROR/DISAGREEMENT IN THE POS PAGE. RWY 1R WAS STILL SHOWING 6 MI TO E OF ACFT POS. EVEN THOUGH WE WERE CORRECTLY PROCEEDING TO RWY 1R IN VISUAL CONDITIONS; THE FMC CREATED A SIGNIFICANT ELEMENT OF DOUBT AS TO WHICH RWY WE WERE REALLY LOOKING AT; RWY 1L OR RWY 1R. SINCE I DID NOT WANT TO DSND BELOW 1700 FT WITHOUT KNOWING FOR SURE THAT WE WERE LOOKING AT CORRECT RWY; I ELECTED TO ABORT APCH AND REQUEST ANOTHER APCH. I FURTHER BELIEVE WE GOT AN ERRONEOUS GPWS WARNING BECAUSE THE AIRPLANE THOUGHT WE WERE LNDG OFF ARPT; AND DID NOT KNOW WHERE WE WERE. AS IT TURNS OUT; FMC WAS IN ERROR. THE AIRPLANE HAS A HISTORY OF FMC PROBS. ALSO RECEIVED SEVERAL 'ERROR' CODES: 'PURGE UPDATES ON FMC' FROM L FMC; AFTER ON GND IN IAD. FMC AND MAP SHIFT WAS WRITTEN UP. HAD WE BEEN IN ANYTHING LESS THAN VISUAL CONDITIONS; THIS COULD HAVE BEEN A SERIOUS PROB. EVEN WHILE RECEIVING ILS TO RWY 19L; FMC CONTINUED TO SHOW RWY COURSE 6 MI E OF ACTUAL LOC. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THE REPORTER HAS RECEIVED NO FEEDBACK FROM MAINT REGARDING THE ANOMALY. HE STATED THERE WAS SOME NOTAM REGARDING ECG VOR THAT HAD ESCAPED THEIR NOTICE WHICH MAY HAVE AFFECTED THE IRU UPDATING UPON ARRIVING OVERLAND. THE PROBLEM; HOWEVER; WAS THAT THE POSITION APPEARED ACCURATE INITIALLY AND THE MAP SHIFT RESULTED IN A SIGNIFICANT ERROR; RATHER THAN A MORE PRECISE POSITION AS WOULD BE EXPECTED FROM AN IRU UPDATE. THE EGPWS WARNINGS WOULD HAVE BEEN A SIGNIFICANT ISSUE HAD THEY NOT HAD VISUAL CONTACT WITH THE GROUND. EVEN MORE POTENTIALLY DISTRESSING WAS THAT THEY HAD LITTLE RESERVE FUEL TO ALLOW FOR TROUBLESHOOTING HAD THEY BEEN FORCED TO PERFORM A GAR DUE TO THE TERRAIN WARNINGS AS IS REQUIRED WHEN IMC.

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