Tower supervisor and controller described a conflict event between a departure and arrival when the ...

Narrative:

We were in the middle of a moderate arrival and departure push. The wind situation made this a more complex operation than normal. The wind was variable 190 to 230. Wind speed was as low as 10 to as high as 17 KTS. Aircraft started to refuse take off clearance due to the tailwind component. The local controller was keeping the aircraft advised of the current wind conditions. I discussed the pilots concerns with both the osic and the tmu flm. After they talked it over I was advised we would remain on our current flow. The tmu flm requested the call signs of aircraft that were refusing to depart due to the current wind. Local controller was using his personal 'memory jogger' of turning the departing aircraft flight progress strip over until he was able to clear the 9L aircraft for takeoff. I completed a call to tmu when I noticed an A320 on takeoff roll runway 9R with a bizjet rolling out on runway 17. I asked the local controller if we were ok with the A320 and the bizjet; he replied 'no'. I immediately had the local controller relived and advised the osic of the situation. Recommendation; less land line conversations between the tower flm and radar room/traffic management.

Original NASA ASRS Text

Title: Tower Supervisor and Controller described a conflict event between a departure and arrival when the Local Controller failed to remember the landing aircraft; memory jogger techniques and coordination requirements listed as casual factors.

Narrative: We were in the middle of a moderate arrival and departure push. The wind situation made this a more complex operation than normal. The wind was variable 190 to 230. Wind speed was as low as 10 to as high as 17 KTS. Aircraft started to refuse take off clearance due to the tailwind component. The Local Controller was keeping the aircraft advised of the current wind conditions. I discussed the pilots concerns with both the OSIC and the TMU FLM. After they talked it over I was advised we would remain on our current flow. The TMU FLM requested the call signs of aircraft that were refusing to depart due to the current wind. Local Controller was using his personal 'memory jogger' of turning the departing aircraft flight progress strip over until he was able to clear the 9L aircraft for takeoff. I completed a call to TMU when I noticed an A320 on takeoff roll Runway 9R with a bizjet rolling out on Runway 17. I asked the Local Controller if we were OK with the A320 and the bizjet; he replied 'No'. I immediately had the Local Controller relived and advised the OSIC of the situation. Recommendation; less land line conversations between the Tower FLM and RADAR room/Traffic Management.

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	946702
Time
Date	201105
Local Time Of Day	1801-2400
Place
Locale Reference	ZZZ.Airport
State Reference	US
Aircraft 1
Make Model Name	A320
Operating Under FAR Part	Part 121
Flight Phase	Takeoff
Flight Plan	IFR
Aircraft 2
Make Model Name	Small Transport Low Wing 2 Turbojet Eng
Flight Phase	Landing
Person 1
Function	Supervisor / CIC
Person 2
Function	Local
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types Conflict Ground Conflict Critical

Tower supervisor and controller described a conflict event between a departure and arrival when the local controller failed to remember the landing aircraft; memory jogger techniques and coordination requirements listed as casual factors.