PPRuNe Forums

PPRuNe Forums (https://www.pprune.org/)
-   Tech Log (https://www.pprune.org/tech-log-15/)
-   -   Airbus crash/training flight (https://www.pprune.org/tech-log/352696-airbus-crash-training-flight.html)

Safety Concerns 5th July 2010 04:46

It isn't about whether the AOA's were faulty because they weren't. No fault nothing to detect. Something external to the sensor affected them.

This is why accident investigation must encompass more than the flying aspect.

The aircraft had been painted and washed. This involves following strict procedures for good reason. You can affect sensors in an unpredictable way.
Just as pilots have procedures which must be adhered to so does everyone else.

The aircraft departed and for quite a bit of the flight everything was fine, then something happened to 2 out of 3 AOA's. The AOA is an extremely reliable sensor so 2 behaving badly at the same time is unheard of. This needs investigating. It isn't about my input is more worthy than yours, its about finding out what happened here and what happened involves more than just flight crew.

Something was technically wrong with that aircraft, we need to know what and why otherwise it will happen again.

Scotty Beamup 5th July 2010 07:03

I think you should read my post.

Scotty Beamup 5th July 2010 07:14

And while i'm at it DW, the simple facts of the matter were that in the final seconds of the flight, while the captain had the side stick in the full nose up position the elevators were full nose down. This may have been a result of summation (in that the stabiliser was full nose up) who cares? If a pilot is ordering full nose up on the elevators, shouldn't he get it?

BOAC 5th July 2010 07:19

Absolutely, SC, hence my #1169. I must be remembered, however, that once all the designers and engineers are done, and something is wrong with what they have done, that we have, for the foreseeable future at least, one human there who SHOULD be able to do some old fashioned flying (that is without software) and save the a/c and lives.

Yes, if something prevents them doing that it must be investigated and designed/engineered out - see para a). I have yet to see any evidence that such existed, but the F/O's sidestick trace would be of interest to me - or have I missed it on the traces? On an AB, does the 'Captain's sidestick position' always represent that or the master stick position?

EDIT: Picking up on Scotty: I think from what I have learned the sidestick is a rate demand rather than a position demand? Hence if the nose-up stab effort (at 263kts) was producing at least the designed max pitch rate, the elevators would be in opposition? Whether the airframe would have withstood max elevator as well I do not know. The nose was pitching up fairly rapidly after all at impact

Once again we appear to have the excessive stab trim/pitch couple causing the major upset. Is it time this was eliminated in the software? Perhaps some over-rideable limit on trimming range? As we know this is certainly an area where crew training needs to change.

CONF iture 8th July 2010 03:23

BOAC,

For the pitch control, the flight law is a load factor demand law.
Most probably, for the final dive, the pitch demand was limited by the load factor protection.
This could be the reason the BEA was not interested in publishing the vertical acceleration graph.

Originally Posted by bearfoil
Rumour only: The aircraft "protected" itself into the Ocean. allegedly.

... could be more fonded that we might think.


The F/O's sidestick trace would be of interest to me too.
Who thinks the F/O remained of ice in those extreme attitudes ...
Me being in his seat it would have been "dual input" all over the place, or at best "priority right" ... if I could stay cool enough.

BOAC 8th July 2010 08:19

Thanks for the clarification, Conf. The emphasis has to be on how they got to 51 degrees nose down at 1620' (a real 'coffin corner!) and not what the controls did thereafter.

TyroPicard 8th July 2010 10:34

You're right BOAC - I suppose 97°of bank might have something to do with it...
Re sidesticks - there is no "master", the inputs are summed algebraically unless one pilot presses and holds the "takeover pushbutton" (same as AP disconnect pb). You should be able to tell from the FDR trace whether there is a dual input in Direct Law (if the control positions don't accord with capt. sidestick position) - can't see one. But in Normal/Alternate Law I reckon you need the FDR info on dual input.

What interests me is the lack of CVR information in the BEA interim report once it all went wrong- I would like to know whether the crew said anything about:
a) being in Direct Law
b) moving the THS from fully nose-up
c) why they raised the gear
d) why they looked at ECAM HYD system.
I like to think the final report will tell us....

BOAC 8th July 2010 11:20

Indeed , it proves two things - use of aileron on a stalled wing is not a good idea and the best way to drop the nose is to apply lots of bank.

I suspect the CVR is not 'pretty' and may therefore not reach the public domain.

Do you deduce that they deliberately 'looked' at the HYD page or is there some automatic call or could someone just have 'missed' on a selection? Likewise why the ENG page later?

CONF iture 8th July 2010 12:49


Originally Posted by BOAC
The emphasis has to be on how they got to 51 degrees nose down at 1620' (a real 'coffin corner!) and not what the controls did thereafter.

This is still nice to understand why the elevators did the opposite to the sidestick ... s(?) request.
Now, 17 seconds earlier, the airplane was at 3800 feet in a 57 degrees nose up attitude and virtually no speed. The emphasis could be on how they got there first.
It is amazing to consider that for a full minute, that airplane was out of control before it finally crashed.

The most interesting part should be to analyze what role played those two frozen AoA sensors in this flight.

BOAC 8th July 2010 13:57


This is still nice to understand why the elevators did the opposite to the sidestick ... s(?) request.
- well, I would think as per my para3 (italic) in #1177 that the elevators were attempting to limit the g caused by the THS setting?

Regarding 'how they got where' the '57 up' is all part of the route to 51 down. I think we are all pretty convinced, are we not, that the '57 up' was power/pitch?

CONF iture 8th July 2010 15:05


Regarding 'how they got where' the '57 up' is all part of the route to 51 down. I think we are all pretty convinced, are we not, that the '57 up' was power/pitch?
We are ... but the power/pitch was not manageable due to the excessive THS up position which got there because of the faulty AoA sensors that were telling the same lie and silently discarded the only probable (?) reliable AoA data.

TyroPicard 8th July 2010 17:18

BOAC

Do you deduce that they deliberately 'looked' at the HYD page
Good question - no thoughts either way now, although my previous post assumes they selected it, it's just one of the events that the CVR might explain a little. The HYD key is next to the F/CTL key, but if that was the target I would expect it to appear almost immediately after the wrong selection was realised.
Re the survivabilty of 50°pitch, to me it all hinges on the THS - was it stuck or did they just not move it (Direct Law = Manual pitch trim)? With the trim in a more normal position and the a/c in Direct Law a recovery should have been possible - and they probably would not have reached that attitude and the resultant low speed in the first place.

BOAC 8th July 2010 19:07

"the parameter is recorded every four seconds" says the report and 4 seconds later displays 'ENG'? Does that mean anything to you?

p51guy 8th July 2010 20:26

In a Boeing with competent pilots this could not have happened. Once again I think automation took over and the pilots were along for the ride. They probably were trying to use the proper recovery but automation overrode their inputs. The pitchup was probably a result of too much thrust being generated at critical speed. The pilots on a Boeing would have reduced the power to control the pitch and recovered with little problem. Pilots know how to recover from low speed stick shaker situations. They also know how to not be (to) agressive with thrust until they can control pitch.

p51guy 8th July 2010 21:45

too, not to. I hate those errors.

CONF iture 8th July 2010 22:37


Originally Posted by p51guy
They also know how to not be too agressive with thrust until they can control pitch.

Like in AMS ... ?

bearfoil 8th July 2010 22:51

I think p51guy wrote.... "competent pilots"

bear

stillalbatross 8th July 2010 23:30


In a Boeing with competent pilots this could not have happened
More Boeing drivel. So any crash that occurred in a Boeing occurred because the pilots weren't competent? And anyone who flies an Airbus isn't aware of the thrust arm with underwing engines? Or standard stall recovery?

Anyone on a public forum making such comments should first start off with "my experience on both types is............"

So P51 guy, were the pilots in the Cali accident competent?

vapilot2004 9th July 2010 04:40

AI v BCA drivel
 
I feel the occurrences of multiple crashes over the years of AI aircraft during training/test flights point more towards a misunderstanding of the protections and automatic functions of the computerized flight control system rather than indicating a critical defect in design.

A deeper understanding of the FBW protections as they apply in complex degradation scenarios seems to be called for if we are to avoid future incidents and crashes.

The question "Why does it do that?" should never be a part of a crew's standard vernacular.

p51guy 9th July 2010 13:31

Being competent doesn't mean you can't make a mistake. The Cali captain was considered quite competent but no one will deny they made a huge mistake that night. Being competent means you understand how to manage an aircraft properly and can demonstrate it. CFIT has been accomplished by quite a few crews considered competent.


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


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