Narrative:

We had flown the aircraft 2 legs without any problems prior to this leg. During programming of the FMGS, I noticed that there was no map display in plan mode of the first officer's navigation display. Also, 'autoplt #2 inoperative' was displayed on the status page. Maintenance was advised and they performed what I believe was an FMGS #2 reset. After normal engine starts, an ECAM message 'autothrottle inoperative' appeared. We elected to start our taxi (we were blocking inbound aircraft into the ramp) and troubleshot the problem. What followed next were several very busy mins as I was reviewing the aircraft handbook, checking the QRH, talking with ground control, and talking with maintenance over the radio. During this time, the runways were changed for departure and the workload being what it was, the new runway was not entered into the mcdu. With the advice of maintenance, the autothrottle problem was fixed, the before takeoff checklist was completed and we were cleared for takeoff. With the advance of power on the takeoff roll, an ECAM message 'FMGS navigation position discrepancy' appeared. Having problems with FMGS #2 at the gate followed by a reset then further problems with the autothrottle on taxi, we were not too sure what was wrong with the FMGS when the new ECAM message appeared and the captain made the decision to abort the takeoff at approximately 80 KTS. We cleared the runway and returned to the gate without incident. At the gate, while discussing the situation, it was discovered the new runway was never entered into the mcdu. This caused the ECAM message to appear.

Related reports:

Google
 

Original NASA ASRS Text

Title: AIRBUS 319 FLC ABORTED TKOF DUE TO AN FMS NAV ECAM MESSAGE WHICH TURNED OUT TO BE CAUSED BY THE MASTER NAV COMPUTER DATA WAS NOT PROVIDED WITH THE NEW TKOF RWY ASSIGNMENT.

Narrative: WE HAD FLOWN THE ACFT 2 LEGS WITHOUT ANY PROBS PRIOR TO THIS LEG. DURING PROGRAMMING OF THE FMGS, I NOTICED THAT THERE WAS NO MAP DISPLAY IN PLAN MODE OF THE FO'S NAV DISPLAY. ALSO, 'AUTOPLT #2 INOP' WAS DISPLAYED ON THE STATUS PAGE. MAINT WAS ADVISED AND THEY PERFORMED WHAT I BELIEVE WAS AN FMGS #2 RESET. AFTER NORMAL ENG STARTS, AN ECAM MESSAGE 'AUTOTHROTTLE INOP' APPEARED. WE ELECTED TO START OUR TAXI (WE WERE BLOCKING INBOUND ACFT INTO THE RAMP) AND TROUBLESHOT THE PROB. WHAT FOLLOWED NEXT WERE SEVERAL VERY BUSY MINS AS I WAS REVIEWING THE ACFT HANDBOOK, CHKING THE QRH, TALKING WITH GND CTL, AND TALKING WITH MAINT OVER THE RADIO. DURING THIS TIME, THE RWYS WERE CHANGED FOR DEP AND THE WORKLOAD BEING WHAT IT WAS, THE NEW RWY WAS NOT ENTERED INTO THE MCDU. WITH THE ADVICE OF MAINT, THE AUTOTHROTTLE PROB WAS FIXED, THE BEFORE TKOF CHKLIST WAS COMPLETED AND WE WERE CLRED FOR TKOF. WITH THE ADVANCE OF PWR ON THE TKOF ROLL, AN ECAM MESSAGE 'FMGS NAV POS DISCREPANCY' APPEARED. HAVING PROBS WITH FMGS #2 AT THE GATE FOLLOWED BY A RESET THEN FURTHER PROBS WITH THE AUTOTHROTTLE ON TAXI, WE WERE NOT TOO SURE WHAT WAS WRONG WITH THE FMGS WHEN THE NEW ECAM MESSAGE APPEARED AND THE CAPT MADE THE DECISION TO ABORT THE TKOF AT APPROX 80 KTS. WE CLRED THE RWY AND RETURNED TO THE GATE WITHOUT INCIDENT. AT THE GATE, WHILE DISCUSSING THE SIT, IT WAS DISCOVERED THE NEW RWY WAS NEVER ENTERED INTO THE MCDU. THIS CAUSED THE ECAM MESSAGE TO APPEAR.

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.