Pick a motor
Shortlist the motors that fit your rocket, fly it on each one, and choose an ejection delay, all
with hpr on the command line.
This guide shortlists the motors that fit a rocket, flies it on each, and picks an ejection
delay, all with hpr on the command line. It’s for a flier choosing a motor for a design they
already have.
The steps:
- List the motors that fit.
- Fly the rocket on each.
- Compare them.
- Choose the delay.
- Put the choice in your design.
The examples use the guides’ own rocket,
level-1.ork,
with a 38 mm motor mount. Fly your .ork introduces it.
List the motors that fit
Start from the mount’s diameter: a motor’s case must match it. In OpenRocket, the motor mount
tube’s inner diameter is the size. A 38 mm mount takes 38 mm motors. hpr motors list filters
the 1,004 motors built into the simulator by diameter, impulse class or maker. Here, Loki’s 38 mm
H motors:
$ hpr motors list --diameter 38 --class H --manufacturer Loki
6 motors from ThrustCurve.org's solid motor catalog: every solid motor's record and every data file but a restricted one, captured 2026-10-28; size and delays from each motor's default file's header, the rest from its curve, or from ThrustCurve.org's record where no file of it is bundled.
designation maker class dia mm (in) len mm (in) impulse N·s avg N burn s delays
H100-SF Loki H 38 (1.50) 178 (7.0) 200.9 104.4 1.92 5-8-10-13-17
H90-LR Loki H 38 (1.50) 178 (7.0) 237.1 93.4 2.54 5-8-10-14
H144-LW Loki H 38 (1.50) 178 (7.0) 239.2 153.3 1.56 5-8-10-13-17
H125-CT Loki H 38 (1.50) 177.8 (7.0) 241.7 125.0 1.93 8-18
H160-LB Loki H 38 (1.50) 178 (7.0) 255.4 177.8 1.44 7-9-12-15
H500-LW Loki H 38 (1.50) 292 (11.5) 319.8 517.5 0.62 5-7-9-12-15
The figures are worked out from each motor’s default ThrustCurve.org curve file, the curve
the simulator flies (The bundled motors). The delays column
lists the ejection delays as the file’s header writes them, in seconds after burnout. A - separates
the settings: 5-9-13 is 5, 9 and 13 s, and 8-18 is 8 and 18 s. The header can list fewer delays
than the maker sells, so check the motor’s instructions. P (or 1000) is a plugged motor with no
ejection charge.
A Level 1 certification flight uses an H or I motor (NAR and Tripoli’s Level 1 rules; Check stability for a certification flight quotes them).
Every solid motor ThrustCurve.org listed on October 28, 2026 is built in, such as
--motor H128W, and the 924 with a curve file fly; the 80 with none are listed but can’t. Most
of the 924 (685) fly with a warning: their curve file’s total impulse, average thrust or burn time
is more than 1% off ThrustCurve.org’s own figures for the motor
(the whole catalog). Check such a motor against its maker’s
data. A name several makers use, such as G80, is refused with a name for each motor
(A name several makers share). A newer motor’s curve is fetched once online and kept
(Fetch a motor the simulator doesn’t have).
hpr motors search lists what vendors have in stock and at what price
(Motors you can buy). hpr motors show gives one motor’s figures as
the simulator reads its curve:
$ hpr motors show I175WS
I175WS (AeroTech), from the bundled catalog
impulse class I (320.01–640 N·s)
total impulse 333.2 N·s
average thrust 177.5 N measured; 175 N nominal, as the designation names it
peak thrust 252.6 N
burn time 1.88 s, from 0.023 s to 1.900 s (NFPA 1125, 5% of peak)
propellant WS, the maker's code for Super White Lightning, as ThrustCurve.org names it
propellant mass 168.0 g (5.9 oz) of 348.0 g (12.3 oz) loaded
casing 38 mm (1.50 in) across, 214 mm (8.4 in) long
delays 5 s, 9 s, 13 s
curve file https://www.thrustcurve.org/simfiles/5f4294d20002e900000008bf/ (flown)
RASP (.eng), from a certification test, public domain
passes the 1% check: total impulse +0.05%, average thrust +0.57%, burn time -0.66%
curve file https://www.thrustcurve.org/simfiles/5f9245ad1bca580004171795/
RockSim (.rse), from a user, public domain
passes the 1% check: total impulse +0.05%, average thrust +0.57%, burn time -0.66%
How far to trust it. Copied from ThrustCurve.org's curve file, downloaded 2026-10-28, not measured
by HPR Sim: the size, masses and delays from the file's header, the impulse, thrusts and burn time
from its curve, which can differ from the maker's rated figures. Each file is checked against
ThrustCurve.org's figures and OpenRocket's reading of its impulse and peak thrust, not against the
maker's data: checks of the file, not of the motor. The motor's printed data and its maker's
instructions come first, and the RSO decides.
More: https://hpr.fusionspace.co/pick-a-motor.html
Fly the rocket on each
--motor flies the design with another motor in its mount, and --delay sets that motor’s
ejection delay. Without --delay, the motor fires no charge. A parachute set to open on the
charge, as the guide rocket’s is, then never opens. Give one of the motor’s delays, in seconds, or
P for a plugged motor when your electronics fire the charges. This flies the guide rocket on a
Loki H125, with a 10 s delay:
$ hpr sim validation/fixtures/ork/guides/level-1.ork --motor H125-CT --delay 10
Level 1 guide rocket (level-1.ork)
configuration 1 of 2: [H170M-10] with --motor H125-CT --delay 10
help: --config flies the others, by number or name: 2 [I175WS-9]
a simulated flight, not a measurement
static margin 1.59 calibers off the rail; least 1.59 calibers, at 0.17 s, before apogee
CG and CP 0.818 m (32.2 in) and 0.923 m (36.3 in) aft of the nose tip, off the rail
apogee 914.5 m (3000 ft) above the site at 11.42 s
rail exit speed 25.9 m/s (85 ft/s)
delay apogee 9.42 s after burnout, with the charges held; the motor's set delay: 10 s; its charge fires 0.58 s after apogee; the delay may fire 2.0 s short or long (NFPA 1125): climbing at 14.1 m/s (46 ft/s) to 2.58 s after apogee (no speed: falling with nothing open, a fall HPR Sim doesn't predict)
descent 4.7 m/s (15 ft/s) at landing under `Parachute`
motor: 1 × H125-CT (from the bundled catalog, as of 2026-10-28) in `Motor mount tube`, lit at launch
recovery: `Parachute` at the ejection charge, 0.520 m² of drag area, opened at 12.00 s
launched at 0.00000° N, 0.00000° E, 0 m (0 ft) above sea level, from 1.5 m (4.9 ft) of vertical rail above its aft end, in calm air
note: the file's 1 recovery device flies as OpenRocket flies it. Each opens fully at its event, with the file's drag coefficient or OpenRocket's own. Once one opens, the rocket descends as a point under the open devices' drag alone
warning: drag: issue #18: skin friction is taken as fully turbulent; on a smooth surface a laminar run near the nose lowers it, by 3.6% on RocketPy's Calisto at Mach 0.3. If this surface is that smooth, the apogee, top speed and drift read low, and the flutter margin and largest dynamic pressure look better than they are
warning: stability: issue #172: the static margin read up to 0.1108 calibers above OpenRocket's on four private designs, cause unknown; this flight's may read high by as much
warning: stability: issue #1290: on one of two wind-tunnel models, the center of pressure sat 0.11 to 0.92 calibers aft of the tunnel's at Mach 0.6 and 0.8, as the report's curve reads; fitted over −3° to 4°, about 0.08 at 0.8. So from Mach 0.6 the flight margin may read high. This flight reaches Mach 0.64 at 1.6 s
help: issues: https://github.com/nrdptel/fusionspace-eridanus/issues/<number>
event time height speed
liftoff 0.02 s 0.4 m (1 ft) 0.0 m/s (0 ft/s)
rail exit 0.17 s 1.9 m (6 ft) 25.9 m/s (85 ft/s)
burnout 2.00 s 303.8 m (997 ft) 201.2 m/s (660 ft/s)
apogee 11.42 s 914.5 m (3000 ft) 0.1 m/s (0 ft/s)
charge 12.00 s 912.8 m (2995 ft) 5.6 m/s (18 ft/s)
deployment 12.00 s 912.8 m (2995 ft) 5.6 m/s (18 ft/s), airspeed 5.6 m/s (18 ft/s)
ground hit 202.71 s 0.0 m (0 ft) 4.7 m/s (15 ft/s)
(heights are the center of gravity's above the site; speeds are over the ground, and a deployment's
airspeed through the air)
top speed 217.0 m/s (712 ft/s) at 1.56 s
top Mach number 0.639
landing 0.7 m (2 ft) from the pad at 202.71 s, at 4.7 m/s (15 ft/s)
How far to trust it. Simulated from the design file, not measured. Against 60 logged flights of
fliers' own designs, the simulated apogee averaged 8.0% above the logged one. HPR Sim flew each in
its day's air from ERA5, a weather reanalysis, and each logged apogee is the height climbed in it.
The simulated apogee was within 10% on 31 and read low on 15, by at most 20%. This flight was flown
in the standard atmosphere. On a day warmer than it at the site, the rocket can climb higher than
this apogee; --weather flies the day's air. Plan a waiver or a field's ceiling with room above this
apogee; the altimeter's reading is the one to log, and the RSO decides.
More: https://hpr.fusionspace.co/accuracy.html
And on a harder-hitting I motor, a Loki I377, with the same delay:
$ hpr sim validation/fixtures/ork/guides/level-1.ork --motor I377-CT --delay 10
Level 1 guide rocket (level-1.ork)
configuration 1 of 2: [H170M-10] with --motor I377-CT --delay 10
help: --config flies the others, by number or name: 2 [I175WS-9]
a simulated flight, not a measurement
static margin 1.18 calibers off the rail; least 1.18 calibers, at 0.08 s, before apogee
CG and CP 0.845 m (33.3 in) and 0.923 m (36.3 in) aft of the nose tip, off the rail
apogee 1320.4 m (4332 ft) above the site at 12.02 s
rail exit speed 42.3 m/s (139 ft/s)
delay apogee 11.02 s after burnout, with the charges held; the motor's set delay: 10 s; its charge fires 1.02 s before apogee; the delay may fire 2.0 s short or long (NFPA 1125): climbing at 30.8 m/s (101 ft/s) to falling at 9.5 m/s (31 ft/s)
descent 5.0 m/s (16 ft/s) at landing under `Parachute`
motor: 1 × I377-CT (from the bundled catalog, as of 2026-10-28) in `Motor mount tube`, lit at launch
recovery: `Parachute` at the ejection charge, 0.520 m² of drag area, opened at 11.43 s
launched at 0.00000° N, 0.00000° E, 0 m (0 ft) above sea level, from 1.5 m (4.9 ft) of vertical rail above its aft end, in calm air
note: the file's 1 recovery device flies as OpenRocket flies it. Each opens fully at its event, with the file's drag coefficient or OpenRocket's own. Once one opens, the rocket descends as a point under the open devices' drag alone
warning: design checks: the motor in `Motor mount tube` reaches 22.0 mm past the mount's forward end (configuration [H170M-10] with --motor I377-CT --delay 10). The mass, CG and margin are for the motor as drawn: where a ring or bulkhead closes the mount there, the real case sits that much further aft. At ignition the static margin is 1.12 calibers as drawn, and 0.94 with the case 22.0 mm further aft
warning: drag: issue #67: a cone-like nose's or shoulder's pressure drag reads high from Mach 0.8 (about twice a measured cone's at Mach 0.85, still +15% at 1.5). So the apogee, top speed and drift read low, and the flutter margin and largest dynamic pressure look better than they are. This flight reaches Mach 1.10 at 1.1 s
warning: drag: issue #68: base drag reads high from Mach 0.8 to 1.2 (0.225 against a measured 0.156 at Mach 0.9). So the apogee, top speed and drift read low, and the flutter margin and largest dynamic pressure look better than they are. This flight reaches Mach 1.10 at 1.1 s
warning: drag: issue #222: supersonic pressure drag on an ogive nose or airfoil fins is about twice OpenRocket's, and which is right is unresolved. If HPR Sim's drag is high, the apogee, top speed and drift read low, and the flutter margin and largest dynamic pressure look better than they are. This flight reaches Mach 1.10 at 1.1 s
warning: drag: issue #18: skin friction is taken as fully turbulent; on a smooth surface a laminar run near the nose lowers it, by 3.6% on RocketPy's Calisto at Mach 0.3. If this surface is that smooth, the apogee, top speed and drift read low, and the flutter margin and largest dynamic pressure look better than they are
warning: stability: issue #172: the static margin read up to 0.1108 calibers above OpenRocket's on four private designs, cause unknown; this flight's may read high by as much
warning: stability: issue #1290: on one of two wind-tunnel models, the center of pressure sat 0.11 to 0.92 calibers aft of the tunnel's at Mach 0.6 and 0.8, as the report's curve reads; fitted over −3° to 4°, about 0.08 at 0.8. So from Mach 0.6 the flight margin may read high. This flight reaches Mach 1.10 at 1.1 s
warning: stability: issue #1198: the center of pressure sat 0.67 to 1.35 calibers aft of a wind tunnel's on two models at Mach 0.9, so past Mach 0.8 the flight margin may read high. This flight reaches Mach 1.10 at 1.1 s
help: issues: https://github.com/nrdptel/fusionspace-eridanus/issues/<number>
event time height speed
liftoff 0.00 s 0.3 m (1 ft) 0.0 m/s (0 ft/s)
rail exit 0.08 s 1.8 m (6 ft) 42.3 m/s (139 ft/s)
burnout 1.43 s 384.0 m (1260 ft) 335.1 m/s (1099 ft/s)
charge 11.43 s 1318.2 m (4325 ft) 10.1 m/s (33 ft/s)
deployment 11.43 s 1318.2 m (4325 ft) 10.1 m/s (33 ft/s), airspeed 10.1 m/s (33 ft/s)
apogee 12.02 s 1320.4 m (4332 ft) 0.0 m/s (0 ft/s)
ground hit 269.86 s 0.0 m (0 ft) 5.0 m/s (16 ft/s)
(heights are the center of gravity's above the site; speeds are over the ground, and a deployment's
airspeed through the air)
top speed 371.7 m/s (1219 ft/s) at 1.08 s
top Mach number 1.095
landing 0.8 m (3 ft) from the pad at 269.86 s, at 5.0 m/s (16 ft/s)
How far to trust it. Simulated from the design file, not measured. Against 60 logged flights of
fliers' own designs, the simulated apogee averaged 8.0% above the logged one. HPR Sim flew each in
its day's air from ERA5, a weather reanalysis, and each logged apogee is the height climbed in it.
The simulated apogee was within 10% on 31 and read low on 15, by at most 20%. This flight was flown
in the standard atmosphere. On a day warmer than it at the site, the rocket can climb higher than
this apogee; --weather flies the day's air. Plan a waiver or a field's ceiling with room above this
apogee; the altimeter's reading is the one to log, and the RSO decides.
More: https://hpr.fusionspace.co/accuracy.html
The warning says the I377’s case reaches 22.0 mm (0.87 in) past the mount tube’s forward end.
The 292 mm (11.5 in) case sits 10 mm (0.39 in) out of the back of the rocket’s 260 mm (10 in)
mount tube. The simulator flies it as drawn. If a ring or bulkhead closes the mount’s forward
end, the real case stops there and sits 22.0 mm (0.87 in) further aft. The warning gives the static
margin at ignition both ways, as drawn and moved aft. Moving the case aft moves the center of
gravity aft, so the second figure, 0.94 calibers, is the lower one. The simulator flies the first.
Whether the case fits the real rocket is for you to check.
--motor replaces the motor of the configuration flown. --config picks which of the file’s
configurations it goes in, and --mount picks which mount, if the design has several.
Compare them
Read the same lines for each motor: margin, apogee, rail exit speed, delay and descent. Between the two flights above:
- The I377 climbs higher. If your field has a ceiling, its waiver sets it, not the simulator.
- The I377 leaves the rail much faster. The safety codes ask for a speed that ensures a stable flight but give no number. Competitions set their own, such as 25 m/s (82 ft/s) for the Spaceport America Cup (Rail exit speed quotes them).
- The stability margin changes with the motor. A motor’s mass sits behind the center of gravity. So a heavier motor moves the center of gravity aft, toward the center of pressure, and shrinks the margin. Check it with every motor you might fly (Check stability for a certification flight).
- The I377 takes the rocket past the speed of sound, Mach 1. The H125 stays well below it, and the H170M, at Mach 0.842, barely enters the range from Mach 0.8 to 1.2. In that range, HPR Sim’s center of pressure is up to 2.36 calibers behind NASA’s wind-tunnel data (Known gaps). So its margin there reads high, and published guidance asks for a larger margin (Compare with published guidance).
To fly a few more motors, change --motor and --delay and run it again. --json prints each
flight as data, for a script that tabulates many.
Choose the delay
The delay line’s first figure is the coast, from burnout to apogee, with the charges held. A
delay near it fires the charge near apogee, where the rocket moves slowest. The coast is taken
from the same flight flown with no charge firing. A charge that fires early opens the parachute
while the rocket climbs, and the coast would come out short. A delay that is too short would then
look nearly right. So the delay line’s apogee can come later than the apogee line’s, which is
the flight as flown. The gap is the climb an early parachute cost. The second figure is the delay
you gave, and the third says how far from the held apogee the charge fires. In the events table,
the charge row gives the speed at that moment. The further the charge is from apogee, the faster
the rocket moves when the parachute comes out.
The last figure is how far the delay may fire from its label. Then come the speeds at its short end and its long end. NFPA 1125, the code commercial motors are certified to, lets a delay miss its label by 1.5 s or 20%, whichever is greater, up to 3 s (Choosing the numbers). The limit holds for a motor type’s certification firings. It doesn’t bound every motor, nor a delay drilled to a time no label gives. The band’s speeds are vertical, up or down; the events table’s are the total speed.
An end gets no speed where the flight with the charges held stops matching the one a charge meets. That happens more than 1 s past apogee, where it falls tail first with nothing open, a fall the simulator doesn’t predict. It also happens after another parachute or streamer opens, such as a drogue at apogee. The line says which. Pick a delay whose two ends both suit your recovery. Compare the climb at the short end and the fall at the long end with your parachute’s and harness’s ratings.
In the H125 flight above, the coast is 9.42 s, and the 10 s delay fires the charge 0.58 s after apogee. A delay 2.0 s short fires it climbing at 14.1 m/s (46 ft/s). One 2.0 s long fires it 2.58 s after apogee, in the fall the simulator gives no speed for. The H125 comes in delays of 8, 10, 12, 14 and 18 s, more than its file’s header lists, so 10 s is the nearest. The simulator flies any delay you give. Give one the maker sells, or one your motor’s delay can be adjusted to.
A delay is a burning fuse, and real ones vary from motor to motor. The simulator flies the stated
time exactly. The band on the delay line shows what the code’s tolerance means for your rocket.
Monte Carlo dispersion, in the library, can scatter the delay.
The guide rocket’s own second configuration, [I175WS-9], is an example where the set delay
fires before apogee:
$ hpr sim validation/fixtures/ork/guides/level-1.ork --config 2
Level 1 guide rocket (level-1.ork)
configuration 2 of 2: [I175WS-9]
help: --config flies the others, by number or name: 1 [H170M-10]
a simulated flight, not a measurement
static margin 1.67 calibers off the rail; least 1.67 calibers, at 0.14 s, before apogee
CG and CP 0.813 m (32.0 in) and 0.923 m (36.3 in) aft of the nose tip, off the rail
apogee 1100.7 m (3611 ft) above the site at 11.48 s
rail exit speed 28.9 m/s (95 ft/s)
delay apogee 9.82 s after burnout, with the charges held; the motor's set delay: 9 s; its charge fires 0.82 s before apogee; the delay may fire 1.8 s short or long (NFPA 1125): climbing at 26.6 m/s (87 ft/s) to falling at 9.5 m/s (31 ft/s)
descent 4.5 m/s (15 ft/s) at landing under `Parachute`
motor: 1 × I175WS (from the bundled catalog, as of 2026-10-28) in `Motor mount tube`, lit at launch
recovery: `Parachute` at the ejection charge, 0.520 m² of drag area, opened at 10.97 s
launched at 0.00000° N, 0.00000° E, 0 m (0 ft) above sea level, from 1.5 m (4.9 ft) of vertical rail above its aft end, in calm air
note: the file's 1 recovery device flies as OpenRocket flies it. Each opens fully at its event, with the file's drag coefficient or OpenRocket's own. Once one opens, the rocket descends as a point under the open devices' drag alone
warning: drag: issue #67: a cone-like nose's or shoulder's pressure drag reads high from Mach 0.8 (about twice a measured cone's at Mach 0.85, still +15% at 1.5). So the apogee, top speed and drift read low, and the flutter margin and largest dynamic pressure look better than they are. This flight reaches Mach 0.83 at 1.8 s
warning: drag: issue #68: base drag reads high from Mach 0.8 to 1.2 (0.225 against a measured 0.156 at Mach 0.9). So the apogee, top speed and drift read low, and the flutter margin and largest dynamic pressure look better than they are. This flight reaches Mach 0.83 at 1.8 s
warning: drag: issue #18: skin friction is taken as fully turbulent; on a smooth surface a laminar run near the nose lowers it, by 3.6% on RocketPy's Calisto at Mach 0.3. If this surface is that smooth, the apogee, top speed and drift read low, and the flutter margin and largest dynamic pressure look better than they are
warning: stability: issue #172: the static margin read up to 0.1108 calibers above OpenRocket's on four private designs, cause unknown; this flight's may read high by as much
warning: stability: issue #1290: on one of two wind-tunnel models, the center of pressure sat 0.11 to 0.92 calibers aft of the tunnel's at Mach 0.6 and 0.8, as the report's curve reads; fitted over −3° to 4°, about 0.08 at 0.8. So from Mach 0.6 the flight margin may read high. This flight reaches Mach 0.83 at 1.8 s
warning: stability: issue #1198: the center of pressure sat 0.67 to 1.35 calibers aft of a wind tunnel's on two models at Mach 0.9, so past Mach 0.8 the flight margin may read high. This flight reaches Mach 0.83 at 1.8 s
help: issues: https://github.com/nrdptel/fusionspace-eridanus/issues/<number>
event time height speed
liftoff 0.02 s 0.4 m (1 ft) 0.0 m/s (0 ft/s)
rail exit 0.14 s 1.9 m (6 ft) 28.9 m/s (95 ft/s)
burnout 1.97 s 385.2 m (1264 ft) 260.5 m/s (855 ft/s)
charge 10.97 s 1099.1 m (3606 ft) 8.0 m/s (26 ft/s)
deployment 10.97 s 1099.1 m (3606 ft) 8.0 m/s (26 ft/s), airspeed 8.0 m/s (26 ft/s)
apogee 11.48 s 1100.7 m (3611 ft) 0.0 m/s (0 ft/s)
ground hit 247.48 s 0.0 m (0 ft) 4.5 m/s (15 ft/s)
(heights are the center of gravity's above the site; speeds are over the ground, and a deployment's
airspeed through the air)
top speed 281.3 m/s (923 ft/s) at 1.75 s
top Mach number 0.830
landing 0.7 m (2 ft) from the pad at 247.48 s, at 4.5 m/s (15 ft/s)
How far to trust it. Simulated from the design file, not measured. Against 60 logged flights of
fliers' own designs, the simulated apogee averaged 8.0% above the logged one. HPR Sim flew each in
its day's air from ERA5, a weather reanalysis, and each logged apogee is the height climbed in it.
The simulated apogee was within 10% on 31 and read low on 15, by at most 20%. This flight was flown
in the standard atmosphere. On a day warmer than it at the site, the rocket can climb higher than
this apogee; --weather flies the day's air. Plan a waiver or a field's ceiling with room above this
apogee; the altimeter's reading is the one to log, and the RSO decides.
More: https://hpr.fusionspace.co/accuracy.html
Put the choice in your design
The simulator doesn’t change your .ork file: set the motor and its delay in OpenRocket, save,
and fly the file again. Without --motor, hpr sim flies the motors and delays the file holds,
as Fly your .ork shows. hpr sim’s delay line checks the delay you set.
What it leaves out
- Each motor flies one thrust curve, ThrustCurve.org’s, and its stated delay exactly. Real motors differ a little from their published curves.
- The simulator’s design checks flag a motor wider than its mount. They warn on one longer than its tube, or that runs into an engine block, thrust ring or bulkhead the design draws inside the mount. They don’t know a retainer or closure the design doesn’t draw.
- A motor named with
--motornarrower than its mount flies with no adapter. A note says so when it is more than 5% narrower; the adapter’s mass is left out. A motor the file holds gets none. - The simulator gives no verdict: it ranks nothing as safe or unsafe. The motor’s printed data, the safety codes and your range safety officer decide.