PPRuNe Forums

PPRuNe Forums (https://www.pprune.org/)
-   Tech Log (https://www.pprune.org/tech-log-15/)
-   -   Did the Asiana crash have basically the same cause as the Indian Airlines A320 crash (https://www.pprune.org/tech-log/607078-did-asiana-crash-have-basically-same-cause-indian-airlines-a320-crash.html)

sheppey 28th Mar 2018 02:11


Now, this may work as intended, but it may also not. Because unlike manual flight, there can be quite a bit of logic involved in what modes are active and how the airplane is going to behave in reality vs. what's expected. So the sequence of button pushes and knob twists may not work
Well described. Yet another case here: Nice day but head in the cockpit pressing buttons

https://www.atsb.gov.au/publications...r/ao-2015-018/

vilas 28th Mar 2018 08:39

No matter what aircraft you fly , whether automatics or manual, you don't fly an approach without ever looking at speed. In Indian crash 27kts, in SFO crash 31kts below Vapp. Not a single call by anyone about speed. Both flights were command checks. Doesn't say much about the checker does it? All involved had lost their scan quite some time ago. They were an accident waiting to happen.

Timmy Tomkins 28th Mar 2018 12:41


Originally Posted by A Squared (Post 10099105)
This is what I'm having difficulty wrapping my mind around. How do you (in daylight, VFR conditions) not notice that the airplane you're piloting is on a trajectory to crash a half mile short of the runway?

Turkish Airlines did it at Schipol (circa 2007?) 3 on the flight deck busy talking

A Squared 28th Mar 2018 19:48


Originally Posted by Timmy Tomkins (Post 10099827)
Turkish Airlines did it at Schipol (circa 2007?) 3 on the flight deck busy talking

FWIW, both the Visibility and Ceiling were below VFR minima (Or at least US VFR minima) they were on a coupled approach following the glidepath.

Not that it excuses them, but It's easier for me to understand not catching the decreasing airspeed as the plane follows the glidepath. To be sure, an inexcusable lapse, but from my perspective very different than being on a visual approach in good vfr conditions and not taking action when your airplane is headed for an impact someplace a long way from the runway (aside from also losing track of airspeed)

I do agree that there are common elements; the autothrottles doing something other than what the pilots were expecting and a period of time where the autiothrottle mode was unrecognized or misunderstood.

FlightDetent 29th Mar 2018 01:20

The non-similarity issue of Asiana againstthe A320 is that if those Airbus gentlemen had only pulled, the A/C would have saved everyone. As well as their "initiation" of the doomed trajectory. They flew the aircraft by actively selecting a mode and not reviewing what they'd done.

Both of the Boeing cases OTOH, the crews found themselves through no wrongs of their own in a LOW energy situation ABOVE G/S, close to the ground. Walked over a trap.

Timmy Tomkins 29th Mar 2018 15:24


Originally Posted by A Squared (Post 10100188)
FWIW, both the Visibility and Ceiling were below VFR minima (Or at least US VFR minima) they were on a coupled approach following the glidepath.

Not that it excuses them, but It's easier for me to understand not catching the decreasing airspeed as the plane follows the glidepath. To be sure, an inexcusable lapse, but from my perspective very different than being on a visual approach in good vfr conditions and not taking action when your airplane is headed for an impact someplace a long way from the runway (aside from also losing track of airspeed)

I do agree that there are common elements; the autothrottles doing something other than what the pilots were expecting and a period of time where the autiothrottle mode was unrecognized or misunderstood.

Fair point re vis I guess. Discipline rules all the time good or bad WX.


All times are GMT. The time now is 20:31.


Copyright © 2024 MH Sub I, LLC dba Internet Brands. All rights reserved. Use of this site indicates your consent to the Terms of Use.