X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: <13brv3@bellsouth.net> Received: from imf17aec.mail.bellsouth.net ([205.152.59.65] verified) by logan.com (CommuniGate Pro SMTP 4.3.4) with ESMTP id 987363 for flyrotary@lancaironline.net; Tue, 07 Jun 2005 12:19:18 -0400 Received-SPF: pass receiver=logan.com; client-ip=205.152.59.65; envelope-from=13brv3@bellsouth.net Received: from ibm57aec.bellsouth.net ([65.6.194.9]) by imf17aec.mail.bellsouth.net with ESMTP id <20050607161832.JXAN13483.imf17aec.mail.bellsouth.net@ibm57aec.bellsouth.net> for ; Tue, 7 Jun 2005 12:18:32 -0400 Received: from rd ([65.6.194.9]) by ibm57aec.bellsouth.net with ESMTP id <20050607161832.PEXX25470.ibm57aec.bellsouth.net@rd> for ; Tue, 7 Jun 2005 12:18:32 -0400 From: "Russell Duffy" <13brv3@bellsouth.net> To: "'Rotary motors in aircraft'" Subject: RE: [FlyRotary] Two Engines In One? Date: Tue, 7 Jun 2005 11:18:32 -0500 Message-ID: <001901c56b7c$8cc42a30$6101a8c0@rd> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_001A_01C56B52.A3EE2230" 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.2527 Importance: Normal In-Reply-To: This is a multi-part message in MIME format. ------=_NextPart_000_001A_01C56B52.A3EE2230 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Would it be possible to treat a 13B as 2 singles that happened to share = a common side housing? What I'm wondering is, can you use 2 carburetors, 2 fuel pumps, 2 ignition systems & CAS's on a single 13B - each rotor independently serviced - and still have reasonable = performance (i.e. HP)? You would still have a common oil and water cooling system - = but hey that eliminates the EFI, ECU, and potentially your electrical system = as single points of engine failure. =20 Hi Joe,=20 =20 You could certainly do that, but a two rotor engine running on one rotor = is supposed to be so rough that you might shut it down just to keep from = having to put up with it. I have to admit that I don't completely understand = why that is, and I'd appreciate it if someone would explain that to me. =20 =20 The next thing to consider is that you'll be making a bit less than half power at best with a constant speed prop. With a fixed pitch, you will = be way over propped, and probably won't be able to get the engine into a = decent power range, so you won't be able to maintain altitude in most planes. = My RV-3 might do OK, but a fully loaded RV-6 won't. =20 Good thought. Full credit for outside the box thinking :-) =20 Cheers, Rusty =20 ------=_NextPart_000_001A_01C56B52.A3EE2230 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Message

Would it be possible to treat a 13B as 2 singles that = happened=20 to share a common side housing? What I'm wondering is, can you use 2=20 carburetors, 2 fuel pumps, 2 ignition systems & CAS's on a single = 13B
-=20 each rotor independently serviced - and still have reasonable = performance (i.e.=20 HP)? You would still have a common oil and water cooling system - but = hey that=20 eliminates the EFI, ECU, and potentially your electrical system as = single points=20 of engine failure.

 
Hi Joe,=20
 
You = could certainly do=20 that, but a two rotor engine running on one rotor is supposed to be so = rough=20 that you might shut it down just to keep from having to put up with=20 it.  I have to admit that I don't completely understand why = that is,=20 and I'd appreciate it if someone would explain that to = me.   =20
 
The next = thing to=20 consider is that you'll be making a bit less than half power at = best with a=20 constant speed prop.  With a fixed pitch, you will be way over = propped, and=20 probably won't be able to get the engine into a decent power range, so = you won't=20 be able to maintain altitude in most planes.  My RV-3 might do = OK, but=20 a fully loaded RV-6 won't.
 
Good = thought.  Full=20 credit for outside the box thinking :-)
 
Cheers,
Rusty
  
------=_NextPart_000_001A_01C56B52.A3EE2230--