Professional Documents
Culture Documents
RS4-2006-4004
Sounding Rocket
Technology Demonstration
for Small Satellite
Launch Vehicle Project
John Tsohas, Lloyd J. Droppers,
Stephen D. Heister
Purdue University
West Lafayette, IN
HTPB
LOX
c*
GOX
=
=
=
=
=
INTRODUCTION
development program has been initiated at
Purdue University School of Aeronautics and
Astronautics to demonstrate technologies critical to
the development of a small satellite launch vehicle.
The first phase of the program involves the design,
manufacturing and flight of a sounding rocket
demonstrator at the NASA Wallops Flight Facility.
The sounding rocket will serve as a test-bed for flight
testing critical technologies including ground
support, propulsion, structures, separation, recovery,
telemetry, navigation, guidance and control
subsystems. Each of these technologies will be
demonstrated sequentially over a series of test flights.
This will be achieved by increasing the test-bed
subsystem complexity in each subsequent flight. Insequence flight testing will allow the designers to
validate and fine-tune each of the aforementioned
subsystems before adding more complexity, cost, risk
and features to the technology demonstrator. By not
having to fly all the vehicle subsystems on the
inaugural flight, it is believed that a step-by-step
flight validation approach will help control the design
process, while concurrently reducing development
cost and risk.
TECHNOLOGY DEMONSTRATOR
ROCKET OVERVIEW
Hybrid propulsion was chosen over liquid and solid
propulsion due to cost, complexity and reliability
constraints placed early in the design process. Hybrid
propulsion offers less complexity and higher
reliability than liquid propulsion. Compared to solid
propulsion, hybrid motors offer higher specific
impulse and are safer in operation due to their ability
to be shut down after ignition. Hydrogen peroxide
was chosen as the oxidizer due to its high density Isp
and its non-toxic, and non-cryogenic properties. This
leads to safer propellant handling procedures which
reduces operation costs compared to other oxidizers
such as liquid oxygen. The performance of hydrogen
peroxide outweighs the self-pressurization and
relative safety of nitrous oxide as an oxidizer. In
addition, Purdue University has the facilities as well
as extensive experience with the use of hydrogen
peroxide as a rocket oxidizer. HTPB is the fuel of
choice due to its relatively high performance and
regression rate, material properties and ease of
manufacturing in comparison with other candidate
hybrid fuels, as determined by thermo-chemical
analysis. Table 1 compares performance of various
hybrid oxidizer/fuel propellant combinations.
The technology demonstrator vehicle is designed to
reach an altitude of 25,000 ft, powered by a 250 lbf
thrust engine, for thrust duration of 8 seconds. For the
initial flights, the propellant feed system will operate
in blow-down mode. More specifically, 1/4 of the
oxidizer tank volume will be loaded with hydrogen
peroxide, while the remaining 3/4 will be pressurized
to a 600 psia MEOP with nitrogen. The pressure in
the tank will decay as the liquid oxidizer exits the
tank, thus leading to a gradual decrease in chamber
pressure and consequently thrust. Follow on flights
will include a pressurant tank and regulator in order
to provide a constant 600 psia MEOP ullage pressure.
The initial flights of the vehicle aim to verify the
performance of the propulsion, structure, and
recovery sub-systems, as well as ground support
equipment for remote loading and draining of
hydrogen peroxide oxidizer. The initial flights will
not make use of active guidance, but instead will use
fin stabilization. To maintain the stability margin, the
vehicle will launch at an initial thrust-to-weight ratio
of 4.5. Table A.1 in the appendix presents a detailed
mass breakdown of the demonstrator vehicle. An
overall vehicle schematic is presented if Fig. 1.
2 of 15
4th Responsive Space Conference 2006
5,800 lbs was required to buckle a 0.056 thick quasiisotropic carbon-fiber tube.
The oxidizer pressure vessel was designed with a
safety factor of 2.0 X MEOP and was analyzed using
hand calculations and ABAQUS finite element
analysis software. The tank is manufactured with
aluminum 6061-T6 body and aluminum 4043 weld
filler material. The vessel has been proof tested to 1.5
X MEOP, and additional vibration tests are
scheduled. A pressure relief valve set to 1.15 X
MEOP will ensure that there is no over-pressurization
of the pressure vessel. For added safety, a normally
open solenoid vent valve is installed, to be closed
during flight using lithium battery power. Fiber-glass
is used to manufacture the nose cone, and composite
honeycomb structure is used to make the guidance
fins. The hybrid rocket engine is manufactured from
aluminum 6061-T6, is designed with a factor of
safety of 2, and has been proof tested to 1.5 X
MEOP.
84.9
82.9
50.2
67.7
O/F
6.1
6.7
7.6
2.1
Ispsl
228.4
222.5
219.5
244.1
Ispvac
331.0
325.5
323.7
366.1
STRUCTURAL DESIGN
The airframe of the demonstration vehicle consists of
a 6 diameter carbon-fiber composite cylinder. The
aluminum oxidizer tank is designed to fit inside the
aero-structure, and is held in place by fiber-glass
mounts which are bolted to the airframe as shown in
Fig. 2. Stainless steel, tubing connects the
oxidizer tank to the hybrid rocket motor, which is
fastened to the aero-structure by three 7075-T651
aluminum brackets, as shown in Fig. 3. A finite
element analysis model of aluminum brackets is
shown in Fig. 4. An additional fiber-grass mount is
used to secure the hybrid motor in position. An
eigenvalue buckling analysis shows that a force of
3 of 15
4th Responsive Space Conference 2006
r = aGox n
(1)
4 of 15
4th Responsive Space Conference 2006
5 of 15
4th Responsive Space Conference 2006
Combustion Chamber
Top Cap
Consumable
Catalyst Bed
Aluminum
Motor Casing
HTPB Fuel
Grain
6 of 15
4th Responsive Space Conference 2006
RECOVERY SUB-SYSTEM
The incremental development of the technology
demonstration sounding rocket relies heavily on
multiple launch and successful recovery of the flight
hardware. This calls for the development of a very
robust and reliable parachute recovery sub-system.
Following a recovery system trade study, the final
design calls for a dual deployment system, with
drogue parachute deployment at apogee, and primary
parachute deployment at 1,200 ft altitude. System
redundancy is achieved by making use of two
completely independent recovery modules for
parachute ejection. Each module contains a lithiumion battery, an R-DAS flight computer and four
pyrotechnic ejection charges (2 per parachute). The
recovery sub-system will be tested on a separate
flight prior to being used on the demonstrator vehicle.
Fig. 11 shows a layout of the recovery sub-system.
7 of 15
4th Responsive Space Conference 2006
DESIGN PHILOSOPHY
The design drivers for launch vehicle development
depend on the needs and resources of the particular
organization. Profit is a typical design driver for
commercial space organizations, research and
development is a typical design driver for
government organizations, and defense and security
applications are for military organizations. These
design drivers are prevalent and visible in all aspects
of the rocket and launch infrastructure design, and the
same is true for a university organization.
The Design Philosophy of a university built launch
vehicle is mainly influenced by the needs, resources
and capabilities of the university organization, its
students and its faculty. The primary driver for a
university is to provide its student body with the
education, and this project will provide practical
engineering experience to design, build, test and fly a
launch vehicle into Earth orbit. Through this design
process, university students and faculty will obtain
the opportunity to conduct research, and to test
innovative design concepts in multiple sub-orbital
and orbital flights. These design drivers lead to the
necessity of orienting the program for multiple design
and flight test cycles, which will lead to increased
student exposure.
In addition to student education and exposure,
funding for the effort will most likely come from
corporate sponsors which are inclined to invest in a
program with clear, high visibility milestones, such
as those provided by test launches. Moreover, the
constraint of working with relatively small groups of
students inhibits the ability of a parallel, rather than
series style development program, due to a much
larger number of students required to complete a
parallel vehicle design effort. Due to these factors an
in-series vehicle development program is proposed.
Using this philosophy, the vehicle will be designed in
three separate stages, each capable of being
manufactured and tested individually. The 3rd stage of
a 3-stage vehicle will be designed, built and tested
first. Upon flight verification of the 3rd stage, the 2nd
stage of the launch vehicle will be built and
assembled. In the same fashion, following successful
flight verification of stage 2, the 1st stage will be
manufactured, assembled and flown. Serial
manufacturing, integration, testing and launch of
each stage individually will help work out the kinks
in the sub-systems without putting the fully
integrated launch vehicle at risk. Moreover, smaller
scale projects within the framework of a larger
program will allow students to participate in a project
8 of 15
4th Responsive Space Conference 2006
CODE DEVOLOPMENT
Computer code was developed to aid in the
conceptual design of a small satellite launch vehicle.
The basic scheme involves solving the ideal rocket
equation for a given mission V, assuming a
propellant mass fraction. The first part of the
simulation runs an engine internal ballistics code in
conjunction with a vehicle trajectory code to estimate
V losses due to gravity and drag, subsequently
updating the required mission V. The inert masses
are tabulated using both calculated and historical
mass estimates, from design handbooks and
experience from the demonstrator vehicle,
subsequently updating the assumed propellant mass
fraction. The vehicle simulation is iterated until it
converges on a design solution.
IDEAL ROCKET PERFORMANCE
The premise of this code is the ideal rocket equation
in the following form.
m
V = Isp * g ln f
mi
m
MR = f
mi
m prop
( MR 1)
= f prop * m pl *
1 MR * (1 f prop )
TRAJECTORY
The trajectory code calculates the vehicle trajectory
based on engine performance input from the internal
ballistic code and with estimates of vehicle mass and
geometry from the ideal rocket performance code. An
equations of motion force balance is performed
which calculates acceleration using a two
dimensional flat Earth model and on gravity, thrust
and drag models. Thrust is calculated using output
from the internal ballistics code, and the ambient
pressure at each altitude using the 1962 U.S.
Standard Atmosphere model. Drag is calculated using
INERT MASS
Using historical trends, an inert mass break down for
the two hybrid rocket stages is calculated and
compared to the allocated inert mass for each stage.
The inert mass code uses historical values based on
SPAD as well as development data from the
demonstrator vehicle (phase 1). The inert masses are
broken down into 5 sub-sections, including propellant
tank mass, ullage mass, pressurant mass, structural
mass, and extraneous mass such as valves, plumbing
and wiring. The propellant tank mass is calculated
using the pressure vessel performance-factor
approach, where the tank mass factor tank is taken
from historical values. The tank mass factor tank is
shown in Eq, 2, where Vtank is tank volume, and Pb is
burst pressure. The helium pressurant mass is
calculated based on isentropic expansion of the
pressurent into the oxidizer tank. Pressurant tank
mass is calculated in a manner similar to the
propellant tank mass. Based on historical data, 10%
of the inert mass was assumed for structural mounts,
airframe, bolts etc. In addition, valves and other
components were estimated as a further 10-15% of
the inert mass. Using the calculated inert mass, the
propellant mass fraction can be updated for further
iteration with the ideal rocket performance code.
9 of 15
4th Responsive Space Conference 2006
mtank =
pbVtank
tank g 0
(2)
11 of 15
4th Responsive Space Conference 2006
CONCLUSIONS
The design drivers for launch vehicle development
depend on the needs and resources of the particular
organization. The primary driver for a university is to
provide its student body with the education, and the
practical engineering experience to design, build, test
and fly a launch vehicle into low Earth orbit.
Through this design process, university students and
faculty will obtain the opportunity to conduct
research, and to test innovative design concepts in
multiple sub-orbital and orbital flights. A sounding
rocket demonstrator is being designed and tested at
Purdue, to serve as a test-bed for flight testing
technologies critical to the development of a small
satellite launch vehicle. The complexity of the subsystems launched will increase with each subsequent
flight. In-sequence testing will allow the designers to
validate and fine-tune the subsystems before adding
more features, cost and complexity to the
demonstrator vehicle. By not having to fly all the
vehicle subsystems on the inaugural flight, it is
believed that a step-by-step flight validation approach
will help control the design process, while
concurrently reducing development cost and risk.
The second phase of the program involves the design
of an orbital vehicle by making use of technologies
demonstrated during the first phase of the program. A
serial development approach will be implemented
whereby the third (final) stage of the vehicle will be
validated in flight before the second stage is built.
Consequently the 1st stage will be built after
successful flight validation of the third and second
stages. As mentioned earlier this incremental
approach will serve to control the design, cost and
risk associated with new launch vehicle development.
To reduce costs associated with structural design,
analysis and manufacturing, a three stage launch
vehicle with a low propellant mass fraction (77%)
would be designed and manufactured. Hybrid
propulsion would be used due to its relative
simplicity over liquid-bi-propellant systems. In
addition,
the
98%
H2O2/HTPB propellant
combination offers high density Isp as well as nontoxic and non-cryogenic properties which leads to
increased safety and a reduction in operation costs. A
small composite solid propellant third stage would
provide the final delta-V at the desired orbital altitude
of 93 miles. Finally, a three stage launch vehicle with
a GLOW of 6,275 lb powered by an 8,790 lbf thrust
first stage engine would satisfy the mission design
requirements.
ACKNOWLEDGEMENTS
The authors would like to thank the members of
the Purdue University Hybrid Sounding Rocket team,
especially Jeremy Corpening and Michael Grant, as
well as Scott Meyer for their help and support. We
would also like to acknowledge the sponsors to the
Hybrid Rocket project and thank them for their
support: ATK Thiokol, SpaceX, Aerojet, Purdue
School of Aeronautics and Astronautics, and Rocky
Mountain Wireline Service.
REFERENCES
1
4
Sutton, G., Biblarz, O., Rocket Propulsion Elements and
Design, 7th ed, John Wiley & Sons, New York, 2001, pp
64.
5
6
Humble, R., Henry, G., Larson, W., Space Propulsion
Analysis and Design, McGraw-Hill, New York, 1995, pg
372.
7
12 of 15
4th Responsive Space Conference 2006
APPENDIX
0.58
0.61
1.0
0.4
0.6
0.2
0.1
0.2
0.6
0.2
0.7
5.2
1.5
6.0
0.39
10.75
0.4
0.38
0.35
0.1
0.3
0.6
0.1
0.15
0.15
3.5
0.5
25.2
2.0
0.3
11.4
0.1
13.8
44.2
11.5
55.7
13 of 15
4th Responsive Space Conference 2006
Figure A.1. Thrust and chamber pressure measurements from flight-weight, 170 lbf thrust engine hot fire
tests.
14 of 15
4th Responsive Space Conference 2006
Altitude [ft]
x 10
2
1
0
20
40
60
80
Time [sec]
100
120
140
100
120
140
100
120
140
6000
4000
2000
0
20
40
60
80
Time [sec]
9500
9000
8500
20
40
60
80
Time [sec]
Figure A.3. Altitude, velocity and thrust versus time for small satellite vehicle 1st stage.
15 of 15
4th Responsive Space Conference 2006