Narrative:

Taxied out to runway 18 in dfw and had a problem with the passenger count. Got that resolved and requested new load. Tower instructed us to go into position and hold as the data came up over ACARS. Traffic was to cross downfield and, since we were to follow a heavy 767, we figured we had enough time to enter the data in the different boxes. Not!! We had to taxi off the runway and get back in line because the takeoff data had changed too much and we had to recompute. Moral of the story is not to outguess the system and to only be ready for takeoff when you're ready.

Google
 

Original NASA ASRS Text

Title: SLOW RECEPTION AND INSERTION OF LOAD INFO CAUSES THE RPTR TO LEAVE THE RWY.

Narrative: TAXIED OUT TO RWY 18 IN DFW AND HAD A PROB WITH THE PAX COUNT. GOT THAT RESOLVED AND REQUESTED NEW LOAD. TWR INSTRUCTED US TO GO INTO POS AND HOLD AS THE DATA CAME UP OVER ACARS. TFC WAS TO CROSS DOWNFIELD AND, SINCE WE WERE TO FOLLOW A HVY 767, WE FIGURED WE HAD ENOUGH TIME TO ENTER THE DATA IN THE DIFFERENT BOXES. NOT!! WE HAD TO TAXI OFF THE RWY AND GET BACK IN LINE BECAUSE THE TKOF DATA HAD CHANGED TOO MUCH AND WE HAD TO RECOMPUTE. MORAL OF THE STORY IS NOT TO OUTGUESS THE SYS AND TO ONLY BE READY FOR TKOF WHEN YOU'RE READY.

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.