X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Received: from fed1rmmtao03.cox.net ([68.230.241.36] verified) by logan.com (CommuniGate Pro SMTP 4.3.2) with ESMTP id 962861 for flyrotary@lancaironline.net; Wed, 25 May 2005 09:43:05 -0400 Received-SPF: none receiver=logan.com; client-ip=68.230.241.36; envelope-from=ALVentures@cox.net Received: from BigAl ([68.7.14.39]) by fed1rmmtao03.cox.net (InterMail vM.6.01.04.00 201-2131-118-20041027) with ESMTP id <20050525134221.JXMV26972.fed1rmmtao03.cox.net@BigAl> for ; Wed, 25 May 2005 09:42:21 -0400 From: "Al Gietzen" To: "'Rotary motors in aircraft'" Subject: Failure analysis Date: Wed, 25 May 2005 06:42:36 -0700 Message-ID: <000a01c5612f$9c8fe3c0$6400a8c0@BigAl> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000B_01C560F4.F0337CC0" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 In-Reply-To: This is a multi-part message in MIME format. ------=_NextPart_000_000B_01C560F4.F0337CC0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit As a rule of thumb in doing 'Failure Analysis' on your installation: we want to look for potential 'single point' failures, and eliminate them to the extent possible (reduce their probability); or make the system tolerant by having a backup. We normally do not need to assume double or multiple failures. That usually results in added complexity, weight, etc., with little gain. An example might be; if you have dual batteries as power source, you don't need to pursue dual alternators. Just thought I'd throw that out there. Al ------=_NextPart_000_000B_01C560F4.F0337CC0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

As a rule of thumb in doing ‘Failure = Analysis’ on your installation: we want to look for potential ‘single = point’ failures, and eliminate them to the extent possible (reduce their = probability); or make the system tolerant by having a backup.  We normally do not = need to assume double or multiple failures.  That usually results in = added complexity, weight, etc., with little gain.

 <= /font>

An example = might be; if you have dual batteries as power source, you don’t need to = pursue dual alternators.

 <= /font>

Just thought = I’d throw that out there.

 <= /font>

Al

------=_NextPart_000_000B_01C560F4.F0337CC0--