Message

X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: <13brv3@bellsouth.net> Received: from imf18aec.mail.bellsouth.net ([205.152.59.66] verified) by logan.com (CommuniGate Pro SMTP 4.3.5) with ESMTP id 1020599 for flyrotary@lancaironline.net; Fri, 24 Jun 2005 15:26:23 -0400 Received-SPF: pass receiver=logan.com; client-ip=205.152.59.66; envelope-from=13brv3@bellsouth.net Received: from ibm61aec.bellsouth.net ([65.6.194.9]) by imf18aec.mail.bellsouth.net with ESMTP id <20050624192538.YDNW2372.imf18aec.mail.bellsouth.net@ibm61aec.bellsouth.net> for ; Fri, 24 Jun 2005 15:25:38 -0400 Received: from rd ([65.6.194.9]) by ibm61aec.bellsouth.net with ESMTP id <20050624192538.SFVN4468.ibm61aec.bellsouth.net@rd> for ; Fri, 24 Jun 2005 15:25:38 -0400 From: "Russell Duffy" <13brv3@bellsouth.net> To: "'Rotary motors in aircraft'" Subject: RE: [FlyRotary] Re: Engine Rebuild - Coolant Leak Cause Date: Fri, 24 Jun 2005 14:25:39 -0500 Message-ID: <000001c578f2$813d1590$6101a8c0@rd> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0001_01C578C8.98670D90" 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_01C578C8.98670D90 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I am certainly open to other hypothesis that explains the two hot spots across from one another. I agree it doesn't seem possible, but it sure looks like something was rubbing and then pushing/cocking the rotor over = at that point. My nephew took some photos when we disassembled the = engine, but I have not yet received them. I'll post them to the list once I do. =20 =20 It will be interesting to see the pics, not only of the housings, but = also the rotor. If there was that much wear to create a blued spot on the housing, you would expect there had to be a similar spot on the rotor, = at least on the side without the jammed object. I still don't see how that could be anywhere but at the thrust surface, or gear of the rotor = though. =20 =20 I did think of a way the corner piece could fit, and that would be if it happened to land in one of the large, milled balancing holes near the = corner of the rotor. It's still a hard theory to swallow. Certainly nothing = good could come from it though. =20 =20 Rusty (wondering if we should keep a loaner engine in the group) ------=_NextPart_000_0001_01C578C8.98670D90 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message

I am certainly open to other hypothesis that = explains the=20 two hot spots across from one another. I agree it doesn't = seem=20 possible, but it sure looks like something was rubbing and then = pushing/cocking=20 the rotor over at that point. My nephew took some = photos when=20 we disassembled the engine, but I have not yet received them. I'll = post=20 them to the list once I do.

It will be=20 interesting to see the pics, not only of the housings, but also the = rotor. If there was that much wear to create a blued = spot on the=20 housing, you would expect there had to be a similar spot on the rotor, = at least=20 on the side without the jammed object. I still don't see how = that=20 could be anywhere but at the thrust surface, or gear of the rotor = though. =20

I did=20 think of a way the corner piece could fit, and that would be if it = happened=20 to land in one of the large, milled balancing holes near the = corner of=20 the rotor. It's still a hard theory to swallow. Certainly = nothing=20 good could come from it though.

Rusty=20 (wondering if we should keep a loaner engine in the=20 group)

------=_NextPart_000_0001_01C578C8.98670D90--