X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Sender: To: lml@lancaironline.net Date: Thu, 27 Dec 2007 21:46:38 -0500 Message-ID: X-Original-Return-Path: Received: from [64.12.143.100] (HELO imo-m12.mail.aol.com) by logan.com (CommuniGate Pro SMTP 5.2c4) with ESMTP id 2621375 for lml@lancaironline.net; Thu, 27 Dec 2007 12:24:57 -0500 Received-SPF: pass receiver=logan.com; client-ip=64.12.143.100; envelope-from=RWolf99@aol.com Received: from RWolf99@aol.com by imo-m12.mx.aol.com (mail_out_v38_r9.3.) id q.bff.2ae48244 (37047) for ; Thu, 27 Dec 2007 12:24:12 -0500 (EST) Received: from webmail-dd14 (webmail-dd14.webmail.aol.com [205.188.104.14]) by cia-db03.mx.aol.com (v121.4) with ESMTP id MAILCIADB035-90b74773dfbb25e; Thu, 27 Dec 2007 12:24:11 -0500 X-Original-To: lml@lancaironline.net Subject: Reliability Question X-Original-Date: Thu, 27 Dec 2007 12:24:11 -0500 X-MB-Message-Source: WebUI X-AOL-IP: 72.19.171.41 X-MB-Message-Type: User MIME-Version: 1.0 From: rwolf99@aol.com Content-Type: multipart/alternative; boundary="--------MB_8CA16C46E56DB00_C4C_2489_webmail-dd14.sysops.aol.com" X-Mailer: AOL Webmail 33161-STANDARD Received: from 72.19.171.41 by webmail-dd14.sysops.aol.com (205.188.104.14) with HTTP (WebMailUI); Thu, 27 Dec 2007 12:24:11 -0500 X-Original-Message-Id: <8CA16C46E56DB00-C4C-1229@webmail-dd14.sysops.aol.com> X-Spam-Flag: NO ----------MB_8CA16C46E56DB00_C4C_2489_webmail-dd14.sysops.aol.com Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii" This is a question for Brent and Hamid, but it also addresses the recent thread on reliability and redundancy. I have been recently educated on the FAA approach to reliability for certified airplanes, which can be simply summarized as a connection between the probability of failure and the resulting consequences.? For the aircraft I was working with, a "catastrophic" failure (results in loss of aircraft, loss of all life) needed to have a probability of 10e-9 (that's one in a billion).? A "major hazard" (damage to aircraft, loss of?a passenger) needed to have a probability of 10e-8.? Similarly, lower consequences were allowed to happen more frequently.? The key point here is that there was no failure that was prohibited -- even a wing falling off.? We just had to make it so unlikely that the risks were acceptably small.? Acceptable risks are lower for airliners, and higher for two-person propeller airplanes. FWIW, this goal was accomplished by making systems -- not components -- more reliable by strategically adding redundancy where it improved systm reliability. My question for Brent and Hamid is this -- given your comments that an EFIS has a finite probability of failure, what is that number?? What would it be for a certified EFIS (like a Chelton) and what would it be for a non-certified system (like a Dynon)? What I am getting at here is a quantitative way of ensuring that our proposed flight display systems have a reliability equal to that on a certified aircraft.? For example, if a Chelton failure probability is one in a million, and a Dynon failure probability?is one in a thousand, and the power supplies are separate (Dynon internal battery backup), wouldn't a Chelton + Dynon give you a one in a billion probability of total failure? By the way, I personally don't believe the failure probability numbers that the systems safety engineers come up with.? I believe that the actual rate of failure is significantly higher.? However, I *do* believe that using this methodology has given us a fleet of aircraft whose reliability we are comfortable with. - Rob Wolf ________________________________________________________________________ More new features than ever. Check out the new AOL Mail ! - http://webmail.aol.com ----------MB_8CA16C46E56DB00_C4C_2489_webmail-dd14.sysops.aol.com Content-Transfer-Encoding: 7bit Content-Type: text/html; charset="us-ascii" This is a question for Brent and Hamid, but it also addresses the recent thread on reliability and redundancy.

I have been recently educated on the FAA approach to reliability for certified airplanes, which can be simply summarized as a connection between the probability of failure and the resulting consequences.  For the aircraft I was working with, a "catastrophic" failure (results in loss of aircraft, loss of all life) needed to have a probability of 10e-9 (that's one in a billion).  A "major hazard" (damage to aircraft, loss of a passenger) needed to have a probability of 10e-8.  Similarly, lower consequences were allowed to happen more frequently.  The key point here is that there was no failure that was prohibited -- even a wing falling off.  We just had to make it so unlikely that the risks were acceptably small.  Acceptable risks are lower for airliners, and higher for two-person propeller airplanes.

FWIW, this goal was accomplished by making systems -- not components -- more reliable by strategically adding redundancy where it improved systm reliability.

My question for Brent and Hamid is this -- given your comments that an EFIS has a finite probability of failure, what is that number?  What would it be for a certified EFIS (like a Chelton) and what would it be for a non-certified system (like a Dynon)?

What I am getting at here is a quantitative way of ensuring that our proposed flight display systems have a reliability equal to that on a certified aircraft.  For example, if a Chelton failure probability is one in a million, and a Dynon failure probability is one in a thousand, and the power supplies are separate (Dynon internal battery backup), wouldn't a Chelton + Dynon give you a one in a billion probability of total failure?

By the way, I personally don't believe the failure probability numbers that the systems safety engineers come up with.  I believe that the actual rate of failure is significantly higher.  However, I *do* believe that using this methodology has given us a fleet of aircraft whose reliability we are comfortable with.

- Rob Wolf

More new features than ever. Check out the new AOL Mail!
----------MB_8CA16C46E56DB00_C4C_2489_webmail-dd14.sysops.aol.com--