PPRuNe Forums - View Single Post - AF 447 Thread No. 7
View Single Post
Old 1st Apr 2012, 00:56
  #1165 (permalink)  
RR_NDB
 
Join Date: Feb 2011
Location: Nearby SBBR and SDAM
Posts: 875
Likes: 0
Received 0 Likes on 0 Posts
Hi,

gums

The basic pilot skills are extremely important.
Rich data base, Intrinsic creativity enhanceable by adrenalin.

Nothing compares.

The big thing I learned was that basic flying skills counted more than all the computer assistance and such when things turned to worms.
In "normal conditions" automated Systems are designed to work near perfection. Who can perform so good during long hours "yaw dampening"? And performing as an autopilot? Just impossible.

When "worms are in sight" the System MUST HELP. This is ABSOLUTELY necessary in a good design (and relates DIRECTLY with the "interface")

It's inconceivable one need to interpret when facing difficult conditions "what the plane is telling" through unreliable, massive, erratic or intermittent indications of it's machine to man, interface.

PR (and sales people) concentrates on the "beauties" of new designs. What we know (in real world) is another face. Every mechanism has limitations.

In AF447 case during this fascinating and rich effort a large group of motivated professionals in a high Synergy addressed most aspects involved, here in PPRuNe.

Certainly HF aspects (closely related to the "interface") will be the "key" to explain crew actions that sadly put the A/C in a "terminal state" in a "near terminal speed".

Mac

PS

I also submit that the 'bus FBW system is not as "safe" as all the PR implies.
May be we could put like:

Airbus SAS approach is not what PR implies. Generating (clearly generated this even in pilots) a perception of something less dependent on "crew skill" than other approaches.

IMHO it's the opposite: In order to be able to interpret (and act) when the 'worms are in sight" the 40 seconds PJ2 mentioned could be too long.

In terms of this loss of control, while it unfolded literally over a period of about 40 seconds, oddly that is tons of time to do something, but it is not a lot of time for assessment, discussion, action.
The "capable pilot" here makes the difference.

Yes, we shall see. We don't have all required information. We need to wait to conclude.

Every judgment before (all relevant factual information) is at least, risky.
RR_NDB is offline