Regardless, I think it's too early to lay definitive blame until the NTSB report comes out.
They spent a minute extra before starting their takeoff roll; it wouldn't have hurt to wait an additional 5 minutes. Commercial flights build in a generous margin for ground ops these days. I doubt this was a factor in this specific case.
> maybe lost them their place in the queue, etc.
They were at the runway already, there's no way for them to have lost their place in the queue for that runway 18L [1].
[1] https://upload.wikimedia.org/wikipedia/commons/a/a9/AUSFAA.p...
Sure there is, enter the runway at bravo, right turn foxtrot, left on alpha and join the conga line. Happens all the time at places like JFK (admittedly Austin is not JFK).
> Sure there is, enter the runway at bravo, right turn foxtrot, left on alpha and join the conga line. Happens all the time at places like JFK (admittedly Austin is not JFK).
This routing appears to require the SouthWest aircraft to enter the active runway with FedEx Heavy on Final to that end, presumably the problem we're trying to avoid ...
In both cases, SW would be well within their rights to say "unable to comply".
More will surely be revealed in the follow up investigation and right now it's all armchair piloting. But I too am a little surprised the Southwest flight took its sweet time to do anything and was seemingly unaware of what was going despite being explicitly informed.
To your point though, we also don’t know what was going on in the cockpit of the 737. Even if they were aware of how close the FedEx jet was, it’s entirely possible something went wrong that caused them to delay the takeoff roll (assuming it was delayed).
There are plenty of things that could have gone wrong on the ground. Separating traffic is the ATCs job and clearly there was a loss of separation. Very hard for me to see how this could be Southwest’s problem particularly since they weren’t yet airborne.