X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Received: from m12.lax.untd.com ([64.136.30.75] verified) by logan.com (CommuniGate Pro SMTP 4.3.4) with SMTP id 986482 for flyrotary@lancaironline.net; Mon, 06 Jun 2005 16:05:08 -0400 Received-SPF: pass receiver=logan.com; client-ip=64.136.30.75; envelope-from=alwick@juno.com Received: from m12.lax.untd.com (localhost [127.0.0.1]) by m12.lax.untd.com with SMTP id AABBLKMBHAC854RS for (sender ); Mon, 6 Jun 2005 13:03:51 -0700 (PDT) X-UNTD-OriginStamp: L941HVjjYzDhN3itp//mkLoCHOBuc8/AcnF0p5OpY+IV7F1sx1LJNw== Received: (from alwick@juno.com) by m12.lax.untd.com (jqueuemail) id KUUA3V2H; Mon, 06 Jun 2005 13:03:37 PDT To: flyrotary@lancaironline.net Date: Mon, 6 Jun 2005 12:30:47 -0700 Subject: Re: [FlyRotary] Re: EC2 problems - solved / rotary risks Message-ID: <20050606.130311.2568.27.alwick@juno.com> X-Mailer: Juno 5.0.33 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary=--__JNP_000_1cc2.2e4f.50ea X-Juno-Line-Breaks: 8-6,9-12,14-15,17-18,21,22-32767 From: al p wick X-ContentStamp: 22:11:1721601543 X-MAIL-INFO:2274e081798945edb49139e08d317091ddf9d1d1b005a5b094 X-UNTD-Peer-Info: 127.0.0.1|localhost|m12.lax.untd.com|alwick@juno.com This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ----__JNP_000_1cc2.2e4f.50ea Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Yes, you are right. But we want to resist the temptation to look for ways "this doesn't apply". We need to seek ways to apply this failure to the rest of your plane. There is common root cause. -al On Mon, 6 Jun 2005 10:49:51 -0400 "John Slade" writes: Thanks, Al. After a slightly bad start, this is starting to get very informative and interesting. Please keep it coming. In the case of the wire/connector, I'm not really worried about it because it'd not an engine out thing, just a loss of communication with the engine monitor. ----__JNP_000_1cc2.2e4f.50ea Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: quoted-printable

Yes, you are right. But we want to resist the temptation to look for = ways=20 "this doesn't apply". We need to seek ways to apply this failure to the = rest of=20 your plane. There is common root cause.

-al

On Mon, 6 Jun 2005 10:49:51 -0400 "John Slade" <sladerj@bellsouth.net> writes:=

Thanks, Al.

After a slightly bad start, this is= =20 starting to get very informative and interesting. Please keep it=20 coming.

In the case of the wire/connector, = I'm not=20 really worried about it because it'd not an engine out thing, just a loss= of=20 communication with the engine monitor.

=20 =20 =20

----__JNP_000_1cc2.2e4f.50ea--