X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Received: from exchange.carey.wa.edu.au ([118.82.44.212] verified) by logan.com (CommuniGate Pro SMTP 5.4c2o) with ESMTPS id 4884619 for flyrotary@lancaironline.net; Sun, 27 Feb 2011 21:56:57 -0500 Received-SPF: none receiver=logan.com; client-ip=118.82.44.212; envelope-from=stevei@carey.asn.au Received: from exchange.carey.local ([10.10.0.5]) by exchange.carey.local ([10.10.0.5]) with mapi; Mon, 28 Feb 2011 10:56:08 +0800 From: To: Date: Mon, 28 Feb 2011 10:56:16 +0800 Subject: Re: [FlyRotary] Re: EC2/ Tracy Thread-Topic: [FlyRotary] Re: EC2/ Tracy Thread-Index: AcvW8wvYl2vxBZxPQbSjSHkd9IiysA== Message-ID: <53382875-DEF0-462C-84FD-7E85120E56E3@carey.asn.au> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_53382875DEF0462C84FD7E85120E56E3careyasnau_" MIME-Version: 1.0 --_000_53382875DEF0462C84FD7E85120E56E3careyasnau_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable True, your right. Steve Izett On 28/02/2011, at 12:48 AM, Steven W. Boese wrote: The same thing can be accomplished without removing and exchanging the inje= ctors by using the injector backup procedure. Steve Boese From: Rotary motors in aircraft [mailto:flyrotary@lancaironline.net] On Beh= alf Of stevei@carey.asn.au Sent: Sunday, February 27, 2011 8:09 AM To: Rotary motors in aircraft Subject: [FlyRotary] Re: EC2/ Tracy Hi Brian You don't have a secondary injector failure do you? If your Pri and Sec injectors are the same, how about swapping them and run= on the secondaries under the staging point and see if she is smooth, thus = confirming the Secondaries are OK. Otherwise if you can run her up on the ground above the staging point and d= isconnect one sec and then the other, you'll be able to confirm the Sec's a= re OK. So if after disconnecting a secondary there is no change, that injector is = Duff. With the other one if she goes smooth, it would suggest the other Sec= is Duff. Just a thought. Steve Izett On 27/02/2011, at 7:28 AM, > > wrote: ________________________________ The contents of this email are confidential and intended only for the named= recipients of this e-mail. If you have received this e-mail in error, you = are hereby notified that any use, reproduction, disclosure or distribution = or the information contained in this e-mail is prohibited. Please notify th= e sender immediately and then delete/destroy the e-mail and any printed cop= ies. All liability for viruses is excluded to the fullest extent of the law= . --_000_53382875DEF0462C84FD7E85120E56E3careyasnau_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable True, your right.

Steve Izett
On 28/02/2011, at 12:48 AM, Steven W. Boese wrote:

The same thi= ng can be accomplished without removing and exchanging the injectors by usi= ng the injector backup procedure.
 <= /o:p>
Steve Boese<= o:p>
 
From:=  Rotary motors in airc= raft [mailto:flyrotary@lancaironline.net] On Behalf Of stevei@carey.asn.au
Sent: Sunday, Febr= uary 27, 2011 8:09 AM
To: Rotary motors = in aircraft
Subject: [FlyRotar= y] Re: EC2/ Tracy
 
Hi Brian
 
You don't have a secondary injector failure do you?
If your Pri and Sec injectors are the same, how about swapping them and run= on the secondaries under the staging point and see if she is smooth, thus = confirming the Secondaries are OK.
Otherwise if you can run her up on the ground above the staging point and d= isconnect one sec and then the other, you'll be able to confirm the Sec's a= re OK. 
So if after disconnecting a secondary there is no change, that injector is = Duff. With the other one if she goes smooth, it would suggest the other Sec= is Duff.
Just a thought.
 
Steve Izett
On 27/02/2011, at 7:28 AM, <bktrub@aol.com> <bktrub@aol.com> wrote:
 


The contents of this email a= re confidential and intended only for the named recipients of this e-mail. = If you have received this e-mail in error, you are hereby notified that any= use, reproduction, disclosure or distribution or the information contained in this e-mail is prohibited. Please notify t= he sender immediately and then delete/destroy the e-mail and any printed co= pies. All liability for viruses is excluded to the fullest extent of the la= w.
 --_000_53382875DEF0462C84FD7E85120E56E3careyasnau_--