B737-300 is cleared into position and hold with close-in traffic that is subsequently sent around.

Attributes
ACN	704699
Time
Date	200607
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : ord.airport
State Reference	IL
Altitude	agl single value : 0
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 : position and hold
Flight Plan	IFR
Aircraft 2
Controlling Facilities	tower : ord.tower
Flight Phase	landing : go around
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Experience	flight time last 90 days : 240 flight time total : 15000 flight time type : 5000
ASRS Report	704699
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Experience	flight time last 90 days : 80 flight time total : 9000 flight time type : 375
ASRS Report	704527
Events
Anomaly	non adherence : required legal separation
Independent Detector	other controllerb
Resolutory Action	controller : separated traffic flight crew : executed go around
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	ATC Human Performance Airport Flight Crew Human Performance
Primary Problem	Ambiguous

Narrative:

We had been directed to expedite our taxi to runway 22L at ord. We apparently had a 10 min window to get airborne. We were directed to taxi into position and hold. We did that. I noticed traffic on approach for runway 27 that was in closer than the separation the tower usually used. I expedited into position and pushed the power up to be able to start the roll earlier once they gave us clearance. We received nothing further from tower. I looked out the left of the cockpit and observed the previous traffic continuing the approach. Tower directed them to go around. They did so; and did not overfly our aircraft. I later called the tower to find if we had misunderstood our clearance. They advised we had complied with all their instructions; and they had intended to clear us for takeoff in time for both our takeoff and the runway 27's traffic landing to both occur.

Original NASA ASRS Text

Title: B737-300 IS CLRED INTO POS AND HOLD WITH CLOSE-IN TFC THAT IS SUBSEQUENTLY SENT AROUND.

Narrative: WE HAD BEEN DIRECTED TO EXPEDITE OUR TAXI TO RWY 22L AT ORD. WE APPARENTLY HAD A 10 MIN WINDOW TO GET AIRBORNE. WE WERE DIRECTED TO TAXI INTO POS AND HOLD. WE DID THAT. I NOTICED TFC ON APCH FOR RWY 27 THAT WAS IN CLOSER THAN THE SEPARATION THE TWR USUALLY USED. I EXPEDITED INTO POS AND PUSHED THE PWR UP TO BE ABLE TO START THE ROLL EARLIER ONCE THEY GAVE US CLRNC. WE RECEIVED NOTHING FURTHER FROM TWR. I LOOKED OUT THE L OF THE COCKPIT AND OBSERVED THE PREVIOUS TFC CONTINUING THE APCH. TWR DIRECTED THEM TO GAR. THEY DID SO; AND DID NOT OVERFLY OUR ACFT. I LATER CALLED THE TWR TO FIND IF WE HAD MISUNDERSTOOD OUR CLRNC. THEY ADVISED WE HAD COMPLIED WITH ALL THEIR INSTRUCTIONS; AND THEY HAD INTENDED TO CLR US FOR TKOF IN TIME FOR BOTH OUR TKOF AND THE RWY 27'S TFC LNDG TO BOTH OCCUR.

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