Welcome to Flightinfo.com

  • Register now and join the discussion
  • Friendliest aviation Ccmmunity on the web
  • Modern site for PC's, Phones, Tablets - no 3rd party apps required
  • Ask questions, help others, promote aviation
  • Share the passion for aviation
  • Invite everyone to Flightinfo.com and let's have fun

Asiana 777 crashed on landing at SFO

Welcome to Flightinfo.com

  • Register now and join the discussion
  • Modern secure site, no 3rd party apps required
  • Invite your friends
  • Share the passion of aviation
  • Friendliest aviation community on the web
"...speed decreasing below Vref and not being noticed.'

An excellent observation.

Forget the aircraft type and it's levels of automation...Where are YOUR eyeballs (and generally speaking, as is common procedure, the Other Guy's) ALL THE WAY DOWN THE APPROACH?

Pretty much, aren't they focused on Airspeed, Altitude, and ILS parameters with accompanying Call-Outs to be made for deviations....?

I believe this will come down to a "Cultural Differences in Operations" and/or a "Training Philosophy" type of thing, as many have speculated thus far. (along with the usual additional aspects of The Accident Chain. )

Just glad the carnage was minimal....So sorry for those two young kids and their families.

:(

Whine
 
Last edited:
NTSB highlights

-At 1600 feet, the autopilot was switched off.
-At 1400 feet, air speed was 170 knots.
- At 1000ft, airspeed was 149 knots,
- At 500ft airspeed was 134k.
- At 200 feet, airspeed was 118 knots, about 16 seconds prior to impact.
-At 125ft, the throttles were being moved forward & airspeed was 112kts.
-The target airspeed for touchdown was 137 knots.
-At about 3 seconds before impact, the FDR recorded its lowest speed of 103 knots. At this time, engines were at 50% power and increasing.
-At impact, air speed was 106 knots, a full 31 knots slower than the target speed
 
Who wants to bet the industry will learn nothing from this, save for maybe the actual professional pilots who understand this stuff?

I know it's still too early to speculate but the NTSB is putting out information about this accident faster than I've ever seen via twitter and other means so I think it's fair to at least start considering what may have occurred. My observations thus far:

- not surprising, Asian cockpit techniques... over-reliance on automation. Inability to actually fly an airplane. Volumes have been written about this issue. Yet the Asians quite regularly tell us Westerners to mind our business when we try to suggest they change their ways. I have personally seen this in India, Japan and Korea. Lots of trivial "make-work" cockpit stuff they do which takes attention away from flying the aircraft. If I had a nickel for every time I heard "You Americans think you know everything... " when working for various carriers in these countries.

- IOE. I've always thought IOE was a pretty risky event as it is. I recall years ago when a check-airman literally talked to me all the way across the Atlantic... all night long. Unreal. How much aviation crap do you have to cover? I was worn out before we even got to TOD. The approach was a blur. In fact I recall my neck being kinked from turning towards him as if to show I'm interested. If I knew then what I know now I would've told him enough is enough. It's impossible to cover it all in 25-40 hrs of IOE. Just show the student how to land and shoot approaches. It will take him or her another 300-1000 hrs to get comfortable with the airplane. That's just the way it is. Someone needs to start telling checkairman that it doesn't make them a bad instructor if they don't talk the whole flight. Cover a few items, yes. Maybe give some pointers on the arrival, approach and landing. But enough with the "let me show you how much I know" technique. Then again, maybe it's 180 degrees different in this case. Maybe the checkairman wasn't giving enough input, clearly not at the critical moments, if this Captain was elder and senior to him.

50% power when you're 35 kts below target speed? Are you kidding me?

- The dumbing down of aviation. Both Boeing and Airbus have strived to make today's aircraft dummy-proof. Which is why you see certain people hired into this profession because of who they know, rather than on their skills and competence. The conventional wisdom has become, "anyone can be trained to fly these things". Well, apparently not when things step outside of one's comfort zone. Even at my airline I see a few of pilots who lack basic airmanship skills. Look at all the posts on all the web-boards talking about what to do if the A/T does this or that. Who cares? Turn the auto-throttles off and fly the airplane. IMO, this should be a requirement. But I know that will never happen.

-Fatigue. These guys were landing a jet after a grueling 11 hr flight at their WOCL. No doubt they were probably awake for 16-18 hrs save for maybe a short nap on the airplane. They were sleep deprived and fatigued. No doubt about it. The fatigue issue was probably amplified if excessive instruction was being conducted across the Pacific. All of the contributing factors to fatigue will be probably be brushed under the rug.

At the end of the day, the so-called "experts" like that talking parrot Schiavo, or the annoying "aviation buff" Richard Quest, and the whole host of non-pilots who have zero idea about how we do our jobs will push for recommendations of further automation, more IOE, whatever.

The reality seems pretty simple, barring any MAJOR engine anomalies, these guys forgot how to fly an airplane likely due to a career defined by automation in the cockpit. Pretty stupid if you ask me. This and the Asian hierarchy variables has always been pretty well known and those of us who have witnessed it have always warned of it's dire consequences.
 
Well said SIR.

Overall, you bring the discussion to it's Essence:

" fly the airplane "

When the simplest tasks become obfuscated with Technology, Automation, Culture, Procedures, and Ego.....The simplest tasks can not be accomplished.

Airplanes stay aloft with one simple factor....."Airspeed".

Remove It....And the rest is for naught.


YKW
 
Last edited:
I know it's still too early to speculate but the NTSB is putting out information about this accident faster than I've ever seen via twitter and other means so I think it's fair to at least start considering what may have occurred.
No kidding. Instead of obfuscatiing information and dodging questions for months until no one cares anymore (and the corporate is glad for that), the NTSB practically gave the cause of accident out the day after-- "they.were.well.below.137.knots." Maybe so other pilots could take heed now, vice years later when new procedures and equipment is in place.

over-reliance on automation. Inability to actually fly an airplane
Saves money on training costs.

IOE. I've always thought IOE was a pretty risky event as it is. I recall years ago when a check-airman literally talked to me all the way across the Atlantic... all night long. Unreal. How much aviation crap do you have to cover? I was worn out before we even got to TOD
Big changes here I think. We don't do IOE much different from Asiana appears to. Again, to save money, cram as many check off items as possible into as few hours as possible. I see IOE getting much longer with possible segments with fed checks at different points in IOE rather than just one at the end.

The dumbing down of aviation. Both Boeing and Airbus have strived to make today's aircraft dummy-proof. Which is why you see certain people hired into this profession because of who they know, rather than on their skills and competence
This has been the very reason for outsourcing. Why be responsible for the skills and training of 10,000 pilots when you can unload 6,000 of them to a system that continual goes through "free-market creative destruction" into lower and lower costs until you have the very cheapest pilot money can buy--that is, one who is a whiz at automation of planes that fly themselves. Until they don't.

whymeworry said:
These guys were landing a jet after a grueling 11 hr flight at their WOCL.
New fatigue reg will help U.S. carriers in this area starting 4 January. But, predictably, many carriers are still building trips that ignore the science of fatigue right up to January 3rd. A late afternoon flight, then a 2-hour sit, and then a west coast to east coast redeye, all in one duty period with two pilots. Not legal under new FAR, clearly counter to the science of the new FAR, but legal and cheaper, so do it.
 
-At 1600 feet, the autopilot was switched off.
-At 1400 feet, air speed was 170 knots.
- At 1000ft, airspeed was 149 knots,
- At 500ft airspeed was 134k.
- At 200 feet, airspeed was 118 knots, about 16 seconds prior to impact.
-At 125ft, the throttles were being moved forward & airspeed was 112kts.
-The target airspeed for touchdown was 137 knots.
-At about 3 seconds before impact, the FDR recorded its lowest speed of 103 knots. At this time, engines were at 50% power and increasing.
-At impact, air speed was 106 knots, a full 31 knots slower than the target speed

These numb-nuts must have been enjoying the view out the window. They sure as heck weren't flying the plane. I wonder if they knew what the stick-shaker was when it fired....

...'heads up A$$'...comes to mind here...
 
These numb-nuts must have been enjoying the view out the window. They sure as heck weren't flying the plane. I wonder if they knew what the stick-shaker was when it fired....

...'heads up A$$'...comes to mind here...


They probably screwed up, but you're a DICK!
 
"...speed decreasing below Vref and not being noticed.'

An excellent observation.

Forget the aircraft type and it's levels of automation...Where are YOUR eyeballs (and generally speaking, as is common procedure, the Other Guy's) ALL THE WAY DOWN THE APPROACH?

Pretty much, aren't they focused on Airspeed, Altitude, and ILS parameters with accompanying Call-Outs to be made for deviations....?

I believe this will come down to a "Cultural Differences in Operations" and/or a "Training Philosophy" type of thing, as many have speculated thus far. (along with the usual additional aspects of The Accident Chain. )

Just glad the carnage was minimal....So sorry for those two young kids and their families.

:(

Whine


Where their eyeballs usually feel the body clock telling them they are: 3:30 am in REM sleep. That's the local Seoul time when this accident happened. I'm not saying they were in deep sleep, but landing after a long flight at 3-4am body clock time can lead to fatigue/tiredness and performance issues related to that. There were two crews, each takes a break on the Seoul-SFO flight. How long did each crewmember actually sleep in their rest break? Previous 72 hr lookback rest? There are so many human performance issues that are not known yet. This needes to come out, and over time it will.

No accident is ever just one simple reason. It's a chain of events, and one of those chains likely will be a tired crew landing at 4am their body clock time.
 

Latest resources

Back
Top