Narrative:

After landing on runway 3 at abq, I exited the runway at taxiway C. Taxiway C is set up as a high speed taxiway exit from runway 3, so my taxi speed was probably 30 KTS and decreasing as I taxied north on taxiway C. Momentarily, my attention was diverted to 2 F16's making low approachs, gars, on runway 8. As I refocused on taxiway C, I realized I was rapidly approaching runway 30/12 and hadn't received clearance to cross. I brought the aircraft to a stop, but not before I had crossed the hold short line. Within seconds after I had stopped, abq tower told us to contact ground. When we switched to ground control, we reported clear of runway 3. Ground control cleared us to cross runway 12 and told us to hold short of runway 8. In my opinion, the contributing factors were: a mind set of a quick taxi to our gate in an attempt to get back on schedule, the fact that this was the first time I had flown with this first officer and I was not familiar with how he managed radio communication and how tentative he might be with regard to asking for a frequency change or clearance to continue taxiing, and finally the fact that the tower controller was trying to manage 2 different runways and the operations of at least 5 different aircraft simultaneously (2 F16's on low approach, 2 holding short awaiting departure on runway 8, and 1 aircraft clearing runway 3 (our aircraft). Solutions: first and foremost, a re-emphasis on stopping when clearing an active runway, second, keeping the pace of events slower during the first couple of flts with an unfamiliar crew member, and finally, with this location, the installation of wigwag lights may help remind pilots of the presence of a runway along this taxi route.

Related reports:

Google
 

Original NASA ASRS Text

Title: A B732 CREW, AFTER LNDG, TAXIED PAST THE HOLD SHORT LINE OF AN INTERSECTING RWY.

Narrative: AFTER LNDG ON RWY 3 AT ABQ, I EXITED THE RWY AT TXWY C. TXWY C IS SET UP AS A HIGH SPD TXWY EXIT FROM RWY 3, SO MY TAXI SPD WAS PROBABLY 30 KTS AND DECREASING AS I TAXIED N ON TXWY C. MOMENTARILY, MY ATTN WAS DIVERTED TO 2 F16'S MAKING LOW APCHS, GARS, ON RWY 8. AS I REFOCUSED ON TXWY C, I REALIZED I WAS RAPIDLY APCHING RWY 30/12 AND HADN'T RECEIVED CLRNC TO CROSS. I BROUGHT THE ACFT TO A STOP, BUT NOT BEFORE I HAD CROSSED THE HOLD SHORT LINE. WITHIN SECONDS AFTER I HAD STOPPED, ABQ TWR TOLD US TO CONTACT GND. WHEN WE SWITCHED TO GND CTL, WE RPTED CLR OF RWY 3. GND CTL CLRED US TO CROSS RWY 12 AND TOLD US TO HOLD SHORT OF RWY 8. IN MY OPINION, THE CONTRIBUTING FACTORS WERE: A MIND SET OF A QUICK TAXI TO OUR GATE IN AN ATTEMPT TO GET BACK ON SCHEDULE, THE FACT THAT THIS WAS THE FIRST TIME I HAD FLOWN WITH THIS FO AND I WAS NOT FAMILIAR WITH HOW HE MANAGED RADIO COM AND HOW TENTATIVE HE MIGHT BE WITH REGARD TO ASKING FOR A FREQ CHANGE OR CLRNC TO CONTINUE TAXIING, AND FINALLY THE FACT THAT THE TWR CTLR WAS TRYING TO MANAGE 2 DIFFERENT RWYS AND THE OPS OF AT LEAST 5 DIFFERENT ACFT SIMULTANEOUSLY (2 F16'S ON LOW APCH, 2 HOLDING SHORT AWAITING DEP ON RWY 8, AND 1 ACFT CLRING RWY 3 (OUR ACFT). SOLUTIONS: FIRST AND FOREMOST, A RE-EMPHASIS ON STOPPING WHEN CLRING AN ACTIVE RWY, SECOND, KEEPING THE PACE OF EVENTS SLOWER DURING THE FIRST COUPLE OF FLTS WITH AN UNFAMILIAR CREW MEMBER, AND FINALLY, WITH THIS LOCATION, THE INSTALLATION OF WIGWAG LIGHTS MAY HELP REMIND PLTS OF THE PRESENCE OF A RWY ALONG THIS TAXI RTE.

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.