Narrative:

Approaching the top of descent; we got an ECAM message: 'navigation/air data computer; FM/GPS position disagreement.' while running the position disagreement checklist; we determined that our position was approximately 200 mi away from where the FMC said we were. So our navigation system was lost and we advised ATC. When we did so; they gave us clearance direct to ZZZ and a crossing restr of 11000 ft 35 mi prior to ZZZ. We became occupied with the idea of how to do that in raw data. We figured it out and made the crossing restr. We were now faced with the idea of landing on runway 29 with a headwind of 28 KTS gusting to 40 KTS. It was bumpy and we only had the localizer raw data and vectors with which to navigation. We were in clouds until approximately 1800 ft AGL. Consequently we did not get back to the position disagreement checklist and accomplish the last item which was 'egpws -- off.' we accomplished all other checklists and the position disagreement checklist with the exception of that last item. On short final in VMC the 'too low terrain -- pull up' warning went off. We knew why it was going off; because the airplane thought it was 200 mi behind us. We had a clear visual of the runway and were clearly in a position to land. We both agreed to ignore the egpws and land. Landing was uneventful. The only thing I can think of that would have prevented the mistake of not finishing that checklist is to have realized that we did not call the position disagreement checklist complete. Had I realized that then; we would have probably gone back to the checklist and found the last item.

Related reports:

Google
 

Original NASA ASRS Text

Title: DISTRACTED BY AN APPARENTLY UNASSOCIATED NAV SYSTEM PROBLEM; FLT CREW OF A300 FAILS TO DISARM THE EGPWS SYSTEM AS REQUIRED BY A SECOND ANOMALY; A FLT POS DISAGREE ECAM WARNING. THE COMBINED NAV ISSUE AND THE STILL ENGAGED EGPWS RESULTS IN AN ANOMALOUS TERRAIN WARNING ON FINAL APCH IN VMC.

Narrative: APCHING THE TOP OF DSCNT; WE GOT AN ECAM MESSAGE: 'NAV/ADC; FM/GPS POS DISAGREEMENT.' WHILE RUNNING THE POS DISAGREEMENT CHKLIST; WE DETERMINED THAT OUR POS WAS APPROX 200 MI AWAY FROM WHERE THE FMC SAID WE WERE. SO OUR NAV SYS WAS LOST AND WE ADVISED ATC. WHEN WE DID SO; THEY GAVE US CLRNC DIRECT TO ZZZ AND A XING RESTR OF 11000 FT 35 MI PRIOR TO ZZZ. WE BECAME OCCUPIED WITH THE IDEA OF HOW TO DO THAT IN RAW DATA. WE FIGURED IT OUT AND MADE THE XING RESTR. WE WERE NOW FACED WITH THE IDEA OF LNDG ON RWY 29 WITH A HEADWIND OF 28 KTS GUSTING TO 40 KTS. IT WAS BUMPY AND WE ONLY HAD THE LOC RAW DATA AND VECTORS WITH WHICH TO NAV. WE WERE IN CLOUDS UNTIL APPROX 1800 FT AGL. CONSEQUENTLY WE DID NOT GET BACK TO THE POS DISAGREEMENT CHKLIST AND ACCOMPLISH THE LAST ITEM WHICH WAS 'EGPWS -- OFF.' WE ACCOMPLISHED ALL OTHER CHKLISTS AND THE POS DISAGREEMENT CHKLIST WITH THE EXCEPTION OF THAT LAST ITEM. ON SHORT FINAL IN VMC THE 'TOO LOW TERRAIN -- PULL UP' WARNING WENT OFF. WE KNEW WHY IT WAS GOING OFF; BECAUSE THE AIRPLANE THOUGHT IT WAS 200 MI BEHIND US. WE HAD A CLR VISUAL OF THE RWY AND WERE CLEARLY IN A POS TO LAND. WE BOTH AGREED TO IGNORE THE EGPWS AND LAND. LNDG WAS UNEVENTFUL. THE ONLY THING I CAN THINK OF THAT WOULD HAVE PREVENTED THE MISTAKE OF NOT FINISHING THAT CHKLIST IS TO HAVE REALIZED THAT WE DID NOT CALL THE POS DISAGREEMENT CHKLIST COMPLETE. HAD I REALIZED THAT THEN; WE WOULD HAVE PROBABLY GONE BACK TO THE CHKLIST AND FOUND THE LAST ITEM.

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.