X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Sender: To: lml@lancaironline.net Date: Tue, 29 Aug 2006 01:02:40 -0400 Message-ID: X-Original-Return-Path: Received: from vms042pub.verizon.net ([206.46.252.42] verified) by logan.com (CommuniGate Pro SMTP 5.1c.3) with ESMTP id 1353204 for lml@lancaironline.net; Mon, 28 Aug 2006 17:45:14 -0400 Received: from vms076.mailsrvcs.net ([192.168.1.1]) by vms042.mailsrvcs.net (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) with ESMTPA id <0J4Q008HX9QZV0E8@vms042.mailsrvcs.net> for lml@lancaironline.net; Mon, 28 Aug 2006 16:44:59 -0500 (CDT) Received: from 130.76.64.18 ([130.76.64.18]) by vms076.mailsrvcs.net (Verizon Webmail) with HTTP; Mon, 28 Aug 2006 16:44:58 -0500 (CDT) X-Original-Date: Mon, 28 Aug 2006 16:44:58 -0500 (CDT) From: Steve Rosenzweig Subject: Pitot-Statics X-Originating-IP: [130.76.64.18] X-Original-To: lml@lancaironline.net X-Original-Message-id: <8408216.950571156801499266.JavaMail.root@vms076.mailsrvcs.net> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7bit I was recently tracking down a pitot leak. Turns out I have some kind of valve or sensor (that has two wires connected to it) that is T'eed between the pitot and static systems. I've verified this happens to be where my leak is. But what the heck is it that would be plummed between pitot and static side? Anybody venture a guess. thanks Steve Rosenzweig Lancaster, CA N171DK