Message

X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: <13brv3@bellsouth.net> Received: from imf24aec.mail.bellsouth.net ([205.152.59.72] verified) by logan.com (CommuniGate Pro SMTP 4.3c5) with ESMTP id 934338 for flyrotary@lancaironline.net; Thu, 05 May 2005 23:21:27 -0400 Received-SPF: pass receiver=logan.com; client-ip=205.152.59.72; envelope-from=13brv3@bellsouth.net Received: from rd ([65.6.194.9]) by imf24aec.mail.bellsouth.net (InterMail vM.5.01.06.11 201-253-122-130-111-20040605) with ESMTP id <20050506032043.BREI2434.imf24aec.mail.bellsouth.net@rd> for ; Thu, 5 May 2005 23:20:43 -0400 From: "Russell Duffy" <13brv3@bellsouth.net> To: "'Rotary motors in aircraft'" Subject: RE: [FlyRotary] Re: EGT temps Date: Thu, 5 May 2005 22:20:52 -0500 Message-ID: <002c01c551ea$a1b3a7f0$6101a8c0@rd> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_002D_01C551C0.B8DD9FF0" 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_002D_01C551C0.B8DD9FF0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable So, could "timing being retarded/firing too late" cause "higher than = normal EGT"? Anyone else think there might be a timing problem if someone = reports "higher than other folks' EGT"? Not making a "dogmatic statement" this time, just asking for a sanity check or other operational anecdotes. =20 =20 Hi David, =20 Timing can certainly cause high EGT's, but I did the usual test with = mine on the ground, and thought it was the same as before. Basically, I ran = WOT, adjusted the timing via mode # (I can't remember). I found the highest = rpm to be a couple clicks above where I was already set, so I left it there. = I might consider advancing it some, but it's easy to tone down the temps = with the mixture. =20 =20 I believe the temp "limit" for 321 stainless is 1800, so I'll try to = stay under that... unless I need some impressive number to beat Ed with :-) =20 Rusty =20 ------=_NextPart_000_002D_01C551C0.B8DD9FF0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message

So, could "timing being retarded/firing = too late"=20 cause "higher than normal EGT"? Anyone else think there might be a = timing=20 problem if someone reports "higher than other folks' EGT"? Not = making a=20 "dogmatic statement" this time, just asking for a sanity check or other=20 operational anecdotes.

Hi=20 David,

Timing can=20 certainly cause high EGT's, but I did the usual test with mine on = the=20 ground, and thought it was the same as before. Basically, I = ran WOT,=20 adjusted the timing via mode # (I can't remember). I found the=20 highest rpm to be a couple clicks above where I was already set, so = I left=20 it there. I might consider advancing it some, but it's easy = to tone=20 down the temps with the mixture.

I believe the=20 temp "limit" for 321 stainless is 1800, so I'll try to stay under = that...=20 unless I need some impressive number to beat Ed with=20 :-)

Rusty

= ------=_NextPart_000_002D_01C551C0.B8DD9FF0--