Return-Path: <13brv3@bellsouth.net> Received: from imf22aec.mail.bellsouth.net ([205.152.59.70] verified) by logan.com (CommuniGate Pro SMTP 4.2.1) with ESMTP id 410714 for flyrotary@lancaironline.net; Tue, 14 Sep 2004 14:56:56 -0400 Received-SPF: pass receiver=logan.com; client-ip=205.152.59.70; envelope-from=13brv3@bellsouth.net Received: from rd ([65.6.194.9]) by imf22aec.mail.bellsouth.net (InterMail vM.5.01.06.11 201-253-122-130-111-20040605) with ESMTP id <20040914185327.OVOD219.imf22aec.mail.bellsouth.net@rd> for ; Tue, 14 Sep 2004 14:53:27 -0400 From: "Russell Duffy" <13brv3@bellsouth.net> To: "'Rotary motors in aircraft'" Subject: RE: [FlyRotary] Re: Limp home mode Date: Tue, 14 Sep 2004 13:53:33 -0500 Message-ID: <001401c49a8c$2222ee30$6101a8c0@rd> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0015_01C49A62.394CE630" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Importance: Normal In-Reply-To: This is a multi-part message in MIME format. ------=_NextPart_000_0015_01C49A62.394CE630 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I wonder if each rotor could be plumbed separately with its own EWP and = evap core radiator. I don't see any way of doing that without significantly customizing the = iron housings. =20 =20 Rusty (rewelding one of my EWP adapters that leaks like a sieve) ------=_NextPart_000_0015_01C49A62.394CE630 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message

I wonder if each rotor could be plumbed separately = with its own=20 EWP and evap core radiator.

I don't = see any way=20 of doing that without significantly customizing the iron=20 housings.  
 
Rusty = (rewelding one of=20 my EWP adapters that leaks like a = sieve)
------=_NextPart_000_0015_01C49A62.394CE630--