Hi,

My understanding of the BEA note is they are not accurate ....
When you make the sum of speed invalid time it's more than "less than one minute"
It's two losses of speed indication
Was better to put also a foot note for the second loss of valid speed.
It's important for the case.

No because the notes where in chronological order. They put that note after the first loss of indication. Which is where it belonged.

BTW can you tell me where you got this quote you posted?

I ask because google has never heard of that quote.... and gogole knows everything. ;)

I stand by post#1 here, posted nearly two years ago, and would repeat another post somewhere else that an easily accessible big button on this type of system is needed to enable direct control (assuming, of course, we have pilots in the cockpit and not computer operators:mad:).

There is still, even after all these years and accidents, much yet to be discovered on this FBW system and its failure/reversionary modes which appear to be built on the assumption that 'nothing can really go wrong so we don't need to worry too much about it.' Murphy's law applies.

beinville
you say I should google it?
jesus is that where you get your knowledge from?

Fact from personal experience .

All of my stall warnings in airliners have occurred in approach configuration low down in turbulence except for one in a high level holding pattern which was a mach stall.

Besides the obvious factors the margin over the stall is at it's minimum.

Once in initial climb at MTOW we hit minus 20+knots windshear with T/O thrust - procedure was full thrust and +5 pitch or thereabouts.
Speed was below V2.
Skipper followed procedure but speed decreased - he ignored my calls so I got on the stick and gently pushed it to drop the nose a couple of degrees and we started accelerating.(lower drag).

You have to realize that today everyone is taught to follow SOP but they do not always work.

The pilots did NOT fight the trim.
Please read the Report!
They produced/aggravated the trim.
Had they pushed the stick forward the NU trim would have been reduced by the Auto- trim.
There is NO indication of a runaway trim. It seems it was a commanded trim.

No I'm asking you why you say I am wrong?

The plane stalled at ~37,000 feet. There was absolutely no reason the pilot had to 'grab sky". Quite the contrary he was too high and (most surly) would not have stalled at 15,000 feet.

Now if you can tell me how I'm wrong, I'm all ears.

AND BTW your training or the lack thereof has nothing to do with this flight.

As I read BEA I was puzzled by THS being in almost full up position for about 3,5 minutes and not changing its position although PF made pitch-down input. Unfortunately report doesn't mention for how long pitch-down input lasted. I took my copy of A330 FCOM (not current one) and found out, please correct if I am wrong, that flight control law could have changed from ALT 2 to Abnormal attitude as angle of attack was greater than 30 deg causing no auto trim available until angle of attack decreases below 30 deg, which according to BEA report did not happen.

https://lh4.googleusercontent.com/-w...011_095849.jpg

Is there any indication in the cockpit when this happens?

Stall recovery and auto flight
 

All

We have a loss of airspeed data because of ice in the pito that lasted for under a minute.

This triggered Alternate Law

After this the pitos came back, with the aircraft in a deep stall

Some questions :

1. Could the auto flight system be re-engaged in the stall ?

2. If so , would Alpha floor pulled them out of the stall ?


Simon

BEA Report – The trimmable horizontal stabilizer (THS) passed from 3 to 13 degrees nose-up in about 1 minute and remained in the latter position until the end of the flight.

The last recorded values were a pitch attitude of 16.2 degrees nose-up, a roll angle of 5.3 degrees left and a vertical speed of -10,912 ft/min.

Where is the BEA quoted (THS) trim nose-up angle measured?

Is it an internal computed value displayed on EICAS?

Is it 13.2º on the cockpit pedestal trim wheels?

Is it 13.2º as shown on some aircraft where the horizontal stabiliser (tailplane) leading edge fairing meets the vertical fin?

Or ..... ?

It seems the problem is even the best pilots don't totally understand everything about their aircraft! It seems you need to do an IT course not a flight training course for this plane! Then you have the problem of airbus themselves claiming it couldnt stall!How many incidents have occurrd with the computer workIng against the pilots!

Frankly it's like a horror si-Fi movie of robots that try take over the world, the machine thinks it's better then the pilots, and the makers don't understand the complicated rare events, the events that kill.:oh:

Hi,

Seem's Google is no more reliable .. lol
http://henrimarnetcornus.20minutes-b...1718484589.pdf

I'm not sure how this nonsense got started... the computer was not "working against the pilot"... The report today CLEARLY says that all engine controls and input controls were functioning perfectly.

The pilots were working against common sense. When a plane stalls you push the nose down, not up. End of discussion.

> Seem's Google is no more reliable .. lol

OK anything more reliable than some guy's blog who today posted a quote that nobody has ever seen before?

Hmmm, looking through all the ACARS and the information we have at the moment I surely must have overseen the part where it was stated that all PRIM's were deactivated. I have seen PRIM1 and SEC1 but nothing more.
Could you point me to the information indicating loss of all PRIM's ?
That would have led to Direct Law btw.
Also I'm missing the part where it was stated that the pilots were vigorously commanding Nose Down only to be overriden by the Trim ?

henra one thing I really learned tonight is that people just make stuff up.

Beinville
you have to step back and put your thinking hat on.

One of the most frightening and unique generated sounds in a cockpit is the death rattle.

Add the fear, fatigue, disorientation and hypoxia factors to a host of contradictory information then the brain prioritizes.

The crew were faced with false stall warnings, overspeed warnings, control law warning, turbulence, probable dutch roll and a stab that was moving to the aft limit for whatever b****y reason.

I very much doubt if anyone in the crew had ever flown manually at altitude.

The body tenses with stress and fear and primeval instinct is to wrap oneself up in the foetal position - which could have resulted in the PF inadvertently putting a nose up input on the stick while he was sorting out the roll and what was really happening.

They had very little time and whether or not they had any correct speed indications they did not have the time to diagnose what was right or wrong.

Remember the air india 747 which rolled on it's back with a faulty horizon after take off - one instrument failure only.

BA nearly lost a 747 - the LAX one- as the crew didn't understand the basics of the fuel system and that technology goes back to Noah.
They also had the whole night to play around with it and get it wrong.

The myriad of posts trying to fathom out the computer system shows that it is not understood by the average bloke.

From yesterday's note from the BEA ... apart from the stall warning ... indeed there seems to be no indication (from the CVR) that they realized they were into a stall? If there was, why would the BEA chose to leave it out of their note?

That kind of analysis is the last thing I would expect to see in an accident report.

The crew deserves a more thorough analysis

I think Blind Pew needs to follow his own advice and step back...

Ten out of ten for drama, five out of ten for accuracy. False stall and overspeed warnings are to be expected wth unreliable IAS. Control law warning - no big deal, alternate law is benign. Turbulence? An assumption. Dutch roll? And assumption. Moving stab? Not an issue. It was functioning as designed and the crew would not likely even be aware of the stab position.

I have flown an Airbus manually at altitude. It's exactly the same as flying it at 10,000 feet thanks to the flight control laws, either in Normal or Alternate law. It's not an issue.

Errrrr - you don't accidentally put full back stick on, and not for 30 secs. Your arm will get very tired.

Thats why you have an unreliable airspeed recall item.

There was never any chance of losing the aircraft, and the issue which manifested itself only became apparent at top of descent and would have resolved itself of it's own accord anyway. Lots of fuss about nothing.

Fortunately 'average blokes' aren't let loose on multi-million dollar airliners. They have to have a lot of training first, which is why many Airbus experienced pilots find this kind of speculation tedious.:ugh: