A slc local controller reported a late go-around instruction due to a conflict between the previous ...

Narrative:

A MD82 landed runway 34R; a B737 was 2 miles in trail. Ground control called over and said that the MD82 had traffic on the parallel taxiway H north bound; a heavy airbus. I instructed the MD82 to hold short of the taxiway and exit the runway at H9 and to contact ground control. I observed the MD82 exit the runway but start to slow down and then come to a complete stop on the runway side of the hold short line. I called to ground to get the MD82 moving and saw that the B737 was too close to the landing threshold and the MD82 was not moving. I instructed the B737 to go around but I used the wrong call sign. When I figured out that I had used the wrong call sign; the B737 was over the runway but I still sent him around. The MD82 was still holding short of the hold short line. The B737 said that he was on the runway but going around. There was no danger of a collision but I had to follow procedures. The reason the heavy was on taxiway H is that taxiway G was closed for construction. The intended flow was to assign runways to eliminate nose to nose taxiing. This was not followed and I think priority should have been given to aircraft exiting the runway. The heavy was taxiing at a high rate of speed which forced me to hold the MD82.

Original NASA ASRS Text

Title: A SLC Local Controller reported a late go-around instruction due to a conflict between the previous landing traffic and a taxiing aircraft; noting agreed upon operational procedures were not followed.

Narrative: A MD82 landed Runway 34R; a B737 was 2 miles in trail. Ground Control called over and said that the MD82 had traffic on the parallel Taxiway H north bound; a heavy airbus. I instructed the MD82 to hold short of the taxiway and exit the runway at H9 and to contact Ground Control. I observed the MD82 exit the runway but start to slow down and then come to a complete stop on the runway side of the hold short line. I called to Ground to get the MD82 moving and saw that the B737 was too close to the landing threshold and the MD82 was not moving. I instructed the B737 to go around but I used the wrong call sign. When I figured out that I had used the wrong call sign; the B737 was over the runway but I still sent him around. The MD82 was still holding short of the hold short line. The B737 said that he was on the runway but going around. There was no danger of a collision but I had to follow procedures. The reason the heavy was on Taxiway H is that Taxiway G was closed for construction. The intended flow was to assign runways to eliminate nose to nose taxiing. This was not followed and I think priority should have been given to aircraft exiting the runway. The heavy was taxiing at a high rate of speed which forced me to hold the MD82.

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

Attributes
ACN	894549
Time
Date	201006
Local Time Of Day	0001-0600
Place
Locale Reference	SLC.Airport
State Reference	UT
Aircraft 1
Make Model Name	MD-82
Operating Under FAR Part	Part 121
Flight Phase	Landing
Flight Plan	IFR
Aircraft 2
Make Model Name	B737 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	Landing
Route In Use	Visual Approach
Flight Plan	IFR
Person 1
Function	Local
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types Conflict Ground Conflict Less Severe Ground Incursion Runway

A slc local controller reported a late go-around instruction due to a conflict between the previous landing traffic and a taxiing aircraft; noting agreed upon operational procedures were not followed.