Return-Path: <13brv3@bellsouth.net> Received: from imf21aec.mail.bellsouth.net ([205.152.59.69] verified) by logan.com (CommuniGate Pro SMTP 4.1.4) with ESMTP id 2602565 for flyrotary@lancaironline.net; Wed, 24 Sep 2003 21:43:15 -0400 Received: from rad ([68.212.13.204]) by imf21aec.mail.bellsouth.net (InterMail vM.5.01.05.27 201-253-122-126-127-20021220) with ESMTP id <20030925014313.RAUY1847.imf21aec.mail.bellsouth.net@rad> for ; Wed, 24 Sep 2003 21:43:13 -0400 From: "Russell Duffy" <13brv3@bellsouth.net> To: "'Rotary motors in aircraft'" Subject: RE: [FlyRotary] Coil problem or is it? Date: Wed, 24 Sep 2003 20:43:13 -0500 Message-ID: <000e01c38306$62638e80$0201a8c0@rad> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000F_01C382DC.798D8680" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4510 Importance: Normal In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 This is a multi-part message in MIME format. ------=_NextPart_000_000F_01C382DC.798D8680 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Now, here are the pestering nagging questions: Why would relatively new plugs fail when given the total load? Why would both plugs fail at the = same time? Is there something going on that is being overlooked? Has = anybody else ever seen this happen? (Ed/ Eddie, are you there?) Did this = happen because I'm so close to 2R4? =20 Hey, don't try to lay this on me :-) (2R4 is my home airport) =20 The real test would be to put the plugs back in, and see if it still = fails. I would be worried that there was a broken wire going to the coil. I'm = not familiar with the second gen coils, but I assume there's power, or = ground, or something that can take out the coil. I would run it briefly as is, = and make sure it's still OK, then put the plugs you just took out in, and = run it again. I would make every effort not to touch any wiring other than the plug wires. If that's bad, I would put the new plugs back in, and try again, still without touching any other wires. That test will give you = a pretty good idea if it's really the plugs. =20 =20 It does seem hard to believe that the plugs could both be bad, unless = maybe they missed you, and died of loneliness :-) =20 BTW, I know you're short on time in town, and I think I have one new set = of plugs at the hanger. If you need them, let me know and we can meet somewhere. =20 =20 Good luck, Rusty =20 =20 =20 ------=_NextPart_000_000F_01C382DC.798D8680 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message

Now, here are the pestering nagging questions:  = Why would=20 relatively new plugs fail when given the total load?  Why would = both plugs=20 fail at the same
time?   Is there something going on that = is being=20 overlooked?  Has anybody
else ever seen this happen?  (Ed/ = Eddie,=20 are you there?)  Did this happen because I'm so close to = 2R4?

 
Hey, = don't try to lay=20 this on me :-)     (2R4 is my home=20 airport)
 
The real = test would be=20 to put the plugs back in, and see if it still fails.  I would be = worried=20 that there was a broken wire going to the coil.  I'm not familiar = with the=20 second gen coils, but I assume there's power, or ground, or something = that can=20 take out the coil.  I would run it briefly as is, and make sure = it's still=20 OK, then put the plugs you just took out in, and run it again.  I = would=20 make every effort not to touch any wiring other than the plug = wires.  If=20 that's bad, I would put the new plugs back in, and try again, still = without=20 touching any other wires.  That test will give you a pretty = good idea=20 if it's really the plugs.  
 
It does = seem hard to=20 believe that the plugs could both be bad, unless maybe they missed = you, and=20 died of loneliness :-)
 
BTW, I = know you're short=20 on time in town, and I think I have one new set of plugs at the = hanger.  If=20 you need them, let me know and we can meet=20 somewhere.  
 
Good=20 luck,
Rusty
  
 
     


------=_NextPart_000_000F_01C382DC.798D8680--