Return-Path: <13brv3@bellsouth.net> Received: from [209.114.234.2] (HELO IPOfCard1.guest-tek.com) by logan.com (CommuniGate Pro SMTP 4.2b2) with ESMTP id 3163444 for flyrotary@lancaironline.net; Mon, 12 Apr 2004 20:02:49 -0400 Received: from USDCLES112NB160 ([198.18.1.149]) by IPOfCard1.guest-tek.com (8.11.6/8.11.6) with SMTP id i3CNoeu25260 for ; Mon, 12 Apr 2004 19:50:40 -0400 From: "Russell Duffy" <13brv3@bellsouth.net> To: "Rotary motors in aircraft" Subject: RE: [FlyRotary] Crank angle sensor Date: Mon, 12 Apr 2004 19:02:15 -0500 Message-ID: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000F_01C420C0.AB4EBBD0" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) Importance: Normal In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 This is a multi-part message in MIME format. ------=_NextPart_000_000F_01C420C0.AB4EBBD0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Does anybody know if there is any difference between the crank angle sensors on 13B turbo? I noticed some small differences in the label numbers. Bulent I was hoping someone had a more definitive answer, but I don't think there's a difference. If there was, Tracy would have to make sure which CAS you had, or you would have heard about people ending up with the wrong one and having problems. Cheers, Rusty (brrrrrr) ------=_NextPart_000_000F_01C420C0.AB4EBBD0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Does anybody know if there is any difference between = the crank=20 angle sensors
on 13B turbo? I noticed some small differences in the = label=20 numbers.
Bulent

 
I was = hoping someone had=20 a more definitive answer, but I don't think there's a = difference.   If=20 there was, Tracy would have to make sure which CAS you had, or you would = have=20 heard about people ending up with the wrong one and having = problems. =20
 
Cheers,
Rusty=20 (brrrrrr)





------=_NextPart_000_000F_01C420C0.AB4EBBD0--