Narrative:

Pdx ground controller issued clearance to taxi from the ramp to runway 10L via taxiway a to taxiway A5 to taxiway T (main terminal ramp area). While reaching the complicated intersection of txwys T and a, the captain and I were distraction by a B737 taxiing in close from our left. After some discussion we determined we had the right of way. We did not notice the lighted runway identify box usually associated with the hold short line at tower controled airports. After turning right off taxiway T and proceeding out to runway 10L, we determined that we had taxied over the hold short line for runway 10L by approximately 40 ft. There was no traffic on final and we stopped. We were 100 ft from runway 10L. The hold short line is used for both runways 10L and 21, in other words there is only one hold short line for two runways, this confused us. At the time we stopped we were called by ground control and advised that we were indeed over the hold short line. No traffic conflict was caused. No hazard to other aircraft. Contributing factors: unfamiliarity with airport, fatigue, 4 1/2 hours late, construction on taxiway a route to runway 10L, requiring a detour to taxiway T, and a poorly marked hold short line running diagonal across the intersection of several txwys. Callback conversation with reporter revealed the following information: this reporter has been back to pdx, and is now familiar with the concept of a diagonal hold line for two runways. This first officer still takes issue with the fact that this is an uncommon type of hold short line and the adjacent runway holding position sign is too far away from the intersection and unnoticeable. This flight crew had been flying all night, but this reporter feels that this was a minor factor in the incident. The combination of the distraction with the B737 just at the time that the aircraft approached the runway holding position marking, was the main cause of the crew's inability to hold short.

Related reports:

Google
 

Original NASA ASRS Text

Title: AN CARGO F27 FLC INADVERTENTLY TAXIED PAST THE HOLD SHORT AREA FOR RWY 10L AT PDX. THE FLC WAS DISTR BY AN ACFT TAXIING NEARBY AND MISSED ALL CUES THAT WOULD HAVE CAUSED THEM TO HOLD SHORT.

Narrative: PDX GND CTLR ISSUED CLRNC TO TAXI FROM THE RAMP TO RWY 10L VIA TXWY A TO TXWY A5 TO TXWY T (MAIN TERMINAL RAMP AREA). WHILE REACHING THE COMPLICATED INTXN OF TXWYS T AND A, THE CAPT AND I WERE DISTR BY A B737 TAXIING IN CLOSE FROM OUR L. AFTER SOME DISCUSSION WE DETERMINED WE HAD THE RIGHT OF WAY. WE DID NOT NOTICE THE LIGHTED RWY IDENT BOX USUALLY ASSOCIATED WITH THE HOLD SHORT LINE AT TWR CTLED ARPTS. AFTER TURNING R OFF TXWY T AND PROCEEDING OUT TO RWY 10L, WE DETERMINED THAT WE HAD TAXIED OVER THE HOLD SHORT LINE FOR RWY 10L BY APPROX 40 FT. THERE WAS NO TFC ON FINAL AND WE STOPPED. WE WERE 100 FT FROM RWY 10L. THE HOLD SHORT LINE IS USED FOR BOTH RWYS 10L AND 21, IN OTHER WORDS THERE IS ONLY ONE HOLD SHORT LINE FOR TWO RWYS, THIS CONFUSED US. AT THE TIME WE STOPPED WE WERE CALLED BY GND CTL AND ADVISED THAT WE WERE INDEED OVER THE HOLD SHORT LINE. NO TFC CONFLICT WAS CAUSED. NO HAZARD TO OTHER ACFT. CONTRIBUTING FACTORS: UNFAMILIARITY WITH ARPT, FATIGUE, 4 1/2 HRS LATE, CONSTRUCTION ON TXWY A RTE TO RWY 10L, REQUIRING A DETOUR TO TXWY T, AND A POORLY MARKED HOLD SHORT LINE RUNNING DIAGONAL ACROSS THE INTXN OF SEVERAL TXWYS. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THIS RPTR HAS BEEN BACK TO PDX, AND IS NOW FAMILIAR WITH THE CONCEPT OF A DIAGONAL HOLD LINE FOR TWO RWYS. THIS FO STILL TAKES ISSUE WITH THE FACT THAT THIS IS AN UNCOMMON TYPE OF HOLD SHORT LINE AND THE ADJACENT RWY HOLDING POS SIGN IS TOO FAR AWAY FROM THE INTXN AND UNNOTICEABLE. THIS FLC HAD BEEN FLYING ALL NIGHT, BUT THIS RPTR FEELS THAT THIS WAS A MINOR FACTOR IN THE INCIDENT. THE COMBINATION OF THE DISTR WITH THE B737 JUST AT THE TIME THAT THE ACFT APCHED THE RWY HOLDING POS MARKING, WAS THE MAIN CAUSE OF THE CREW'S INABILITY TO HOLD SHORT.

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.