Originally posted by wwattles
Regarding the RSO inspection, I couldn't imagine what it would be like to have the RSO take my painstakingly packed chute out of my rocket, unfurl it to check the harness, the connection points, the shrouds, the blanket/wadding/etc, and then say, "Okay, you're good. Go out to the pads." I'd look at him and say, "Not until you take 15 of YOUR minutes and repack this chute!" When I did my L1 and L2 flights, the RSO gave my rocket a VERY thorough check-over, but didn't pull it apart for inspecting the innards. He did, however, ask me very detailed questions about its construction. "What type of harness connection?" "How long a shock cord, and what type?" "How much noseweight and what kind?" "What size chute and what material?" "How many centering rings, what material, and what adhesive?" I would expect no less from a responsible RSO.
As for the ultimate responsibility, it lies with the rocketeer. Anyone who thinks otherwise hasn't looked at the NAR L2 exam recently. The RSO can only check the rocket, but the ultimate responsibility to ensure safe design and build is the rocketeer him/herself.
</Rant>
WW
Originally posted by jflis
Just to chime in (been reading with interest).
There are many good ideas here and some not so good. Also, I am sure many good ideas missing. It's all a part of the process.
One suggestion/request/recommendation: Do not *require* rocksim data.
It sounds like a good idea, but it isn't for many reasons.
- I've seen designs identified as *stable* in rocksim actually be unstable or marginally stable
- The tool is too limiting (I am NOT saying it isn't *good*. It is a fine tool. But it is still too limiting). You could not, for example, sim the ACME spitfire. Nor, for that matter the Decaffeinator, the Drake, the Stingray, the Night Whisper, The Deuce's Wild, the Tres, etc, etc, etc. Limiting. Yes, you can *approximate* many of these designs, but it is just and "approximation" from a tool that isn't perfect in the first place. Limiting.
- Not everyone has it, has access to it, nor should be required to buy it. There is no requirement for me to be a NAR member to fly rockets at a NAR event. Nor is it a requirement to own rocksim, nor is it a requirement to belong to a NAR section (where a copy may be found).
- Not needed. 45+ years of rocketry supports this.
Just a pet peeve. Rocksim is a great tool, don't get me wrong. But it should not ever be a requirement to enjoy rocketry.
jim
Everyone is asking for strict rules to make things safer but they dont understand their going ot bite off more than they can chew and in the end it will make going to a launch painstaking cause of al the crap you would have to go through just to launch a rocket
Originally posted by sandman
We need to help with suggestions...nobody is trying to make this hard...we just don't want to be lax in our inspections by RSO's and we're looking for ways the committee can improve the situation.
Perhaps a club needs more control over the process, but at this point the addition of more bureaucracy is not going to help.
Originally posted by sandman
That sounds like a contradiction.
What I see coming out of the committee is a set of guidelines for better control of the process.
I guess if you want to you could call that "bureaucracy"...I'd call it "guidlines".
Originally posted by cjl
and there should be a system where everyone can tell when and where a rocket is coming in hard.
Originally posted by LaneKG
I would like try having people who have a track on a rocket to point at the rocket with one hand Then if it is is incoming they can yell out and motion the affected party to move out of the way with their other hand. If you don't see it it is impossible to know what to do.
Anybody doing this?
Originally posted by teflonrocketry1
Jim,
If you were the RSO and were given simulation data that idicates a ballistic mode of recovery (e.g. no ejection charge) in a particular model (e.g. 8lb bowling ball loft) will put the flight on top of the RSO table with 90% accuracy, would you push the launch button?
Bruce S. Levison, NAR #69055
Enter your email address to join: