Narrative:

We were told to taxi to runway 36R for takeoff. 1 aircraft ahead of us took off on runway 36R and we were expected to go next on the same runway. All checklists had been completed in anticipation of takeoff. Instead of being cleared for takeoff as expected; controller cleared us to cross runway 36R and taxi into position and hold on runway 36L. I asked pm to verify the clearance was position and hold and not hold short. I also asked pm to change the runway. I knew from the performance data which I reviewed at the gate that we were legal on either runway and that the v-spds were almost identical (within 1 KT of each other). I glanced down at my mcdu screen and verified that runway 36L was showing (on flight plan page). Before we even came to a stopped position on the runway; we were cleared for takeoff and after positioning throttles to flex; got an ECAM warning. Since we were so slow; I was going to discontinue takeoff but; pm advised warning regarded flex temperature so we decided to go to toga. During acceleration; I noticed that the v-spds were not showing and asked pm to call out speeds from mcdu. After takeoff; had to turn on autothrottle system and continued normally from that point on. I remembered reading about this situation in a recent bulletin and we referred to it to review what had occurred. I assume pm had changed performance page when I had asked him to change the runway and when I had checked the flight plan page. Also; the taxi distance between the 2 runways is short and much needed to be done in that short span of time. In addition; in retrospect; I may have been task loading the pm by asking him to do data entry; reconfirm clearance; etc in such a short time. Lastly; in the latest integration of FMS2+; the warning to check takeoff data after a runway change has been removed. This was an important barrier. Had this not changed; this situation may have been caught when I glanced down at the mcdu to verify the runway change. In the next update to the FMS software; it would be helpful to restore the warning.

Related reports:

Google
 

Original NASA ASRS Text

Title: AN A319 ASSIGNED RUNWAY 36R AS THEY TAXIED ONTO 36L DID NOT FULLY RE-PROGRAM THE FMGC FOR THE NEW RUNWAY. AS A RESULT THE CAPTAIN HAD NO AIRSPEED BUGS NOR PROPER REDUCED TAKEOFF THRUST.

Narrative: WE WERE TOLD TO TAXI TO RWY 36R FOR TKOF. 1 ACFT AHEAD OF US TOOK OFF ON RWY 36R AND WE WERE EXPECTED TO GO NEXT ON THE SAME RWY. ALL CHKLISTS HAD BEEN COMPLETED IN ANTICIPATION OF TKOF. INSTEAD OF BEING CLRED FOR TKOF AS EXPECTED; CTLR CLRED US TO CROSS RWY 36R AND TAXI INTO POS AND HOLD ON RWY 36L. I ASKED PM TO VERIFY THE CLRNC WAS POS AND HOLD AND NOT HOLD SHORT. I ALSO ASKED PM TO CHANGE THE RWY. I KNEW FROM THE PERFORMANCE DATA WHICH I REVIEWED AT THE GATE THAT WE WERE LEGAL ON EITHER RWY AND THAT THE V-SPDS WERE ALMOST IDENTICAL (WITHIN 1 KT OF EACH OTHER). I GLANCED DOWN AT MY MCDU SCREEN AND VERIFIED THAT RWY 36L WAS SHOWING (ON FLT PLAN PAGE). BEFORE WE EVEN CAME TO A STOPPED POS ON THE RWY; WE WERE CLRED FOR TKOF AND AFTER POSITIONING THROTTLES TO FLEX; GOT AN ECAM WARNING. SINCE WE WERE SO SLOW; I WAS GOING TO DISCONTINUE TKOF BUT; PM ADVISED WARNING REGARDED FLEX TEMP SO WE DECIDED TO GO TO TOGA. DURING ACCELERATION; I NOTICED THAT THE V-SPDS WERE NOT SHOWING AND ASKED PM TO CALL OUT SPDS FROM MCDU. AFTER TKOF; HAD TO TURN ON AUTOTHROTTLE SYS AND CONTINUED NORMALLY FROM THAT POINT ON. I REMEMBERED READING ABOUT THIS SITUATION IN A RECENT BULLETIN AND WE REFERRED TO IT TO REVIEW WHAT HAD OCCURRED. I ASSUME PM HAD CHANGED PERFORMANCE PAGE WHEN I HAD ASKED HIM TO CHANGE THE RWY AND WHEN I HAD CHKED THE FLT PLAN PAGE. ALSO; THE TAXI DISTANCE BTWN THE 2 RWYS IS SHORT AND MUCH NEEDED TO BE DONE IN THAT SHORT SPAN OF TIME. IN ADDITION; IN RETROSPECT; I MAY HAVE BEEN TASK LOADING THE PM BY ASKING HIM TO DO DATA ENTRY; RECONFIRM CLRNC; ETC IN SUCH A SHORT TIME. LASTLY; IN THE LATEST INTEGRATION OF FMS2+; THE WARNING TO CHK TKOF DATA AFTER A RWY CHANGE HAS BEEN REMOVED. THIS WAS AN IMPORTANT BARRIER. HAD THIS NOT CHANGED; THIS SITUATION MAY HAVE BEEN CAUGHT WHEN I GLANCED DOWN AT THE MCDU TO VERIFY THE RWY CHANGE. IN THE NEXT UPDATE TO THE FMS SOFTWARE; IT WOULD BE HELPFUL TO RESTORE THE WARNING.

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.