X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Received: from m12.lax.untd.com ([64.136.30.75] verified) by logan.com (CommuniGate Pro SMTP 4.3.4) with SMTP id 984013 for flyrotary@lancaironline.net; Fri, 03 Jun 2005 18:35:52 -0400 Received-SPF: pass receiver=logan.com; client-ip=64.136.30.75; envelope-from=alwick@juno.com Received: from m12.lax.untd.com (localhost [127.0.0.1]) by m12.lax.untd.com with SMTP id AABBLBY2RALLKK22 for (sender ); Fri, 3 Jun 2005 15:34:55 -0700 (PDT) X-UNTD-OriginStamp: L941HVjjYzDhN3itp//mkPWuSBLOmxwNd7nbCPvLP9CldsIFrpypCg== Received: (from alwick@juno.com) by m12.lax.untd.com (jqueuemail) id KULUJK8A; Fri, 03 Jun 2005 15:34:49 PDT To: flyrotary@lancaironline.net Date: Fri, 3 Jun 2005 15:26:42 -0700 Subject: Re: [FlyRotary] Re: Rotary risks Message-ID: <20050603.153423.1276.16.alwick@juno.com> X-Mailer: Juno 5.0.33 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary=--__JNP_000_6496.1ba0.38a4 X-Juno-Line-Breaks: 8-6,11,15-23,25,28-30,35-36,41-42,44-50,51-32767 From: al p wick X-ContentStamp: 18:9:2153883443 X-MAIL-INFO:301c1cacc5a10d8c9cec78ac5578e99dc159917848a9d8d9c5489159486548896901b5c91c71acf1ac68c515e92ccc158ca11901c8980931056c21bd113878fc212d1d8da5a500d14100b8319898c93848c9c848f188c1c1e83cede1059981755cadad28bca87c9c9511f825dd95c8c9c978dd618959714dd84d09 X-UNTD-Peer-Info: 127.0.0.1|localhost|m12.lax.untd.com|alwick@juno.com This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ----__JNP_000_6496.1ba0.38a4 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I agree Rusty. I believe it's most important to talk about the actions we can take to reduce the risks. That's my goal. There's lot's of simple things we can do. We know that if you make 20 changes to your engine, 4 of those changes represent most of the risk. So we just have to nail those 4. The other part is how easy to overlook the good stuff. I'm so impressed with Perry's approach. He undertook extremely risky project, but if you look at some of his techniques, it's inspiring. In fact I was inspired and copied his methods. -al wick Artificial intelligence in cockpit, Cozy IV powered by stock Subaru 2.5 N9032U 200+ hours on engine/airframe from Portland, Oregon Prop construct, Subaru install, Risk assessment, Glass panel design info: http://www.maddyhome.com/canardpages/pages/alwick/index.html On Fri, 3 Jun 2005 15:50:15 -0500 "Russell Duffy" <13brv3@bellsouth.net> writes: But it's so clear that the path most take is of extreme risk, I thought it best to post what I had so far. I thought "maybe one or two guys will read this and take more effective action at reducing risk". Hi Al, Do you intend to provide us with a complete analysis when you have it finished? If so, then I'd suggest that everyone just hold your questions until such time. If this isn't something you're planning to do, then I think very little will be accomplished by statements such as the one I quoted above. I think most everyone here will read a report with an open mind, however, like any suggestions or advice, each of us will make our own decision on the validity of the report. I also think we all probably have a good idea where the danger lies, and fortunately, it's in components we can control, rather than the internal engine itself. BTW, if you want to see why your ears have been burning the last few days , you can sift through the posts on the archive: http://lancaironline.net/lists/flyrotary/List.html Cheers, Rusty Mazda 13B rotary powered RV-3 (flying) Kolb Slingshot (Mazda single rotor project) Sonerai-IIL (Subaru...NOT) ----__JNP_000_6496.1ba0.38a4 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message
I agree Rusty. I believe it's most important to talk about the actions= we=20 can take to reduce the risks. That's my goal. There's lot's of simple = things we=20 can do. We know that if you make 20 changes to your engine, 4 of those = changes=20 represent most of the risk. So we just have to nail those 4.
The other part is how easy to overlook the good stuff. I'm so = impressed=20 with Perry's approach. He undertook extremely risky project, but if you = look at=20 some of his techniques, it's inspiring. In fact I was inspired and copied = his=20 methods.
 
 -al wick
Artificial intelligence in cockpit, Cozy IV powered = by=20 stock Subaru 2.5
N9032U 200+ hours on engine/airframe from Portland,=20 Oregon
Prop construct, Subaru install, Risk assessment, Glass panel = design=20 info:
http://www.maddyhome.com/canardpages/pages/alwick/index.html
 
On Fri, 3 Jun 2005 15:50:15 -0500 "Russell Duffy" <13brv3@bellsouth.net> writes:

But it's so clear that the path most take is of extreme= risk,=20 I thought it best to post what I had so far. I thought "maybe one or two = guys=20 will read this and take more effective action at reducing risk".

Hi=20 Al,
 
Do you = intend to=20 provide us with a complete analysis when you have it finished?  If = so,=20 then I'd suggest that everyone just hold your questions until such time.&= nbsp;=20 If this isn't something you're planning to do, then I think very little = will=20 be accomplished by statements such as the one I quoted above. =20
 
I think = most everyone=20 here will read a report with an open mind, however, like any suggestions = or=20 advice, each of us will make our own decision on the validity of the=20 report.  I also think we all probably have a good idea where = the=20 danger lies, and fortunately, it's in components we can control, rather = than=20 the internal engine itself. 
 
BTW, if = you want to=20 see why your ears have been burning the last few days <g>, you can = sift=20 through the posts on the archive:
http://= lancaironline.net/lists/flyrotary/List.html
 
Cheers,
Rusty
Mazda 13B rotary powered RV-3=20 (flying)
Kolb Slingshot (Mazda single rotor=20 project)
Sonerai-IIL=20 (Subaru...NOT)
 

----__JNP_000_6496.1ba0.38a4--