Narrative:

After aircraft push from gate, initial taxi clearance from ground control was to taxi to runway 9L via txwys a, A6, and J. This is a relatively short taxi, but we were 4TH in line for the runway. During this time, we were instructed by ground to monitor tower on frequency 126.9. Since the before takeoff checklist was being performed and we were 4TH in line for runway 9L, I did not immediately change the radio to the new frequency. About 30 seconds later, ground again told us to monitor frequency 126.9, at which point I changed channels. Once on tower frequency, tower asked why we weren't turning right on taxiway west for runway 4L. I surmised tower must have given these change of runway instructions previously while we were still on ground (121.75). In the airbus the computers must be reprogrammed for the new runway, as well as new takeoff data calculated, flap settings and takeoff speeds. The length of taxiway west to runway 4L is only about 200 yards. While these computations were being performed, tower cleared us for position and hold runway 4L. At this time, I thought tower gave a new tower frequency of 127.4 for takeoff. I asked the captain if he concurred, and he did, so I answered and changed frequency. While on the runway awaiting takeoff clearance, I heard departure talking to an aircraft with a similar call sign to ours. I then realized we were on a wrong frequency and went back to tower on 126.9. Tower asked where we had been and said he had given takeoff clearance to us, but since we had not acknowledged he had to send one aircraft around. Tower canceled our takeoff clearance, but then immediately reissued, 'cleared for takeoff runway 4L, heading 070 degrees,' at which point takeoff occurred without incident. I feel tower needs to understand that when reissuing or changing runways for an automated aircraft like the airbus, a lot needs to be accomplished in a very short time and that needs to be compensated for during their expedited operations. Supplemental information from acn 434472: approaching taxiway west on taxiway J we were told (a bit curtly) to turn right on taxiway west for runway 4L. This was the first time we had heard any mention of runway 4L. We turned on taxiway west and the first officer began to enter the new data and re-do the takeoff checklist, finishing it as we taxied into position. About that time we thought we heard a new frequency for us. What I thought I heard was a new departure control frequency assignment (127.4), which didn't surprise me because it was sunday and they often combine departure sectors on wkends. What I think happened next was that the first officer, relatively inexperienced in air carrier operations and this airplane and ord in particular, somehow thought this new frequency was given because of the last min runway change, and thought it was runway 4L's frequency, and so changed to it. He even asked me if he'd gotten it correct ('127.4?'). I nodded yes, meaning I had heard the same 127.4. He apparently took that to mean that I had also thought that we were to change to that frequency now, which he did. When he changed the frequency, I thought he was merely entering it in the standby frequency window so that it would be ready to switch to when airborne. The result was that we held on the runway for a min or so, effectively 'NORDO,' causing another aircraft to have to go around. An aircraft holding short on taxiway east caught my attention by flashing his landing light, and we began looking around the cockpit for something awry, and found the wrong frequency set. We put the correct one in and checked in with tower (and got a snide remark back). The confign at the time at ord was: departing runways 4L, 9L, 32L and 14L. Landing runways 4L, 4R, 9L and (I think) runway 9R. This type and tempo of operation leaves virtually no room for error. That we have as few as we do is a credit to both the controllers and air crews who (usually) perform at their very best. It's just too bad airports like ord have to operate at the edge of the envelope so much of the time.

Google
 

Original NASA ASRS Text

Title: AN A320 IN POS AND HOLDING FOR TKOF AT ORD RWY 4L GUARDS THE WRONG FREQ WITH THE TWR. CTLR THEN ISSUED A GAR TO AN ACFT ON SHORT FINAL.

Narrative: AFTER ACFT PUSH FROM GATE, INITIAL TAXI CLRNC FROM GND CTL WAS TO TAXI TO RWY 9L VIA TXWYS A, A6, AND J. THIS IS A RELATIVELY SHORT TAXI, BUT WE WERE 4TH IN LINE FOR THE RWY. DURING THIS TIME, WE WERE INSTRUCTED BY GND TO MONITOR TWR ON FREQ 126.9. SINCE THE BEFORE TKOF CHKLIST WAS BEING PERFORMED AND WE WERE 4TH IN LINE FOR RWY 9L, I DID NOT IMMEDIATELY CHANGE THE RADIO TO THE NEW FREQ. ABOUT 30 SECONDS LATER, GND AGAIN TOLD US TO MONITOR FREQ 126.9, AT WHICH POINT I CHANGED CHANNELS. ONCE ON TWR FREQ, TWR ASKED WHY WE WEREN'T TURNING R ON TXWY W FOR RWY 4L. I SURMISED TWR MUST HAVE GIVEN THESE CHANGE OF RWY INSTRUCTIONS PREVIOUSLY WHILE WE WERE STILL ON GND (121.75). IN THE AIRBUS THE COMPUTERS MUST BE REPROGRAMMED FOR THE NEW RWY, AS WELL AS NEW TKOF DATA CALCULATED, FLAP SETTINGS AND TKOF SPDS. THE LENGTH OF TXWY W TO RWY 4L IS ONLY ABOUT 200 YARDS. WHILE THESE COMPUTATIONS WERE BEING PERFORMED, TWR CLRED US FOR POS AND HOLD RWY 4L. AT THIS TIME, I THOUGHT TWR GAVE A NEW TWR FREQ OF 127.4 FOR TKOF. I ASKED THE CAPT IF HE CONCURRED, AND HE DID, SO I ANSWERED AND CHANGED FREQ. WHILE ON THE RWY AWAITING TKOF CLRNC, I HEARD DEP TALKING TO AN ACFT WITH A SIMILAR CALL SIGN TO OURS. I THEN REALIZED WE WERE ON A WRONG FREQ AND WENT BACK TO TWR ON 126.9. TWR ASKED WHERE WE HAD BEEN AND SAID HE HAD GIVEN TKOF CLRNC TO US, BUT SINCE WE HAD NOT ACKNOWLEDGED HE HAD TO SEND ONE ACFT AROUND. TWR CANCELED OUR TKOF CLRNC, BUT THEN IMMEDIATELY REISSUED, 'CLRED FOR TKOF RWY 4L, HDG 070 DEGS,' AT WHICH POINT TKOF OCCURRED WITHOUT INCIDENT. I FEEL TWR NEEDS TO UNDERSTAND THAT WHEN REISSUING OR CHANGING RWYS FOR AN AUTOMATED ACFT LIKE THE AIRBUS, A LOT NEEDS TO BE ACCOMPLISHED IN A VERY SHORT TIME AND THAT NEEDS TO BE COMPENSATED FOR DURING THEIR EXPEDITED OPS. SUPPLEMENTAL INFO FROM ACN 434472: APCHING TXWY W ON TXWY J WE WERE TOLD (A BIT CURTLY) TO TURN R ON TXWY W FOR RWY 4L. THIS WAS THE FIRST TIME WE HAD HEARD ANY MENTION OF RWY 4L. WE TURNED ON TXWY W AND THE FO BEGAN TO ENTER THE NEW DATA AND RE-DO THE TKOF CHKLIST, FINISHING IT AS WE TAXIED INTO POS. ABOUT THAT TIME WE THOUGHT WE HEARD A NEW FREQ FOR US. WHAT I THOUGHT I HEARD WAS A NEW DEP CTL FREQ ASSIGNMENT (127.4), WHICH DIDN'T SURPRISE ME BECAUSE IT WAS SUNDAY AND THEY OFTEN COMBINE DEP SECTORS ON WKENDS. WHAT I THINK HAPPENED NEXT WAS THAT THE FO, RELATIVELY INEXPERIENCED IN ACR OPS AND THIS AIRPLANE AND ORD IN PARTICULAR, SOMEHOW THOUGHT THIS NEW FREQ WAS GIVEN BECAUSE OF THE LAST MIN RWY CHANGE, AND THOUGHT IT WAS RWY 4L'S FREQ, AND SO CHANGED TO IT. HE EVEN ASKED ME IF HE'D GOTTEN IT CORRECT ('127.4?'). I NODDED YES, MEANING I HAD HEARD THE SAME 127.4. HE APPARENTLY TOOK THAT TO MEAN THAT I HAD ALSO THOUGHT THAT WE WERE TO CHANGE TO THAT FREQ NOW, WHICH HE DID. WHEN HE CHANGED THE FREQ, I THOUGHT HE WAS MERELY ENTERING IT IN THE STANDBY FREQ WINDOW SO THAT IT WOULD BE READY TO SWITCH TO WHEN AIRBORNE. THE RESULT WAS THAT WE HELD ON THE RWY FOR A MIN OR SO, EFFECTIVELY 'NORDO,' CAUSING ANOTHER ACFT TO HAVE TO GO AROUND. AN ACFT HOLDING SHORT ON TXWY E CAUGHT MY ATTN BY FLASHING HIS LNDG LIGHT, AND WE BEGAN LOOKING AROUND THE COCKPIT FOR SOMETHING AWRY, AND FOUND THE WRONG FREQ SET. WE PUT THE CORRECT ONE IN AND CHKED IN WITH TWR (AND GOT A SNIDE REMARK BACK). THE CONFIGN AT THE TIME AT ORD WAS: DEPARTING RWYS 4L, 9L, 32L AND 14L. LNDG RWYS 4L, 4R, 9L AND (I THINK) RWY 9R. THIS TYPE AND TEMPO OF OP LEAVES VIRTUALLY NO ROOM FOR ERROR. THAT WE HAVE AS FEW AS WE DO IS A CREDIT TO BOTH THE CTLRS AND AIR CREWS WHO (USUALLY) PERFORM AT THEIR VERY BEST. IT'S JUST TOO BAD ARPTS LIKE ORD HAVE TO OPERATE AT THE EDGE OF THE ENVELOPE SO MUCH OF THE TIME.

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.