Narrative:

I was planning an international flight between tokyo, japan and dallas, tx. In my planning, as company policy and FARS allow, I utilized redispatch procedures. The initial destination was salt lake city, ut. After the flight was airborne, I realized that the flight would be overweight for landing at the initial destination. I contacted the flight en route and advised of a change in the initial destination. I changed it to denver, co to allow a landing weight below maximum should it not be able to continue to dallas. The contributing factors to this error were the computer's inability to provide warnings of the overweight condition at the initial destination, and the workload put on the dispatcher in an 8 hour shift.

Google
 

Original NASA ASRS Text

Title: DISPATCHER DISCOVERED A DISPATCH ERROR AFTER ACFT HAD DEPARTED WITH A RECLRNC FLT PLAN.

Narrative: I WAS PLANNING AN INTL FLT BTWN TOKYO, JAPAN AND DALLAS, TX. IN MY PLANNING, AS COMPANY POLICY AND FARS ALLOW, I UTILIZED REDISPATCH PROCS. THE INITIAL DEST WAS SALT LAKE CITY, UT. AFTER THE FLT WAS AIRBORNE, I REALIZED THAT THE FLT WOULD BE OVERWT FOR LNDG AT THE INITIAL DEST. I CONTACTED THE FLT ENRTE AND ADVISED OF A CHANGE IN THE INITIAL DEST. I CHANGED IT TO DENVER, CO TO ALLOW A LNDG WT BELOW MAX SHOULD IT NOT BE ABLE TO CONTINUE TO DALLAS. THE CONTRIBUTING FACTORS TO THIS ERROR WERE THE COMPUTER'S INABILITY TO PROVIDE WARNINGS OF THE OVERWT CONDITION AT THE INITIAL DEST, AND THE WORKLOAD PUT ON THE DISPATCHER IN AN 8 HR SHIFT.

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.