X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Received: from imf22aec.mail.bellsouth.net ([205.152.59.70] verified) by logan.com (CommuniGate Pro SMTP 4.3.2) with ESMTP id 960432 for flyrotary@lancaironline.net; Mon, 23 May 2005 10:04:16 -0400 Received-SPF: pass receiver=logan.com; client-ip=205.152.59.70; envelope-from=sladerj@bellsouth.net Received: from ibm67aec.bellsouth.net ([65.2.89.207]) by imf22aec.mail.bellsouth.net (InterMail vM.5.01.06.11 201-253-122-130-111-20040605) with ESMTP id <20050523140331.HNQB2086.imf22aec.mail.bellsouth.net@ibm67aec.bellsouth.net> for ; Mon, 23 May 2005 10:03:31 -0400 Received: from JSLADE ([65.2.89.207]) by ibm67aec.bellsouth.net (InterMail vG.1.02.00.01 201-2136-104-101-20040929) with ESMTP id <20050523140331.DRSA8829.ibm67aec.bellsouth.net@JSLADE> for ; Mon, 23 May 2005 10:03:31 -0400 From: "John Slade" To: "Rotary motors in aircraft" Subject: RE: [FlyRotary] Re: Technical Advisor and official rotary association Date: Mon, 23 May 2005 10:03:26 -0400 Message-ID: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_01E3_01C55F7E.A9CB05E0" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 In-Reply-To: Importance: Normal This is a multi-part message in MIME format. ------=_NextPart_000_01E3_01C55F7E.A9CB05E0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit The thought of having a full fledged, tax exempt, card carrying organization that essentially tells the insurance company what's right and wrong just rubs me the wrong way. We are clearly too scattered to be effective .....Fuel and ignition systems have a lot in common. I think both Rusty and Jim have good points. What we need is an on-line, current and ever growing guide to what works and what doesn't. Most of the errors that can bring down a rotary aren't specific to the rotary engine - that's why we use it. It's hard to kill internally. The basic categories are: fuel, ignition, cooling, lubrication, procedures..... Being a virtual community, we can best do this using the internet. Personally, I don't have much faith in the wiki thing. Ideally, someone who's "been there and done that" like Ed or Tracy needs to compile the known information into an on-line book, and keep it up to date with the current consensus in each area. This would be a considerable effort which ought to be paid for (and would typically die out if it isn't). My 2c. John ------=_NextPart_000_01E3_01C55F7E.A9CB05E0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

The thought of = having a full=20 fledged, tax exempt, card carrying organization that essentially tells = the=20 insurance company what's right and wrong just rubs me the wrong=20 way. 
We are clearly too scattered to be effective = .....Fuel and=20 ignition systems have a lot in common.

I think both Rusty and Jim have good points. = What=20 we need is an on-line, current and ever growing guide to = what=20 works and what doesn't. Most of the errors that can bring down a rotary = aren't=20 specific to the rotary engine - that's why we use it. It's hard to kill=20 internally.  The basic categories are: fuel,=20 ignition, cooling, lubrication, procedures.....

Being a virtual community, we can best do this = using the=20 internet. Personally, I don't have much faith in the wiki thing. = Ideally,=20 someone who's "been there and done that" like Ed or Tracy needs to = compile the=20 known information into an on-line book, and keep it up to date with = the=20 current consensus in each area. This would = be a=20 considerable effort which ought to be paid for (and would typically die = out if=20 it isn't).

My 2c.

John

 

------=_NextPart_000_01E3_01C55F7E.A9CB05E0--