>A very interesting thread on automation. Could we get another thread going
>from the humble pilot's perspective. When I'm flying a Bugsmasher model
>900 I'm really only interested in the automation installed, when to use it,
>and when to turn the bloody thing off. From a CRM standpoint these should
>be crew decisions and we need to address how the crew decides to use, not
>use, or abandon automation.
And (in part) John Bent of Cathay Pacific wrote:
>Regarding training (some other comments) there is realy no
>big deal about training requirements - BUT old style training programmes
>won't work well. Lots of thought and preparation has to go into
>appropriate training, not more of the same. If you use the traditional
>approach it will be a monster experience, involving weeks of technical
>indigestion. "Operational" training is the key, as exemplified by US AQP
>processes. CRM is also essential on new technology types.
After vigorously debating the merits of the various airframe manufacturers'
design approaches, we have come to the issue of how to TRAIN our crews to
best use the equipment our bosses have already purchased. How much does
the crew NEED to know about their automated systems to operate them safely
and efficiently? Is AQP the ideal way to define this, or is it just better
than what we used to do? How do we account for automation issues in our
CRM and human factors training?
Best regards,
Neil Krey
neilkrey_at_why.net
http://users.why.net/neilkrey/