Received-SPF: pass
 receiver=logan.com; client-ip=205.152.59.65; envelope-from=bobperk@bellsouth.net
From: "Bob Perkinson" <bobperk@bellsouth.net>
To: "Rotary motors in aircraft" <flyrotary@lancaironline.net>
Subject: Fault Tree
Date: Thu, 17 May 2007 11:06:11 -0500
Message-ID: <ILEAJJGIFLOMDOBNJCPPOEJMCCAA.bobperk@bellsouth.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
In-Reply-To: <list-2048803@logan.com>
Importance: Normal

Has any one developed a fault tree to follow when situations arise where the
problem with the EC-2 system is not out rightly known?  Each time I hear of
a problem the rabbits come out of the woods and start running, each rabbit
is a good one but which rabbit is the right one, there have been many
different rabbits chased along this line, and I was thinking that a Good
Fault Tree analyzes would be very helpful. Then when someone has a problem
with the EC-2, they could pull out the structure tree and go down the list
until they either found the problem or hit the end of the list, at which
time they would throw up there hands and ask for help on the list.  I think
this would help simplicity the problem solving process.  I know that not all
aircraft are configured the same but if they are using the EC 2 they are all
basically wired alike or should be.  The complexity of, and many modes that
this computer has, would I think warrant a well written fault analyses tree.
Like any tree it will grow over time, and by the time it is fully matured
might contain enough combined knowledge to keep Tracy’s phone quiet for a
few days,

Any Volunteers!!


Bob Perkinson
Hendersonville, TN.
RV9 N658RP Reserved
If nothing changes
Nothing changes