B737-300 crew exited landing runway onto another runway without clearance to taxi on that runway.

Attributes
ACN	498960
Time
Date	200101
Day	Wed
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : bwi.airport
State Reference	MD
Altitude	agl single value : 0
Environment
Light	Daylight
Aircraft 1
Controlling Facilities	tower : bwi.tower
Operator	common carrier : air carrier
Make Model Name	B737-300
Operating Under FAR Part	Part 121
Navigation In Use	other
Flight Phase	landing : roll
Flight Plan	IFR
Aircraft 2
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	descent : approach
Route In Use	approach : traffic pattern
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Experience	flight time total : 21300
ASRS Report	498960
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Experience	flight time last 90 days : 160 flight time total : 7000 flight time type : 3350
ASRS Report	499314
Events
Anomaly	conflict : ground less severe ground encounters other incursion : runway non adherence : far non adherence : published procedure non adherence : company policies non adherence : clearance other anomaly other
Independent Detector	other controllera other flight crewa
Resolutory Action	none taken : anomaly accepted
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Flew visual approach to runway 28 at bwi. Landing rollout exited onto runway 33L with immediate right turn onto taxiway right. Company aircraft was on short final for runway 33L. As I approached the intersection of the 2 runways, I was slowing, anticipating a turnoff at the intersection. At that same time, tower radioed about repositioning due to traffic on final for runway 33L. He said something about taxiway R1 and I assumed wrongly that he meant the right turn off of runway 33L. However, a second look at the commercial chart page showed taxiway R1 to be the next exit past the intersection. No go around was necessary due to the separation we had and the short time we were in the intersection. Probable causes: 1) unfamiliarity with specific taxiway intersection in bwi. 2) assumption of my part that tower was asking us to expedite the turn off with permission to use runway 33L for the turn onto taxiway right. 3) tower's radio transmission was not real clear. Prevention: 1) listen closer to instruction and if unsure, take the conservative approach and roll to next intersection. 2) never assume an intersection exit will be given. 3) review with first officer possible txwys for exiting the runway prior to landing.

Original NASA ASRS Text

Title: B737-300 CREW EXITED LNDG RWY ONTO ANOTHER RWY WITHOUT CLRNC TO TAXI ON THAT RWY.

Narrative: FLEW VISUAL APCH TO RWY 28 AT BWI. LNDG ROLLOUT EXITED ONTO RWY 33L WITH IMMEDIATE R TURN ONTO TXWY R. COMPANY ACFT WAS ON SHORT FINAL FOR RWY 33L. AS I APCHED THE INTXN OF THE 2 RWYS, I WAS SLOWING, ANTICIPATING A TURNOFF AT THE INTXN. AT THAT SAME TIME, TWR RADIOED ABOUT REPOSITIONING DUE TO TFC ON FINAL FOR RWY 33L. HE SAID SOMETHING ABOUT TXWY R1 AND I ASSUMED WRONGLY THAT HE MEANT THE R TURN OFF OF RWY 33L. HOWEVER, A SECOND LOOK AT THE COMMERCIAL CHART PAGE SHOWED TXWY R1 TO BE THE NEXT EXIT PAST THE INTXN. NO GAR WAS NECESSARY DUE TO THE SEPARATION WE HAD AND THE SHORT TIME WE WERE IN THE INTXN. PROBABLE CAUSES: 1) UNFAMILIARITY WITH SPECIFIC TXWY INTXN IN BWI. 2) ASSUMPTION OF MY PART THAT TWR WAS ASKING US TO EXPEDITE THE TURN OFF WITH PERMISSION TO USE RWY 33L FOR THE TURN ONTO TXWY R. 3) TWR'S RADIO XMISSION WAS NOT REAL CLR. PREVENTION: 1) LISTEN CLOSER TO INSTRUCTION AND IF UNSURE, TAKE THE CONSERVATIVE APCH AND ROLL TO NEXT INTXN. 2) NEVER ASSUME AN INTXN EXIT WILL BE GIVEN. 3) REVIEW WITH FO POSSIBLE TXWYS FOR EXITING THE RWY PRIOR TO LNDG.

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.