Narrative:

We contacted iad ground on 121.9 and received clearance to taxi to runway 30. While approaching W2, 2 aircraft in front of us were holding short of that taxiway. When they continued their taxi without us hearing ATC to give them any instructions, we supposed that ATC forgot to assign us another frequency (132.45). Sure enough, when we monitored both 121.9 and 132.45, we heard ATC calling us and cleared us to continue on W2 for runway 30 (no hold short instructions were issued at that time). Since both my first officer and myself were not sure on which frequency to stay on, we decided to continue to monitor both frequencys (communication #1 121.9, #2 132.45). We continued our taxi and taxi checklist and since XA30 is a very busy time, I kept my eye outside to observe other aircraft movements. Somewhere along our taxi, we both decided that we are on 132.45. I therefore turned communication #1 off and kept listening on communication #2 only. Suddenly, my first officer asked me whether we were supposed to hold short of runway 2. I said no, but then realized that the radios were now switched and 132.45 was in communication #1. ATC indeed gave us a hold short clearance, but I couldn't hear it since I was still monitoring communication #2. We just passed runway 2 when we realized the problem so we called ground control immediately. We were told to continue to taxi and switch to tower. To the best of my knowledge, no conflict situation occurred. This problem could have been avoided if the correct frequency would have been assigned (why do they never mention the use of a second ground frequency on the ATIS in iad)? The confusion that resulted prevented me from hearing the hold short clearance.

Related reports:

Google
 

Original NASA ASRS Text

Title: DEV FROM CLRNC CLRNC LIMIT OVERSHOT - FLC DID NOT 'HOLD SHORT' BECAUSE OF A RADIO FREQ MONITORING PROB WITHIN THE CREW.

Narrative: WE CONTACTED IAD GND ON 121.9 AND RECEIVED CLRNC TO TAXI TO RWY 30. WHILE APCHING W2, 2 ACFT IN FRONT OF US WERE HOLDING SHORT OF THAT TXWY. WHEN THEY CONTINUED THEIR TAXI WITHOUT US HEARING ATC TO GIVE THEM ANY INSTRUCTIONS, WE SUPPOSED THAT ATC FORGOT TO ASSIGN US ANOTHER FREQ (132.45). SURE ENOUGH, WHEN WE MONITORED BOTH 121.9 AND 132.45, WE HEARD ATC CALLING US AND CLRED US TO CONTINUE ON W2 FOR RWY 30 (NO HOLD SHORT INSTRUCTIONS WERE ISSUED AT THAT TIME). SINCE BOTH MY FO AND MYSELF WERE NOT SURE ON WHICH FREQ TO STAY ON, WE DECIDED TO CONTINUE TO MONITOR BOTH FREQS (COM #1 121.9, #2 132.45). WE CONTINUED OUR TAXI AND TAXI CHKLIST AND SINCE XA30 IS A VERY BUSY TIME, I KEPT MY EYE OUTSIDE TO OBSERVE OTHER ACFT MOVEMENTS. SOMEWHERE ALONG OUR TAXI, WE BOTH DECIDED THAT WE ARE ON 132.45. I THEREFORE TURNED COM #1 OFF AND KEPT LISTENING ON COM #2 ONLY. SUDDENLY, MY FO ASKED ME WHETHER WE WERE SUPPOSED TO HOLD SHORT OF RWY 2. I SAID NO, BUT THEN REALIZED THAT THE RADIOS WERE NOW SWITCHED AND 132.45 WAS IN COM #1. ATC INDEED GAVE US A HOLD SHORT CLRNC, BUT I COULDN'T HEAR IT SINCE I WAS STILL MONITORING COM #2. WE JUST PASSED RWY 2 WHEN WE REALIZED THE PROB SO WE CALLED GND CTL IMMEDIATELY. WE WERE TOLD TO CONTINUE TO TAXI AND SWITCH TO TWR. TO THE BEST OF MY KNOWLEDGE, NO CONFLICT SIT OCCURRED. THIS PROB COULD HAVE BEEN AVOIDED IF THE CORRECT FREQ WOULD HAVE BEEN ASSIGNED (WHY DO THEY NEVER MENTION THE USE OF A SECOND GND FREQ ON THE ATIS IN IAD)? THE CONFUSION THAT RESULTED PREVENTED ME FROM HEARING THE HOLD SHORT CLRNC.

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.