DAB Controller described a technical loss of separation event during a LAHSO operation resulting from confused coordination efforts between positions in the Tower; listing construction as a contributing factor.
Synopsis
DAB Controller described a technical loss of separation event during a LAHSO operation resulting from confused coordination efforts between positions in the Tower; listing construction as a contributing factor.
Narrative
I was working Ground Control. Construction was in progress on Taxiway Whiskey and Papa (two frequently used routes). All aircraft needed to cross Runway 7L had to use Runway 16 or Taxiway Echo. Aircraft Y was inbound on Runway 16 to hold short of Runway 7L. Cab coordinated/requested that I release Runway 16 north of Runway 7L to Local Control which I did; after issuing hold short instructions to those aircraft previously cleared to cross. Aircraft X called ready to taxi back to the ramp from Runway 7R and Runway 16. I already had several aircraft on Taxiway Echo waiting to cross 7L so I instructed Aircraft X to taxi straight ahead on Runway 16 and hold short of Runway 7L. At that moment; it did not occur to me that I could only use my portion of the runway to cross aircraft; not to taxi them. No traffic was issued to either Aircraft X or Aircraft Y. Both aircraft were instructed to old short of Runway 7L; one from the north and one from the south; which they complied with. Not having construction going on during peak hours would have helped.
Second reporter narrative
I was working the Cab coordinator position. There were two Local Controllers and one Ground Controller. Training was being preformed on Local 1. The airport was landing on Runway 7L/R. One primary taxiway was closed for painting which increased both workload and complexity. The arrival sector set up an arrival for the crossing Runway 16. This runway belonged to Ground Control for aircraft movement. I coordinated with Ground Control for release of Runway 16 to Local 1 for the landing aircraft. While the Controller was stopping traffic short of the runway; I tried to locate the memory strips we use as memory aids. One was missing from the Tower so we only had two. Ground released the runway and I gave the Controller one of the two memory aids. I informed Local 1 that Runway 16 was released to them and handed him the second memory aid. I then went to Local Two and informed them that traffic was landing Runway 16 to hold short of Runway 7L. I did not have a memory aid the give them. At some point; Local 2 had turned an aircraft off on Runway 16 and told them to contact Ground. I was monitoring Local 1 frequency at the time and did not here Local 2. At some point the Aircraft X called Ground Control. Ground did not taxi the aircraft clear of Runway 16 but instead taxied them opposite direction to the landing traffic. I did not know of this. I was assisting Local 1 with keeping an eye on the trainee working the position. When I turned during a scan I saw Aircraft X trying to turn off the runway into the construction area on Taxiway Papa. There were numerous trucks and personal in this area painting the taxiway. I also noticed the landing aircraft (Aircraft Y) was rolling out on Runway 16. I asked Ground Control what that aircraft (Aircraft X) was doing on Runway 16. The Controller said Local One was holding short so he/she was taxing on the runway. The FLM in the Tower was made aware of the situation at that point. First the missing memory aid in the Tower needs to be replaced. Second painting of major taxiways should be limited to off peak hours when possible. Third when taxiway options are limited for Ground Control LAHSO operations should not take place on the crossing runway.
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.