Narrative:

Cause: flight computer down/incorrect decision by msp service manager. Flight iodd lax msp estimated time of arrival XX02. Iodd msp lgw estimated time of departure XX30. Since iodd inbound was due in before iodd outbound was to depart, iodd outbound was not filed as iodd-north. Msp sp XX23 -X mc overcast 1/2 F R29 lvr 30v35. Iodd inbound held for approximately 20 mins. The msp service manager in charge of iodd outbound was told to hold the flight until iodd inbound was in the gate. During all this time the flight computer system was either down or extremely delayed in response time (the 3RD time this week). While I was trying to compute a manual mgl on iodd the load agent called to notify us iodd pushed from the gate. I instructed the agent to contact the flight to remain in the gate. I also tried to contact the flight via ACARS. Since the computer was down this did not work. I also contacted the gate agent and adjacent gates but could not get through due busy signals and holding. I then contacted msp tower but was put on hold. During XX39 through XX43 there were 2 iodd flts taxiing at msp. The load agent called to notify me that he was unable to contact iodd outbound on ground frequency. I then called the gate for inbound and was notified the flight was in the gate. Again during this time assistance was not available from other dispatchers and chiefs. They were too busy with their own problems due to the flight computer being down. After further investigation it was found that the msp service manager in charge of iodd outbound made the decision to push the flight against instructions to do so.

Related reports:

Google
 

Original NASA ASRS Text

Title: DISPATCH HAS PROBLEM WITH EARLY RELEASE OF ACFT WITH EXACT CALL SIGN AS ARRIVING ACFT. 2 SAME IDENT ACFT TAXIING AT SAME TIME.

Narrative: CAUSE: FLT COMPUTER DOWN/INCORRECT DECISION BY MSP SVC MGR. FLT IODD LAX MSP ESTIMATED TIME OF ARR XX02. IODD MSP LGW ESTIMATED TIME OF DEP XX30. SINCE IODD INBOUND WAS DUE IN BEFORE IODD OUTBOUND WAS TO DEPART, IODD OUTBOUND WAS NOT FILED AS IODD-N. MSP SP XX23 -X MC OVCST 1/2 F R29 LVR 30V35. IODD INBOUND HELD FOR APPROX 20 MINS. THE MSP SVC MGR IN CHARGE OF IODD OUTBOUND WAS TOLD TO HOLD THE FLT UNTIL IODD INBOUND WAS IN THE GATE. DURING ALL THIS TIME THE FLT COMPUTER SYS WAS EITHER DOWN OR EXTREMELY DELAYED IN RESPONSE TIME (THE 3RD TIME THIS WK). WHILE I WAS TRYING TO COMPUTE A MANUAL MGL ON IODD THE LOAD AGENT CALLED TO NOTIFY US IODD PUSHED FROM THE GATE. I INSTRUCTED THE AGENT TO CONTACT THE FLT TO REMAIN IN THE GATE. I ALSO TRIED TO CONTACT THE FLT VIA ACARS. SINCE THE COMPUTER WAS DOWN THIS DID NOT WORK. I ALSO CONTACTED THE GATE AGENT AND ADJACENT GATES BUT COULD NOT GET THROUGH DUE BUSY SIGNALS AND HOLDING. I THEN CONTACTED MSP TWR BUT WAS PUT ON HOLD. DURING XX39 THROUGH XX43 THERE WERE 2 IODD FLTS TAXIING AT MSP. THE LOAD AGENT CALLED TO NOTIFY ME THAT HE WAS UNABLE TO CONTACT IODD OUTBOUND ON GND FREQ. I THEN CALLED THE GATE FOR INBOUND AND WAS NOTIFIED THE FLT WAS IN THE GATE. AGAIN DURING THIS TIME ASSISTANCE WAS NOT AVAILABLE FROM OTHER DISPATCHERS AND CHIEFS. THEY WERE TOO BUSY WITH THEIR OWN PROBLEMS DUE TO THE FLT COMPUTER BEING DOWN. AFTER FURTHER INVESTIGATION IT WAS FOUND THAT THE MSP SVC MGR IN CHARGE OF IODD OUTBOUND MADE THE DECISION TO PUSH THE FLT AGAINST INSTRUCTIONS TO DO SO.

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.