Narrative:

Air carrier X was cleared for takeoff on runway 30R at msp at intersection E1. On the takeoff roll at approximately 90 KTS, an 'abort, abort' call was given from msp tower, frequency 123.95. Approximately 1000-1500 ft down the runway (in front of the aborting SF340) was an air carrier Y DC9 that had taxied from intersection C at runway 30R, onto runway 30R heading across runway 30R and runway 22 intersection. SF340 aborted and cleared active runway at intersection E6. Tower cleared both aircraft off of runway. Upon clearing, both aircraft stayed with tower frequency. Tower stated that there was a temporary 'outage' with ground control frequency. Factors I believe led to this: 1) frequent clutter at this particular time of night. Air carrier's inept scheduling of pushing a large number of aircraft from the period of XA15 to XC15 places far too great a burden on msp ground metering (133.57) and north ground (121.8). 2) failure of DC9 crew to use simple visual scan to ensure active runway is clear prior to crossing it. 3) unsure what really happened between ground/tower frequency 'outage.' 4) congestion at taxiway east, runway 22, runway 30R intersection due to the partial closure of runway 30L and runway 12R and associated txwys. Callback conversation with reporter revealed the following information: reporter stated DC9 was on ground control frequency even though the local controller attempted to establish contact with the aircraft on local frequency. After aborting their takeoff, the reporter said they were switched over to a different ground control frequency which also had static and hard to understand. Pilots were able to communicate with each other, however.

Related reports:

Google
 

Original NASA ASRS Text

Title: 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.

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.