Narrative:

I had already calculated my cyyz-[us destination] flight plan; but had not added an alternate in the appropriate page. I then added the alternate to the flight by selecting it in drop down menu. I failed to click re-compute; however; so the alternate showed on the screen but was not actually calculated into the flight plan. Neither my dispatch OJT trainer nor I noticed that alternate burn showed 0 on the flight plan. We released and sent the flight plan on time. The crew sent an ACARS message enroute to advise us they had no fuel for the alternate. We attempted an inflight revision/addition of alternate based on current position; payload; and fuel on board; but the aircraft had insufficient fuel on board to do so. By artificially inflating the fuel on board number; we were finally able to get the plan to run; just to give the crew burn information; however; flight was below 10;000 ft by then; so we opted not to send the information. Destination weather was approximately 1 statute mile at the time so we monitored the flight until it landed in its destination. We had the burn information ready to send if the flight missed approach in their destination. When flight landed; we sent ACARS advising crew we were filing a safety report and recommending they file also. [This was my] first day of OJT. I have worked the system in the past; but had forgotten about this particular 'gotcha.' better time management and closer attention to detail on my part will prevent this error from occurring again. One of the other dispatchers also pointed out the alternate burn column; which provides a quick reference during high workload situations and is a good 'double check.' [I needed better awareness] of how the system works; was not aware that 'release' did not recalculate plan to capture all information. Better time management and attention to detail in spite of time pressure.

Google
 

Original NASA ASRS Text

Title: A Dispatcher undergoing OJT failed to take the step required to program fuel for an alternate airport that was required for dispatch. The flight crew discovered the error only after departure. The destination airport was the most viable airport to resolve the issue at the time it was discovered. It landed safely.

Narrative: I had already calculated my CYYZ-[U.S. destination] flight plan; but had not added an alternate in the appropriate page. I then added the alternate to the flight by selecting it in drop down menu. I failed to click re-compute; however; so the alternate showed on the screen but was not actually calculated into the flight plan. Neither my Dispatch OJT trainer nor I noticed that alternate burn showed 0 on the flight plan. We released and sent the flight plan on time. The crew sent an ACARS message enroute to advise us they had no fuel for the alternate. We attempted an inflight revision/addition of alternate based on current position; payload; and fuel on board; but the aircraft had insufficient fuel on board to do so. By artificially inflating the fuel on board number; we were finally able to get the plan to run; just to give the crew burn information; however; flight was below 10;000 FT by then; so we opted not to send the information. Destination weather was approximately 1 statute mile at the time so we monitored the flight until it landed in its destination. We had the burn information ready to send if the flight missed approach in their destination. When flight landed; we sent ACARS advising crew we were filing a safety report and recommending they file also. [This was my] first day of OJT. I have worked the system in the past; but had forgotten about this particular 'gotcha.' Better time management and closer attention to detail on my part will prevent this error from occurring again. One of the other dispatchers also pointed out the alternate burn column; which provides a quick reference during high workload situations and is a good 'double check.' [I needed better awareness] of how the system works; was not aware that 'release' did not recalculate plan to capture all information. Better time management and attention to detail in spite of time pressure.

Data retrieved from NASA's ASRS site 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.