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.
Synopsis
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.
Second reporter narrative
While working multiple runways; there was a tailwind that varied from 230 to 190 at 12 to 16 KTS. Several aircraft informed me that they would be unable to depart. An A320 was holding in position on Runway 9L for departure. During the time of going back and forth with the pilots about who could go and who couldn't; a bizjet checked in on a short approach for landing on Runway 17. I cleared the bizjet to land. Using my memory jogger; I turned the flight progress strip of the A320 upside down. While waiting for the bizjet to land; I cleared several aircraft to cross Runway 9L into the ramp. The ramp was very congested; so I had to get several gate assignments from the aircraft that needed to cross the runway. When the aircraft crossing the runway cleared; I turned the flight progress strip of the A320 right side up. I checked with the A320 to see if they could still depart with the tailwind. They replied that they could; I then cleared the A320 for departure forgetting about the bizjet landing on Runway 17. When I realized my mistake; I felt it was safer to allow the A320 to depart and the bizjet to land knowing that the bizjet would be able to hold short of Runway 9L. Recommendation; [I need the] use of different memory joggers.
More incidents for this aircraft family →
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.