The question keeps coming up among enthusiasts about how fixed-geometry conventional bell-type rocket engines cannot adequately serve for ascent through the atmosphere. This “justifies” adding technologies such as bell extensions or free-expansion nozzle designs. This document addresses what can be done with a fixed-geometry expansion bell, if you carefully design it for that ascent purpose, and subject to the constraint that you can test the flight article at sea level, open-air nozzle conditions, for both cost-effectiveness, and for testing the actual flight article.
For this study, I
presumed liquid oxygen/liquid hydrogen (LOX-LH2) propellants, and a modest engine design technology
characterized as max chamber pressure (Pc) 2500 psia, with a pressure turndown ratio (P-TDR) of
2.5. Expansion bells are curved, with an “18-8” degree profile, for a constant nozzle kinetic energy efficiency
(ηKE) just over 98.7%. Throat
discharge coefficient was also constant at CD = 0.995. The engine cycle is modeled as “modest modern
technology” with a bleed dump fraction (BF) of 2%. All these variables were held exactly the
same, for the 3 designs explored
here, to investigate the effects of
expansion and thrust sizing effects.
I explored 3 designs:
(1) a conventional “sea level-optimized” design, (2) a typical conventional “vacuum optimized”
design, and (3) the practical compromise
design that I favor for best ascent performance. The sea level “optimization” requires that
the bell expansion be sized for max chamber pressure expanding down to standard
sea level pressure, and with throat and
exit dimensions (and total flow rate) sized so that sea level thrust at max Pc
is a required value.
There is really no such thing as a “vacuum-optimized”
expansion bell! Such would have an
infinite exit area expanding the flow to exactly zero exit plane pressure, which is utter nonsense. Vacuum engine bell designs are not optimized
in any way, they are merely constrained
by practical design constraints. The
word “optimized”, while routinely
used, is a complete misnomer for
such things.
The length and diameter of the bell has to fit practical
dimensional constraints so that the engine will fit within the available space
at the rear end of the stage, often even
more severely constrained than one might think,
if the engine must gimbal for thrust vectoring. For purposes of this study, I simply analyzed to a convenient “typical”
approximation: a nozzle area expansion
ratio of 100. These cannot be fired
open-air nozzle at sea level, even at
full throttle. Higher Pc lowers the
separation altitude, but does not
eliminate the sea level separation problem.
My preferred sizing approach defines a high part-throttle
setting at which the bell expands from the part-throttle Pc to an over-expanded exit
plane pressure Pe that corresponds to being on the verge of
backpressure-induced flow separation at sea level. This allows sea level open-air nozzle testing
of the full flight configuration at that part-throttle setting or higher, a considerable cost savings in development
testing! Such designs are over-expanded, and thus underperform the sea level designs at
sea level. But, they also offer considerably more expansion
ratio, and so perform nearly as well as
the so-called “vacuum optimized” designs,
out in vacuum. It’s a compromise
for ascent!
For such a compromise design to serve in ascent, I size its dimensions and flow rate to meet
the imposed thrust requirement at sea level.
(For “vacuum optimized” designs that can still be tested at sea
level, I size the dimensions and flow
rates to a thrust requirement imposed out in vacuum; that was not done for this study.)
The normal approach to “vacuum-optimized” designs results in
larger expansion ratios that simply cannot be tested at sea level open-air
nozzle at all! The only feasible way to
test them open-air at sea level, is to
fit them with shorter test bells that do not flow-separate. You cannot surface-test the full flight
article that way, but that is what is
often done, anyway.
Sea
Level Design
The sea level design is depicted in Figure 1. Expansion was from max Pc to Pe = sea level
standard pressure. Thrust was sized to a
500,000 lb (226.7 metric tons-force,
2223.7 KN) requirement imposed at sea level, full throttle conditions. I used my “compressible.xlsx” spreadsheet
tool for this effort, specifically the
“r noz alt” worksheet so that performance versus altitude could be
plotted, and ascent-averaged. Selected items from the spreadsheet were
copied to the figure, along with the two
plots the worksheet creates. These were
annotated as shown. Note how the sea
level design can be tested open-air nozzle at sea level, even at the minimum throttle setting. Thrust in vacuum is only a little higher than
sea level. Vacuum specific impulse (Isp)
is much higher than the sea level value,
but the ascent-averaged Isp is only a little lower than the vacuum
value.
Figure 1 – Standard Sea Level Design, As Is Often Used In First Stages for Ascent
Typical
of Standard “Vacuum-Optimized” Designs
This design is depicted in a very similar format in Figure
2. Expansion was sized from max Pc
to a Pe that produced A/A* = 100.
Dimensions and flow rates were sized from a thrust requirement imposed
in vacuum. This was the same 500,000 lb
(226.7 metric tons-force, 2223.7
KN). The vacuum performance is quite
good, as one would expect. This design cannot be used for ascent, or tested open-air nozzle at sea level, because it suffers backpressure-induced flow
separation at all throttle settings. The
nozzle is separated below about 20 kft at 100% Pc, separated below about 25 kft at 85% Pc, and separated below about 40 kft at the min
setting of 40% Pc. The as-sized
dimensions and flow rate are different from those of the sea level design, but not very much different at all! A common chamber power head could be used
with two different bells, by just
adjusting one thrust requirement a little bit.
That was not done here, though.
Figure 2 – Typical of Standard “Vacuum-Optimized”
Designs, Cannot Be Used for Ascent
Compromise
Design Intended For Ascent Use
This design is depicted in Figure 3, using a format very similar to the other two
designs. The expansion was sized for 85%
Pc down to a Pe = 3.63 psia that had just barely above standard sea level
pressure as its flow separation backpressure.
This is overexpanded, as much as
can be tolerated at that throttle setting,
without actually separating. That produces a bigger area expansion ratio
than a sea level design, while still
less than most “vacuum-optimized” designs.
Being intended for ascent use, I imposed the thrust requirement at sea
level, as the same 500,000 lb (226.7
metric tons-force, 2223.7 KN). Both this and the standard sea level design
meet this thrust requirement at sea level and 100% throttle. The compromise design thrusts better out in
vacuum than the sea level design, at
about 587,000 lb, versus only about
531,000 lb. The “vacuum-optimized”
design delivers 500,000 lb in vacuum,
exactly per its design.
The real story is in terms of Isp. The compromise design is overexpanded and has
lower Isp at sea level than the sea level design. However,
its vacuum performance is only a little bit less than that of the so-called
“vacuum-optimized “ design, which cannot
be used at sea level at all!
Further, its ascent-averaged Isp
is actually greater than that of the sea level design. The compromise design can be used for ascent
from sea level to vacuum, with better
ascent-averaged Isp than the sea level design, and nearly the vacuum Isp of the
“vacuum-optimized” design! And it does
this with the same high thrust/weight ratio,
and fewer potential failure modes,
as are inherent in all fixed geometry bell designs. Further,
it is testable at sea level in open-air nozzle mode, and in the full flight configuration, a real plus!
Figure 3 – Compromise Design Intended For Ascent Use
Summary
Comparison
The table shows a summary comparison of the 3 designs. All this was in the figures in more detail.
Discussion of Other Design
Alternatives
There are two design alternatives to the fixed-geometry
expansion bell: (1) the extendible bell
extension, and (2) the free-expansion
approach.
The extendible
bell extension is depicted in Figure 4, which I got from R. Gregory Clark’s
“Polymath” site “exoscentist.blogspot.com”.
Basically, the idea is to add the
bell extension hardware to a sea level design,
which converts it to a “vacuum-optimized” design geometry with the same
chamber power head. You would extend the
bell section somewhere above the altitude at which the vacuum geometry risks
flow separation, something subject to
some design optimization, of course. But,
that would always occur somewhere in the lower stratosphere, in any event,
as can be seen by the curves in Figure 2 above, which have a definite “knee” somewhere near
50 kft altitude.
Figure 4 – Depiction of the Extendible Bell Extension
Concept – From R G Clark’s “Polymath” Site
This approach will indeed increase the ascent-averaged
Isp, to something between the vacuum
design value and the sea level design value,
and likely much closer to the vacuum value, as we have already seen. But, besides
imposing geometric restrictions upon the shape and placement of the chamber
power head and plumbing items, adding
this kind of hardware is going to increase engine inert mass!
You will see this as a substantially-lower engine
thrust/weight ratio compared to simpler fixed-geometry designs. That will adversely-affect stage or vehicle
inert masses, and thus also mass ratio
and velocity-increment capabilities. You
will not see as much (if any) improvement over the compromise design, as otherwise only the ascent-averaged Isp
might suggest.
Further, adding
moving hardware with sealing issues adds a long list of potential failure
modes to the list of potential failure modes that any rocket engine
has. This is a safety/reliability
thing, something not so easily
quantified, but very real, nonetheless!
I have no numbers to show, but
I do have to ask the very pertinent question: why would you do this, unless you were absolutely forced into
taking the increased risks?
The free-expansion
nozzle design approach is something I have explored in other
articles on this site. It can take many
forms, but the best-known is the
aerospike nozzle approach. This can be a
coaxial or a 2-D linear design. The 2-D
linear design was intended to be implemented on the X-30 “Venture Star” design,
for one-stage low orbit access, that ultimately proved unsuccessful for a
variety of reasons. Most of those had to
do with losing strength by reducing inert weight too far.
These free-expansion designs all suffer from a common
problem: as the ambient atmospheric
pressure drops to low or zero values,
the streamlines of the propulsion stream diverge excessively and very
adversely, in terms of critically-low effective
kinetic energy efficiency. This
drastically reduces specific impulse (Isp) at high altitudes and on out into
vacuum, and it is inherent, being fundamental compressible flow physics! These things work better than
conventional nozzles from the surface out to the lower stratosphere, but from there on up, Isp performance falls very drastically out
into vacuum. They are absolutely
lousy as vacuum engines, and they inherently
always will be, despite the common false
perceptions to the contrary!
With the fixed-bell designs showing ascent-averaged Isp
closer to the vacuum value than the sea level value, it is to be reasonably expected that
aerospike ascent-averaged Isp will be closer to the utterly-lousy vacuum Isp
levels that these designs produce. Even
if not, the huge deficit the lousy
vacuum performance represents, will drag
the ascent-averaged Isp down catastrophically,
no matter how it is computed.
The earlier articles on this site that explore
free-expansion nozzle performance are listed below. Use the blog archive gadget on the left of this
page to find them very quickly. All
you need is the title and the date.
Click on the year, then the
month, then the title if more than one
article was posted that month.
Rocket Nozzle Types (bells and aerospikes) 4 February 2023
How Propulsion Nozzles Work
12
November 2018
Addendum
The “compressible.xlsx” spreadsheet was put together to
support a course I created in the basics of compressible flow applications. Rocket nozzles are but one application of
this. There are multiple worksheets in
that spreadsheet file, of which only three
relate to estimating rocket engine performance.
One (“prop comb”) is just a data library of supporting
ballistics data for several propellant combinations. Another one (“rocket noz”) does the basic
sizing calculations with sea level and vacuum estimates versus 3 engine power
settings, and is the same as the one that
is also provided for the “orbit basics+” course series. The third one (“r noz alt”) is the same as “rocket
noz”, but with an additional calculation
block of thrust and specific impulse vs altitudes from sea level to vacuum. This is for the 3 power settings, and it creates a couple of plots. There are no inputs, it is automatic.
Figure 5 depicts an image of the basic calculation block
that is in both “rocket noz” and “r noz alt”.
User inputs are highlighted yellow,
and significant results highlighted blue. There are two other inputs that you must deal
with, after putting the basics into the main
input block.
One of these is the design chamber pressure Pc value for
sizing the expansion ratio, and it is
not necessarily the max value. It works
with the exit plane expanded pressure Pe to size the nozzle expansion ratio
A/A*. If you are designing to a fixed
expansion, vary Pe iteratively to obtain
the desired value of A/A*. If instead
you are designing to an incipient nozzle separation situation at one of the
power settings, iteratively set Pe until
you get the desired separation backpressure Psep in that cell for that power
setting (this Psep is usually just barely above standard sea level
pressure).
The other is the appropriate thrust coefficient (sea level CF or out-in-vacuum CFvac) from the sized expansion, to use with the thrust requirement input for sizing dimensions and flow rates. This determines whether you size to that thrust level at sea level or in vacuum. The rest is automatic.
Figure 5 – Basic Calculation Block In Both “rocket noz” and “r
noz alt” Worksheets
The altitude calculation block that is only included in the “r
noz alt” worksheet is depicted in Figure 6. The first 3 columns show altitude in 1000’s
of feet (kft), the ambient pressure
ratio to standard sea level pressure,
and the ambient pressure Pa in psia.
Pa is set to zero at 300 kft (about 90 km) to represent vacuum. There’s a group of columns for each of the
input power settings, in which the
vacuum thrust is corrected to thrust-at-that-altitude with F = Fvac – Pa*Ae, and the Isp computed from F and the total
flow rate at that power setting. The
separation backpressure is also computed for that power setting.
The user is cautioned to look at the separation backpressure
levels and compare those to the ambient pressures at altitude. Wherever the ambient pressure exceeds the
separation backpressure, the bell will
separate at that altitude and power setting.
The plots are generated without regard to separation. There will be a critical altitude below which
separation occurs, if it occurs at
all. That “trigger altitude” will be
different for each power setting.
Each power setting’s specific impulse values are summed and
then divided by the number of entries in the table. This is an approximation-only to the true
ascent-averaged specific impulse at that power setting, but it is “in the ballpark”. Doing it this way ignores the fact that the
vehicle does not spend equal times at each altitude. This is partly made up for, by there being denser points at lower
altitudes.
Figure 6 – The Altitude Calculation Block Only In “r noz alt”
Supporting Plots vs Altitude
If you want a copy of this spreadsheet file, please contact me. There is no user manual for it, though.
This article is probably user manual-enough.
Update 3-5-2024 for -- Launch to Low Earth Orbit: Fixed-Geometry Options
In looking at what I posted,
I noticed an error and two lacks.
The error was
indicating a 2000 psia max Pc in the figures depicting the engines, when what I actually used was 2500 psia as
the max Pc. That has been
corrected in the versions of those figures included below.
The two lacks were (1) not including the sizes of the
engines in the figures, and (2) not
looking at even higher vacuum design exit area ratios A/A* than the 100 that
was in the article as originally posted.
Both lacks have
been fixed with this update. I
added A/A* = 150 and 200 as Figures 2B and 2C,
and to the comparison table.
Plus, I included bell exit
diameters and estimated lengths (throat to exit) in the comparison table, now included as Figure 4 in this update. I also further annotated that comparison
table.
Bear in mind that all of these designs share the same
modest-modern technology design characteristics: max Pc = 2500 psia, pressure turndown ratio in throttling is
2.5:1, for 40% min pressure = 1000 psia, a 2% dumped bleed fraction, an 18-8-degree curved bell profile, and a nozzle throat discharge efficiency of
99.5%. They are all “paper” oxygen-hydrogen
(LOX-LH2) engines. They do not
push the state-of-the-art very hard!
Figure 1 below is the same as Figure 1 in the original article above, except that I corrected the error reporting
max Pc, and I added bell length. This sea level design sizes its
expansion between 2500 psia Pc, and
14.696 psia Pe = Pa at sea level. The
dimensions and flow rates size for 500,000 lb of thrust delivered at sea
level. It is neither over-expanded nor
under-expanded. It is “perfectly
expanded”, as any real “sea level
design” actually is.
Figure 2 below is the same as Figure 2 in the
original article above, except that I
corrected the error reporting max Pc,
and I added bell length. This is
a “vacuum design” sized to an arbitrary A/A* = 100. The dimensions and flow rates size for an
imposed vacuum thrust requirement of 500,000 lb. Under- or over-expandedness at sea level is
irrelevant, since this design is
separated at sea level, at any throttle
setting. It cannot be used for ascent, except as an upper stage engine used only
essentially exoatmospherically.
Figure 2B below is the same as the corrected Figure 2
reported here in every way, excepting
only that the design A/A* = 150, instead
of Figure 2’s 100. Figure 2C below
is the exact same thing yet again,
except that the design expansion ratio is A/A* = 200. These were added to investigate the effects
of higher expansion ratio upon the performance and dimensions of vacuum
engines.
Figure 3 below is the same as Figure 3 in the
original article above, except that I
corrected the error reporting max Pc,
and I added bell length. This one
is my “compromise design”, in which I
trade an over-expanded loss of Isp performance right at sea level, for both higher vacuum Isp, and a higher ascent-averaged Isp, than a traditional sea level design. It is a slightly-larger engine, though.
Figure 4 below is the Table in the original article
above, enlarged, and annotated for the important overall design
considerations that impact vehicle design the most. The basic data in the original table are
unchanged, just rows added representing
the two vacuum designs with the larger expansion ratios. Columns have been added on the right with
values for A/A*, exit diameter De, and an estimate of bell length from throat to
exit plane. Annotations have been added as to what is most
important for designing realistic vehicles.
Figure 1 – The Baseline Sea Level Design, Perfectly-Expanded At Sea Level
Figure 2 – The Baseline Vacuum
Design, Unusable For Ascent, Sized At A/A* = 100
Figure 2B – A Vacuum Design,
Unusable For Ascent, Sized At
A/A* = 150
Figure 2C – A Vacuum Design,
Unusable For Ascent, Sized At
A/A* = 200
Figure 3 – The “Compromise” Design, Usable For Ascent, At a Better Ascent-Averaged Isp
Figure 4 – The Revised Comparison Table, Annotated For Important Overall Design
Considerations
The “compromise” engine is not quite as small as a true sea
level design, but it outperforms the sea
level design for ascents overall, and
this would apply whether single or 2-stage.
It is not as large as the three vacuum engines, although it is fairly close in size to the
A/A* = 100 design, and in its vacuum
performance.
It is much smaller than the A/A* = 150 and = 200
designs, and yet still does not fall all
that far short, in terms of vacuum
performance (under 5% shortfall). A
factor of 1.050 on the velocity ratio dV/Vex is only a factor of about 1.051 applied
between the corresponding mass ratios needed for vehicle or stage design.
The compromise design is like the other fixed-geometry
designs: it will have a very high engine
thrust/weight ratio T/We ~ 50-100. That
cannot be true of anything that is variable geometry!
Conclusions
#1. If you are doing a 2-stage launch vehicle design
(first stage expendable or reusable),
then use the “compromise design” approach to size your first stage
engines. They will outperform a
conventional perfectly-expanded sea level design! The downside is very limited throttle-down
capability at sea level.
Use a “vacuum design” at the largest dimensions you can
tolerate, for your expendable second
stage engines, since the stage point
will always be essentially exoatmospheric,
and very near to horizontal flight.
If your second stage is reusable, it is unclear whether you need a mix
of sea level and vacuum engines, or
you could just use engines designed with the “compromise design” approach. The deciding factor will be the minimum
thrust per engine to actually land.
Vacuum designs cannot be used for this, because they are always flow-separated near
sea level. The “compromise” approach may
be separated, if you have to throttle
below its expansion design point. Only
the true sea level designs will be unseparated at both sea level and min
throttle setting.
#2. If you are doing some sort of single-stage to
orbit design, use the “compromise
design” approach in preference to the traditional perfectly-expanded sea level
engine approach. This will get you a
higher ascent-averaged Isp than the traditional sea level designs can
achieve.
If this is to be a reusable design that lands vertically, the problem is at landing, when the weight is lowest. It is launch that sets the summed thrust of
all engines, with due allowance for an
engine or two nonfunctional. At
landing, you need to be able to shut
down enough of them so that the remaining engine or engines can be throttled
down enough to land, without suffering
separation.
What made the “compromise design” do better in ascent than a
sea level design, was sizing its
expansion in the vicinity of 85% of max Pc.
That is a very small throttle range for vertical landing. You may instead have to include some sea
level engines for landing, that can
throttle deeply.
The way to avoid this issue is to land horizontally, so that thrust at touchdown is not
needed, excepting perhaps a “go-around”
capability. The downside to this is far
higher stage inert fraction,
inherent because of the required lifting shape, whether winged, or as a lifting body. Exclusive of tankage and engine masses, about the min credible airframe mass fraction
will be near 10% or so. The engines and
the propellant tanks add directly to that!
#3. Why make this more difficult with heavier
variable-geometry engines, with a longer
list of failure modes? Why incur the low
vacuum performance of free-expansion designs?
Neither option makes any practical sense.
------
Just in case you do not understand why free-expansion
designs have lousy vacuum performance,
see Figure 5. The nozzle
kinetic energy efficiency reflects only the integrated average of the cosine
factors for exiting streamlines that are not aligned with the thrust axis. Such is measured after the last point of
contact, not before! Thrust
is measured just before the last point of contact, not after!
This applies only to the momentum term m*Ve of thrust. The as-expanded Pe*Ae term is usually smaller
by far, and does not get ratioed by the
kinetic energy efficiency.
The usual nozzle average of cosine factors is literally the
average of 1 on the centerline, and
whatever the outer-edge streamline cosine factor is. That simple arithmetic average may not reflect
the true integrated average. However, it is still somewhere in the ballpark! And because of Prandtl-Meyer expansion
effects at the outer edge of the exiting flow,
at high altitudes, that edge cosine
factor is very near-zero, or even
slightly negative! Thus the nozzle kinetic energy
efficiency is catastrophically low! Almost no matter how you figure it!
And THAT is exactly why free-expansion nozzle designs
of ANY kind, are truly LOUSY
vacuum engine designs! They work better
than conventional bells up to the lower stratosphere, but they inherently degrade very quickly into
uselessness, much above the lower
stratosphere.
I know that many perceive it differently, but you have been lied to, for marketing purposes, in a corporate welfare system. Look instead at the actual engineering numbers. And you will need to understand what
Prandtl-Meyer expansion is, in
compressible flow, to fully make sense
of this.
Figure 5 – Why Free-Expansion Nozzle Designs Always Have
Lousy Vacuum Performance
The recent blog post where I discussed the idea of an extendible nozzle in comparison to a staged combustion engine was spurred by the ESA wanting design ideas for staged combustion engines:
ReplyDeleteTHRUST! Initiative (Technologies for High-thrust Re-Usable Space Transportation).
https://t.co/J1MhjqX9us
(May need to do free registration to access the site.)
A staged-combustion engine such as the Space Shuttle main engine is a billion dollar development, taking several years development time. And SpaceX has been working on the staged-combustion Raptor since 2016 and still has not gotten it to operate reliably. It's said SpaceX has spent $5 to $10 billion on the Superheavy/Starship and commonly for a rocket using a new engine, the engine development costs are over half those of the entire rocket.
Instead, I intend to argue a mid-level pressure, mid-level performance hydrolox engine such as the RS-68 or Vulcain can accomplish the same thing and perhaps a bit more by giving it adaptive nozzles, aka altitude compensation.
It's a little hard to say your calculations show the adaptive nozzle equipped mid-level engine can't match the staged-combustion case because your examples are well beyond the mid-level engines in question. Both the RS-68 and the Vulcain are hydrolox exgines only at ~100 bar, 1500 psia, chamber pressure, while the engines you are considering are at 2,500 psia, over 66% higher chamber pressure.
While it might be possible to get engines at such high chamber pressure without staged-combustion they likely also would be billion dollar developments.
I would be interested to see what your conclusions would be for the case of only a 100 bar chamber pressure engine.
About your aerospike nozzle engine discussion, aerospikes or truncated plugs are always exponentially tapered, while yours are straight-conically shaped. Perhaps that can effect their efficiency?
Bob Clark
"Perhaps that can effect (should be "affect") their efficiency?" -- straight vs curved? Not substantially. I also rather doubt there is much difference between the performance of a nozzle and its sizing, given 1500 vs 2500 psia. There certainly was NOT with solid missile motors. Nearly all of those operated near 2000 psia, hot-soaked. Some higher. Few lower. - GW
DeleteHello, I mentioned TAN in a comment on previous post. These are the links to the original Aerojet technical papers. Quite interested for your thoughts on this. LH2+LOX SSTO with LOX+RP1 augmentation at low altitudes does seem like an elegant solution to the SSTO bell dilemma. I'm interested in how to do a simple spreadsheet model of this, but stuck at how to vary Isp and thrust for the base engine and augmentation with altitude. It seems a bit unlikely that sea level Isp would actually improve with augmentation (as claimed), but I am probably misunderstanding something. Regards, Mark Sinclair
ReplyDeletehttps://apps.dtic.mil/sti/pdfs/ADA454615.pdf
https://apps.dtic.mil/sti/tr/pdf/ADA454590.pdf
I will go retrieve those documents and take a look. Thanks. -- GW
DeleteI read the documents and searched for more recent things. The technology is quite intriguing, and was demonstrated feasible. But, it appears no development ever happened to make it a ready-to-use technology. -- GW
ReplyDelete