Hey, everybody. Just seeing how the blogging function works and asking a little advice. I've been here for a little less than a year and am excited to engage a little more, now that it's summer and I have some time on my hands.
Part of my responsibilities at school is the management of our rocket propulsion lab (http://www.uscrpl.com). The RPL has about 25 undergraduate and graduate students involved, and we build (fairly) large group projects once or twice a year. Last year we did a carbon-cased O motor (that failed at BALLS... we're working on v2) and a two stage P to L 6" vehicle (flew successfully at the MTA in April), as a test for a later P to P attempt.
One of the things that has frustrated me the most about working with the RPL is that I'm one of the few who has lots of experience with rockets, thanks to my Tripoli involvement, and as such I'm one of the few who sees the bigger picture of the entire rocket -- making me one of the few who can, on launch day, process the vehicle and prepare it for flight. I don't like monopolizing the group's time this way, as launch day usually ends up as 23 people wondering if there's anything they can do, and me running around screaming.
I'm thinking, to remedy this situation, of having everyone build and launch a rocket in a smaller group -- perhaps 2-3 students -- so that they are forced to have hands-on experience through the entire process. My initial thoughts for the process are to cover the following points:
- Vehicle Design: including fin sizing and placement, aerodynamic stability requirements, securing the motor, integrating avionics and recovery;
- Motor Design: including hardware manufacture, physical and chemical design, thermal considerations, and determination of ballistic parameters;
- Assembly: including the build process (from scratch, likely just using standard HPR parts), programming and placement of avionics, motor hardware machining, propellant mixing and packing process, and recovery testing;
- Prep and Flight: including preparation of deployment systems, motor finishing and assembly, igniter construction, vehicle processing, rail integration, avionics arming, and launch
Does that about cover the process? It's a lot of stuff, but I'm thinking of using the entire semester for this project, and most people have expertise in one (or more) of the areas already outlined. The overall goal is to give everybody a view of the big picture of the project, and perhaps a little more insight into the design process, with the eventual aim of removing the big "last week rush" before launch day that we always seem to hit.
Of course, even working on my own I always have that big "last week rush", so maybe that's inevitable!
If you have any thoughts or comments on the program (aerospace professionals -- what else should I emphasize to make us students more valuable to you in the future?), please let me know in the comments section. We'll get started in late August.
You need to be a member of Our Planet to add comments!
Join this network