Upon conclusion of the first Alka-Rocket Challenge, the two lead members of our Alka team graduated. However the younger members of the team stepped up in a big way to continue thier legacy, and immediately got to work putting together a new Alka project team, coming up with design changes, and delivering new ideas. After 10 months of hard work we qualified for the final round of the competition, and again took 1st place.

Building off of our knowledge from last year, we knew that our rocket had to be as small and light as possible, while remaining strength and stability.

Having more time for project development, we were able to explore more options for our rocket materials. We moved away from 3D-printing the body tubes and instead laid up our own fiberglass ones on a custom mandrill we lathed out of steel. This allowed us to produce substantially stronger and lighter rockets. For the same reasons, we switched to fiberglass for the fins as well. ​

We would have liked to move away from 3D printing the nose cone and boat tail of our rocket as well, but were not able to because of their more complex shapes and our strict schedule. This is an improvement we hope to incorporate into our rocket next year.

Again, using our knowledge from the previous year to our advantage, we knew that it was most efficient for us to have a propulsion system that remained stationary on the ground rather than one that was carried with the rocket.

The most major design change to our launcher was barrel length. Through some gas expansion problem-solving and lots of trial and error, we were able to find the optimal barrel length for maximum acceleration. Additionally, we found that PVC inconsistencies and shrinkage in cold weather was negatively affecting our rocket's performance. Because of this, we switched to using a poly-carbonate barrel which eliminated shrinkage and reduced drag, resulting in a massive performance boost.​

Additionally, we used our increased budget of money and time to rebuild almost every component of our pressure chamber using higher quality materials and with more care than the previous year. This ensured that our system was both as safe and reliable as possible.

Because we wanted an easier and more solid method of communicating with our flight computer, we decided to use a Raven rather than our own Arduino-based computer. We also upgraded to batteries with much higher capacities. This meant an increase in weight, but we decided it was worth the trade off of being able to now affix every component of our avionics bay more permanently and without the worry of needing to disconnect the batteries to charge or swap them. Additionally, all components were connected in a much more solid, compact manner, making it substantially easier for us to insert and remove the avionics system as a whole from our rocket.

In Fall of 2017, industry giant Bayer put out word of a rocketry competition that they and the Big Ten were going to co-run. A few members of the University of Minnesota Rocket Team decided to form a new project team and devote their lives to winning this competition... and win we did. After uncountable sleepless nights and an unfathomable amount of Alka Seltzer tablets later, we set the Guinness World Record for the "highest launch of an effervescent tablet rocket" at 429 feet and carried home a $25,000 check from Bayer.

Link to a news article reporting the record here.

After several design iterations and simulations in OpenRocket, we settled on a design that was going to give us a good compromise of stability and drag. Because this is not your usual rocket, which typically carries its propellant, we were not able to simply scale down the design of one of our full-sized rockets from past competitions.​

Due to the characteristics of our Alka Seltzer fuel (high-impulse, but extremely short 'burn' time) we new that we wanted our rocket to be very light while having the strength to withstand the abrupt force of our pressurized gas. We considered several materials that fit these requirements including fiberglass, carbon fiber, acrylic, aluminum, and various plastics. Because of being the most versatile, low-cost, and the easiest to work with option, we decided on 3D-printing most of our components. This also allowed us to make design changes very rapidly, which was essential in designing the most efficient rocket possible in the small amount of time given.

When deciding how we wanted to utilize our fuel to power our rocket we had to main design options. One option would be to design a 'typical' rocket, which has an integrated fuel tank and carries its propellant, releasing its pressurized gas as it accelerates upward. The second option would be to leave the fuel tank on the ground, dumping all our our pressure at once and firing our rocket upward with a single, rapid, release of gas. We found that the second option was going to be superior to the first for our rocket, as a design this small simply could not fit an integrated fuel tank with anywhere near the thrust potential of a larger tank fixed to the ground.​

This method of propulsion was very unique in the field of rocketry, and forced us to think about much more in our design process than in your typical rocket; we now had to consider expansion speeds and capacities of our gas, maximum attainable pressure, aerodynamics of a projectile, and much more. This also gave us confidence, as our design was very much 'outside of the box' and we felt as though this would give us a leg up on the competition.

The flight computer is the brains of the rocket. It records our flight data which we use for post-flight analysis, allowing us to easily identify possible issues and make improvements to our rocket. Additionally, the flight computer is responsible for triggering our parachute recovery system.​

Since our rocket design was so compact, we decided to create our own custom flight computer using an Arduino Nano and several data-collecting components. Additionally, this would enable us to add any functionality we wanted, including features pulled from various commercially available units, giving us the exact performance we needed without any unnecessary components.