AF 447 Thread No. 8
Join Date: Aug 2005
Location: fl
Posts: 2,561
Likes: 0
Received 0 Likes
on
0 Posts
I have never fllown with a side stick but no Boeing pilot at FL350 would pull back to the stops if he lost his airspeed and autopilot, why would an Airbus guy do it? No monitoring pilot would let the pilot flying do it either. Is this really how Airbus pilots normally fly?

@ bubbers, et al
Yep, beats the hell outta me. Hold what ya got and analyze the situation.
maybe the "boldface" or whatever the commercial folks call it was not a good idea - like pull to 5 degrees of pitch and so forth.
For others, re: elevator versus stick inputs
Good grief, we've been thru this. The position of the control surfaces on a FBW jet do not reflect the pilot inputs via sidestick, wheel or whatever. They move to achieve the commanded gee, AoA or roll rate. The rudder will move to help roll coordination, with no input from the pilot.
In the 'bus, the THS will gradually move one direction or the other to reduce the amount of control input to achieve the "commanded" gee.
Waiting for the final and the immense amount of comments from we in the peanut gallery shortly thereafter.
Yep, beats the hell outta me. Hold what ya got and analyze the situation.
maybe the "boldface" or whatever the commercial folks call it was not a good idea - like pull to 5 degrees of pitch and so forth.
For others, re: elevator versus stick inputs
Good grief, we've been thru this. The position of the control surfaces on a FBW jet do not reflect the pilot inputs via sidestick, wheel or whatever. They move to achieve the commanded gee, AoA or roll rate. The rudder will move to help roll coordination, with no input from the pilot.
In the 'bus, the THS will gradually move one direction or the other to reduce the amount of control input to achieve the "commanded" gee.
Waiting for the final and the immense amount of comments from we in the peanut gallery shortly thereafter.

Join Date: Jun 2009
Location: NNW of Antipodes
Age: 80
Posts: 1,330
Likes: 0
Received 0 Likes
on
0 Posts
The BEA's English translation of the recommendations issued following their report into the Tarom incident is as follows:-
As far as I can ascertain, those basic recommendations have been fulfilled, e.g.
Following several accident investigations in which the Bureau Enquêtes-Accidents participated, the following recommendation was issued on 24 January 1995:
Various incidents or accidents (see list below) involving public transport aircraft show the following common characteristics:
See preliminary report, published 3 November 1994.
As a result, the Bureau Enquêtes-Accidents recommends:
- that a study be launched so that the pilot’s priority over all Automatic Flight Systems is maintained in all circumstances.
This could be done :
Various incidents or accidents (see list below) involving public transport aircraft show the following common characteristics:
- Configuration: Automatic Pilot and/or auto-throttle lever (or auto thrust) in operation.
- Circumstances: pilot flying overrides (voluntarily or involuntarily) the Automatic Flight System, or acts contrary to the indications of the Flight Director.
- Aggravating circumstances:
- the pilot flying is not always aware of his action in opposition with the Automatic Flight Systems and never perceives the consequences thereof,
- the pilot not flying (even instructors) is not aware of the conflict between the pilot at the controls and the Automatic Flight Systems.
- Consequences:
- the reaction of the Automatic Flight Systems leads to potentially dangerous configurations: out of trim, engine thrust incompatible with the trajectory chosen by the pilot, etc.
- Flight crew,
- either is not aware of the situation, and thus cannot take corrective measures,
- or observes the aircraft configuration without understanding the causes. This incomprehension (also related to limited knowledge of systems) leads to a loss of time in analyzing the situation, or even to an erroneous analysis, generally associated with a lack of adequate communicationmbetween crew members
See preliminary report, published 3 November 1994.
As a result, the Bureau Enquêtes-Accidents recommends:
- that a study be launched so that the pilot’s priority over all Automatic Flight Systems is maintained in all circumstances.
This could be done :
a) by the disconnection of Automatic Flight Systems (automatic pilot and auto-throttle lever or auto thrust) in the event of conflict between the pilot’s actions and those of the Automatic Flight System or Flight Director.
b) and/or by clear information in the cockpit (possibly an alarm) warning the flight crew of such a conflict.
b) and/or by clear information in the cockpit (possibly an alarm) warning the flight crew of such a conflict.
Auto Pilot :-
Auto OFF if abs(φ) >45°, or θ <-13°, or θ >+25°, or CAS < VLS, or CAS >(VMO/MMO or VLE/VFE), or Pitch Angle Protection ACTIVE.
Auto Pilot:-
Unavailable if abs(φ) >40°, or θ <-10°, or θ >+22°, or CAS < VLS, or CAS >(VMO/MMO or VLE/VFE), or Pitch Angle Protection ACTIVE.
Auto OFF if abs(φ) >45°, or θ <-13°, or θ >+25°, or CAS < VLS, or CAS >(VMO/MMO or VLE/VFE), or Pitch Angle Protection ACTIVE.
Auto Pilot:-
Unavailable if abs(φ) >40°, or θ <-10°, or θ >+22°, or CAS < VLS, or CAS >(VMO/MMO or VLE/VFE), or Pitch Angle Protection ACTIVE.
- The A/P and A/THR disconnected when a couple of ADR's had a disagreement over speeds.
- The THS trim continued the way it was designed to, though due to a change in the control law, it would appear that the crew had no idea that the Alpha protections had been lost.
- Except when the Abnormal Attitude Law has been triggered, auto trim is still functioning and a constant stick NU/ND command will cause the THS to follow in an attempt to maintain a load factor of +1g - be aware!
- The Stall Warning operated correctly while the aircraft was within the Normal Flight Envelope, but wasn't heeded.

Join Date: Jul 2002
Location: UK
Posts: 3,182
Likes: 0
Received 0 Likes
on
0 Posts

Join Date: Jan 2008
Location: uk
Posts: 861
Likes: 0
Received 0 Likes
on
0 Posts
Not at FL350 he didn't. which maybe means bubbers wins on a technicality.
The point, however, remains that LOC accidents, and specifically mishandled stalls, are happening across range of types/mfrs/airlines.
If it was just 'buses falling out of the sky I'd be clamouring for investigation of the bus specific sidestick and fbw etc. - but that isn't what is happening.
If the effort were focused on the bus stuff only, then we could only ever fix part of the problem and risk fixing nothing if in fact the causes are elsewhere and common across types. Far better to try and identify common causes, surely ?
The point, however, remains that LOC accidents, and specifically mishandled stalls, are happening across range of types/mfrs/airlines.
If it was just 'buses falling out of the sky I'd be clamouring for investigation of the bus specific sidestick and fbw etc. - but that isn't what is happening.
If the effort were focused on the bus stuff only, then we could only ever fix part of the problem and risk fixing nothing if in fact the causes are elsewhere and common across types. Far better to try and identify common causes, surely ?

Join Date: Feb 2011
Location: Nearby SBBR and SDAM
Posts: 875
Likes: 0
Received 0 Likes
on
0 Posts
Role of A/C
Pariès cited 16 events similar to AF447, all of which showed poor understanding, rare implementation of unreliable airspeed procedures and stall warnings which were "perceived but mostly not believed".

Join Date: Jul 2002
Location: UK
Posts: 3,182
Likes: 0
Received 0 Likes
on
0 Posts
Granted, but in that case the Birgenair jet never made it to cruise level. While it doesn't satisfy all of the criteria Bubbers set, it satisfies the important ones - namely doing precisely the wrong thing minus speed indications and with autopilot behaving erratically. It also puts a dent in the "other pilot would see the inappropriate control deflection and take over", because in that case the F/O did not. The Stony Point NWA B727 was at FL 248 when exactly the same thing happened.

Join Date: Oct 2011
Location: Lower Skunk Cabbageland, WA
Age: 73
Posts: 360
Likes: 0
Received 0 Likes
on
0 Posts

Dozy:
You keep on saying that, and I keep on countering that your premise is based on false logic. One or two cases proves nothing at all. One could (I do) also speculate that, if one had a data base of, say, 100 such incidents, equally distributed between SS and yoke aircraft, it might be more appropriate to draw the conclusion that you do IF there was no difference in the associated statistics. I.E., if we're going to make guesses on this issue, I would guess that in 100 cases of LOC-to-stall, MORE pilots would notice the inappropriate input when it was a yoke. But....I have no more proof for that than you do for your opposite conclusion. 
True, I can't fly, but I can think!
It also puts a dent in the "other pilot would see the inappropriate control deflection and take over", because in that case the F/O did not. The Stony Point NWA B727 was at FL 248 when exactly the same thing happened.

True, I can't fly, but I can think!

Last edited by Organfreak; 3rd Jul 2012 at 15:58. Reason: So many typos; so little time

Join Date: Nov 2005
Location: Potomac Heights
Posts: 469
Likes: 0
Received 0 Likes
on
0 Posts
... but no Boeing pilot at FL350 would pull back to the stops if he lost his airspeed and autopilot...
So what about the possibility that the PF simply did not process/comprehend that when the A/P went into Alternate Law, that Alpha Protect was no longer active -- and that he would need to use the side stick more like a Boeing yoke than an Airbus joystick? Thus, it wasn't that he was dumb, just that he had a brain freeze in not fully comprehending that his protections were gone (despite this warning being given on the ECAM).

Join Date: Apr 2007
Location: Bristol
Age: 76
Posts: 56
Likes: 0
Received 0 Likes
on
0 Posts
Just catching up on the discussions.
I found the Jean Pariès presentation very interesting. In the conclusion he recommends an "Overall paradigm shift" in design and training. Well, how about giving the crew a synthetic view of the aircraft generated from the sensors, something like the MS Flt Sim outide spot view, say 3/4 rear view. We see this kind of display on visualisations of FDR readouts. It would give the crew (when at their most 'startled') an immediate understanding of the aircraft's pitch/roll attitude relative to the horizon, and also (if it were possible to generate) their FPV in 3D.
I found the Jean Pariès presentation very interesting. In the conclusion he recommends an "Overall paradigm shift" in design and training. Well, how about giving the crew a synthetic view of the aircraft generated from the sensors, something like the MS Flt Sim outide spot view, say 3/4 rear view. We see this kind of display on visualisations of FDR readouts. It would give the crew (when at their most 'startled') an immediate understanding of the aircraft's pitch/roll attitude relative to the horizon, and also (if it were possible to generate) their FPV in 3D.

Join Date: Dec 2010
Location: Middle America
Age: 83
Posts: 1,167
Likes: 0
Received 0 Likes
on
0 Posts
Dozy,
The same thing did not happen except for the end result. There was a different reason. The NWA B727 crew forgot to turn on the pitot heaters. So when they iced over, all indications were that they were all of a sudden speeding up, therefore they reduced speed. There was nothing to tell them they were at the right speed in reality. The speeds they were seeing on the instruments were erroneous, they didn't go away and they appeared real to them sadly.
I think caution needs to be applied when comparing accidents of this type, one 3 years ago and one ~ 40 years ago.
The Stony Point NWA B727 was at FL 248 when exactly the same thing happened.
I think caution needs to be applied when comparing accidents of this type, one 3 years ago and one ~ 40 years ago.

Join Date: Feb 2011
Location: Nearby SBBR and SDAM
Posts: 875
Likes: 0
Received 0 Likes
on
0 Posts
"Overall paradigm shift" in design and training.
Hi,
SRMman:
Long time ago some of us raised the issue. A very serious one.
Unfortunately i am too busy to do more in this Thread:
http://www.pprune.org/tech-log/48135...anomalies.html
SRMman:
Long time ago some of us raised the issue. A very serious one.
Unfortunately i am too busy to do more in this Thread:
http://www.pprune.org/tech-log/48135...anomalies.html

Join Date: Jan 2008
Location: uk
Posts: 861
Likes: 0
Received 0 Likes
on
0 Posts
The stall was precipitated by the flight crew's improper reaction to erroneous airspeed and Mach indications
loss of control of the aircraft because the flight crew failed to recognize and correct the aircraft's high-angle-of-attack, low-speed stall
The flightcrew continued to increase the noseup attitude of
the aircraft following the operation of the stall warning stick shaker.
You could write those statements about either accident.loss of control of the aircraft because the flight crew failed to recognize and correct the aircraft's high-angle-of-attack, low-speed stall
The flightcrew continued to increase the noseup attitude of
the aircraft following the operation of the stall warning stick shaker.
Yes, there is a big difference in aviation between 40yrs ago and 3yrs ago but that doesn't mean history provides nothing to learn from. The problem of crews failing to recognize stall, pulling up into stalls, pulling back through stall warnings, and failing to correct the other guy doing it is not new and didn't start with fbw and sidesticks.

Join Date: Oct 2011
Location: Lower Skunk Cabbageland, WA
Age: 73
Posts: 360
Likes: 0
Received 0 Likes
on
0 Posts
IF789 said:
You're sure right about that, but some of us are suspicious that sidesticks could make this problem harder to suss out under pressure, since the other guy can't see them.
=this has been a pre-recorded announcement=
The problem of crews failing to recognize stall, pulling up into stalls, pulling back through stall warnings, and failing to correct the other guy doing it is not new and didn't start with fbw and sidesticks.
=this has been a pre-recorded announcement=






Join Date: Jul 2002
Location: UK
Posts: 3,182
Likes: 0
Received 0 Likes
on
0 Posts
The fact is that whether you can see the sidestick or not (and FWIW in the sim I could get a good idea of what the guy in the opposite seat was doing with the stick based on his posture), a combination of monitoring the aircraft's response plus timely and effective communication with your colleague in the opposite seat should nullify that potential problem.

Join Date: Oct 2011
Location: Lower Skunk Cabbageland, WA
Age: 73
Posts: 360
Likes: 0
Received 0 Likes
on
0 Posts
@ DW
Admittedly that's a good point taken in isolation, but as you so eloquently put it, the amount of evidence available is not sufficient to make a statistically valid conclusion. "Suspicions" based on an assumption that something stands to reason are just that - opinion and conjecture.

....a combination of monitoring the aircraft's response plus timely and effective communication with your colleague in the opposite seat should nullify that potential problem.
=I HAVE SPOKEN=


Join Date: Mar 2009
Location: S23W046
Age: 72
Posts: 57
Likes: 0
Received 0 Likes
on
0 Posts
Camparing pears with apples, do you?
@DW
As far as I remember the Birgen Air accident was mainly caused by failure of shutting off the A/T system, which by design took thrust to idle because of the false overspeed sensed by blocked pitot. The FO very well was aware of the situation, but it seemed to be also a cultural issue that he did not take control.
So IMHO this has very little resemblance with a yoke versus SS issue.
Why do I sense some reluctance throughout all your postings to realize that humans not always react the way that engineers plan and sometimes design the human - machine interface the way that the human has to configure himself to the machine instead the other way around?
As far as I remember the Birgen Air accident was mainly caused by failure of shutting off the A/T system, which by design took thrust to idle because of the false overspeed sensed by blocked pitot. The FO very well was aware of the situation, but it seemed to be also a cultural issue that he did not take control.
So IMHO this has very little resemblance with a yoke versus SS issue.
Why do I sense some reluctance throughout all your postings to realize that humans not always react the way that engineers plan and sometimes design the human - machine interface the way that the human has to configure himself to the machine instead the other way around?

Join Date: Dec 2002
Location: UK
Posts: 2,342
Likes: 0
Received 0 Likes
on
0 Posts
Re Overall paradigm shift" in design and training.
Pariès expands paradigm shift elsewhere as “the change from safety through conformity, to safety through variation management”. Variation is described by Hollnagel:- http://ipac.ca/documents/The_resilie...ion%5B1%5D.pdf
"… other pilot would see the inappropriate control deflection and take over"
I doubt that there would be a fair range of data to support either view, but anecdotal evidence suggests that pilots don’t ‘see’ a control input as inappropriate, particularly where both have similar but erroneous situation awareness. Aspect of this are discussed in http://www.pprune.org/safety-crm-qa-...ervention.html.
In addition, it would be poor practice to train pilots to use an input as a measure of aircraft control, where the really important aspect is the output - what the aircraft is doing – what has the control input achieved.
Pariès expands paradigm shift elsewhere as “the change from safety through conformity, to safety through variation management”. Variation is described by Hollnagel:- http://ipac.ca/documents/The_resilie...ion%5B1%5D.pdf
"… other pilot would see the inappropriate control deflection and take over"
I doubt that there would be a fair range of data to support either view, but anecdotal evidence suggests that pilots don’t ‘see’ a control input as inappropriate, particularly where both have similar but erroneous situation awareness. Aspect of this are discussed in http://www.pprune.org/safety-crm-qa-...ervention.html.
In addition, it would be poor practice to train pilots to use an input as a measure of aircraft control, where the really important aspect is the output - what the aircraft is doing – what has the control input achieved.

Join Date: Jul 2002
Location: UK
Posts: 3,182
Likes: 0
Received 0 Likes
on
0 Posts
Why do I sense some reluctance throughout all your postings to realize that humans not always react the way that engineers plan and sometimes design the human - machine interface the way that the human has to configure himself to the machine instead the other way around?
I've said this before, but there seems to be a persistent rumour that the Airbus FBW design was the work of engineers and management alone with no pilot input - which is categorically not true.
The difference between the Airbus and Boeing FBW designs is solely down to the dialogue having different conclusions (because the pool of engineers and pool of pilots was different). As Organfreak says, there is insufficient evidence to prove that one design is any safer or more intituitve than another, so all we have to go on are our own conclusions based on the information to hand.
Remember that the yoke design grew from the requirement to have cables connected to all flight surfaces, and until the late '80s was a de facto standard that reached acceptance over time - it was not designed to be the ultimate piloting interface, nor was it ever so.

Last edited by DozyWannabe; 3rd Jul 2012 at 20:22.
