X-Virus-Scanned: clean according to Sophos on Logan.com
Return-Path: <msteitle@gmail.com>
Received: from mail-ew0-f167.google.com ([209.85.219.167] verified)
  by logan.com (CommuniGate Pro SMTP 5.2.13)
  with ESMTP id 3578928 for flyrotary@lancaironline.net; Mon, 13 Apr 2009 08:51:51 -0400
Received-SPF: pass
 receiver=logan.com; client-ip=209.85.219.167; envelope-from=msteitle@gmail.com
Received: by ewy11 with SMTP id 11so3047541ewy.19
        for <flyrotary@lancaironline.net>; Mon, 13 Apr 2009 05:51:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:mime-version:received:in-reply-to:references
         :date:message-id:subject:from:to:content-type;
        bh=7M/25cldgBzj8GLcf+yg/Fuh4c6PWV1fXroQoCmQfEc=;
        b=MWpWULKEAe7FzWlE5h96y9UM9bF6/mzDkX+OW6qDwNmBQbO31bmkdn5wsafI0qshQm
         YyzsPYCSsKotUfJS+ugxBya6OxfjK8euHxAw0m7PcmeqvXIYL8KC5zWbkHzrv1H3YDHf
         oLFbtEki8xcuSUEgcBow+8X65qq6FRF7lwBtQ=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=s1tq56ik3ZfCcD/vBhjb/k325kONh3cewIF8Al2db5VjWdmM3brosvjSIPGtGUSd2P
         vYMePw2uTgQLAS802YK3xyL54oIWx3fA434dtxtco6T5AMSikqGt+MERHmgo1yGX3QZ6
         57PWq31b0FEFD1pJeAXYW/1b9RhNCdNO5QNMI=
MIME-Version: 1.0
Received: by 10.210.137.14 with SMTP id k14mr5239078ebd.92.1239627073465; Mon, 
	13 Apr 2009 05:51:13 -0700 (PDT)
In-Reply-To: <list-3578668@logan.com>
References: <list-3578668@logan.com>
Date: Mon, 13 Apr 2009 07:51:13 -0500
Message-ID: <5cf132c0904130551p387fcd03ja4f8669877de4d1f@mail.gmail.com>
Subject: Re: [FlyRotary] Re: Gary Casey was [FlyRotary] Re: Rotary Engines
From: Mark Steitle <msteitle@gmail.com>
To: Rotary motors in aircraft <flyrotary@lancaironline.net>
Content-Type: multipart/alternative; boundary=0015174c11a65e2d1504676f2b3d

--0015174c11a65e2d1504676f2b3d
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Al,

After giving it some thought, I like your suggestion.  Otherwise, where do
you stop... "bug splats on prop resulting in reduction of airspeed..."
We're trying to get a handle on the big issues here.  Maybe it will get dow=
n
to the finer details at a later date.  I changed your criteria
slightly.  The criteria reads, "Engine related failures causing sufficient
loss of power rendering the aircraft unable to complete the flight as
planned."  This would include any engine system malfunction serious enough
to require an unplanned landing.  Engine systems include the engine and
gearbox, exhaust & intake (including throttle body/carb and air filter),
cooling system (including heat exchangers and all hoses and fittings),
charging/electrical system, ignition/efi system, oiling system, and
motormount.  It would not include items such as weather, airframe or contro=
l
surface issues, fuel starvation (due to dry tanks), pilot incapacitation,
bird strikes, etc.
So, I will edit my spreadsheet to include only the incidents which meet the
above criteria.  Future additions will be limited to this criteria as well.
I will add a column to designate which system(s) failure was the cause of
the incident.  Unless someone can approximate the hours at the time of thes=
e
failures, I will not include it.

Here's another suggestion, it would be great if someone could start a
tracking system where we can keep track of the total hours flown by all
rotary-powered a/c.  Any takers?

Mark
On Sun, Apr 12, 2009 at 10:22 PM, Al Gietzen <ALVentures@cox.net> wrote:

>
>
> Well, now you are getting into non-incidents.  That list is inexhaustible=
.
>
> Yes; I=92d suggest if we are going to do this at all; how about restricti=
ng
> to =93engine related failure causing sufficient loss of power rendering t=
he
> aircraft unable to maintain altitude.=94
>
>
>
> Al G
>

--0015174c11a65e2d1504676f2b3d
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div>Al,</div>
<div>=A0</div>
<div>After giving it some thought, I like your suggestion.=A0 Otherwise, wh=
ere do you stop... &quot;bug splats on prop resulting in=A0reduction of air=
speed...&quot;=A0 We&#39;re trying to get a handle on the big issues here.=
=A0 Maybe it will get down to the finer details at a later date.=A0 I chang=
ed your=A0criteria slightly.=A0=A0The criteria reads,=A0&quot;Engine relate=
d failures causing sufficient loss of power rendering the aircraft unable t=
o complete the flight as planned.&quot;=A0 This would include any engine sy=
stem malfunction serious enough to require an unplanned=A0landing.=A0 Engin=
e systems include the=A0engine and gearbox, exhaust &amp; intake (including=
 throttle body/carb and air filter), cooling system (including heat exchang=
ers and all hoses and fittings), charging/electrical system, ignition/efi s=
ystem, oiling system, and motormount. =A0It would not include items such as=
 weather, airframe or control surface issues, fuel starvation (due to dry t=
anks), pilot incapacitation, bird strikes,=A0etc.=A0 <br>
</div>
<div>So, I will edit=A0my spreadsheet to include only the incidents which m=
eet the above criteria.=A0 Future=A0additions will be limited to this crite=
ria as well.=A0 I will add a column to designate which system(s) failure wa=
s the cause of the incident.=A0 Unless=A0someone can approximate the hours =
at the time of these failures, I will not include it.</div>

<div>=A0</div>
<div>Here&#39;s=A0another suggestion, it would be great if someone could st=
art a tracking system where we can=A0keep track of=A0the total=A0hours flow=
n by all rotary-powered a/c.=A0 Any takers?</div>
<div>=A0</div>
<div>Mark<br></div>
<div class=3D"gmail_quote">On Sun, Apr 12, 2009 at 10:22 PM, Al Gietzen <sp=
an dir=3D"ltr">&lt;<a href=3D"mailto:ALVentures@cox.net">ALVentures@cox.net=
</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div lang=3D"EN-US" vlink=3D"blue" link=3D"blue">
<div>
<div class=3D"im">
<p style=3D"MARGIN-LEFT: 0.5in"><font face=3D"Times New Roman" size=3D"3"><=
span style=3D"FONT-SIZE: 12pt">=A0</span></font></p>
<p style=3D"MARGIN-BOTTOM: 12pt; MARGIN-LEFT: 0.5in; MARGIN-RIGHT: 0in"><fo=
nt face=3D"Times New Roman" size=3D"3"><span style=3D"FONT-SIZE: 12pt">Well=
, now you are getting into non-incidents.=A0 That list is inexhaustible.</s=
pan></font></p>
</div>
<div>
<div>
<p><font face=3D"Verdana" color=3D"blue" size=3D"2"><span style=3D"FONT-SIZ=
E: 11pt; COLOR: blue; FONT-FAMILY: Verdana">Yes; I=92d suggest if we are go=
ing to do this at all; how about restricting to =93engine related failure c=
ausing sufficient loss of power rendering the aircraft unable to maintain a=
ltitude.=94</span></font></p>

<p><font face=3D"Verdana" color=3D"blue" size=3D"2"><span style=3D"FONT-SIZ=
E: 11pt; COLOR: blue; FONT-FAMILY: Verdana">=A0</span></font></p>
<p><font face=3D"Verdana" color=3D"blue" size=3D"2"><span style=3D"FONT-SIZ=
E: 11pt; COLOR: blue; FONT-FAMILY: Verdana">Al G</span></font></p></div></d=
iv></div></div></blockquote></div><br>

--0015174c11a65e2d1504676f2b3d--