Originally Posted by
mngmt mole
Without trying to be a "Monday Morning Quarterback" (look it up), there are certain basic essential skills in this job (especially as a Captain). One of them is not infringing a parallel localizer in an airport such as SFO. Although the UA should also be held to account, we cannot be making errors like this. Needless to say, the prior post correctly identifies the main problem, one that will steadily get worse. When you replace experience, judgement and confidence with low time and rote learned computer warriors, you are simply counting down the days to disaster. Not this time, but soon enough. One day our senior management (and all their predecessors since about 1994) will have the blood of hundreds on their eternal consciences. There is no doubt on that point. Tick tock....
This is undoubtedly true. If it was simply forgetting to arm the LOC. Fine, it happens, although arguably someone in a four man crew ought to pick that up. However, allowing the aircraft to fly through the final track and onto the path for 28R whilst simultaneous visuals are in progress is a no-no!!! The aircraft needs to be disconnected and hand flown to ensure separation. Yes, UA needs to avoid CX as the following traffic, but I bet they were surprised to see CX blow through the LOC. In that case, they have no choice but to climb and perhaps turn to keep CX insight.
The infrastructure at SFO is not ideal, but it isn’t changing anytime soon due to environmental regulations. Airlines have operated safely there for decades using simultaneous parallel visuals and departures off the ones. CX and other Asian carriers are almost always given the easier assignment, which is straight in while domestic carriers get the visual following traffic. Par usual, CX makes mountains outta molehills.