Return-Path: Sender: "Marvin Kaye" To: lml@lancaironline.net Date: Sat, 26 Mar 2005 11:41:41 -0500 Message-ID: X-Original-Return-Path: Received: from lakermmtao08.cox.net ([68.230.240.31] verified) by logan.com (CommuniGate Pro SMTP 4.3c3) with ESMTP id 822158 for lml@lancaironline.net; Sat, 26 Mar 2005 11:07:29 -0500 Received-SPF: none receiver=logan.com; client-ip=68.230.240.31; envelope-from=Walter@advancedpilot.com Received: from [10.0.1.3] (really [68.227.132.71]) by lakermmtao08.cox.net (InterMail vM.6.01.04.00 201-2131-118-20041027) with ESMTP id <20050326160634.CUWM18351.lakermmtao08.cox.net@[10.0.1.3]> for ; Sat, 26 Mar 2005 11:06:34 -0500 Mime-Version: 1.0 (Apple Message framework v619.2) In-Reply-To: References: Content-Type: multipart/alternative; boundary=Apple-Mail-6-402003771 X-Original-Message-Id: <3b23525c81223afcee3a833642bc79f7@advancedpilot.com> From: W Atkinson Subject: Re: [LML] Re: Superchargers X-Original-Date: Sat, 26 Mar 2005 10:06:29 -0600 X-Original-To: "Lancair Mailing List" X-Mailer: Apple Mail (2.619.2) --Apple-Mail-6-402003771 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=ISO-8859-1; format=flowed Rob: We are amassing a rather substantial volume of engine monitor=20 downloaded data of real events. When comparing these to KNOWN test=20 stand data, we can determine the actual change of events in the flight=20= data. We have one engine which was run under a considerable amount of=20= detonation with NO detrimental results. We have now seen several=20 events which were clearly pre-ignition; one which started out as=20 detonation with a progression into pre-ignition. You can see in the=20 data, when the plug failed and the vent became self-limiting. George did an exhaustive study of all of the NTSB cases where either=20 detonation or pre-ignition were listed as causal agents (the stack of=20 paper was four feet tall). The review of that data suggests that most=20= of the catastrophic events are, in fact, not detonation, but=20 pre-ignition. We have now had enough real-time and recorded experience with=20 detonation to be fairly comfortable with our understanding of what it=20 is and is not. It is as you described. It is not as detrimental as we=20= have always assumed. Engines can sustain hours of detonation without=20 harm and there are actually some TC'd engines which experience light=20 detonation routinely on takeoff. Pre-ignition, OTOH, is UGLY. It's=20= the bad actor of the pair. It can destroy your engine in 30 seconds. What we have come to believe is that detonation is basically not an=20 issue at all in NA, conforming engines being run on conforming fuel. Walter On Mar 26, 2005, at 9:26 AM, REHBINC@aol.com wrote: In a message dated 3/25/2005 10:49:10 PM Eastern Standard Time,=20 Walter@advancedpilot.com writes: Thank you for the thorough explanation of the event s as you understand them. **Both problems are commonly lumped together and low octane and high cylinder temps can result in either one. When preignition gets bad, it will destroy the engine faster than detonation. It also is harder to detect preignition before serious damage is done.** Both are commonly but incorrectly lumped together.=A0 They are two very different events.=A0 Walter =A0 I guess my atrocious english is rearing its ugly head again. You are=20 quite correct and that is how I should have worded my statement. Further, the data indicates that it is actually quite likely that damage from detonation as you have listed and is commonly sited is really a result of preignition.=A0 We have observed extended periods of detonation in which there is no damage whatsoever to the cylinder, rings, valves, etc.=A0 I realize that this is counter to the = conventional wisdom, but it is in harmony with the observed data. Do you have a source for the data you refer to? I would like to read up=20= on it. =A0 I was fortunate enough not to generate very much data of my own. Just=20 two broken pistons and=A0one broken ring. I scattered two engines, but=20= that was due to alternate forms of stupidity. =A0 Rob --Apple-Mail-6-402003771 Content-Transfer-Encoding: quoted-printable Content-Type: text/enriched; charset=ISO-8859-1 Rob: We are amassing a rather substantial volume of engine monitor downloaded data of real events. When comparing these to KNOWN test stand data, we can determine the actual change of events in the flight data. We have one engine which was run under a considerable amount of detonation with NO detrimental results. We have now seen several events which were clearly pre-ignition; one which started out as detonation with a progression into pre-ignition. You can see in the data, when the plug failed and the vent became self-limiting. George did an exhaustive study of all of the NTSB cases where either detonation or pre-ignition were listed as causal agents (the stack of paper was four feet tall). The review of that data suggests that most of the catastrophic events are, in fact, not detonation, but pre-ignition. We have now had enough real-time and recorded experience with detonation to be fairly comfortable with our understanding of what it is and is not. It is as you described. It is not as detrimental as we have always assumed. Engines can sustain hours of detonation without harm and there are actually some TC'd engines which experience light detonation routinely on takeoff. Pre-ignition, OTOH, is UGLY. It's the bad actor of the pair. It can destroy your engine in 30 seconds. What we have come to believe is that detonation is basically not an issue at all in NA, conforming engines being run on conforming fuel. Walter On Mar 26, 2005, at 9:26 AM, REHBINC@aol.com wrote: ArialIn a message dated 3/25/2005 10:49:10 PM Eastern Standard Time, Walter@advancedpilot.com writes: ArialThank you for the thorough explanation of the event s as you = understand Arial = them. Arial**Both problems are commonly lumped together and low octane and = high Arial cylinder temps can result in either one. When preignition gets bad, it = Arialwill destroy the engine faster than detonation. It also is harder to = Arialdetect preignition before serious damage is done.** ArialBoth are commonly but incorrectly lumped together.=A0 They are two = very Arial different = events.=A0 Arial = Walter = Arial=A0 ArialI guess my atrocious english is rearing its ugly head again. You are quite correct and that is how I should have worded my statement. ArialFurther, the data indicates that it is actually quite likely = that Arial damage from detonation as you have listed and is commonly sited is Arialreally a result of preignition.=A0 We have observed extended periods of = Arialdetonation in which there is no damage whatsoever to the = cylinder, Arial rings, valves, etc.=A0 I realize that this is counter to the = conventional Arial wisdom, but it is in harmony with the observed data. ArialDo you have a source for the data you refer to? I would like to read up on = it. = Arial=A0 ArialI was fortunate enough not to generate very much data of my own. Just two broken pistons and=A0one broken ring. I scattered two engines, but that was due to alternate forms of stupidity. = Arial=A0 = ArialRob --Apple-Mail-6-402003771--