Narrative:

I was working local assist to the local 1 controller. Aircraft X was released from the local 2 controller as a svtu (south ventura) departure reference a vtu departure they had. Local 1 had to wait for traffic to land runway 25L before putting aircraft X in position so there was a little bit of a delay before getting him moving. I ran aircraft X down as svtu (meaning the controller would verbally issue a 220 heading at the shoreline).when aircraft X was cleared for takeoff aircraft Y was inside of a 2 mile final and it was recognized immediately that we would have to send aircraft Y around. I started coordinating the go around with departure control and did not hear if the 220 heading was issued to aircraft X. Meanwhile; LC1 was telling me to pass on to departures that aircraft X would be turning 220 but at the same time I noticed hhr tower had traffic just south of aircraft Y at 900 and aircraft Y was at 1300 climbing; so I called them to get a point out and issue traffic. At that point departure called and asked what aircraft X was doing; since he was now offshore side by side with the vtu departure from LC2. I said he's turning 220 and coming to you. I pointed out to LC1 that aircraft X needed to be turned and switched; which he did.everyone needs to be more aware. It's a very complex operation here at lax; especially with the construction that is going on here and the increase in flights. We are all working overtime; high time on position; add to that that there is some sort of OJT happening all the time and it's a lot.

Google
 

Original NASA ASRS Text

Title: LAX Local Assist Controller reported of a traffic conflict with a go-around and HHR Airport traffic. During this event; Local Control forgot to issue a heading to a departure.

Narrative: I was working Local Assist to the Local 1 controller. Aircraft X was released from the Local 2 controller as a SVTU (South Ventura) departure reference a VTU departure they had. Local 1 had to wait for traffic to land Runway 25L before putting Aircraft X in position so there was a little bit of a delay before getting him moving. I ran Aircraft X down as SVTU (meaning the controller would verbally issue a 220 heading at the shoreline).When Aircraft X was cleared for takeoff Aircraft Y was inside of a 2 mile final and it was recognized immediately that we would have to send Aircraft Y around. I started coordinating the go around with Departure control and did not hear if the 220 heading was issued to Aircraft X. Meanwhile; LC1 was telling me to pass on to departures that Aircraft X would be turning 220 but at the same time I noticed HHR tower had traffic just south of Aircraft Y at 900 and Aircraft Y was at 1300 climbing; so I called them to get a point out and issue traffic. At that point departure called and asked what Aircraft X was doing; since he was now offshore side by side with the VTU departure from LC2. I said he's turning 220 and coming to you. I pointed out to LC1 that Aircraft X needed to be turned and switched; which he did.Everyone needs to be more aware. It's a very complex operation here at LAX; especially with the construction that is going on here and the increase in flights. We are all working overtime; high time on position; add to that that there is some sort of OJT happening all the time and it's a lot.

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.