Hybrid Motor Rocket Competition
2010-2011 Hybrid Motor High Powered Rocket Competition
Sponsored by the NASA Florida Space Grant Consortium, Florida Space Institute and the
North
The objective of the competition is to build and launch a hybrid powered rocket. There are two categories of competition to choose from. The first category consists of launching a hybrid rocket to the maximum altitude. The second category challenges the teams to fly their rocket closest to 2000 feet in altitude. There must be at least two teams competing in each category. If there is only one team, it will be asked to move to the other category.
1) The rocket can be built from scratch or from a kit.
2) The engine must be a hybrid motor rated “G” or from a lower class. The engine can be built from scratch or purchased from a company. NOTE: If the motor is built from scratch or is modified in anyway, a minimum of 2 documented motor tests must be done to demonstrate the safety, quality, and performance of the motor. Documentation must be performed and submitted before launch and must show thrust curves, impulse, burn-time, etc from the 2 tests (please confer with the judges prior to making any modifications to the motor).
3) Points will be awarded for the phases of the competition. The flight is worth 80% of the total points and the teams Engineering Notebook report is worth 20% of the total points. The points for each part are as follows:
a. Points for Flight
i. 100 pts for highest or closest to altitude
ii. 90 pts for 2nd highest or closest to altitude
iii. 80 pts or 3rd highest or closest to altitude
iv. 70 pts for 4th highest or closest to altitude
v. 0-10 pts for self built motor
vi. 0-5 pts for self built rocket
b. Points for Engineering Notebook
i. Rocksim or other software Simulations (30 pts)
ii. Engineering Data (70 pts)
The engineering notebook will be a bound notebook which will have all of the team’s engineering data, calculations, drawings and sketches, test results, notes, ideas, meeting notes, etc. This notebook will be returned to the teams on flight day. NOTE: The notebook is NOT a formal final report. We are looking for your project workbook.
This competition is open to any university or community college team in
Part I - Proposal
The faculty advisor of the university team must submit a 2 page proposal with a budget of up to $1000.00. The proposal will include the team name, project manager name and email address, the name of the project manager’s alternate and email address, the team members and their email addresses and status(e.g. sophomore, junior, senior etc), hometown, gender, race (needed for reporting to funding authority) and the category or categories the team plans to compete in.
All teams that submit a proposal will be able to take part in the competition and compete for the prizes. At least 6 teams (from both categories) will be selected and awarded up to $1000 to build the rocket (detailed budget must be provided in the proposal). For teams that design their own engines, static testing and data from two test launches is expected. The funds will be provided as a cost reimbursable grant to the faculty advisor. The funds can be used for supplies, motors, kits and travel. Salary and capital expenditure is not allowed. Indirect costs are not allowed.
Part II – Reports & Flight
Teams will then build and test their rockets for flight and submit their engineering notebook due approximately 2 weeks before the launch. Also, the program manager or their alternate representative from each team will be required to submit by email every 2 weeks a “progress and accomplishment report” of no more then 3/4 page text to the PBWiki page @ http://hybridrocket.pbworks.com/. Reports should include work done plus attachments including parts lists, photos, etc. NOTE: There are no points awarded for submitting the Progress Reports however, points will be deducted for non-submittal and late reports.
Also, each team will be required to submit to the PBWiki page @ http://hybridrocket.pbworks.com/ a Hazard Analysis and a Failure Modes & Effects Analysis by the time listed in the Timeline below. The Hazard Analysis should focus on the handling and use of the nitrous oxide and any pyrotechnic systems or materials. The Failure Modes & Effects Analysis should focus on what kinds of things could go wrong with your launch equipment and rocket, as well as, what you have done to mitigate or reduce the identified failure modes. These reports should be no more than 4 pages in length. They should be updated and resubmitted as your designs evolve. The reports are to show that you are ready to test and fly your rockets and motors safely. Failure to submit these reports may result in your being removed from the competition.
Teams will have their rockets and motors inspected for safety by a NEFAR representative just before launch. NEFAR will sponsor the launch in at the club site in Bunnell. Launch must take place before 2:00pm on the day of the launch. NOTE: we are not responsible for problems at the NEFAR launch site. Be there early. Don’t wait until it is too late to launch. To be awarded points for flight you must have a successful flight; i.e. Launch, deployment of recovery system, and controlled landing. All other flights will be judged on a case by case base. NOTE: rockets deemed unsafe will not be allowed to fly in the competition until fixed and approved.
Part III. - Prizes
The winning teams from each category will receive prize money according to the following chart.
Place | Maximum Altitude Category | Closest to 2000 ft. Category |
$500.00 | $750.00 | |
$300.00 | $450.00 | |
$100.00 | $200.00 |
Time line
Sept. 17th: Proposal with Budget, Deadline
Oct. 1rd: Announcement of winners and grant awarded to faculty advisor
Oct. 15th: First of the every two week report due.
Nov. 19th: Hazard Analysis, Failure Modes & Effects Analysis due.
Mar. 26th: Engineering Notebook due at Florida Space Grant Offices.
Apr. 9th: Launch (May 14th: alternate date)
Altitude Determination
Altimeters
A recording barometric altimeter must be used to record data for competition. While it is the duty of the Contest Director to provide the flier with the launch site specifications so the altimeter may be calibrated to the correct base altitude, it is up to flier to provide proof of a properly calibrated altimeter to the Contest Director upon request.
Altimeters with altitude sensors other than barometric sensors, such as accelerometers or magnetic apogee detection, may be used to deploy the recovery systems. However, they are prohibited from use in determining the actual altitude.
Determining Actual Altitude
The actual flight profile will be determined by the competition judges. The graph or other flight profile display provided by a recording device will be examined for accuracy. If it is shown that a sudden peak in altitude is attributable to the ejection charge, that peak will be not be used to determine the recorded altitude. The altitude just prior to or just after that sudden peak will be the official recorded altitude. The contestant may protest the judge’s altitude determination.
Launch Rails & Firing Electronics
Teams that provide their own launch rails/pads and firing electronics must have them inspected for safety by a NEFAR representative. NOTE: firing electronics must be at least 150 feet away from launch rails/pads. Firing electronics should incorporate at least one safety switch to prevent accidental ignition of rocket during setup. If you wish to use NEFAR launch equipment please contact Robert Eppig for our NEFAR representative contact information – to check if what you need is available.
Static Judging
For the teams that build their rocket and/or engine from scratch, their scores from the judges will reflect the originality and performance of the rocket and/or the engine
Motor Class Total Impulse
G or less: 160 Newton-seconds or less
Submit Proposal and Questions and Engineering Notebook to:
Robert Eppig 321-452-9834 ext 218 reppig@mail.ucf.edu
Mail Stop: FSGC
Center for Space Education
Bldg. M6-306, Room 7010
Kennedy Space Center, FL 32899
Competing Teams will receive a login to the PBWiki site by Oct 9, 2010