B737-300 crew had a runway incursion at ord because of confusing controller instructions and high tr...

Attributes
ACN	530521
Time
Date	200111
Day	Tue
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : ord.airport
State Reference	IL
Altitude	agl single value : 0
Environment
Light	Night
Aircraft 1
Controlling Facilities	tower : ord.tower
Operator	common carrier : air carrier
Make Model Name	B737-300
Operating Under FAR Part	Part 121
Flight Phase	ground : taxi
Flight Plan	IFR
Aircraft 2
Controlling Facilities	tower : ord.tower
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Flight Phase	descent : approach
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
ASRS Report	530521
Person 2
Function	flight crew : first officer
Events
Anomaly	incursion : runway non adherence : company policies non adherence : clearance non adherence : published procedure non adherence : far other anomaly other
Independent Detector	other flight crewa other flight crewb
Resolutory Action	controller : issued new clearance none taken : detected after the fact other
Consequence	other
Supplementary
Problem Areas	Flight Crew Human Performance Airport ATC Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

After landing on runway 27R in ord, we were instructed to turn left off the runway onto taxiway east. As we slowed, we were told to turn left on taxiway right and contact ground. I noticed that we were very close to runway 22R but we had to get off runway 27R because of landing traffic, but they were also landing runway 22R. I crossed the runway 22R hold line on taxiway right to get off runway 27R but held short of runway 22R. The first officer called ground and we were told to cross runway 22R. Then hold short runway 22R and go back to tower. Tower told us to cross runway 22R and not stop and go back to ground. There was much confusion with the ATC instructions and it caused a possible runway incursion.

Original NASA ASRS Text

Title: B737-300 CREW HAD A RWY INCURSION AT ORD BECAUSE OF CONFUSING CTLR INSTRUCTIONS AND HIGH TFC VOLUME.

Narrative: AFTER LNDG ON RWY 27R IN ORD, WE WERE INSTRUCTED TO TURN L OFF THE RWY ONTO TXWY E. AS WE SLOWED, WE WERE TOLD TO TURN L ON TXWY R AND CONTACT GND. I NOTICED THAT WE WERE VERY CLOSE TO RWY 22R BUT WE HAD TO GET OFF RWY 27R BECAUSE OF LNDG TFC, BUT THEY WERE ALSO LNDG RWY 22R. I CROSSED THE RWY 22R HOLD LINE ON TXWY R TO GET OFF RWY 27R BUT HELD SHORT OF RWY 22R. THE FO CALLED GND AND WE WERE TOLD TO CROSS RWY 22R. THEN HOLD SHORT RWY 22R AND GO BACK TO TWR. TWR TOLD US TO CROSS RWY 22R AND NOT STOP AND GO BACK TO GND. THERE WAS MUCH CONFUSION WITH THE ATC INSTRUCTIONS AND IT CAUSED A POSSIBLE RWY INCURSION.

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.

B737-300 crew had a runway incursion at ord because of confusing controller instructions and high traffic volume.