SAAB 340 AT MSP CLRED FOR TKOF ON RWY 30R. WHEN THE DEPARTING SAAB 340 REACHED 90 KIAS; TWR INSTRUCTED THE CREW TO ABORT DUE TO A DC9 XING NEAR THE INTXN OF RWY 22.

Narrative

ACR X WAS CLRED FOR TKOF ON RWY 30R AT MSP AT INTXN E1. ON THE TKOF ROLL AT APPROX 90 KTS; AN 'ABORT; ABORT' CALL WAS GIVEN FROM MSP TWR; FREQ 123.95. APPROX 1000-1500 FT DOWN THE RWY (IN FRONT OF THE ABORTING SF340) WAS AN ACR Y DC9 THAT HAD TAXIED FROM INTXN C AT RWY 30R; ONTO RWY 30R HDG ACROSS RWY 30R AND RWY 22 INTXN. SF340 ABORTED AND CLRED ACTIVE RWY AT INTXN E6. TWR CLRED BOTH ACFT OFF OF RWY. UPON CLRING; BOTH ACFT STAYED WITH TWR FREQ. TWR STATED THAT THERE WAS A TEMPORARY 'OUTAGE' WITH GND CTL FREQ. FACTORS I BELIEVE LED TO THIS: 1) FREQUENT CLUTTER AT THIS PARTICULAR TIME OF NIGHT. ACR'S INEPT SCHEDULING OF PUSHING A LARGE NUMBER OF ACFT FROM THE PERIOD OF XA15 TO XC15 PLACES FAR TOO GREAT A BURDEN ON MSP GND METERING (133.57) AND N GND (121.8). 2) FAILURE OF DC9 CREW TO USE SIMPLE VISUAL SCAN TO ENSURE ACTIVE RWY IS CLR PRIOR TO XING IT. 3) UNSURE WHAT REALLY HAPPENED BTWN GND/TWR FREQ 'OUTAGE.' 4) CONGESTION AT TXWY E; RWY 22; RWY 30R INTXN DUE TO THE PARTIAL CLOSURE OF RWY 30L AND RWY 12R AND ASSOCIATED TXWYS. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR STATED DC9 WAS ON GND CTL FREQ EVEN THOUGH THE LCL CTLR ATTEMPTED TO ESTABLISH CONTACT WITH THE ACFT ON LCL FREQ. AFTER ABORTING THEIR TKOF; THE RPTR SAID THEY WERE SWITCHED OVER TO A DIFFERENT GND CTL FREQ WHICH ALSO HAD STATIC AND HARD TO UNDERSTAND. PLTS WERE ABLE TO COMMUNICATE WITH EACH OTHER; HOWEVER.