 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
The dispatcher's first three releases were in error due to automatic modification made by the computerized dispatch system.
| Attributes | |
| ACN | 1089697 |
| Time | |
| Date | 201305 |
| Aircraft 1 | |
| Make Model Name | Commercial Fixed Wing |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Parked |
| Flight Plan | IFR |
| Person 1 | |
| Function | Dispatcher |
| Qualification | Dispatch Dispatcher |
| Events | |
| Anomaly | No Specific Anomaly Occurred All Types |
Narrative:
The computer autocalculated routes for a flight to sfo. I created release 1 for the flight one and a half hours later with the understanding that the computer autocalculates 4 hours prior to scheduled departure time. The flight was scheduled to depart an hour and a half later. The first release included an optimized route around a meso-scale weather system in the midwest region and had sjc as an alternate. The captain called to increase fuel; so release 2 was generated for the fuel request. Afterwards; I noticed the alternate was removed; so a third release was submitted with fuel and sjc added to once again. The captain then called back to report the route on the last two releases did not match the first or flight plan filed with ATC. I generated release 4 to match the original route on the ATC strip; fuel; and alternate I believe the computer autocalculated the release twice; thus changing my optimized route and removing my alternate. Had the captain not caught the discrepancy; the route would have been dangerous and the release would have been illegal.
Original NASA ASRS Text
Title: The Dispatcher's first three releases were in error due to automatic modification made by the computerized dispatch system.
Narrative: The computer autocalculated routes for a flight to SFO. I created release 1 for the flight one and a half hours later with the understanding that the computer autocalculates 4 hours prior to scheduled departure time. The flight was scheduled to depart an hour and a half later. The first release included an optimized route around a meso-scale weather system in the Midwest Region and had SJC as an alternate. The Captain called to increase fuel; so release 2 was generated for the fuel request. Afterwards; I noticed the alternate was removed; so a third release was submitted with fuel and SJC added to once again. The Captain then called back to report the route on the last two releases did not match the first or flight plan filed with ATC. I generated release 4 to match the original route on the ATC strip; fuel; and alternate I believe the computer autocalculated the release twice; thus changing my optimized route and removing my alternate. Had the Captain not caught the discrepancy; the route would have been dangerous and the release would have been illegal.
Data retrieved from NASA's ASRS site as of July 2013 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.