Skip to main content Skip to navigation
Washington State University Aerospace Club

Hybrid Propulsion Timeline

As Part of this year’s rocket design effort we have a great and motivated team working to accomplish some lofty goals. Among those are Solid and Hybrid Propulsion Teams which are working on creating and testing our own propulsion system. Our current plan is to implement the solid propulsion this coming year’s competition, while the Hybrid propulsion system is to be vetted for the following year’s rocket. This team has put together this timeline for the year with plans to test early next year. Here is the Timeline: Wish us luck!

Timeline:

Sept. 27-Oct. 3:

  • Read up on Hybrid Propulsion from the past teams (3-4 Weeks)
  • Prepare and give PowerPoint presentation (Monday)
  • Look into Funding (2-3 Weeks)

Oct. 4-10

  • Read up on Hybrid Propulsion from the past teams (3-4 Weeks)
  • Fuel/Oxidizer Selection (2-3 Weeks)
  • Look into Funding (2-3 Weeks)

Oct. 11-17

  • Read up on Hybrid Propulsion from the past teams (3-4 Weeks)
  • Fuel/Oxidizer Selection (2-3 Weeks)
  • Research fuel grain casting methods (2-3 Weeks)
  • Look into Funding (2-3 Weeks)

Oct. 18-24

  • Read up on Hybrid Propulsion from the past teams (3-4 Weeks)
  • Fuel/Oxidizer Selection (2-3 Weeks)
  • Research fuel grain casting methods (2-3 Weeks)
  • System diagram (3-4 Weeks)

Oct. 19-31

  • Research fuel grain casting methods (2-3 Weeks)
  • System diagram (3-4 Weeks)
  • Assess test stand needs (1-2 Weeks)
  • Research necessary gauges for data collection (2-3 Weeks)

Nov. 1-7

  • System diagram (3-4 Weeks)
  • Assess test stand needs (1-2 Weeks)
  • Research necessary gauges for data collection (2-3 Weeks)
  • Injector selection (1-2 Weeks)

Nov. 8-14

  • System diagram (3-4 Weeks)
  • Research necessary gauges for data collection (2-3 Weeks)
  • Injector selection (1-2 Weeks)
  • Solidworks 3D image of the entire motor and injector (1-2 Weeks)

Nov. 15-21

  • Solidworks 3D image of the entire motor and injector (1-2 Weeks)
  • Injector creation “scaled” (2-3 Weeks)
  • Modify test stand (2-3 Weeks)
  • Efficiency calculations (1-2 Weeks)

Nov. 22-28

  • Injector creation “scaled” (2-3 Weeks)
  • Modify test stand (2-3 Weeks)
  • Efficiency calculations (1-2 Weeks)
  • EES Modeling of motor (1-2 Weeks)

Nov. 29-Dec. 5

  • Injector creation “scaled” (2-3 Weeks)
  • Modify test stand (2-3 Weeks)
  • EES Modeling of motor (1-2 Weeks)
  • Fuel Grain casting “scaled” (1-2 Weeks)

Dec. 6-12

  • Fuel Grain casting “scaled” (1-2 Weeks)
  • Get approval to test fire “scaled” (1-2 Weeks)
  • Test injector water/air “scaled” (1-2 Weeks)
  • Data collection (1-2 Weeks)

Dec. 13-19

  • Get approval to test fire “scaled” (1-2 Weeks)
  • Test injector water/air “scaled” (1-2 Weeks)
  • Modifications to prototype “scaled” (1-2 Weeks)
  • Data collection (1-2 Weeks)

Jan. 10-16

  • Get approval to test oxidizer (1-2 Weeks)
  • Analyze Data (1-2 Weeks)
  • Modify test stand for oxidizer “scaled” (2-3 Weeks)
  • Miscellaneous

Jan. 17-23

  • Get approval to test oxidizer (1-2 Weeks)
  • Analyze Data (1-2 Weeks)
  • Modify test stand for oxidizer “scaled” (2-3 Weeks)
  • Miscellaneous

Jan. 24-30

  • Modify test stand for oxidizer “scaled” (2-3 Weeks)
  • Test fuel/oxidizer “scaled” (2-3 Weeks)
  • Make full-scale injector (2-3 Weeks)
  • Make full-scale motor casing (2-3 Weeks)

Jan. 31-Feb. 6

  • Test fuel/oxidizer “scaled” (2-3 Weeks)
  • Make full-scale injector (2-3 Weeks)
  • Make full-scale motor casing (2-3 Weeks)
  • Analyze Data for fuel/oxidizer test (1-2 Weeks)

Feb. 7-13

  • Test fuel/oxidizer “scaled” (2-3 Weeks)
  • Make full-scale injector (2-3 Weeks)
  • Make full-scale motor casing (2-3 Weeks)
  • Analyze Data for fuel/oxidizer test (1-2 Weeks)

Feb. 14-20

  • Analyze Data from test (1-2 Weeks)
  • Predict expected data for full-scale test (2-3)
  • Scale up entire design (3-4 Weeks)
  • Modify EES Calculations for full-scale (2-3 Weeks)

Feb. 21-27

  • Analyze Data from test (1-2 Weeks)
  • Predict expected data for full-scale test (2-3)
  • Scale up entire design (3-4 Weeks)
  • Modify EES Calculations for full-scale (2-3 Weeks)

Feb. 28- Mar. 5

  • Predict expected data for full-scale test (2-3)
  • Scale up entire design (3-4 Weeks)
  • Modify EES Calculations for full-scale (2-3 Weeks)
  • Modify Test Stand for full-scale (2-3 Weeks)

Mar. 6-12

  • Scale up entire design (3-4 Weeks)
  • Modify Test Stand for full-scale (2-3 Weeks)
  • Cast full-scale Motor (3-4 Weeks)
  • Get approval for full-scale test (2-3 Weeks)

Mar. 13-19

  • Modify Test Stand for full-scale (2-3 Weeks)
  • Cast full-scale Motor (3-4 Weeks)
  • Get approval for full-scale test (2-3 Weeks)
  • Last-minute modifications of full-scale design (2-3 Weeks)

Mar. 20-26

  • Cast full-scale Motor (3-4 Weeks)
  • Get approval for full-scale test (2-3 Weeks)
  • Last-minute modifications of full-scale design (2-3 Weeks)
  • Miscellaneous

Mar. 27- Apr. 2

  • Cast full-scale Motor (3-4 Weeks)
  • Last-minute modifications of full-scale design (2-3 Weeks)
  • Full-scale test of prototype (3-4 Weeks)
  • Solidworks version of prototype body (2-3 Weeks)

Apr. 3-9

  • Full-scale test of prototype (3-4 Weeks)
  • Analyze Data from test (2-3 Weeks)
  • Solidworks version of prototype body (2-3 Weeks)
  • Analyzing of internal piping (2-3 Weeks)

Apr. 10-16

  • Full-scale test of prototype (3-4 Weeks)
  • Analyze Data from test (2-3 Weeks)
  • Solidworks version of prototype body (2-3 Weeks)
  • Analyzing of internal piping (2-3 Weeks)

Apr. 17-23

  • Full-scale test of prototype (3-4 Weeks)
  • Analyze Data from test (2-3 Weeks)
  • Analyzing of internal piping (2-3 Weeks)
  • Modify prototype for 2nd test (1-2 Weeks)

Apr. 24-30

  • 2nd Full-scale test of prototype (2-3 Weeks)
  • Modify prototype for 2nd test (1-2 Weeks)
  • EES modeling of full-scale rocket (2-3 Weeks)
  • Presentation to Rocket group (2-3 Weeks)

May 1-7

  • 2nd Full-scale test of prototype (2-3 Weeks)
  • EES modeling of full-scale rocket (2-3 Weeks)
  • Presentation to Rocket group (2-3 Weeks)
  • Modify full-scale rocket (1-2 Weeks)

May 8-14

  • 2nd Full-scale test of prototype (2-3 Weeks)
  • EES modeling of full-scale rocket (2-3 Weeks)
  • Presentation to Rocket group (2-3 Weeks)
  • Modify full-scale rocket (1-2 Weeks)

Designing a rocket phase 1

We are starting this year with a great turnout for the first meeting 20+ people! For those of you wanting to get involved there are a few things to know.

First of all we are going to move team communication to a teamwork chatroom called slack. I recommend getting the desktop app and mobile app.

Follow the link and create an account

https://wsuaerospace.slack.com/

We are organizing ourselves into the following subteams:

Structures

This team will include but is not limited to Fuselage, Aerodynamics, Interfaces between parts.

Electronics

All things including wires and PCB’s primarily in assistance with the recovery system. Electronics will also likely need to interface with the hybrid propulsion

Recovery

With big plans to make our own ram air parachute, there is a lot of work to do as far as sewing of our own parachute, and the control system with plans to guide it back to the launch site

Payload

The conversation has been started with Pullman high school as we look to a high school senior to design and build a payload to go up in our rocket

Hybrid Propulsion

This is a continuation of ME483 taught last semester, the hybrid team from the class will lead up a team with the club to develop a hybrid propulsion system for our rocket.

Solid Propulsion

Lastly A team is going to be assembled for creation of a custom casted solid rocket motor. Safety being the top priority for both of these teams!

As members new and old select teams keep in mind that nobody is confined to a box by selecting a team, this is just for your primary interest.

Feel Free to email me if there are any issues getting onto slack

Kevin.cavender@wsu.edu

Next up:

We are going to be putting together a house of quality for our rocket the final will be posted on the site.