X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Received: from fed1rmmtao107.cox.net ([68.230.241.39] verified) by logan.com (CommuniGate Pro SMTP 5.2.0) with ESMTP id 2757643 for flyrotary@lancaironline.net; Mon, 25 Feb 2008 23:34:44 -0500 Received-SPF: none receiver=logan.com; client-ip=68.230.241.39; envelope-from=dale.r@cox.net Received: from fed1rmimpo02.cox.net ([70.169.32.72]) by fed1rmmtao107.cox.net (InterMail vM.7.08.02.01 201-2186-121-102-20070209) with ESMTP id <20080226043401.XBHN8249.fed1rmmtao107.cox.net@fed1rmimpo02.cox.net> for ; Mon, 25 Feb 2008 23:34:01 -0500 Received: from [192.168.1.104] ([72.223.44.12]) by fed1rmimpo02.cox.net with bizsmtp id u4a41Y00C0Flgvc0000000; Mon, 25 Feb 2008 23:34:04 -0500 Message-ID: <47C396B8.30707@cox.net> Date: Mon, 25 Feb 2008 21:34:00 -0700 From: Dale Rogers User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: Rotary motors in aircraft Subject: Re: [FlyRotary] Just shoot me...more info References: In-Reply-To: Content-Type: multipart/alternative; boundary="------------050801050603080108010503" This is a multi-part message in MIME format. --------------050801050603080108010503 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Chris, I can't help you directly, but here's a troubleshooting tip from a old Field Service Engineer: Don't add anything new until you've resolved the problems you already know about. If things go (even further) South, it makes it even harder to isolate the cause(s). Dale R. COZY MkIV Ch. 13 Christopher Barber wrote: > Oh, I forgot to mention when I went from A to B, the engine started to > die on B, but it did fire right back up when switched back to A. > > Thanks for the venting arena. I guess I should stop going to the > hangar and coming back to the computer with more "issues". > . > > All the best, > > Chris Barber > Houston --------------050801050603080108010503 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Chris,

I can't help you directly, but here's a troubleshooting tip from a old Field Service Engineer:

Don't add anything new until you've resolved the problems you already know about. If things go (even further) South, it makes it even harder to isolate the cause(s).

Dale R.
COZY MkIV
Ch. 13

Christopher Barber wrote:

Oh, I forgot to mention when I went from A to B, the engine started to die on B, but it did fire right back up when switched back to A.

Thanks for the venting arena. I guess I should stop going to the hangar and coming back to the computer with more "issues". <sigh><HEAVY sigh>.

All the best,

Chris Barber

Houston

--------------050801050603080108010503--