Be careful....

Meh we've gotten some pretty in depth debriefs before, but not stuff that I'm going to go plaster on the internet. The NTSB will probably be involved on this one.
Any idea if the 767 would be doing an autoland here or do they have HUD assist?
 
Any idea if the 767 would be doing an autoland here or do they have HUD assist?

I’m still a new CA on the 767, but looking at that weather, runway, NOTAMS, and available approaches I would elect to do a Cat 3 autoland (or in my case as a high mins CA, I’d have to do a Cat 2 autoland).

Only caveat is I don’t know if they had any MELs that would affect that. Not sure how much EFVS would help either, but certainly I would’ve been monitoring TCAS.
 
These kinds of things happen, even though they shouldn’t. At least we have some modern systems and technology that can help flightcrews detect aircraft on the runway that crews such as USAir 427 / SKW 5569 didn’t have available back in the day.
 
767 hater!

10F21FEB-FF35-4148-89B5-2C4C9A045D69.jpeg
 
Any idea if the 767 would be doing an autoland here or do they have HUD assist?
I am nearly they were doing an autoland. I listened to a longer recording. On their initial check-in with Tower, they said they were doing the ILS CAT III to 18L.

The HUD would still be down and the EFVS most likely turned on.
 
Rumors in the ATC world are that with this particular individual it was deemed only a matter of time.
I hate to dogpile, but is it normal to schedule same runway ops with no visual separation in cat II conditions and then just expect everything to happen the right way? People in my circles are trying to hate on WN for not rolling, but minus the "I'd be squirming up a storm if I was them" aspect, as far as I can tell there is no immediacy requirement for takeoff. The same situation would exist if they had to reject.

The controller seemed very checked out, from the audio.

To me, it sounds like FedEx called Southwest to abort and then went on the go, which IMO was pretty good.
 
I hate to dogpile, but is it normal to schedule same runway ops with no visual separation in cat II conditions and then just expect everything to happen the right way? People in my circles are trying to hate on WN for not rolling, but minus the "I'd be squirming up a storm if I was them" aspect, as far as I can tell there is no immediacy requirement for takeoff. The same situation would exist if they had to reject.

The controller seemed very checked out, from the audio.

To me, it sounds like FedEx called Southwest to abort and then went on the go, which IMO was pretty good.

I don’t have tower experience so someone else will have to answer, but one quote I read is “the CIA should investigate this guy cause only Al Qaeda would have issued that clearance.”
 
Whats crazy/sad/frustrating is that most facilities have a person like this, I would say. The career long trainee who files complaints about everything the minute it becomes apparent he/she cannot actually separate aircraft and issue safety alerts. Nothing is ever this persons fault, and everybody else needs to just work around them because management is too afraid of the threat of a lawsuit for EEO stuff that they just let it all go. "They'll get better after they certify".

Agency wide, staffing is so terrible that alot of places feel forced to sign everyone off because god dammit, we need the bodies, and you may suck at this job but getting you certified is my only hope of ever getting off 6 day work weeks. Then factor in all the COVID sign offs who management rushed through in order to pretend like our staffing was better, who have never seen real traffic in their entire training career, now on their own and struggling mightily. I see it literally every day at work, working around weak controllers who get completely overwhelmed the second traffic picks up and have no business on the radio.

Whats sad is that the FAA is just going to move and/or promote this guy again, or come up with some stupid rule about having every position in the facility split at 630AM, all because this one idiot that from the sounds of it never should have been working AUS Tower by himself to begin with tried to slam his only two planes together, and from what the tapes sound, make absolutely no effort to ever separate them.

Whats crazy is that from what Ive read, there wasnt anybody coming in behind FDX either. It wouldve been a 2-3 min wait for the SWA to go off safely, and this wouldnt be national news. Just absolutely no excuse for that decision from the tower controller.
 
Whats crazy/sad/frustrating is that most facilities have a person like this, I would say. The career long trainee who files complaints about everything the minute it becomes apparent he/she cannot actually separate aircraft and issue safety alerts. Nothing is ever this persons fault, and everybody else needs to just work around them because management is too afraid of the threat of a lawsuit for EEO stuff that they just let it all go. "They'll get better after they certify".

Agency wide, staffing is so terrible that alot of places feel forced to sign everyone off because god dammit, we need the bodies, and you may suck at this job but getting you certified is my only hope of ever getting off 6 day work weeks. Then factor in all the COVID sign offs who management rushed through in order to pretend like our staffing was better, who have never seen real traffic in their entire training career, now on their own and struggling mightily. I see it literally every day at work, working around weak controllers who get completely overwhelmed the second traffic picks up and have no business on the radio.

Whats sad is that the FAA is just going to move and/or promote this guy again, or come up with some stupid rule about having every position in the facility split at 630AM, all because this one idiot that from the sounds of it never should have been working AUS Tower by himself to begin with tried to slam his only two planes together, and from what the tapes sound, make absolutely no effort to ever separate them.

Whats crazy is that from what Ive read, there wasnt anybody coming in behind FDX either. It wouldve been a 2-3 min wait for the SWA to go off safely, and this wouldnt be national news. Just absolutely no excuse for that decision from the tower controller.

Can't you just stick those people on running clearances?
 
To me, it sounds like FedEx called Southwest to abort and then went on the go, which IMO was pretty good.
IMO, the FedEx crew calling for the Southwest crew to reject wasn’t a good thing. All it did was create confusion, which could have potentially made things worse. Not to say they were in the wrong, because this squarely falls on ATC. Although I will say this about the Southwest crew. If they did a standing takeoff (is that policy over there with low vis?) they should have informed ATC knowing that traffic was on a 3 mile final. I’m sure ATC was counting on the typical quick roll from Southwest.

Not that this is related, but wasn’t this the same controller that was on freq during the Virgin/Southwest drama a few weeks ago?
 
Back
Top