A tower controller reports an arriving aircraft initiated a go-around due to traffic crossing the ru...

Narrative:

Aircraft X was waiting for a release. I asked aircraft X if they had the numbers for runway 26L. They were working on it. I didn't want to put aircraft X in between the runways if they would be unable runway 26L. They were ready when aircraft Y was on a 2.5 mile final and I gave aircraft X the clearance to cross runway 26R and 'runway 26L luaw [line up and wait] traffic 2 mile final no delay'. I then informed aircraft Y traffic crossing upfield. Aircraft X was almost off the runway but was still in the safety area for runway 26R moving towards runway 26L.aircraft Y initiated a go-around at 0.69 mile final and 1;300 feel MSL going 150 knots. I instructed aircraft Y to maintain 4;000 feet with the intention of giving them heading 255 and departure frequency after the altitude readback and established on the go-around. Aircraft Y incorrectly readback the altitude with a question of 7;000 feet. I restated maintain 4;000 feet and to contact socal departure. I held aircraft X short of runway 26L due to traffic on 4 mile final runway 26L and the aircraft Y going around. During this workload I forgot to give aircraft Y a heading and departure frequency. After switching they turned south and contacted riverside sector. I had no time during this event to try and coordinate with departure control.there are several things I could have done differently. Cleared aircraft Y for the visual approach for runway 26L and depart aircraft X off runway 26R. I still didn't have my release when aircraft Y was far enough out to change runways. I could have gotten aircraft X a 3rd new flow time and given him a delay due to the delayed IFR releases. I could have also held aircraft X in between the runways but I wasn't sure yet that aircraft X was going to be able to depart runway 26L. I could have let aircraft Y arrive then luaw aircraft X.I should have given aircraft Y the altitude; heading and departure frequency all at once.

Original NASA ASRS Text

Title: A Tower Controller reports an arriving aircraft initiated a go-around due to traffic crossing the runway. The Controller forgot to issue complete go-around instructions to the aircraft prior to switching them to the Departure Controller.

Narrative: Aircraft X was waiting for a release. I asked Aircraft X if they had the numbers for Runway 26L. They were working on it. I didn't want to put Aircraft X in between the Runways if they would be unable Runway 26L. They were ready when Aircraft Y was on a 2.5 mile final and I gave Aircraft X the clearance to cross Runway 26R and 'Runway 26L LUAW [line up and wait] traffic 2 mile final no delay'. I then informed Aircraft Y traffic crossing upfield. Aircraft X was almost off the Runway but was still in the safety area for Runway 26R moving towards Runway 26L.Aircraft Y initiated a go-around at 0.69 mile final and 1;300 feel MSL going 150 knots. I instructed Aircraft Y to maintain 4;000 feet with the intention of giving them heading 255 and departure frequency after the altitude readback and established on the go-around. Aircraft Y incorrectly readback the altitude with a question of 7;000 feet. I restated maintain 4;000 feet and to contact SoCal departure. I held Aircraft X short of Runway 26L due to traffic on 4 mile final Runway 26L and the Aircraft Y going around. During this workload I forgot to give Aircraft Y a heading and departure frequency. After switching they turned south and contacted riverside sector. I had no time during this event to try and coordinate with departure control.There are several things I could have done differently. Cleared Aircraft Y for the visual approach for Runway 26L and depart Aircraft X off Runway 26R. I still didn't have my release when Aircraft Y was far enough out to change Runways. I could have gotten Aircraft X a 3rd new flow time and given him a delay due to the delayed IFR releases. I could have also held Aircraft X in between the Runways but I wasn't sure yet that Aircraft X was going to be able to depart Runway 26L. I could have let Aircraft Y arrive then LUAW Aircraft X.I should have given Aircraft Y the altitude; heading and departure frequency all at once.

Data retrieved from NASA's ASRS site 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	1432152
Time
Date	201703
Local Time Of Day	1201-1800
Place
Locale Reference	ONT.Airport
State Reference	CA
Aircraft 1
Make Model Name	B737 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	Taxi
Route In Use	None
Flight Plan	IFR
Aircraft 2
Make Model Name	Bombardier/Canadair Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	Final Approach
Flight Plan	IFR
Person 1
Function	Local
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Time Certified In Pos 1 (yrs) 1.3
Person 2
Function	Pilot Flying Captain
Qualification	Flight Crew Air Transport Pilot (ATP)
Events
Anomaly	ATC Issue All Types Conflict Ground Conflict Less Severe Deviation - Procedural Clearance Deviation - Track / Heading All Types

A tower controller reports an arriving aircraft initiated a go-around due to traffic crossing the runway. The controller forgot to issue complete go-around instructions to the aircraft prior to switching them to the departure controller.