Narrative:

I was working the south local position (landing/departing runway 28; departing runway 22L) at the center tower at chicago O'hare. I cleared an A319 to land on runway 28 when the A319 was at the marker. I issued an E170 instructions to 'line up and wait (luaw)' on runway 22L. The E170 read back the luaw instructions; soon after it appeared that the E170 had a stuck mic. Without success; I attempted to establish communications with the E170. I attempted to locate the VHF emergency frequency (121.5) on the control panel; but was not able to locate it. I then issued go-around instructions several times to the A319 who did not hear my instructions due to the E170's stuck mic. The A319 landed on runway 28 with the E170 still in position on runway 22L. Another air carrier (#2 for runway 28) was also at this time attempting to contact me on 120.75 for a landing clearance for runway 28. I issued the other air carrier go-around instructions when the other air carrier was on approximately a 2.5 mile final. The other air carrier complied with the missed approach instructions. A third aircraft was on final for runway 28. The third aircraft could not establish communications with me on 120.75; so the third aircraft contacted 3RD local on 132.7. The 3RD local controller stated that he 'had the third aircraft'. I then heard 3RD local then clear the third aircraft to land on runway 28. As that was occurring; after repeated attempted to contact the E170; I re-established communications with the E170. I instructed the E170 to taxi straight ahead on runway 22L; and then exit at S4 and to hold short of runway 28. The third aircraft; short final; called me on 120.75 and I issued a runway 28 landing clearance. Recommendation: have a dedicated VHF and VHF emergency frequency or 'push to talk' button on the main page of the rdvs. I had to divert too much attention trying in vain to locate the VHF emergency frequency on a page that has approximately 20 similar looking frequency selectors.

Related reports:

Google
 

Original NASA ASRS Text

Title: ORD Local Controller described a potential conflict event when traffic taxied into position experienced a 'stuck mike' requiring multiple go around instructions; the reporter indicating the RDVS required too much attention during this instance.

Narrative: I was working the South Local position (landing/departing Runway 28; departing Runway 22L) at the Center Tower at Chicago O'Hare. I cleared an A319 to land on Runway 28 when the A319 was at the marker. I issued an E170 instructions to 'Line Up and Wait (LUAW)' on runway 22L. The E170 read back the LUAW instructions; soon after it appeared that the E170 had a stuck mic. Without success; I attempted to establish communications with the E170. I attempted to locate the VHF Emergency frequency (121.5) on the control panel; but was not able to locate it. I then issued go-around instructions several times to the A319 who did not hear my instructions due to the E170's stuck mic. The A319 landed on Runway 28 with the E170 still in position on Runway 22L. Another Air Carrier (#2 for Runway 28) was also at this time attempting to contact me on 120.75 for a landing clearance for Runway 28. I issued the other Air Carrier go-around instructions when the other Air Carrier was on approximately a 2.5 mile final. The other Air Carrier complied with the missed approach instructions. A third aircraft was on final for Runway 28. The third aircraft could not establish communications with me on 120.75; so the third aircraft contacted 3RD Local on 132.7. The 3RD Local Controller stated that he 'had the third aircraft'. I then heard 3RD Local then clear the third aircraft to land on Runway 28. As that was occurring; after repeated attempted to contact the E170; I re-established communications with the E170. I instructed the E170 to taxi straight ahead on Runway 22L; and then exit at S4 and to hold short of Runway 28. The third aircraft; short final; called me on 120.75 and I issued a Runway 28 landing clearance. Recommendation: have a dedicated VHF and VHF emergency frequency or 'push to talk' button on the main page of the RDVS. I had to divert too much attention trying in vain to locate the VHF emergency frequency on a page that has approximately 20 similar looking frequency selectors.

Data retrieved from NASA's ASRS site as of April 2012 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.