3 ms·
I'm a private pilot who has flown into SFO once, and flies over SFO on a regular basis (I'm based at Palo Alto airport). This is not being overblown. If you l
by lisper 9y ago
I'm a private pilot who has flown into SFO once, and flies over SFO on a regular basis (I'm based at Palo Alto airport). This is not being overblown. If you listen to the audio tape, the tower orders the go-around at the 33 second mark, and United 1 reports that "Air Canada flew directly over us" 16 seconds later. That is a breathtakingly close call.
Safety margins are wide when pilots don't screw up. But this one did. Royally.
- dotancohen 9y ago> Safety margins are wide when pilots don't screw up. But this one did. Royally. And the safety margin was wide enough to absorb that screw up. This is _why_ we have wide safety margins. So that one screw up doesn't absorb all of it. People will always screw up, and policy accounts for that fact.
- lisper 9y ago> And the safety margin was wide enough to absorb that screw up. Barely.
- wfunction 9y agoCan you tell me what the second safety margin that kicked in here and saved them was? Seems to me that it was another pilot noticing them and asking "Where's this guy goin'?" which is not something I'd consider to be a safety margin kicking in... it sounds like sheer dumb luck, where the last margin had already failed.
- CaliforniaKarl 9y agoUnfortunately we don't have enough information here to know for sure. For example, the approach controller may have noticed that a plane they recently handed off to Tower was not yet lined up. The controller would then call up to Tower to make Tower aware of the issue. Or, Tower may have a screen showing them a radar view of the approach, similar to Approach's screen. They may have noticed it there. But, the nature of aviation radio is such that you use one frequency to transmit and receive. That means you can't speak over anyone else; you have to wait for them to stop talking before you can start. And if you mess up, there's no easy way for you to know (except when someone else on frequency says "blocked").
- jbg_ 9y ago* Conditions were clear. The pilot landing would likely have seen the aircraft on the ground in plenty of time to go around. * Conditions were clear. The pilot landing would have an increasing probability of noticing their mistake from lights on the runway and taxiway as they got closer to landing. * After being alerted that the pilot landing could see lights on what they thought was the runway, the ATC would likely have paid closer attention to the various tools available to them to see the location and heading of the aircraft. And finally, the one factor that happened to be the first of these to happen: * Multiple pilots looking directly toward the oncoming aircraft, one of whom alerted ATC. Just because this happened first doesn't mean the other things failed or wouldn't have happened.
- wfunction 9y ago> And finally, the one factor that happened to be the first of these to happen: > * Multiple pilots looking directly toward the oncoming aircraft, one of whom alerted ATC. I don't get this. You're an engineer/pilot/whomever filing for {the current system/pilot/plane/whatever-needs-approval} to get approved. The power-that-be (e.g. FAA) asks you what your safety margins are. You cite "other pilots looking directly at my aircraft in the 30-second span of my mistake" as one of your "safety margins"? ...what?
- dotancohen 9y agoIf you think that's bad, wait until you discover what safety margins exist on the highways, and how much professional training drivers receive.
- deleted 9y ago[deleted]
- jbg_ 9y agoI'm inclined to agree with you. Airports tending to be full of hyper-aware pilots who are communicating on the same radio frequencies as you shouldn't really be considered a safety margin, but it can still prevent accidents sometimes. Incidentally, Aviation Herald reports[1] that "AC-759 had already overflown taxiway C by about 0.25nm when ATC instructed the aircraft to go around" and further that "it is estimated that AC-759 overflew the first two aircraft by 100 feet". 100 feet isn't much, and I imagine this was utterly terrifying for the pilots lined up on the taxiway, but 0.25nm past the beginning of taxiway C is basically touchdown point on the runway (had they been lined up with it), and they were still 100 feet above the ground. That indicates pretty strongly that the pilot of AC-759 had noticed their mistake and was taking evasive action already, before ATC instructed them to go around. [1] https://avherald.com/h?article=4ab79f58&opt=0 https://avherald.com/h?article=4ab79f58&opt=0
- baq 9y agoconsidering that jet turbines take 5 seconds to spool up to go-around and 8 to full thrust at landing airspeeds (...not entirely sure if that's correct - that's the best i could google), the margin was about 10 seconds. i'm inclined to agree that it should be a terrifying incident that ended in a successful landing.
- mikeash 9y agoThe recording is edited for highlights. The LiveATC archive has a ~40 second interval between "go around" and "flew directly over us" and even that archive is edited to remove silence, so the real interval may have been even longer.
- lisper 9y agoCan you post/link the unedited version? I can't find it. Notwithstanding the timing on the tape, the AC jet could not have been very far away because the fact that he was lined up with the taxiway was first noted by a plane on the ground. That would not have been evident unless the plane was very close.
- mikeash 9y agoThere's a less-edited version here: http://archive-server.liveatc.net/ksfo/KSFO-Twr2-Jul-08-2017-0630Z.mp3 http://archive-server.liveatc.net/ksfo/KSFO-Twr2-Jul-08-2017... The action starts at about 14:45. I suspect there isn't much silence removed in this particular area, so 40 seconds may be close to the actual time. I haven't been able to find a pure unedited version. They may not be saved.