Narrative:

We received a taxi clearance of: 'taxi via K to runway 6L, hold short of runway 32.' we normally use runway 32 for departure, but with winds 140 degrees at 10 KTS, I had expected runway 6R. When we received the clearance for runway 6L, I entered that runway in our FMS computer and missed the 'hold short of runway 32' command. As we taxied out into runway 32 stopway (taxiway K crosses runway 32 on the stopway) I recognized my mistake, we called ground control, and they sent us to tower. (We were approximately halfway across the stopway.) tower then cleared us to runway 6L without further comment. No evasive action was taken by other aircraft, runway 32 was not in use at that time. Primary cause of incursion: entering data into the computer while receiving clearance. Contributing factors: stopway hold line worn away, needs to be re-painted. Callback conversation with reporter revealed the following: reporter states that the main problem with missing the clearance was that ground initiated the call and the clearance while reporter was clearing the ground crew off the phone line. Thus reporter did not really hear the clearance and asked first officer were we cleared to runway 6L. The response was yes with no further explanation. The paint and being night were additional problems as the paint is pretty well worn. This was a very slow night and, when first officer reported position as 'on the stopway,' clearance was to continue and contact tower. Aircraft was a B737- 400. Reporter does not blame the poorly painted line for his error, but does say that the visibility of the hold line is a 'wake up call' when taxiing.

Related reports:

Google
 

Original NASA ASRS Text

Title: B737-400 CROSSES RWY STOPWAY WHEN INSTRUCTED TO HOLD SHORT.

Narrative: WE RECEIVED A TAXI CLRNC OF: 'TAXI VIA K TO RWY 6L, HOLD SHORT OF RWY 32.' WE NORMALLY USE RWY 32 FOR DEP, BUT WITH WINDS 140 DEGS AT 10 KTS, I HAD EXPECTED RWY 6R. WHEN WE RECEIVED THE CLRNC FOR RWY 6L, I ENTERED THAT RWY IN OUR FMS COMPUTER AND MISSED THE 'HOLD SHORT OF RWY 32' COMMAND. AS WE TAXIED OUT INTO RWY 32 STOPWAY (TXWY K CROSSES RWY 32 ON THE STOPWAY) I RECOGNIZED MY MISTAKE, WE CALLED GND CTL, AND THEY SENT US TO TWR. (WE WERE APPROX HALFWAY ACROSS THE STOPWAY.) TWR THEN CLRED US TO RWY 6L WITHOUT FURTHER COMMENT. NO EVASIVE ACTION WAS TAKEN BY OTHER ACFT, RWY 32 WAS NOT IN USE AT THAT TIME. PRIMARY CAUSE OF INCURSION: ENTERING DATA INTO THE COMPUTER WHILE RECEIVING CLRNC. CONTRIBUTING FACTORS: STOPWAY HOLD LINE WORN AWAY, NEEDS TO BE RE-PAINTED. CALLBACK CONVERSATION WITH REPORTER REVEALED THE FOLLOWING: RPTR STATES THAT THE MAIN PROB WITH MISSING THE CLRNC WAS THAT GND INITIATED THE CALL AND THE CLRNC WHILE RPTR WAS CLRING THE GND CREW OFF THE PHONE LINE. THUS RPTR DID NOT REALLY HEAR THE CLRNC AND ASKED FO WERE WE CLRED TO RWY 6L. THE RESPONSE WAS YES WITH NO FURTHER EXPLANATION. THE PAINT AND BEING NIGHT WERE ADDITIONAL PROBS AS THE PAINT IS PRETTY WELL WORN. THIS WAS A VERY SLOW NIGHT AND, WHEN FO RPTED POS AS 'ON THE STOPWAY,' CLRNC WAS TO CONTINUE AND CONTACT TWR. ACFT WAS A B737- 400. RPTR DOES NOT BLAME THE POORLY PAINTED LINE FOR HIS ERROR, BUT DOES SAY THAT THE VISIBILITY OF THE HOLD LINE IS A 'WAKE UP CALL' WHEN TAXIING.

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.