Narrative:

Aircraft X was holding short of runway 29R requesting a straight out departure. At that time there was an IFR coordinated business jet on taxiway a abeam the antenna site. I departed aircraft X without delay to give them ample time to distance themselves from the jet; and it was my plan to delay getting the release with socal on the jet for that same reason. However; the controller in charge dialed the shout line to the laker sector anyway. Then the front line manager who was working the ground control position coordinated a runway 29L crossing and the laker controller responded back to the call the controller in charge had made; both at the same time. I hurriedly coordinated with the ground controller in order to respond to the laker departure controller. I departed the jet and then noticed that arriving aircraft Y; a helicopter; was over taxiway hotel at the same time that another small aircraft was trying to taxi southbound on that taxiway. I believe there were two causes for this event. One was me rushing to get two coordinations done at the same time. The other was both me and the supervisor on ground control failing to adequately scan the airspace to visually acquire aircraft Y we were coordinating for.even though the controller in charge initiated the call to the laker sector; I had the option and should have decided to simply call them back at a later time. That would have let me better focus on my coordination with the ground controller. Second; the ground controller should be aware of the local controller's traffic before they coordinate with them. Talking with that front line manager later in his office; he admitted that he was not aware of aircraft Y's position before he coordinated with me. Since aircraft Y arrived almost immediately; that indicates that aircraft Y was on a short left base and obstructed by the roof of the tower cab when the coordination was made. Thirdly; I as the local controller must be diligent in visually acquiring aircraft Y traffic I am coordinating for. Extra care should also used when working with a front line manager that may not be as proficient at working traffic as a cpc.

Related reports:

Google
 

Original NASA ASRS Text

Title: TOA Local Controller reports of bad communication with the Ground Controller; which causes an airborne aircraft to fly closely to a departing aircraft.

Narrative: Aircraft X was holding short of Runway 29R requesting a straight out departure. At that time there was an IFR coordinated business jet on Taxiway A abeam the antenna site. I departed Aircraft X without delay to give them ample time to distance themselves from the jet; and it was my plan to delay getting the release with SOCAL on the jet for that same reason. However; the CIC dialed the shout line to the Laker Sector anyway. Then the front line manager who was working the Ground Control position coordinated a Runway 29L crossing and the Laker Controller responded back to the call the CIC had made; both at the same time. I hurriedly coordinated with the Ground Controller in order to respond to the Laker Departure Controller. I departed the jet and then noticed that arriving Aircraft Y; a helicopter; was over taxiway hotel at the same time that another small aircraft was trying to taxi southbound on that taxiway. I believe there were two causes for this event. One was me rushing to get two coordinations done at the same time. The other was both me and the Supervisor on Ground Control failing to adequately scan the airspace to visually acquire Aircraft Y we were coordinating for.Even though the CIC initiated the call to the Laker Sector; I had the option and should have decided to simply call them back at a later time. That would have let me better focus on my coordination with the Ground Controller. Second; the Ground Controller should be aware of the Local Controller's traffic before they coordinate with them. Talking with that Front Line Manager later in his office; he admitted that he was not aware of Aircraft Y's position before he coordinated with me. Since Aircraft Y arrived almost immediately; that indicates that Aircraft Y was on a short left base and obstructed by the roof of the Tower Cab when the coordination was made. Thirdly; I as the Local Controller must be diligent in visually acquiring Aircraft Y traffic I am coordinating for. Extra care should also used when working with a front line manager that may not be as proficient at working traffic as a CPC.

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.