|
My hose info would be under cooling, if everyone sends there bits of knowledge the group can critic it & then it can be archived. This would give builders a good starting point The info from the more experienced rotary members would be of great value to them.
Georges B.
-------Original Message-------
Date: 05/22/05 16:14:14
Subject: [FlyRotary] Re: The Rotary Powered Flyers Association
Excellent start, David. You've got the ball rolling.
The only problem I can foresee is that we are few and scattered across the
country, continent and world. Many are still gainfully employed (i.e. not
retired), etc. My point is for someone to go from Texas to Washington state
to do an inspection as an example may be cost prohibited (money and time
wise).
I think we need to have "regional" teams and some "reasonable" conditions.
Like within 500 or 1000 miles or 2 hours or whatever. Otherwise, I'm
afraid the simple logistics could keep many folks from participating. All
teams should (in my opinion) operate from the same basic ground rules
(whatever they turn out to be), our "checklist" should be identical so that
in effect you get the same "service and benefit" from any team that may
visit.
My suggestion is to start working on a "Checklist". That could start here
on the list - not necessary for face to face for to get that ball rolling.
We even have some material such as the "Best Practices List" and the Weki?
thing (that I am not familiar with) that may well provide a starting point.
My point here is if we are to be successful we will need such a "checklist"
and if we are unable to develop one, I question how effective we are going
to be. It should at least have a subpart that a builder could start
consulting from day one - as John Slade mentioned, with no guidance while
constructing - people are going to be a bit resistive to having invested
time and money and then are told they need to rip it out and start over.
Help prevent the problem rather than help me fix it sort of approach. I
know we could never cover all avenues and should not try. I think we focus
on the rotary engine aspect particularly the critical subsystems such as: .
1. Fuel
2. Ignition
3. Controller
4. Electrical Wiring
5. Lubrication
6. Cooling
7. Motor Mount
8. Exhaust
9. Intake
etc.
In each case, we might start out with a brief description of the function of
the subsystem, principles of operation, possible gotchas, examples of good
(or bad) approaches.
Clearly it would be a live body of knowledge that would continue to be added
to and refined.
Just some thoughts on the topic
Ed
----- Original Message -----
Sent: Sunday, May 22, 2005 9:41 AM
Subject: [FlyRotary] The Rotary Powered Flyers Association
> Polling the list...
>
> Interest in forming such a group. Participation requirements will be left
> to be determined.
>
> Goals as previously stated:
> 1) Member Education and Safety
> 2) Pre-First Flight and Phase One Inspections and Support
> 3) Ongoing Peer Technical Support for rotary engined aircraft
> 4) Industry Liason (Insurance, Manufacturers, Kit Builders)
> 5) Accident Investigation / Rotary Engine Expertise
>
> This list serv can serve (with Marv's approval) as the means for
> distributing information regarding the group.
>
> It can incorporate separately, or as an independent EAA chapter, or as an
> adjunct to an existing EAA chapter. Incorporate or add on to a 501C3 so
> that expenses can be deducted by members.
>
> The Annual Business Meeting would be held in a public airshow venue, such
> as OSH, SNF, or Pickneyville.. prefereably someplace centrally located so
> ALL can attend with less than 2 days flying.
>
> Members would volunteer to be advocates for the rotary engine, provide
> peer safety inspections and technical counseling. Reimbursement for
> services/expenses can be considered and are to be determined later.
>
> We can better determine our direction and focus once an initial core group
> decides to start functioning. Once we know who/what our resources are,
> then we can better determine where to begin.
>
> David Staten
> League City (Houston), Texas
>
>
>
>
>
--
No virus found in this incoming message.
Checked by AVG Anti-Virus.
Version: 7.0.322 / Virus Database: 266.11.15 - Release Date: 5/22/2005
. |