I do see the tie-in with procedural noncompliance, and I think, too,
that the attribution of "procedural noncompliance" can be almost a given
in an accident (i.e., the procedures as defined don't lead to an
accident). I wonder, then, what this this telling us: the useful
information, I think, comes from looking at the quality of the
procedure, the cues that could/should have triggered its application,
the details of the crew's execution, the usefulness of the procedure in
coping with the problem, etc., in addition to (or instead of) merely
concluding that a procedure wasn't complied with. Sometimes too there
are several SOPs, some more general and some more specific, that could
be considered to apply to a single situation or moment during an
accident sequence...
Concerning your program, it sounds like a very interesting formulation.
Is is going to carry through to the simulator, as Vince suggests, by
introducing errors in some controlled fashion?
I haven't seen the article you mentioned, and I would apprec. very much
getting a copy. My fax is 202-314-6339.
Best regards,
Ben
> ----------
> From: DOWD MR. NORMAN[SMTP:ndowd_at_caribsurf.com]
> Sent: Tuesday, December 16, 1997 2:20 PM
> To: crm-devel_at_db.erau.edu
> Subject: Re: Procedural Non-compliance
>
>
> Hi Ben,
>
> Do you see a tie in between Boeing's Accident Prevention Strategies
> which show non compliance by the PF and your NTSB study? We are
> developing an error module which links the two and asks the pilots why
> SOPs in there experience haven't been adhered to. From there
> we expect to develop the prevention strategies from the class on how
> they try to - minimize the frequency of error, limit the
> extent of error, and cope or trap error. (ala Bob H.)
>
> The concept of the Accident pyramid is being employed as the visual
> model (Jacques S.).
>
> I'd be interested in your comments on the re-analysis of your data
> that includes the complexity of the operating environment and
> how it affects the performance differences as a function of pilot
> flying. (presented at the Houston CRM meeting by NASA/UT.) If you
> don't have a copy I could fax you one.
>
> Cheers
> Norm Dowd
>