AF 447 Thread No. 7
Reprogram what?
Something to ponder?
The thread over the past few days seems to be fairly fixated on autotrim behavior and stick "feel" (or the lack of it, particularly w.r.t. trim). However I think (personal opinion, I'll take the flack) that in any control task, humans are amazingly adept at learning and understanding whatever set of controls we are given (subject to sufficient training/use/learning). What I see here is a collection of folk that have various backgrounds (F4, F16, Boeing this or that, and more) and I think it is fair to say each specific aircraft had unique "quirks". I see comments here related to the lack of trim response on the Airbus sidestick (unlike the yoke crew where trim unloads the force needed to maintain an attitude), but, 'hello!' the F-16 is no different... and in fact I'd state the F-16 is a good analog to the Airbus flight control system, except, more extremely, the F-16 sidestick moves almost not at all - I think the travel is something like an eighth of an inch (Gums?) total. Control is achieved not by waving the stick around but by applying pressure to it. Quite different. Similarly many of us will have played with various flight simulator games... while I suspect many here are gasping in horror at the mention of such 'toys' the point is even with significantly compromised controls (compared to the aircraft) many gamers become extremely adept at controlling the 'aircraft' and can fly the thing pretty much like the plane. What we do is we LEARN. Humans are good at this.
What's my point? The point is we can throw mud at the Airbus control system, but like or not, thousands of Airbus aircraft are trucking around the worlds airways with millions of passengers and they are not falling out the sky any more often that those from other manufacturers. The point is, the crews of those aircraft learn how they work and understand the behavior of trim, just the same way they learn the response rate to a stick input, and so on. Just because that control system is different to Boeing or Embraer or whatever, doesn't mean it is not as good. Clearly it is, since those planes are certified and make millions of flights daily.
You can argue as much as you like that changing this or that is the hail Mary for the aircraft type, but that just doesn't hold water. Does ANYONE seriously think Airbus is going to change the sidestick to provide force feedback for example? The stick currently is force 'loaded' (spring loaded I believe) and I don't really see the need to change that. But others have previously argued otherwise.
So, why'd AF447 fall out the sky, you might ask? Back to something I wrote earlier - "In any control task, humans are amazingly adept at learning and understanding whatever set of controls we are given (subject to sufficient training/use/learning)". This is what went wrong, not the aircraft design. For whatever reason (pitot icing), the automation dropped out, and as designed, handed the aircraft back to the most sophisticated computing devices on the aircraft - the humans. Unfortunately the most important safety device on the aircraft got it wrong. Unfortunately they got it wrong over and over. Zoom-climb (wrong), pulled into a stall (wrong), continued pull (wrong), TO/GA (wrong - but I'll pass on that since it seems this might have been a trained response), lack of CRM (wrong), and so on. Lot's of wrong here.
But what was really "wrong"? Training. Training. Training. With sufficient training the crews response clearly would/should have been different - very much so. Would it be different today - I suspect emphatically "yes". Because this accident has highlighted so many issues, any Airbus pilot worth his paycheck should have been following the accident investigation and learned a massive amount - mostly what not to do, but I'm sure a lot about the Airbus control systems. The key word in the previous sentence = LEARNED.
How did Gums learn to fly the F-16? Hands on the stick and throw the thing around the sky (some in simulators I hope... job security for me!), but NOT hundreds (or thousands) of hours tooling across the oceans on autopilot.... I see so many references to pilots with 11,000 hours (or whatever) and every time my immediate thought is "subtract ALL autopilot hours off that and what do you REALLY have???". Low hundreds perhaps, if we're lucky...
In my book this is the problem. The time when the crew were needed the most, was exactly when the automation took a timeout - and that corresponds exactly to the skill-set the crew has least ability.
So what am I advocating? More hand-flying on the line? Perhaps not - the autopilot is there for a good reason and does a great job. Simply holding the stick for hours transiting the Atlantic doesn't teach much. We need to get pilots into aerobatic aircraft and get their basic flying skills on the edge of the envelope up to snuff - recover from stalls, spins, etc. Then get those same crew into the training devices (simulators, flat-panel trainers, etc) and fail the automation and get their hands on the stick. Create situations where the control laws degrade. Learn Alt Law. A lot of sim time is spent training one engine out situations on takeoff, etc - are the current training scenarios really relevant today - how often do engines fail? I believe that LOC is the single most significant cause of accidents today - not engines failing/catching fire/etc.
Don't get me wrong - if there are simple changes to the systems within the Airbus cockpit that will help, they surely should be implemented (I suspect the stall warning inhibit below 60 knots should be revisited). But the single most significant change is reprogramming the HUMANS who get to sit in the very front seats.
- GY
The thread over the past few days seems to be fairly fixated on autotrim behavior and stick "feel" (or the lack of it, particularly w.r.t. trim). However I think (personal opinion, I'll take the flack) that in any control task, humans are amazingly adept at learning and understanding whatever set of controls we are given (subject to sufficient training/use/learning). What I see here is a collection of folk that have various backgrounds (F4, F16, Boeing this or that, and more) and I think it is fair to say each specific aircraft had unique "quirks". I see comments here related to the lack of trim response on the Airbus sidestick (unlike the yoke crew where trim unloads the force needed to maintain an attitude), but, 'hello!' the F-16 is no different... and in fact I'd state the F-16 is a good analog to the Airbus flight control system, except, more extremely, the F-16 sidestick moves almost not at all - I think the travel is something like an eighth of an inch (Gums?) total. Control is achieved not by waving the stick around but by applying pressure to it. Quite different. Similarly many of us will have played with various flight simulator games... while I suspect many here are gasping in horror at the mention of such 'toys' the point is even with significantly compromised controls (compared to the aircraft) many gamers become extremely adept at controlling the 'aircraft' and can fly the thing pretty much like the plane. What we do is we LEARN. Humans are good at this.
What's my point? The point is we can throw mud at the Airbus control system, but like or not, thousands of Airbus aircraft are trucking around the worlds airways with millions of passengers and they are not falling out the sky any more often that those from other manufacturers. The point is, the crews of those aircraft learn how they work and understand the behavior of trim, just the same way they learn the response rate to a stick input, and so on. Just because that control system is different to Boeing or Embraer or whatever, doesn't mean it is not as good. Clearly it is, since those planes are certified and make millions of flights daily.
You can argue as much as you like that changing this or that is the hail Mary for the aircraft type, but that just doesn't hold water. Does ANYONE seriously think Airbus is going to change the sidestick to provide force feedback for example? The stick currently is force 'loaded' (spring loaded I believe) and I don't really see the need to change that. But others have previously argued otherwise.
So, why'd AF447 fall out the sky, you might ask? Back to something I wrote earlier - "In any control task, humans are amazingly adept at learning and understanding whatever set of controls we are given (subject to sufficient training/use/learning)". This is what went wrong, not the aircraft design. For whatever reason (pitot icing), the automation dropped out, and as designed, handed the aircraft back to the most sophisticated computing devices on the aircraft - the humans. Unfortunately the most important safety device on the aircraft got it wrong. Unfortunately they got it wrong over and over. Zoom-climb (wrong), pulled into a stall (wrong), continued pull (wrong), TO/GA (wrong - but I'll pass on that since it seems this might have been a trained response), lack of CRM (wrong), and so on. Lot's of wrong here.
But what was really "wrong"? Training. Training. Training. With sufficient training the crews response clearly would/should have been different - very much so. Would it be different today - I suspect emphatically "yes". Because this accident has highlighted so many issues, any Airbus pilot worth his paycheck should have been following the accident investigation and learned a massive amount - mostly what not to do, but I'm sure a lot about the Airbus control systems. The key word in the previous sentence = LEARNED.
How did Gums learn to fly the F-16? Hands on the stick and throw the thing around the sky (some in simulators I hope... job security for me!), but NOT hundreds (or thousands) of hours tooling across the oceans on autopilot.... I see so many references to pilots with 11,000 hours (or whatever) and every time my immediate thought is "subtract ALL autopilot hours off that and what do you REALLY have???". Low hundreds perhaps, if we're lucky...
In my book this is the problem. The time when the crew were needed the most, was exactly when the automation took a timeout - and that corresponds exactly to the skill-set the crew has least ability.
So what am I advocating? More hand-flying on the line? Perhaps not - the autopilot is there for a good reason and does a great job. Simply holding the stick for hours transiting the Atlantic doesn't teach much. We need to get pilots into aerobatic aircraft and get their basic flying skills on the edge of the envelope up to snuff - recover from stalls, spins, etc. Then get those same crew into the training devices (simulators, flat-panel trainers, etc) and fail the automation and get their hands on the stick. Create situations where the control laws degrade. Learn Alt Law. A lot of sim time is spent training one engine out situations on takeoff, etc - are the current training scenarios really relevant today - how often do engines fail? I believe that LOC is the single most significant cause of accidents today - not engines failing/catching fire/etc.
Don't get me wrong - if there are simple changes to the systems within the Airbus cockpit that will help, they surely should be implemented (I suspect the stall warning inhibit below 60 knots should be revisited). But the single most significant change is reprogramming the HUMANS who get to sit in the very front seats.
- GY

Join Date: Jul 2011
Location: Northern Hemisphere
Posts: 195
Likes: 0
Received 0 Likes
on
0 Posts
You're right, but it's also a general statement of the need to be cautious about what is or is not "simple" in software without detailed knowledge. A fair few years in software development has taught me that it's very easy for someone to believe they know enough about the internals of a system to assess the impact of a change request, when in fact they don't.
Career experience may be different from person to person, particularly when it’s a few years worth. A certain amount of time is required for one to become a principal, and even more to be higher on the career ladder. Very Large, very complex software systems have been around for quite some time, and there are plenty of people with a few decades of experience of being major contributors in the middle of things, of being those that made things happen.
But this is besides the point. It does not matter how easy is to fix it. If it need be fixed, then it need be fixed. A signal from a manufacturer that is not confident it can fix a problem of minor magnitude, shows trouble.
And therein lies the dillema - warning vs actual conditions. Maybe I didn't expalin well.
You did explain well - it is fully appreciated - but there is also a misunderstanding, as I referred to the "state" or "condition" of "Stall of the airplane", as a generic term, not specific to the Airbus nomenclature that you’ve described.
Finally, the way I understand the THS, and it’s made clear by the few pages from when I should have posted this reply - sorry for the delay - I am not the only one. It seems it is a lot bigger problem to leave its behavior as it is now, than to fix it.
Last edited by airtren; 19th Nov 2011 at 12:56.

Per Ardua ad Astraeus
Join Date: Mar 2000
Location: UK
Posts: 18,579
Likes: 0
Received 0 Likes
on
0 Posts
Mbird - can you expand on
please? I am not sure I understand what you are saying and have a feeling I might not want to understand it either.
Gums -
- you need to define marginal here, as where they were cruising on the carpet graph is where we all fly - day in day out, and is fine and safe..
Once the aircraft is stalled, the control inputs do not have much influence on the aircraft, and sometimes act in a contrary fashion.
Gums -
- flying with marginal delta between overspeed and stall at high altitude

Training, training, training
Salute!
Thanks for the nice words, Garage.
We had no simulator back in 1979. Didn't have one for another three years, and it was a POS.
We had a very simple FBW system with few "laws" or "protections" compared to the Airbus. Our "laws" were based upon maneuver limits and not "autopilot" functions like max bank angle, restricted pitch attitude, etc. Our "limits" were there to provide max performance while reducing the odds of a ham-fisted pilot getting into trouble.
Our autopilot was extremely limited in its authority. The GD flight control wizards didn't want something getting in the way of their system.
I see the reverse in the Airbus.
I do not want to see airline pilots "experimenting" with the limits of their jets, especially with 200 SLF's in the back. But I would hope that they would occasionally fly some planes that have classic stall characteristics and learn to cope with unusual conditions.
I had just arrived at Hill when we got the word that our neat jet, which could not stall or spin or....., could enter a "deep stall" due to the basic FBW design and the aft c.g. we used. So we saw the films and the test pilot interviews and we were PREPARED for when it happened to us!
We had little, if any, "feel" for mach buffet due to the wing design. So the Airbus crews had a leg up on us. But they also had a small envelope that allows for little error WRT mach and AoA. They had to be "better" than us in that regard.
My feeling is that better training will be the cure, and not a massive overhaul of the FBW system
Thanks for the nice words, Garage.
We had no simulator back in 1979. Didn't have one for another three years, and it was a POS.
We had a very simple FBW system with few "laws" or "protections" compared to the Airbus. Our "laws" were based upon maneuver limits and not "autopilot" functions like max bank angle, restricted pitch attitude, etc. Our "limits" were there to provide max performance while reducing the odds of a ham-fisted pilot getting into trouble.
Our autopilot was extremely limited in its authority. The GD flight control wizards didn't want something getting in the way of their system.
I see the reverse in the Airbus.
I do not want to see airline pilots "experimenting" with the limits of their jets, especially with 200 SLF's in the back. But I would hope that they would occasionally fly some planes that have classic stall characteristics and learn to cope with unusual conditions.
I had just arrived at Hill when we got the word that our neat jet, which could not stall or spin or....., could enter a "deep stall" due to the basic FBW design and the aft c.g. we used. So we saw the films and the test pilot interviews and we were PREPARED for when it happened to us!
We had little, if any, "feel" for mach buffet due to the wing design. So the Airbus crews had a leg up on us. But they also had a small envelope that allows for little error WRT mach and AoA. They had to be "better" than us in that regard.
My feeling is that better training will be the cure, and not a massive overhaul of the FBW system

Join Date: Jul 2011
Location: Northern Hemisphere
Posts: 195
Likes: 0
Received 0 Likes
on
0 Posts
I mentioned an aspect of control input yesterday that I am not sure the majority of you picked up on. Once the aircraft is stalled, the control inputs do not have much influence on the aircraft, and sometimes act in a contrary fashion. ....
PF is thus clueless about the net effect of his total input on actual elevator position. We can see the average control inputs pretty easily on the DFDR readout, but the PF could not. The feedback channel he had used all his flying career was no longer available.
He was operating open loop.
PF is thus clueless about the net effect of his total input on actual elevator position. We can see the average control inputs pretty easily on the DFDR readout, but the PF could not. The feedback channel he had used all his flying career was no longer available.




.
Last edited by airtren; 18th Nov 2011 at 14:02.

Join Date: Jan 2005
Location: W of 30W
Posts: 1,939
Likes: 0
Received 0 Likes
on
0 Posts
Originally Posted by GY
For whatever reason (pitot icing), the automation dropped out, and as designed, handed the aircraft back to the most sophisticated computing devices on the aircraft - the humans.
Then include it in the wrongs ... Why not ?

Join Date: Jul 2011
Location: Northern Hemisphere
Posts: 195
Likes: 0
Received 0 Likes
on
0 Posts
@ Machinbird (re: #369)
...
I'm not sure the autotrim was a barrier to stall escape (I understand "barrier" as something wich prevent you (strictly) to escape stall; THS NU will for sure delay the escape, but I'm not qualified enough to say it will prevent it, even if it stay full NU; in fact, my guess would be it prevents not)
...
I'm not sure the autotrim was a barrier to stall escape (I understand "barrier" as something wich prevent you (strictly) to escape stall; THS NU will for sure delay the escape, but I'm not qualified enough to say it will prevent it, even if it stay full NU; in fact, my guess would be it prevents not)
It may be just semantics, but "delaying", may practically mean "preventing it", when it's part of a complex set of causes of a final fatal outcome.

Join Date: Nov 2010
Location: FR
Posts: 478
Likes: 0
Received 0 Likes
on
0 Posts
GarageYears,
I totally agree with your last post. As for myself, I concentrate on "small" technical problems (autotrim, stall warning) because I don't feel qualified to discuss -more important- training issues. Besides, here is the tech log.
The risk is of concentrating "only" on those relatively minor issues, and take them as an excuse to continue to "save costs" on the training...
Don't get me wrong - if there are simple changes to the systems within the Airbus cockpit that will help, they surely should be implemented (I suspect the stall warning inhibit below 60 knots should be revisited). But the single most significant change is reprogramming the HUMANS who get to sit in the very front seats.
The risk is of concentrating "only" on those relatively minor issues, and take them as an excuse to continue to "save costs" on the training...

My feeling is that better training will be the cure, and not a massive overhaul of the FBW system
It's been an expensive "lessons learned," hasn't it, this crash of AF 447?
It has cost dearly AF, 228 people and their families, and who knows how many others.
In its wake, it is likely that a good many AB flying folk (and organizations) have delved deeply into their machines and know them better now than they did on May 30, 2009.
To fly your aircraft you have to know your aircraft.
What was it we used to say in the Navy?
NATOPS is written in blood.
Looks like a few things have not changed yet ...

Join Date: Aug 2011
Location: Grassy Valley
Posts: 2,123
Likes: 0
Received 0 Likes
on
0 Posts
From the git, AB has been marketing complexity as dependability, and "Ease of Operation" as simplicity.
Both are utter lies, and errant horse----. Training needs to start at the Line, and I don't mean the AIR Line. The Production LINE.
To require pampered pilots to inherit a wild thang in the worst of circumstances, without some history of mitigation/preparation, is manslaughter, imo.
My opinion, and we'll see what France thinks.
Wolf, I appreciate your experience, but flying the line is not Blue Water.
Nor should it be. These babies are not Ace Sixkiller, nor should they be.
They are Lambs for slaughter, 447 case in point.
Both are utter lies, and errant horse----. Training needs to start at the Line, and I don't mean the AIR Line. The Production LINE.
To require pampered pilots to inherit a wild thang in the worst of circumstances, without some history of mitigation/preparation, is manslaughter, imo.
My opinion, and we'll see what France thinks.
Wolf, I appreciate your experience, but flying the line is not Blue Water.
Nor should it be. These babies are not Ace Sixkiller, nor should they be.
They are Lambs for slaughter, 447 case in point.

Join Date: Jul 2009
Location: Not far from a big Lake
Age: 81
Posts: 1,461
Likes: 0
Received 0 Likes
on
0 Posts
Originally Posted by AZR
I'm not sure the autotrim was a barrier to stall escape (I understand "barrier" as something wich prevent you (strictly) to escape stall; THS NU will for sure delay the escape, but I'm not qualified enough to say it will prevent it, even if it stay full NU; in fact, my guess would be it prevents not)

If I clarify my definition of a barrier as an impediment that can be overcome with some degree of difficulty, I think you will see that a we are still in agreement regarding the import of the nearly full nose up trim.
Originally Posted by Garage Years
Does ANYONE seriously think Airbus is going to change the sidestick to provide force feedback for example? The stick currently is force 'loaded' (spring loaded I believe) and I don't really see the need to change that. But others have previously argued otherwise.
Originally Posted by BOAC
Mbird - can you expand on (below) please?
Once the aircraft is stalled, the control inputs do not have much influence on the aircraft, and sometimes act in a contrary fashion.
BOAC, I am probably not telling you anything you don't already know. Once you stall you will likely find that your control inputs may have a reversed effect in the case of roll (due to adverse yaw), or that the surfaces are relatively ineffective and the aircraft's motions due to vortex shedding and cross channel aerodynamic coupling mask the effects of your control inputs. The elevator inputs are masked by the THS input and likely a post stall phugoid like effect results (a nose bobble). To have an influence, you need to make a control input and hold it or in the case of roll, you need to use the rudder and lay off the ailerons.


Join Date: Feb 2005
Location: Correr es mi destino por no llevar papel
Posts: 1,435
Received 0 Likes
on
0 Posts
Originally Posted by mm43
the PF effectively spent 4 minutes battling with a compromised yaw damper that contributed to the roll and at no time was the SS left in the longitudinal neutral position. Without regurgitating the stuff long since posted (many times), if you simply don't know, the result will be equally simple.
Originally Posted by HazelNuts39
Probably turbulence: Transition from updraft to downdraft could very well create sufficient reduction of "gee" to satisfy the "gee" demanded by a moderate nose-down SS input, without immediately dropping the nose.
Catch is that the sentence I've quoted is often understood to be the description of the principle on which Airbus FBW operates. It is not. It is the description of end result.
Sidestick command does not order G in absolute terms. It adds G demand to already measured, therefore if hit by updraft giving you 1.3G, pull on the stick that would give you 1.1 absolute from straight and level will now result in 1.4 pitch up. Push giving 0.9 would now be 1.2. Same goes for coordinated turn induced acceleration. In other words, stick G command is superimposed on measured level on normal acceleration. Why would anyone make so complicated flight controls system, Because...
Originally Posted by BOAC
When I move a control I expect a proportionate response in the desired direction.
What our esteemed PPRuNe colleague has described as his own experience is what you would get if G command were absolute. In real life it is possible to achieve such a net result only with: severe malfunction of inertial reference, severe malfunction of flight control systems or severe turbulence. Until the time our honourable PPRuNe colleague decides to quit his incommunicado status and shed some more light on his story, I'll file it under "unreliable".
Originally Posted by BOAC
- the more we think we discover the worse it gets!
(...)
For heaven's sake - are you serious? Where have we gone wrong? (Answers on a postcard, please).
(...)
For heaven's sake - are you serious? Where have we gone wrong? (Answers on a postcard, please).
Originally Posted by idle bystander
I was under the impression that the reason I trusted my life to the people at the pointy-end was because they were like me, shared my fascination with things aeronautical, and had both the interest in and the knowledge of just what it is that keeps them up there amongst the clouds.
Originally Posted by idle bystander
Somebody please re-assure me that I'm wrong; that what NARVAL wrote, and what was so warmly applauded by quite a few 'pilots' on this forum, does not represent the average level of expertise of commercial pilots, that most of them do actually understand what keeps them in the air, because otherwise I'm sticking to sailing!
Originally Posted by Retired F4
BEA only tells us, that the flight control inputs in the simulator produced comparable outputs to the flight controls and caused comparable flight behaviour. Nothing more, and nothing less.
(...)
Where does it leave us then?
It only proves, that concerning the flight control system the aircraft had no malfunctions and that another A330 with the same crew (or with a different crew performing the same inputs) at the same place in the same environment would have ended in the drink too. This recognition might cause more headache for a manufacturer than finding the cause in one faulted part.
(...)
Where does it leave us then?
It only proves, that concerning the flight control system the aircraft had no malfunctions and that another A330 with the same crew (or with a different crew performing the same inputs) at the same place in the same environment would have ended in the drink too. This recognition might cause more headache for a manufacturer than finding the cause in one faulted part.
Originally Posted by OK465
So that although the movements of the control surfaces were consistent with pilot inputs throughout the entire event, there is no direct statement of finding to the effect that after the aircraft exited the flight envelope the aircraft longitudinal movements were still consistent with these pilot inputs even though control surface positions were. Nor does this appear to imply anything further.
Originally Posted by HazelNuts39
That statement presupposes knowledge of the aerodynamic characteristics outside of the envelope where these characteristics have been established by flight test, perhaps extrapolated using wind tunnel data. Once these characteristics are known, it would not be particularly difficult to model them (at least for the longitudinal motion), and to use them in a simulation to produce your statement.
Originally Posted by AlphaZuluRomeo
On the other hand, I've never heard of a pilot "taking the time" to trim up (manually) his aircraft while "fighting" an upset, worsening it.
Originally Posted by gums
I look at the Airbus protections and laws and am impressed by how many are related to attitude versus AoA or even gee. The pterodactyl FBW system I flew 15 years before the A320 was AoA dominant. At low AoA you could get to 9 gees, but as "q" decreased, you hit the AoA limit and the gee available reduced until it was one gee, So at 25 deg AoA we flew at one gee with stick all the way back, regardless of our trimmed gee. And I point out that we trimmed manually for gee using the collie hat or the trim wheel. So we could trim for zero gee and if we let go of the stick the jet would try to achieve zero gee ( neat feature to gain energy, called unloading). Our trim limits were about - 1.4 gee and + 3.4 gee. The Airbus doesn't work this way.
(...)
I was blessed by a system that didn't care about "autopilot" type limits such as attitude or roll angle. We had no limits on that. It was all gee and AoA and rate limits. Not "protections", but "limits". So we lived or died using the cards we were dealt. And the rules were simple. I don't see this with the Airbuss control logic. Sorry for all the folks here that fly the plane. But that's the way I see it.
(...)
I was blessed by a system that didn't care about "autopilot" type limits such as attitude or roll angle. We had no limits on that. It was all gee and AoA and rate limits. Not "protections", but "limits". So we lived or died using the cards we were dealt. And the rules were simple. I don't see this with the Airbuss control logic. Sorry for all the folks here that fly the plane. But that's the way I see it.
Originally Posted by gums
Lastly, and for those who have not flown to the limits and beyond... If the wing camber does not have a decent washout, then the wing stall will progress from outboard to inboard. This results in movement of the center of pressure forward and actually reduces dynamic stability more than static stability. Hence, it becomes harder to get the nose down. It also reduces aileron/spoiler effectiveness.
Originally Posted by gums
I strongly disagree with the loss of AoA "protections" when airspeed is FUBAR.
Originally Posted by gums
After all, the jet is in "direct law" until liftoff, isn't it? And then switches to "normal" law.
Originally Posted by Machinbird
The feedback channel he had used all his flying career was no longer available. He was operating open loop.
Originally Posted by rudderrudderrat
The crew probably never "felt" the stall - they only observed the effects of it then remained in denial and disbelief.
Originally Posted by rudderrudderrat
Is the difference because it wasn't a requirement due to the low probability?
Originally Posted by DozyWannabe
"Don't fight with the stick; If you feel you overcontrol, release the stick.". It's pretty much accepted that the FBW Airbus setup requires a slightly different technique to get the best out of it compared with more conventional aircraft, but the methods to do so seem pretty well nailed-down, though I'm sure that it takes a leap of faith to release the stick under certain conditions.
Originally Posted by Machinbird
A crew not recognizing a stall! That just should not happen. Particularly with the amount of time they had at their disposal to recover.
Originally Posted by GarageYears
But what was really "wrong"? Training. Training. Training

Join Date: Jul 2009
Location: Not far from a big Lake
Age: 81
Posts: 1,461
Likes: 0
Received 0 Likes
on
0 Posts
Quote:
Originally Posted by Machinbird
The feedback channel he had used all his flying career was no longer available. He was operating open loop.
Not really. This is really a Human Factors type evaluation of what the PF had to work with while using his mayonnaise stirring stick technique, and only applies while in a stall. He is not supposed to be in a stall, but it appears that mayonnaise stirring is a particularly bad control technique while in a stall. That might be a lesson we can take from this.
I'll bet there are quite a few engineers that do not agree.
Quote:
Originally Posted by Machinbird
A crew not recognizing a stall! That just should not happen. Particularly with the amount of time they had at their disposal to recover.
Quote:
Originally Posted by GarageYears
But what was really "wrong"? Training. Training. Training
Even the BEA seems to hold the viewpoint espoused by Garage Years and myself:
.
I've been trying to pin down what specific training in my background convinces me that I would recognize the stall in the same situation that the AF447 crew faced.
The two factors are:
Originally Posted by Machinbird
The feedback channel he had used all his flying career was no longer available. He was operating open loop.
Originally Posted by Clandestino
That would be very damning, if found true. Proper way to perform instrument flying in civil aeroplane is by visual reference to instruments, not to column/stick position. Taught from day one of IR training. That's why no one made a fuss about non-backdriven sticks on Airbus. At least no one not anonymous.
Originally Posted by Clandestino
Protections are lost because there is no simple way to compute whether airspeed or AoA is wrong.
Quote:
Originally Posted by Machinbird
A crew not recognizing a stall! That just should not happen. Particularly with the amount of time they had at their disposal to recover.
Quote:
Originally Posted by GarageYears
But what was really "wrong"? Training. Training. Training
Originally Posted by Clandestino
While I might agree, I'd advise caution not to slip into conjecture. First 3 reports are heavy on technical side while HF side is seemingly neglected, which comes as no surprise to me as it is much more difficult and time consuming part of the investigation. Human are not machines, which sometimes comes as mixed blessing. While aeroplane doesn't care what time of day it is, human beings tend to perform better at 10:00 AM than 04:00.
Consequently, the BEA recommends:
that EASA review the content of check and training programmes and make
mandatory, in particular, the setting up of specific and regular exercises dedicated
to manual aircraft handling of approach to stall and stall recovery, including at
high altitude
that EASA review the content of check and training programmes and make
mandatory, in particular, the setting up of specific and regular exercises dedicated
to manual aircraft handling of approach to stall and stall recovery, including at
high altitude
I've been trying to pin down what specific training in my background convinces me that I would recognize the stall in the same situation that the AF447 crew faced.
The two factors are:
- Having read D. P. Davies description of the deceptive nature of the stall in a relatively level attitude.
- Having spent time maneuvering swept wing aircraft to their performance limits. (This has already saved my posterior on more than one occasion. Once was in a puddle jumper.)

Join Date: Oct 2009
Location: UK
Posts: 1,270
Likes: 0
Received 0 Likes
on
0 Posts
Hi Machinbird,
I was wondering the same thing myself. The Airbus Flight Training Study Guide (2003) had the following recommendation when in ALT LAW and approaching the stall: (see page 13) http://www.737ng.co.uk/a320training.pdf
"Eventually, the master warning and aural warnings will activate (crickets and “STALL, STALL” ). Recover at the stall warning by selecting TOGA thrust, maintain a pitch attitude for level flight and accelerate through VLS."
Unfortunately, AF 447 crew discovered that it doesn't work at FL 350.
(They probably had it demonstrated at 5,000 ft in their sim conversion course.)
I've been trying to pin down what specific training in my background convinces me that I would recognize the stall in the same situation that the AF447 crew faced.
"Eventually, the master warning and aural warnings will activate (crickets and “STALL, STALL” ). Recover at the stall warning by selecting TOGA thrust, maintain a pitch attitude for level flight and accelerate through VLS."
Unfortunately, AF 447 crew discovered that it doesn't work at FL 350.
(They probably had it demonstrated at 5,000 ft in their sim conversion course.)

Join Date: Jul 2009
Location: France - mostly
Age: 84
Posts: 1,688
Likes: 0
Received 0 Likes
on
0 Posts
Originally Posted by Clandestino
Sidestick command does not order G in absolute terms. It adds G demand to already measured, therefore if hit by updraft giving you 1.3G, pull on the stick that would give you 1.1 absolute from straight and level will now result in 1.4 pitch up. Push giving 0.9 would now be 1.2.
I've read somewhere that full back side stick corresponds to a demand of 2.5 g. Suppose you are at 1.3 g with neutral side stick, then pull the stick to the back stop. What do you get?
Then we have this description in mm43's post #366: "With STICK FREE in turbulence, small deviations do occur on the flight path but with a tendancy of the A/C to regain a steady condion". Does that functionality only exist with stick free?
Originally Posted by Clandestino
I realize you were talking hypothetically. To set the record clear who might not understand: such a test will never be made.
Last edited by HazelNuts39; 18th Nov 2011 at 21:04.

Join Date: Feb 2005
Location: Correr es mi destino por no llevar papel
Posts: 1,435
Received 0 Likes
on
0 Posts
Originally Posted by Machinbird
mayonnaise stirring stick technique
Originally Posted by Rudderrudderrat
Recover at the stall warning by selecting TOGA thrust, maintain a pitch attitude for level flight and accelerate through VLS."
Unfortunately, AF 447 crew discovered that it doesn't work at FL 350.
Unfortunately, AF 447 crew discovered that it doesn't work at FL 350.
Originally Posted by rudderrudderrat
They probably had it demonstrated at 5,000 ft in their sim conversion course.
Originally Posted by HazelNuts39
I've read somewhere that full back side stick corresponds to a demand of 2.5 g. Suppose you are at 1.3 g with neutral side stick, then pull the stick to the back stop. What do you get?
Originally Posted by HazelNuts39
"With STICK FREE in turbulence, small deviations do occur on the flight path but with a tendency of the A/C to regain a steady condition". Does that functionality only exist with stick free?
Now you reminded me I have to further qualify my statement that Airbus is not particularly prone to aircraft-pilot coupling; it is valid in still air. In turbulence, tendency of the airplane to self-correct pitch and bank disturbances may (and too often does) lead to pilot induced oscillation. Statement you quoted is mighty correct and is followed by very good advice to avoid large interventions with stick.

Join Date: Jan 2008
Location: uk
Posts: 861
Likes: 0
Received 0 Likes
on
0 Posts
"Eventually, the master warning and aural warnings will activate (crickets and “STALL, STALL” ). Recover at the stall warning by selecting TOGA thrust, maintain a pitch attitude for level flight and accelerate through VLS."
Unfortunately, AF 447 crew discovered that it doesn't work at FL 350.
(They probably had it demonstrated at 5,000 ft in their sim conversion course.)
Unfortunately, AF 447 crew discovered that it doesn't work at FL 350.
(They probably had it demonstrated at 5,000 ft in their sim conversion course.)

Join Date: Jan 2008
Location: uk
Posts: 861
Likes: 0
Received 0 Likes
on
0 Posts
If this and other LOCs were down to pilots who could handle a conventional aircraft perfectly well in the same circumstances but were constrained/prevented/confused by the airbus flight control laws, then I'd agree - ditch Alt laws and drop straight to direct. Give the crew the conventional aircraft if/when things start going wrong.
...but I don't think the above is a correct assumption. There's a subset of pilots (probably including those who care enough to follow accident threads on here) who would handle direct law just fine (or better), but is that the majority when I also see comment after comment along the lines of Machinbird's "compare what we learned about actual aircraft handling compared to what is presently being taught in the puppy mills, it is night and day".
Second:
I don't think stopping autotrim would have affected this accident. I know you've argued that had the nose gone down they'd have diagnosed the stall, but I'm not so sure. When the a/c did pitch down in stall what was the reaction ? Pull-up, hard. If you're already prepared and briefed for stall in the sim, the nose drop is going to be obvious, but if you think the a/c isn't responding right (which looks like an issue in roll at least even before the stall) and you're pulling back and the a/c suddenly drops the nose, what will you do ?
Third:
Changing something one way to "fix" one accident may make things worse in other cases and end up killing more people. We should look at all the LOC incident history not just this one. I've done some looking, though not in any way a systematic survey, in what I've read the common factors were:
Airbus: no. FBW: no. Sidestick: no. Trim / AutoTrim: oh yes. Time after time. Not every incident, but probably a majority - and much more common factor than the others.
But what is the typical problem with trim, what's its MO when it kills ? Looks to me like it's trim-up before stall, autos drop out, trim not managed by crew then contributing to the upset and/or preventing the recovery. Exactly the opposite of 447 - which looks like the odd one out.

Join Date: Feb 2001
Location: UK
Posts: 647
Likes: 0
Received 0 Likes
on
0 Posts
IF789, in the sample of accidents you looked at, as well as finding a common factor with autotrim, do you see a common factor in what has been identified as the problem by more than one expert above – to quote, training, training, training - ?
Chris N
Chris N

Join Date: Jan 2008
Location: uk
Posts: 861
Likes: 0
Received 0 Likes
on
0 Posts
Maybe not, but I can't provide the reassurance asked for. I raised similar concerns myself back here and triggered a well written response from PJ2 here
Could be a lot of reasons for that. PJ2's comments referenced above; increased auto-everything; SPOs and regulation (RVSM) that all but prohibit hand flying; and Glass.
That last one's a huge difference for the non-pilot looking in (and maybe for the trainee starting out...). Look in at the old style hundreds of steam gauges and row after row of switches and be awed, and fearful - you better learn and understand every one of those, this is complicated. Look instead these days at three computer screens a handful of switches and (maybe) a joystick - well, how hard can it be ?
Yet the fundamentals of flight haven't changed, the machine underneath is as complex as ever, if not more so, and the margin for error doing a few hundred knots in an aluminium can at 30k ft is still just as small...
Yes, there are many of us who understand the arrows and hooks and keeping 'rubber side down'. The problem we are facing here is that a particular system of flight (NB no names) appears to engender in some the chance to forget all this and become reliant on the system to look after them.
That last one's a huge difference for the non-pilot looking in (and maybe for the trainee starting out...). Look in at the old style hundreds of steam gauges and row after row of switches and be awed, and fearful - you better learn and understand every one of those, this is complicated. Look instead these days at three computer screens a handful of switches and (maybe) a joystick - well, how hard can it be ?
Yet the fundamentals of flight haven't changed, the machine underneath is as complex as ever, if not more so, and the margin for error doing a few hundred knots in an aluminium can at 30k ft is still just as small...
