X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Received: from m12.lax.untd.com ([64.136.30.75] verified) by logan.com (CommuniGate Pro SMTP 4.3.4) with SMTP id 989507 for flyrotary@lancaironline.net; Wed, 08 Jun 2005 22:58:54 -0400 Received-SPF: pass receiver=logan.com; client-ip=64.136.30.75; envelope-from=alwick@juno.com Received: from m12.lax.untd.com (localhost [127.0.0.1]) by m12.lax.untd.com with SMTP id AABBLRNAGA3AU32J for (sender ); Wed, 8 Jun 2005 19:57:10 -0700 (PDT) X-UNTD-OriginStamp: L941HVjjYzDhN3itp//mkDJMNYUr9vMAFRsShQ9fu1ScxMypw0V2xg== Received: (from alwick@juno.com) by m12.lax.untd.com (jqueuemail) id KUZ7HLAL; Wed, 08 Jun 2005 19:56:38 PDT To: flyrotary@lancaironline.net Date: Wed, 8 Jun 2005 19:55:42 -0700 Subject: Re: [FlyRotary] Re: coolant leak Message-ID: <20050608.195627.3460.15.alwick@juno.com> X-Mailer: Juno 5.0.33 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary=--__JNP_000_62c7.5eb6.5fd7 X-Juno-Line-Breaks: 8-6,9-10,13-14,20-21,25-35,41-42,43-32767 From: al p wick X-ContentStamp: 38:19:875606448 X-MAIL-INFO:2c898909691c9c5dc5acec090dec6c7588c9b5ec38f5a9956938b5c9387d3868916d486189c809c10971694d6c3c254d5d1cd56d98d815e9b17945ed75dd79006505d5002d X-UNTD-Peer-Info: 127.0.0.1|localhost|m12.lax.untd.com|alwick@juno.com This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ----__JNP_000_62c7.5eb6.5fd7 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Thanks for all the info guys. I'm very ignorant here, it's going to take a while of lurking to understand all the stuff you guys are so familiar with. So clearly, Ed had some strong indications that he had a problem. You will soon know the direct cause of the problem, sounds like you guys know most of the details now. I've found after years of problem solving, there is great value to seeking the other causes. When you look into other causes and you ask " What about the way we go about....contributed to this?" then your solution can be far reaching. Your solution can reduce the risk of other items. Perhaps as we learn more details, there will be interest in this approach. BTW, I placed OAT sensor in my wheel pants. It works great for measuring oat AND warning me brakes are getting too hot. I did it because I read of plane that burned to ground from hot brakes. I didn't expect it to work, but the location I picked ended up being ideal. -al wick Artificial intelligence in cockpit, Cozy IV powered by stock Subaru 2.5 N9032U 200+ hours on engine/airframe from Portland, Oregon Prop construct, Subaru install, Risk assessment, Glass panel design info: http://www.maddyhome.com/canardpages/pages/alwick/index.html On Wed, 8 Jun 2005 16:48:31 -0400 "Tracy Crook" writes: There was a ton of warning signs of Ed's coolant sealing problems. A biggie was pressure in the system after the engine cooled completely down (like next day) The picture on my website (it's a boy!) shows the clue. There were other signs as well but it is human nature to hope that it was not the worst case possibility (Coolant O-ring problem). But don't jump to conclusions yet, we still don't know what it was. Tracy (BMW had bad crank sensor ----__JNP_000_62c7.5eb6.5fd7 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: quoted-printable

Thanks for all the info guys. I'm very ignorant here, it's going to = take a=20 while of lurking to understand all the stuff you guys are so familiar=20 with.

So clearly, Ed had some strong indications that he had a problem. You = will=20 soon know the direct cause of the problem, sounds like you guys know most = of the=20 details now.

I've found after years of problem solving, there is great value to = seeking=20 the other causes. When you look into other causes and you ask " What about = the=20 way we go about....contributed to this?" then your solution can be far = reaching.=20 Your solution can reduce the risk of other items. Perhaps as we learn = more=20 details, there will be interest in this approach.

BTW, I placed OAT sensor in my wheel pants. It works great for = measuring=20 oat AND warning me brakes are getting too hot. I did it because I read=20 of plane that burned to ground from hot brakes. I didn't expect it to = work,=20 but the location I picked ended up being ideal.

-al wick
Artificial intelligence in cockpit, Cozy IV powered by = stock=20 Subaru 2.5
N9032U 200+ hours on engine/airframe from Portland, OregonProp=20 construct, Subaru install, Risk assessment, Glass panel design=20 info:
http://www.maddyhome.com/canardpages/pages/alwick/index.html

On Wed, 8 Jun 2005 16:48:31 -0400 "Tracy Crook" <lors01@msn.com> writes:

There was a ton of warning signs of Ed's coolant sealing problems.&= nbsp;=20 A biggie was pressure in the system after the engine cooled completely = down=20 (like next day) The picture on my website (it's a boy!) shows the clue.&= nbsp;=20 There were other signs as well but it is human nature to hope that it was= not=20 the worst case possibility (Coolant O-ring problem). But don'= t=20 jump to conclusions yet, we still don't know what it was.

Tracy (BMW had bad crank sensor

----__JNP_000_62c7.5eb6.5fd7--