X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Received: from fed1rmmtao101.cox.net ([68.230.241.45] verified) by logan.com (CommuniGate Pro SMTP 5.3.10) with ESMTP id 4599690 for flyrotary@lancaironline.net; Thu, 02 Dec 2010 09:17:29 -0500 Received-SPF: none receiver=logan.com; client-ip=68.230.241.45; envelope-from=alventures@cox.net Received: from fed1rmimpo03.cox.net ([70.169.32.75]) by fed1rmmtao101.cox.net (InterMail vM.8.01.03.00 201-2260-125-20100507) with ESMTP id <20101202141652.WJWA4818.fed1rmmtao101.cox.net@fed1rmimpo03.cox.net> for ; Thu, 2 Dec 2010 09:16:52 -0500 Received: from BigAl ([72.199.216.14]) by fed1rmimpo03.cox.net with bizsmtp id eEGh1f00B0KDB3c04EGshC; Thu, 02 Dec 2010 09:16:52 -0500 X-VR-Score: 0.00 X-Authority-Analysis: v=1.1 cv=nEJmMjsgzJU/SHHRi/ff9TR/+4hQZ6PdArDqWXwhaYs= c=1 sm=1 a=X3RON_n6e0IA:10 a=TPvrVRyicAsl4VeEYn0L5g==:17 a=kviXuzpPAAAA:8 a=Ia-xEzejAAAA:8 a=7g1VtSJxAAAA:8 a=cFOmIXYHerSLzLW-phcA:9 a=rCUkgRzIwVY1Wc-79l4A:7 a=6D0If2TnBPpW0pS6zO7M8EfwN2EA:4 a=CjuIK1q_8ugA:10 a=Qa1je4BO31QA:10 a=4vB-4DCPJfMA:10 a=EzXvWhQp4_cA:10 a=lnTb-I4C6uiwfQhHE7EA:9 a=YkIoC9_wYarJMVklqjcA:7 a=B_iL1Alxy6QWTb-SkDkypDnz5ZUA:4 a=TPvrVRyicAsl4VeEYn0L5g==:117 X-CM-Score: 0.00 Authentication-Results: cox.net; none From: "Al Gietzen" To: "'Rotary motors in aircraft'" Subject: RE: [FlyRotary] Re: Help - O2 sensor removal Date: Thu, 2 Dec 2010 06:16:37 -0800 Message-ID: <6CB65780D45746B3AE485D054F6DFCD6@BigAl> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000E_01CB91E8.80806750" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6863 Importance: Normal In-Reply-To: X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.5994 Thread-Index: AcuQ9f8DJ1QjC2AqTsad7CFl1zBQDgBNKm4g This is a multi-part message in MIME format. ------=_NextPart_000_000E_01CB91E8.80806750 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Subject: [FlyRotary] Re: Help - O2 sensor removal =20 Use anti- seize next time.=20 Brian Trubee Looking at the new Bosch O2 sensor, I find the threads amply covered = with an anti-seize compound; and recall the prior one was the same. So that's = been done. Haven't had a chance yet to have another go at removing it, but = I'm sure it will get done. Meanwhile the current one is still functional. Thanks, Al =20 -----Original Message----- From: Al Gietzen To: Rotary motors in aircraft Sent: Tue, Nov 30, 2010 2:39 pm Subject: [FlyRotary] Help - O2 sensor removal After about 130 hrs my O2 sensor seemed to be getting a little sluggish; = so I decided to replace it. I put a wrench on it and unable to budge it. A bigger wrench and still no luck - getting worried about cracking the = weld around the bung, or some other damage. Any ideas about getting that = thing loose? =20 I didn't put anything on the threads when I put it in - perhaps next = time; but what? =20 =20 -- Homepage: http://www.flyrotary.com/ Archive and UnSub: http://mail.lancaironline.net:81/lists/flyrotary/List.html =20 ------=_NextPart_000_000E_01CB91E8.80806750 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable

Subject: [FlyRotary] Re: Help - O2 sensor removal

 

Use anti- seize next time. 

Brian Trubee

Looking at the new Bosch O2 sensor, I find the threads amply covered with an = anti-seize compound; and recall the prior one was the same. So = that’s been done.  Haven’t had a chance yet to have another go at = removing it, but I’m sure it will get done. Meanwhile the current one is still functional.

Thanks,<= /font>

Al

 

-----Original Message-----
From: Al Gietzen <ALVentures@cox.net>
To: Rotary motors in aircraft <flyrotary@lancaironline.net>
Sent: Tue, Nov 30, = 2010 2:39 = pm
Subject: [FlyRotary] Help - O2 sensor removal

After about 130 hrs my O2 sensor seemed to be getting a little sluggish; so I = decided to replace it. I put a wrench on it and unable to budge it.  A = bigger wrench and still no luck – getting worried about cracking the weld = around the bung, or some other damage.  Any ideas about getting that thing = loose?

 <= /font>

I didn’t put anything on the threads when I put it in – = perhaps next time; but what?

 <= /font>

 <= /font>

 

------=_NextPart_000_000E_01CB91E8.80806750--