Second SFO Disaster Avoided Seconds Before Crash 248
sabri writes "On July 25th, flight EVA28, a Boeing 777 flying from Taiwan to SFO, was on the final approach for runway 28L when they were alerted by ATC that they were only at 600ft above the ground at less than 4NM from the threshold. SFO's tower directed the flight crew to climb immediately and declare missed approach. Assuming they were flying at 140 knots (typical approach speed of a 777), they were less than 2 minutes from the runway and at a 3 degree angle (approx 500ft/min descent), about a minute from impact. This is the same type of aircraft and runway used by the crashed Asiana flight. Similar weather conditions and awfully similar flight path. Is there a structural problem with computer-aided pilot's ability to fly visual approaches?"
NO (Score:5, Informative)
"Is there a structural problem with computer-aided pilot's ability to fly visual approaches?"
No, Just Pilot error. The 777 has constantly landed at SFO everyday for years without issue and the cause of the Asiana has been well-documented.
Re:What? (Score:5, Informative)
That would be nm. NM is Nautical Mile.
Re:This /. headline is sensationalist drivel (Score:4, Informative)
Re:NO (Score:4, Informative)
As a professional pilot, I have to agree that this seems to be a case of poor pilotage whether they were using the autopilot or not. This goes less to being under trained and more to complacency on the part of the flight crew. I would hazard a guess that the pilot of this one also had thousands of hours of flight time just as the pilot of the Asiana flight did (about 10,000 hours for the later). When flying an airplane one MUST be aware of where they are in the four dimensional space and where they should be; the term for it is "situational awareness". The "are" can be of the flight crews own making or caused by other factors and the "should be" may or may not be attainable. When the "are" is other factors and the "should be" is not attainable then it is a true accident.
Re:This /. headline is sensationalist drivel (Score:2, Informative)
Descending from 600ft at a rate of 500ft per minute only takes 72 seconds. You can't spool up and recover from a steep decline like that in a matter of seconds. It wasn't an emergency yet, but there was no time left for an argument or misunderstanding either.
Structural issue with Asian Airlines (Score:4, Informative)
I suggest you read this post from a former UAL Pilot and Flight instructor for Asiana:
http://originalforum.justhelicopters.com/DisplayThread.asp?BD=2020564&Page=1&ForumID=23&msgid=2020564&OM=2020564&Return=DisplayThread.asp&D83jsd=True [justhelicopters.com]
In short, the culture in SE Asia produces pilots who are well trained to operate an aircraft as a piece of Machinery, however are unable to "Fly".
Re:NO (Score:2, Informative)
My understanding is that the visual aid for 28L is PAPI [wikipedia.org], not VASI. Unfortunately, it and the ILS have been out of service since early June because they are moving the threshold for 28L northward, farther away from the seawall. With both ILS and PAPI out, you truly are making a "visual approach".
Speaking as an old Army ATC, I cannot imagine why they didn't move the PAPI at the same time they moved the threshold. It doesn't take that long to recalibrate it. ILS does take longer, but an in-place PAPI is a powerful aid to staying on-path and on-slope.
It's worse (Score:5, Informative)
responding to my own post because I looked at the data [flightaware.com].
At 1500 feet they were descending at 2220 feet per minute. I assume this is when ATC freaked out. By 800 feet they were 'only' descending at a rate of 1920 feet per minute. By 600 feet they were still descending at 420 feet per minute. The next measure they were still at 600 feet but ascending at 900 feet per minute. So somewhere between 600 feet and going down and 600 feet and going up, they were below 600 feet. The data resolution is every 15 seconds, so roughly speaking they probably hit 500 feet on the way down.
Assuming the decrease from 2200 FPM to 1920 FPM is the first indication of a correction, it took them 1000' of altitude to correct their rate.
So, based on their initial rate of 2200 FPM and a 500 foot "cushion", it looks like they had 13 seconds "extra" to spare, and at that we need to figure in how much higher the transponder is than the landing gear and figure in wave height. Somebody buy that ATC a beer (after work).
Disagree (Score:5, Informative)
Sorry, but I learned to fly at San Carlos airport (next to Redwood Shores, right adjacent to SFO airport and airspace) so I know a little bit of flying AND the area. I cannot see anything "unsafe" in the approach to SFO. Ofc I don't fly a "heavy", so if a pilot of one of those wants to disagree I'll bow to superior knowledge. But as long as there is no ("heavy") pilot who disagrees I'll say the only thing a LITTLE bit difficult is the approach over water.
However, even that is not an issue, you should have learned an easy way to track the point where you are going to touch down without ANY technical aids (we are talking visual approaches here, and visibility is near perfect in that area almost most of the time, esp. during the day): Keep your head in a position that you can easily remember and fix a point on the runway over a fixed point in front of you inside the airplane. When you look from your fixed head position over the fixed point inside the cockpit to the point on the runway it should not move. If it does (up or down) you are going to over- or under-shoot. That works independent of what the actual sink rate and speed (ergo the angle) is, always.
But then, my very own flight instructor later asked ME to demonstrate when I went on to learn aerobatics (i.e. "real flying") - turned out the "professional" pilots hardly ever do anything but "straight & level". Also, 5000 hours does not seem a lot if most of it is spent not just "straight and level", under computer control, and "at altitude". Only while maneuvering, incl. take off and landing, do you exercise flying skills. I said "flying skills", piloting skills include a lot more of course, from talking to ATC to calculating course, fuel, etc. etc. What those "professionals" seem to lack is good old FLYING SKILLS. It may sound strange from a lowly "small airplane pilot", but when I read that that Air France flight from Brazil went down because the pilots wanted to pull up when the airplane was in a stall (or close) - FOR MINUTES!!! - I really couldn't believe it - with some solid (small airplane!) training every pilot knows that you can never, ever pull UP to get out of trouble unless you have excess speed to trade for.
That doesn't mean I could fly a big airplane (wouldn't even be able to start it I guess), but while it does not matter to anyone that I lack the skills to fly a big airplane it matters to all passengers if the pilots cannot FLY (not "pilot") their airplane. I mean "fly" as in "without computer".
Is there an airline pilot here? I'm curious, what would you say about the FLYING skills of (big airplane) pilots? It seems that in the US the situation isn't bad, that this is an Asian (or Korean?) problem, and as I read it in an aviation forum not necessarily one of culture (at least not any more) but of many variables, including how easy it is for a lot of people to get to fly privately in the US vs. small countries like S.Korea, so that when a S.Korean wants to become a pilot they start from zero and do the training with an eye on the cockpit jobs (ASAP ofc, time is money), so no time/resources to do "fun flying" (like acro, which really, really teaches to fly). Then there's that even if you go into the job with good skills, how much is left after 10 years of mostly computer-aided careful "by the book" flying? How many pilots keep their (low-level) flying skills sharp by flying a small airplane in their spare time, to do "fun stuff" and "unusual attitudes and maneuverer"?
Re:Captain Wi Tu Low is at it again (Score:4, Informative)
It's not racist.
The airline was Asian and in English you can make phrases out of Asian sounding names.
Do you also consider jokes about "Oliver Klozoff" and "Yuri Nater" and "Ivana Tinkle" racist too?
Once you add "asian drivers" to the mix sure, but just the names is merely playing with the sounds of words.
Re:Disagree (Score:5, Informative)
I learned to fly at San Carlos too (and Palo Alto... West Valley Flying Club).
Take a look at:
http://webtrak.bksv.com/oak [bksv.com]
Put in 7/23/2013 and 8:45pm Look for EVA28. It will be a large purple plane coming in from the top left of the screen passing over the center of SFO at 11,000'.
The plane that crashed did the same thing. It pass over SFO at high altitude (common) and then turned cross-wide while rapidly descending. I live in Portola Valley and lived in Palo Alto... You can hear planes doing this because they make a very distinctive whooshing sound as they deploy flaps and decelerate.
EVA28 got to 600' and aborted landing between the San Mateo bridge and Coyote point.
I've heard from a 777 pilot, and this seems plausible to me... that this plane has an automated mode where it will auto-throttle when you're coming in for a landing, allowing you to pitch only and letting the plane handle the throttle.
The problem is on rapid descent, pilots will disengage the auto-throttle. If they fail to re-engage it... they'll pitch up as they're getting too low and expect the auto-throttle to kick in. When it doesn't, there isn't much time to realize it's off and either turn it back on, or throttle back up.
Worse, throttling up in these jets takes a while to kick in.
600'... if the description of the auto-throttle situation is correct... wow, that almost splashed.