A Tower Local Controller and a Ground Controller reported the Local Controller cleared an aircraft for takeoff before a previous arrival had taxied off the runway.
Synopsis
A Tower Local Controller and a Ground Controller reported the Local Controller cleared an aircraft for takeoff before a previous arrival had taxied off the runway.
Narrative
I was working local control and it was a busy night. Weather was bad and we were in swap. We started off landing runway XX but needed to change to land runway XY due to the winds. Ceilings were reported between 250 ft and 400 ft. The operation on the overnight shift is complicated by a large taxiway closure; taxiway 1; which limits us to one taxiway for arrivals; departures; and repositions for overnight parking. This particular runway combination where we land runway XY and depart runway XZ is one where a lot of coordinating takes place. Aircraft landing have to exit and taxi on the same taxiway as the opposite direction departures so planning ahead and good coordination between ground control and local is critical to a successful operation. On this particular night most of the aircraft were rolling out a little longer than normal so they roll through the intersection and have to be brought back to the other side of the field. We had to utilize taxiing on runway XZ when we had time between departures to be able to keep the airport moving during this busy time. Ground control had asked for use of runway XZ the last time for Aircraft X so he could get the aircraft out of the way. I believe the aircraft missed the first instructed turn off point and was given alternate instructions. I instructed Aircraft Y to line up and wait while waiting for the next arrival to land and for Aircraft X to clear the departure runway. It was foggy with not great visibility and I missed Aircraft X in my scan when I cleared Aircraft Y for takeoff. Aircraft X went off immediately and I instructed the departure to stop; which they did. Thus far the construction project has been manageable to work around; but with the busy travel/ bad weather season almost upon us; a little more flexibility of not closing needed taxiways during busy swap events would definitely make a difference.
Second reporter narrative
ILS Rwy XX. Twy 1 closed between Twy 2 and Twy 3. Due to the taxiway closure; inbound traffic was using Rwy XY to taxi past the outbound traffic on Twy 4. LC (Local Control) turned the arriving Aircraft X onto Rwy XY and switched him to my frequency (GC). I advised Aircraft X to turn right at Twy 5 then taxi 6;4;7;1 to parking. Aircraft X read the instructions back correctly but then slowly taxied by Twy 5. I informed LC that Aircraft X did not turn on 5 and will exit the Rwy at Twy 8 instead. LC acknowledged and told the next arrival; who was on Twy 6; that the previous arrival was not turning at Twy 5 and that they could join Twy 4 and contact GC. Shortly thereafter; the next arrival landed and exited Rwy XX; LC then cleared Aircraft Y for takeoff of Rwy XY; while Aircraft X was still taxiing on Rwy XY to exit at 8. Realizing the conflict; I implored Aircraft X to expedite its exit from the runway and they complied. LC told Aircraft Y to stop and they were able to cancel their takeoff. Both aircraft taxied back to their ramps. There should be a way of identifying a runway conflict on the ASDE prior to takeoff. Meaning that if the ASDE detects that there is an aircraft in position and something is on the same runway that would be a conflict; the aircraft in position would turn red to let the controller know that they should not launch. There should be a clearer decision-making process when it comes to giving away crucial taxiways for construction. If we are in SWAP and there are traffic pushes; that should supersede a construction closure.
More incidents for this aircraft family →
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.