X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Sender: To: lml@lancaironline.net Date: Tue, 26 Jun 2007 20:39:53 -0400 Message-ID: X-Original-Return-Path: Received: from elasmtp-scoter.atl.sa.earthlink.net ([209.86.89.67] verified) by logan.com (CommuniGate Pro SMTP 5.1.10) with ESMTP id 2141747 for lml@lancaironline.net; Tue, 26 Jun 2007 15:46:41 -0400 Received-SPF: none receiver=logan.com; client-ip=209.86.89.67; envelope-from=rtitsworth@mindspring.com DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=gwQ923s3Z3rEYuET2NNldxvriDff4mXoPbSDwLqEAdgjNepx7jlaAY8EaLkgp+NW; h=Received:From:To:Subject:Date:Message-ID:MIME-Version:Content-Type:X-Mailer:X-MimeOLE:thread-index:In-Reply-To:X-ELNK-Trace:X-Originating-IP; Received: from [69.3.205.76] (helo=RDTVAIO) by elasmtp-scoter.atl.sa.earthlink.net with asmtp (Exim 4.34) id 1I3GzF-0006ct-3z for lml@lancaironline.net; Tue, 26 Jun 2007 15:46:05 -0400 From: "rtitsworth" X-Original-To: "'Lancair Mailing List'" Subject: Throttle/ Prop / Mix Cable Placement X-Original-Date: Tue, 26 Jun 2007 15:45:56 -0400 X-Original-Message-ID: <00c201c7b82a$9d611130$84affea9@RDTVAIO> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_00C3_01C7B809.164F7130" X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138 thread-index: Ace4HHqrfuB7cr1BTw2w4UvMXFD8/wAC9WUA In-Reply-To: X-ELNK-Trace: b17f11247b2ac8f0a79dc4b33984cbaa0a9da525759e2654b2e1a2b2fbd208d07c054943fc63644399f37241381ec17c350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 69.3.205.76 This is a multi-part message in MIME format. ------=_NextPart_000_00C3_01C7B809.164F7130 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit I'm (almost) ready to drill the firewall holes for the Throttle/Prop/Mixture cables on my ES (basically the same F/W as a IV). 1. I've considered the placement of other items on the firewall and the location of the major hoses near the firewall (fuel lines etc). 2. I'm also cognizant of keeping the cables away from the rudder pedal movement area on the inside. 3. Obviously sharp bends (and/or twists) are to be avoided. However, I'd like to be sure I'm not ignoring anything else important (I don't know what I don't know). I've looked through lots of pictures of other's planes which I have, and they all seem to be a little different. Is there any reason not to get the cables as close as possible to the correct placement/orientation before the firewall (and then relatively straight back to the panel)? This would seem to simplify the spaghetti behind the panel - perhaps at the expense of the spaghetti fwd of the firewall. It seems one disadvantage of this approach is that there isn't any service loop behind the panel without loosening the cables at the firewall grommets. Perhaps this is not important if the cables/controls are on their own sub-panel. Any other thoughts/insights/lessons learned??? Rick Titsworth ------=_NextPart_000_00C3_01C7B809.164F7130 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

I’m (almost) ready to drill = the firewall holes for the Throttle/Prop/Mixture cables on my ES (basically = the same F/W as a IV).

 

1. I’ve considered the = placement of other items on the firewall and the location of the major hoses near the firewall (fuel lines etc).

2. I’m also cognizant of = keeping the cables away from the rudder pedal movement area on the = inside.

3. Obviously sharp bends (and/or = twists) are to be avoided.

 

However, I’d like to be sure = I’m not ignoring anything else important (I don’t know what I = don’t know).  I’ve looked through lots of pictures of other’s planes which = I have, and they all seem to be a little different.  =

 

Is there any reason not to get the = cables as close as possible to the correct placement/orientation before the = firewall (and then relatively straight back to the panel)?  This would seem = to simplify the spaghetti behind the panel – perhaps at the expense = of the spaghetti fwd of the firewall.  It seems one disadvantage of this = approach is that there isn’t any service loop behind the panel without = loosening the cables at the firewall grommets.  Perhaps this is not important = if the cables/controls are on their own sub-panel.

 

Any other thoughts/insights/lessons learned???

 

Rick = Titsworth

 

 

------=_NextPart_000_00C3_01C7B809.164F7130--