A B737 flight crew crosses over an active runway 29L at tus, az.

Attributes
ACN	471723
Time
Date	200005
Day	Mon
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : tus.airport
State Reference	AZ
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tower : bwi.tower
Operator	common carrier : air carrier
Make Model Name	B737 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	ground : taxi
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp pilot : commercial pilot : instrument pilot : multi engine
Experience	flight time last 90 days : 230 flight time total : 10000 flight time type : 5400
ASRS Report	471723
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Events
Anomaly	incursion : runway non adherence : clearance other anomaly other
Independent Detector	other controllera
Resolutory Action	controller : issued advisory none taken : detected after the fact
Consequence	faa : investigated
Supplementary
Problem Areas	Flight Crew Human Performance ATC Human Performance Airport
Primary Problem	ATC Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

We landed on runway 21 in tus. Turned off runway 21 onto taxiway D -- only taxiway back to terminal. We contacted ground and were instructed to taxi on taxiway D and hold short of runway 29R on taxiway D. Read back clearance, resulted in no response from controller. We crossed the hold line on runway 11R and were coming to a stop at hold line on runway 29R. Ground told us to 'stop right there.' we complied and then were cleared to cross runway 29R on taxiway D to the gate. Tus later filed a runway incursion charge stating that we had crossed runway 29L hold line, which we understood the clearance limit was runway 29R on taxiway D. All of our clrncs were read back in their entirety. The controller did not respond differently from our readback. Perhaps if the clearance limit was runway 29L, the mistake could have been caught with a solicited response from the crew to the controller for verification of limit.

Original NASA ASRS Text

Title: A B737 FLC CROSSES OVER AN ACTIVE RWY 29L AT TUS, AZ.

Narrative: WE LANDED ON RWY 21 IN TUS. TURNED OFF RWY 21 ONTO TXWY D -- ONLY TXWY BACK TO TERMINAL. WE CONTACTED GND AND WERE INSTRUCTED TO TAXI ON TXWY D AND HOLD SHORT OF RWY 29R ON TXWY D. READ BACK CLRNC, RESULTED IN NO RESPONSE FROM CTLR. WE CROSSED THE HOLD LINE ON RWY 11R AND WERE COMING TO A STOP AT HOLD LINE ON RWY 29R. GND TOLD US TO 'STOP RIGHT THERE.' WE COMPLIED AND THEN WERE CLRED TO CROSS RWY 29R ON TXWY D TO THE GATE. TUS LATER FILED A RWY INCURSION CHARGE STATING THAT WE HAD CROSSED RWY 29L HOLD LINE, WHICH WE UNDERSTOOD THE CLRNC LIMIT WAS RWY 29R ON TXWY D. ALL OF OUR CLRNCS WERE READ BACK IN THEIR ENTIRETY. THE CTLR DID NOT RESPOND DIFFERENTLY FROM OUR READBACK. PERHAPS IF THE CLRNC LIMIT WAS RWY 29L, THE MISTAKE COULD HAVE BEEN CAUGHT WITH A SOLICITED RESPONSE FROM THE CREW TO THE CTLR FOR VERIFICATION OF LIMIT.

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.