Date: 201703
Local time of day: 1201-1800
Location: ONT.Airport, CA
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
Airspace: Class C ONT
ATC / advisory: Tower ONT
Second aircraft: Bombardier/Canadair Undifferentiated or Other Model
Reporter organization: Government
Reporter function: Local
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Confusion; Situational Awareness; Time Pressure
Second reporter function: Pilot Flying; Captain
Anomaly: ATC Issue All Types; Conflict Ground Conflict; Less Severe; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance
Detector: Person Air Traffic Control; Person Flight Crew
When detected: In-flight; Taxi
Result: Air Traffic Control Issued New Clearance; Flight Crew Executed Go Around / Missed Approach; Flight Crew Requested ATC Assistance / Clarification; General Flight Cancelled / Delayed
Contributing factors: Airport; Human Factors; Procedure
Primary problem: Procedure

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.


Second narrative: We were holding 30 yards short of the hold short line for Runway 26R at ONT; awaiting IFR release. The Controller asked if we could accept Runway 26L for departure. We replied affirmative and quickly ran Performance and Departure Plan Checklist for the new runway. During that time; we were given a 'line up and wait' clearance for Runway 26L. As we crossed the Runway 26R hold short line; I observed a jet at approximately 300 feet beginning a go-around maneuver. The Controller then issued a go-around command to the  jet (too late); and we continued to the hold short line for Runway 26L and queried the Controller about what had just occurred.The Controller assumed we would be quicker crossing the runway and failed to inform us that he had traffic on final for Runway 26R. Completing runway change tasks takes time and had we known he had final approach traffic; we would have asked to delay our crossing clearance until we were ready to proceed. The fact that we were 30 yards from the Runway 26R hold short line to accommodate any departures ahead of our wheels-up time did not help with the delay in crossing the runway.


Synopsis: 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.