X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: <13brv3@bellsouth.net> Received: from imf22aec.mail.bellsouth.net ([205.152.59.70] verified) by logan.com (CommuniGate Pro SMTP 4.3.4) with ESMTP id 989234 for flyrotary@lancaironline.net; Wed, 08 Jun 2005 19:42:53 -0400 Received-SPF: pass receiver=logan.com; client-ip=205.152.59.70; envelope-from=13brv3@bellsouth.net Received: from ibm67aec.bellsouth.net ([65.6.194.9]) by imf22aec.mail.bellsouth.net with ESMTP id <20050608234209.ZMBH16779.imf22aec.mail.bellsouth.net@ibm67aec.bellsouth.net> for ; Wed, 8 Jun 2005 19:42:09 -0400 Received: from rd ([65.6.194.9]) by ibm67aec.bellsouth.net with ESMTP id <20050608234207.CAZQ11273.ibm67aec.bellsouth.net@rd> for ; Wed, 8 Jun 2005 19:42:07 -0400 From: "Russell Duffy" <13brv3@bellsouth.net> To: "'Rotary motors in aircraft'" Subject: RE: [FlyRotary] Remaining pressure when cold (Re: coolant leak) Date: Wed, 8 Jun 2005 18:42:08 -0500 Message-ID: <000001c56c83$af5b29b0$6101a8c0@rd> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0001_01C56C59.C68521B0" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 Importance: Normal In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527 This is a multi-part message in MIME format. ------=_NextPart_000_0001_01C56C59.C68521B0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable >>>> You have a compression leak if.... <<<< Very nice write-up Bill. =20 =20 Dave, I've got to agree that I've never seen pressure after cool down on = any cooling system. Do you have something unusual about your system, like = two different pressure caps, or anything else that might make it behave abnormally? =20 =20 I believe the "normal" way to test for this is to use a coolant pressure tester, or any other method you can devise to pressurize the system. = I'm thinking you could easily have a leak that allowed combustion pressure = to get through, but would never let coolant pressure through, particularly pushing liquid. =20 =20 It would be easy enough to pressurize the coolant system to about 30 psi = and see if the coolant goes into your new turbo. Also, isn't there a test = you can do where you send a sample of coolant out to be tested for = combustion gasses? That might be easier, and more likely to give a final answer. =20 =20 I sure hope it's not leaking Dave. I guess this is another warning sign that I'll never get with my zero pressure system, though if I blow too = many bubbles, the low coolant light will come on. =20 =20 Cheers, Rusty (zero pressure / ignorance is bliss) =20 =20 ------=_NextPart_000_0001_01C56C59.C68521B0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message

 >>>> You have a compression leak = if....=20 <<<<

Very = nice write-up=20 Bill.  
 
Dave, = I've got to agree=20 that I've never seen pressure after cool down on any cooling=20 system.  Do you have something unusual about your system, like = two=20 different pressure caps, or anything else that might make it behave=20 abnormally?  
 
I = believe the "normal"=20 way to test for this is to use a coolant pressure tester, or any = other=20 method you can devise to pressurize the system.   I'm = thinking=20 you could easily have a leak that allowed combustion pressure to get = through,=20 but would never let coolant pressure through, particularly pushing = liquid. =20
 
It would = be easy enough=20 to pressurize the coolant system to about 30 psi and see if the coolant = goes=20 into your new turbo.  Also, isn't there a test you can do where you = send a=20 sample of coolant out to be tested for combustion gasses?  That = might be=20 easier, and more likely to give a final answer.  =
 
I sure hope it's not leaking = Dave.  I=20 guess this is another warning sign that I'll never get with my zero=20 pressure system, though if I blow too many bubbles, the low coolant = light=20 will come on. 
 
Cheers,
Rusty (zero pressure / ignorance = is=20 bliss)
 


 
------=_NextPart_000_0001_01C56C59.C68521B0--