A go around was initiated by an air carrier because of another air carrier crossing the runway.

Attributes
ACN	117710
Time
Date	198907
Day	Sat
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : ord
State Reference	IL
Altitude	agl bound lower : 0 agl bound upper : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	Large Transport, Low Wing, 3 Turbojet Eng
Flight Phase	ground other : taxi
Flight Plan	IFR
Aircraft 2
Operator	common carrier : air carrier
Make Model Name	Large Transport, Low Wing, 3 Turbojet Eng
Flight Phase	landing : go around landing other
Route In Use	arrival other
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : second officer
Qualification	pilot : atp pilot : flight engineer pilot : cfi
Experience	flight time last 90 days : 200 flight time total : 4500 flight time type : 1000
ASRS Report	117710
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : commercial pilot : instrument pilot : atp
Experience	flight time total : 15000 flight time type : 11000
ASRS Report	117584
Events
Anomaly	other anomaly other
Independent Detector	other flight crewa
Resolutory Action	other
Consequence	Other
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	other

Narrative:

While holding short of runway 9R on southwest cargo taxiway for crossing clearance to continue taxi to runway 32L for takeoff, the ord tower controller cleared us to cross the runway with air carrier Y on final at unknown distance. While crossing the runway, air carrier Y flight initiated a go around, expressing dissatisfaction at the controller's decision to cross our flight. When air carrier Y questioned the controller's judgement, the controller replied that 'had air carrier X started across more quickly' air carrier Y would have had plenty of room. Instead of passing judgement and placing blame to cover up an error, other factors should have been considered. Our aircraft was heavy (179.4 tog). It is difficult to initiate a 'quick' taxi under these conditions. My perception of this situation is that an error in judgement was made by the controller in question, causing an unnecessary go-around.

Original NASA ASRS Text

Title: A GO AROUND WAS INITIATED BY AN ACR BECAUSE OF ANOTHER ACR CROSSING THE RWY.

Narrative: WHILE HOLDING SHORT OF RWY 9R ON SW CARGO TXWY FOR XING CLRNC TO CONTINUE TAXI TO RWY 32L FOR TKOF, THE ORD TWR CTLR CLRED US TO CROSS THE RWY WITH ACR Y ON FINAL AT UNKNOWN DISTANCE. WHILE XING THE RWY, ACR Y FLT INITIATED A GO AROUND, EXPRESSING DISSATISFACTION AT THE CTLR'S DECISION TO CROSS OUR FLT. WHEN ACR Y QUESTIONED THE CTLR'S JUDGEMENT, THE CTLR REPLIED THAT 'HAD ACR X STARTED ACROSS MORE QUICKLY' ACR Y WOULD HAVE HAD PLENTY OF ROOM. INSTEAD OF PASSING JUDGEMENT AND PLACING BLAME TO COVER UP AN ERROR, OTHER FACTORS SHOULD HAVE BEEN CONSIDERED. OUR ACFT WAS HEAVY (179.4 TOG). IT IS DIFFICULT TO INITIATE A 'QUICK' TAXI UNDER THESE CONDITIONS. MY PERCEPTION OF THIS SITUATION IS THAT AN ERROR IN JUDGEMENT WAS MADE BY THE CTLR IN QUESTION, CAUSING AN UNNECESSARY GO-AROUND.

Data retrieved from NASA's ASRS site as of August 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.