Slashdot Mirror


Second SFO Disaster Avoided Seconds Before Crash

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?"

20 of 248 comments (clear)

  1. Captain Wi Tu Low is at it again by Lost+Found · · Score: 5, Funny

    Clearly he learned so much from his last flight

    1. Re:Captain Wi Tu Low is at it again by Anonymous Coward · · Score: 5, Funny

      Wrong airline, that's a copilot and you misspelled his name. The pilots first named in the Asiana crash were Captain Sum Ting Wong, Wi Tu Lo, Ho Lee Fuk and Bang Ding Ow". Those names turned out to be wrong though. Other suggestions included Park Ma Plen Tu-Sun and Ha Yu Lan Dis Tang. KTVU's news director "Munchma Quchi" may be to blame for the errors, reported investigative journalist Stephen Colbert.

    2. Re:Captain Wi Tu Low is at it again by lgw · · Score: 5, Funny

      Oh, you're just homophonophobic.

      --
      Socialism: a lie told by totalitarians and believed by fools.
  2. NO by Quick+Reply · · 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.

    1. Re:NO by Anonymous Coward · · Score: 5, Insightful

      To be fair, it does show how dependent these pilots are becoming on their computers. And if they fuck up this often when ILS is down, you have to wonder if they would ever catch it if ILS was miscalibrated or spoofed.

    2. Re:NO by deck · · 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.

    3. Re:NO by bobbied · · Score: 5, Insightful

      To be further in tune with the facts here.... There are more approach aids than the ILS. Safety in aviation is layered and in the case of approach aids there are at least three more ways a pilot should be able to use to judge his approach and correct. There are the VASI lights which tell you if you are too high or low. There are the markings on the runway, which are of standard sizes and locations which aid the pilot who is looking out the windows. Then there is the "visual picture" that the pilot will have seen many times before when landing, even if only in the simulator.

      Any of these *should* have been enough to safely land.

      My guess is that what really happened here is a combination of ATC directions and pilot errors. ATC likely directed a short approach which started pretty high making it difficult for the pilots to properly stabilize the approach. The inexperience of the pilot in command contributed to the issue because it took him longer to make all the complex adjustments, get the gear down, flaps down, get on the glide path at the proper airspeed and complete the landing checklists and he lacked experience to recognize what was happening. The PIC got behind the aircraft and by the time they realized the sink rate was way to high they where to low and slow to recover. They landed way short.

      This is an old story, told time and time again. A flying aircraft does not wait for the pilot who doesn't keep ahead of the situation. Landing and take off phase of flight are fast paced (compared to other phases) and also the least forgiving of falling behind. The PIC fell way behind and failed to fly the aircraft properly. He failed to recognize the danger and deal with the problem and was lucky to survive. In this case I don't think ILS wold have mattered.

      --
      "File to fit, pound to insert, paint to match" - Aircraft Maintenance 101
    4. Re: NO by Mabhatter · · Score: 4, Insightful

      This was brought up in the other crash, that ATC keeps giving exceedingly difficult directions because the AIRPORT has allowed the nearby area to be unsafe... Don't disturb suburbs, malls, and factories that weren't built and shouldnt have been zoned when the runway was built because "they'll feel bad".

      So they issue increasingly dangerous commands to pilots and just expect them to turn on the robot. Then the airport doesn't keep it's maintenance up or scheduled construction and TURNS OFF some the electronic aids used by the robot... Yet doesn't modify the instructions to make them safer.

      The previous crash brought up that this standard approach is more like somebody screaming "TURN NOW!" From the backseat...as a matter of "common practice" again, because it "upsets" neighbors zoning allowed in the flight path not because of technical need.

    5. Re: NO by bobbied · · Score: 5, Insightful

      ILS approaches take time. You have to set up to intercept the final fix at a specified altitude with the aircraft flying the right direction on the localizer. This final fix is usually about 5 miles out and 3,000 AGL. Flying a full standard ILS approach is not normally done because it takes at least 5 min to establish on the localizer going outbound, Cross the outer marker, do the outbound leg and procedure turn to get yourself on the localizer and glide-slope before you cross the outer marker again. Even a "radar assisted" approach takes 3 or so min to get you on the localizer and glide-slope at a set altitude over the outer marker.

      Why do I go though all this? To tell you that turning off the ILS on a clear day is not a factor here. They simply do NOT fly ILS approaches on clear days at busy airports. Nobody has the time. They fly visual approaches almost exclusively because it's faster and easier. They may have the ILS approach configured and may actually look at the needles during the approach, but if you are flying visual approaches, you spend more time looking out the window.

      ATP pilots are usually quite capable of flying their aircraft in very difficult circumstances. The experience and training required to be rated in a large commercial aircraft are pretty high. The folks who meet these requirements are fully capable of flying with or without the automation and must demonstrate their abilities before they are allowed to sit in the cockpit. Flying visual approaches without automation (ILS or otherwise) is not a problem for these guys. Some are better than others at this, but everybody can. It's basically how everybody starts learning how to fly. Small single engine land aircraft fly these kinds of approaches nearly every time and most pilots learn to fly in single engine aircraft.

      What is a problem is that ATC many times asks pilots to do really dangerous things. Flying short, steep and unstabilized approaches makes automation pretty much useless. Given this new revelation, it seem to me that ATC procedures contributed to this accident. I don't think that we have a case where dependance on automation is a problem. What we have is ATC asking pilots to do dangerous things when low and slow. This accident isn't about the ILS being turned off. The weather was clear, nobody would have used the ILS had it been on anyway.

      --
      "File to fit, pound to insert, paint to match" - Aircraft Maintenance 101
    6. Re: NO by sabri · · Score: 4, Insightful

      What is a problem is that ATC many times asks pilots to do really dangerous things. Flying short, steep and unstabilized approaches makes automation pretty much useless. Given this new revelation, it seem to me that ATC procedures contributed to this accident. I don't think that we have a case where dependance on automation is a problem. What we have is ATC asking pilots to do dangerous things when low and slow. This accident isn't about the ILS being turned off. The weather was clear, nobody would have used the ILS had it been on anyway.

      When ATC gives you a clearance which you can't comply with, any PIC has just one answer: "unable".

      Many of these carriers are mandating their pilots to use automation, so the ILS being turned off is a major issue, regardless of them having 250 hours in a SEP/MEP.

      And again, the only person responsible for the safety of any flight in a servicable aircraft is the captain. He can override ATC at any time, of the safety of the flight dictates him to do so. All he needs is to declare an emergency.

      --
      I'm not a complete idiot... Some parts are missing.
  3. So who was phone? by JeanCroix · · Score: 4, Funny

    Is there a structural problem with computer-aided pilot's ability to fly visual approaches?

    Parse fail. I've even had my 3 cups of coffee and I got nothin'.

  4. The only solution by Anonymous Coward · · Score: 5, Funny

    is to ban all airplanes. Because of the children.

  5. Re:What? by Qzukk · · Score: 4, Informative

    That would be nm. NM is Nautical Mile.

    --
    If I have been able to see further than others, it is because I bought a pair of binoculars.
  6. This /. headline is sensationalist drivel by TFoo · · Score: 5, Insightful

    Yes, they were below the glidepath, and yes they blew the approach and had to go around: but this is hardly seconds from disaster or even a close thing. 600' at a normal approach speed is not "close" to the ground and 3.8 NM is more than 3 minutes at Vref which is certainly adequate time to respond.

    These kinds of things happen and the only reason we're even hearing about this one is that it happened at SFO 28L.

    I expected a little less sensationalism and a lot more intelligence from slashdot.

    1. Re:This /. headline is sensationalist drivel by Dwarfgoat · · Score: 4, Funny

      I expected a little less sensationalism and a lot more intelligence from slashdot.

      You must be new here. ;)

      --
      That? That was a pigeon.
    2. Re:This /. headline is sensationalist drivel by Ethan+Black · · Score: 4, Informative

      4 NM / 140 knots = about 1.7 mins (Like the summary says). Not more than 3 minutes. Just a little nitpick; your overall point is still correct: 2 minutes is a LONG time in this kind of situation. Possibly embarrassing for 777 pilots to be doing while in VMC (Visual Meteorological Conditions). Definitely NOT newsworthy. (I fly for a living, missed approaches happen).

  7. TLA overload in OP's FYI from the FAA - WTF? by Overzeetop · · Score: 4, Funny

    So the LDA is OTS at SFO and the FAA published RNAV PRM for SOIA. TTL that ATC stepped in or EVA28 would have been SOL and all passengers DOA.

    --
    Is it just my observation, or are there way too many stupid people in the world?
  8. It's worse by bill_mcgonigle · · Score: 4, Informative

    responding to my own post because I looked at the data.

    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).

    11:54PM 37.5516 -122.2160 298° West 167 192 2,500 -840 Descending FlightAware
    11:55PM 37.5571 -122.2290 298° West 166 191 2,300 -1,200 Descending FlightAware
    11:55PM 37.5629 -122.2420 299° West 174 200 1,900 -1,560 Descending FlightAware
    11:55PM 37.5687 -122.2560 298° West 180 207 1,500 -2,220 Descending FlightAware
    11:55PM 37.5747 -122.2700 298° West 182 209 800 -1,920 Descending FlightAware
    11:56PM 37.5800 -122.2830 297° West 166 191 600 -420 Descending FlightAware
    11:56PM 37.5858 -122.2970 298° West 173 199 600 900 Level FlightAware
    11:56PM 37.5922 -122.3120 298° West 188 216 1,100 2,340 Climbing FlightAware
    11:56PM 37.5950 -122.3190 297° West 187 215 1,500 3,600 Climbing FlightAware
    11:57PM 37.5981 -122.3270 296° West 199 229 2,000 2,700 Climbing FlightAware
    11:57PM 37.6047 -122.3450 295° West 224 258 2,600 1,500 Climbing FlightAware
    11:57PM 37.6116 -122.3630 296° West 230 265 2,800 720 Climbing FlightAware

    --
    My God, it's Full of Source!
    OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
  9. Disagree by mha · · 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"?

    1. Re:Disagree by MrEdofCourse · · 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

      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.