Originally Posted by
360BakTrak
Why not simply have the crossing aircaft switch to the controller working the relevant runway?! Far less chance of these sorts of incidents.
Simple answer: that’s not the way the FAA trains U.S. ATC.
Per 7110.65, 3-1-3, the local (tower) controller has primary responsibility for the active runway(s).
Ground control must obtain approval from the local controller to before authorizing any aircraft to cross an active runway.
The ground controller must then advise the local controller when the active runway cross is complete.
In the KDCA runway incursion (assuming the various video recreations are accurate), the SWA crossing clearance was issued prior to the JBU takeoff clearance. Thus, either the ground controller did not follow procedure by obtaining local controller authorization for the cross or the local controller did authorize the cross but then forgot he had done so and issued the JBU takeoff clearance. Note that in this incident, the local controller was handling 3 active runways (1, 4, 33).
Not convinced that saddling a single controller with issuing takeoff, landing, and crossing clearances would result in fewer runway incursions.