Return-Path: Sender: (Marvin Kaye) To: lml@lancaironline.net Date: Thu, 01 Jan 2004 17:33:53 -0500 Message-ID: X-Original-Return-Path: Received: from razorbill.mail.pas.earthlink.net ([207.217.121.248] verified) by logan.com (CommuniGate Pro SMTP 4.1.8) with ESMTP id 2913522 for lml@lancaironline.net; Thu, 01 Jan 2004 16:04:16 -0500 Received: from lsanca1-ar17-4-61-200-114.lsanca1.elnk.dsl.genuity.net ([4.61.200.114] helo=skipslater) by razorbill.mail.pas.earthlink.net with asmtp (Exim 3.33 #1) id 1Ac9zH-0000LS-00 for lml@lancaironline.net; Thu, 01 Jan 2004 13:04:12 -0800 X-Original-Message-ID: <002901c3d0aa$fd9dc9a0$6501a8c0@earthlink.net> Reply-To: "Skip Slater" From: "Skip Slater" X-Original-To: "Lancair Mailing List" References: Subject: Re: [LML] Legacy CO (carbon Monoxide) warning X-Original-Date: Thu, 1 Jan 2004 13:03:59 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-ELNK-Trace: cbee950bdf563876c8ad50643b1069f8239a348a220c2609c7a60c94bab68aad716f0dd3ddc3f4be350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c I have a panel mounted CO monitor in my ES which I bought from CO Guardian (http://www.coguardian.com/). Shortly after I began flying, it started going off alot, to the point that I suspected there was something wrong with it. I saw one of CO Guardian's reps at an AOPA Convention and he gave me a new unit, no questions asked. I swapped it out and returned the old one. The problem went away and I only got occasional warnings when slow with flaps down. Next came the paint and interior shops. Once I got the plane back in the air, the frequent CO warnings returned. I spoke at length with the same company rep at Oshkosh this past summer. He told me that the sensor in the units can become contaminated by certain chemicals, including many found in a paint shop. Again, he offered to give me a new unit and said he'd have the sensing element from the old one analyzed. When he got the results, they confirmed that some stray molecules from the paint shop (I don't recall what they were) had contaminated the sensor, leaving a much lower threshhold to set off the alarm. The new unit I have now works great and I rarely if ever have any alarms. There are multiple lessons here: First and foremost, take any CO alarm seriously, even if you suspect it's bogus. Next, if you have repeated alarms after thoroughly going over your plane and plugging up any suspected exhaust entry points, try another detector. In my case, I hooked up my new units while the old ones were still installed and confirmed that the older one was going off while the new one wasn't. Finally, be very careful what you expose your detector to. If you're doing any spraying with any chemicals near your plane, it's a good idea to remove your unit until you're finished. Skip Slater N540ES