Narrative:

Due to numerous thunderstorms between alb and ord and at ord, departures had been ground stopped to ord for 2 plus hours. When we got a release to ord, we loaded passenger, pushed off gate and taxied out to runway. We then received a lengthy rerte well south of original route adding 1 hour plus to time en route. Takeoff was delayed until we checked route, estimated fuel burn. This was about 10-15 extra mins because 2 of the fixes given to us were incorrect identifiers, i.e., charleston, wv. 'Hvq' was given as 'chs,' indianapolis, ind was given as 'ind' instead of 'vhp.' local ground had to talk to center to clarify. Rertes at the end of the runway are not always uncommon. However, in this case the rerte should have been given with the release of the flight from the ground stop while we were at the gate. I'm sure the system knew the rerte required as the aircraft was released from the ground stop. By providing this information at the gate we could check with our dispatcher for additional fuel burn, the need to add fuel, passenger connections, operational needs, and most importantly whether the flight crew was able to safely complete the new flight because of factors such as an already long duty day and amount off flight time already flown during the day. This was the case with us on this day. Had I known at the gate of the delays and rerouting adding a couple more hours onto our day I might have canceled the flight or elected to continue safely. This timely dissemination of information allows for a better, safer, and efficient operation.

Google
 

Original NASA ASRS Text

Title: FLC RECEIVED RERTE CLRNC AFTER TAXI OUT FROM GATE. 10-15 MIN DELAY TOOK PLACE PRIOR TO TKOF WHILE FLC VERIFIED NEW ROUTING AND FUEL CAPABILITY.

Narrative: DUE TO NUMEROUS TSTMS BTWN ALB AND ORD AND AT ORD, DEPS HAD BEEN GND STOPPED TO ORD FOR 2 PLUS HRS. WHEN WE GOT A RELEASE TO ORD, WE LOADED PAX, PUSHED OFF GATE AND TAXIED OUT TO RWY. WE THEN RECEIVED A LENGTHY RERTE WELL S OF ORIGINAL RTE ADDING 1 HR PLUS TO TIME ENRTE. TKOF WAS DELAYED UNTIL WE CHKED RTE, ESTIMATED FUEL BURN. THIS WAS ABOUT 10-15 EXTRA MINS BECAUSE 2 OF THE FIXES GIVEN TO US WERE INCORRECT IDENTIFIERS, I.E., CHARLESTON, WV. 'HVQ' WAS GIVEN AS 'CHS,' INDIANAPOLIS, IND WAS GIVEN AS 'IND' INSTEAD OF 'VHP.' LCL GND HAD TO TALK TO CTR TO CLARIFY. RERTES AT THE END OF THE RWY ARE NOT ALWAYS UNCOMMON. HOWEVER, IN THIS CASE THE RERTE SHOULD HAVE BEEN GIVEN WITH THE RELEASE OF THE FLT FROM THE GND STOP WHILE WE WERE AT THE GATE. I'M SURE THE SYS KNEW THE RERTE REQUIRED AS THE ACFT WAS RELEASED FROM THE GND STOP. BY PROVIDING THIS INFO AT THE GATE WE COULD CHK WITH OUR DISPATCHER FOR ADDITIONAL FUEL BURN, THE NEED TO ADD FUEL, PAX CONNECTIONS, OPERATIONAL NEEDS, AND MOST IMPORTANTLY WHETHER THE FLC WAS ABLE TO SAFELY COMPLETE THE NEW FLT BECAUSE OF FACTORS SUCH AS AN ALREADY LONG DUTY DAY AND AMOUNT OFF FLT TIME ALREADY FLOWN DURING THE DAY. THIS WAS THE CASE WITH US ON THIS DAY. HAD I KNOWN AT THE GATE OF THE DELAYS AND REROUTING ADDING A COUPLE MORE HRS ONTO OUR DAY I MIGHT HAVE CANCELED THE FLT OR ELECTED TO CONTINUE SAFELY. THIS TIMELY DISSEMINATION OF INFO ALLOWS FOR A BETTER, SAFER, AND EFFICIENT OP.

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.