Return-Path: Received: from lanfear.nidlink.com ([216.18.128.7]) by truman.olsusa.com (Post.Office MTA v3.5.1 release 219 ID# 0-52269U2500L250S0V35) with ESMTP id com for ; Mon, 27 Dec 1999 15:20:34 -0500 Received: from enaila.nidlink.com (root@enaila.nidlink.com [216.18.128.8]) by lanfear.nidlink.com (8.9.0/8.9.0) with ESMTP id MAA08984 for ; Mon, 27 Dec 1999 12:25:23 -0800 (PST) Received: from regandesigns.com (tnt132-36.nidlink.com [216.18.132.36]) by enaila.nidlink.com (8.9.0/8.9.0) with ESMTP id MAA23733 for ; Mon, 27 Dec 1999 12:25:22 -0800 (PST) Message-ID: <3867CAB8.B194A7F8@regandesigns.com> Date: Mon, 27 Dec 1999 12:23:20 -0800 From: Brent Regan To: Lancair List Subject: Com Radio Antenna Diplexer X-Mailing-List: lancair.list@olsusa.com Mime-Version: 1.0 <<<<<<<<<<<<<<<<--->>>>>>>>>>>>>>>> << Lancair Builders' Mail List >> <<<<<<<<<<<<<<<<--->>>>>>>>>>>>>>>> >> I had a COM radio splitter BUT the performance was so-so. Before I fitted a second antenna (on the belly) it was not uncommon to fly off the squawk (out of range) of one controller before receiving my hand-off. I would have to pull the squawk knob and listen, what a pain. Even though my plane is well wired and shielded, pressing the PTT with altitude hold on caused the nose to drop. After I added the belly antenna, everything got better. Remember that a splitter "splits" the signal so you only get half the signal strength to each radio. This reduces the range by about 30%. This is fine if you fly where there are lots of VORs or use them mostly for localizer/glideslope and use GPS for NAV. I would not recommend using a splitter/switch on the COM as sometimes you need all the range you can get. Brent >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> LML website: http://www.olsusa.com/Users/Mkaye/maillist.html Builders' Bookstore: http://www.buildersbooks.com/lancair >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>