Accuracy and Validation
BurnSim is used to design motors that people then build and fire, so "is this number right?" is a fair question to ask of it. This page sets out what BurnSim's results are checked against, how closely they agree, and - just as important - which numbers it cannot check for you.
Short version: the thermochemistry is validated against NASA's own published reference cases and agrees with them closely. The ballistic simulation is a quasi-steady model built on standard textbook relations; its formulas are checked independently, but its accuracy depends on propellant data you supply. The case strength check reproduces a published spreadsheet exactly, and is hand calculation and nothing more. Nothing here makes a predicted pressure curve a guarantee: treat all results as estimates, test in a safe place, and assume the motor can fail.
Where the thermochemistry comes from
When BurnSim computes C*, specific heat ratio and molar mass from an ingredient recipe (see Propellant Thermochemistry), it is not using a correlation or a lookup table. It solves the chemical equilibrium of the combustion products by minimising Gibbs free energy, the same method NASA's CEA (Chemical Equilibrium with Applications) uses, and it uses NASA's own thermodynamic species data - the TP-2002-211556 library - for the properties of those products.
The solver and the rocket-problem driver are transliterated from CEA's own source, which NASA released under the Apache 2.0 license, and the algorithm is documented in full in NASA RP-1311. This matters for the next section: because BurnSim implements the same algorithm over the same data, NASA's published example cases are a test BurnSim can be held to exactly, rather than merely compared against.
The validation gate: NASA RP-1311 reference cases
RP-1311 ships a set of worked example problems together with CEA's own reference output for each one. BurnSim reproduces seven of them, chosen to exercise different parts of the calculation rather than the same path seven times. Each is an automated test that runs on every build, and the expected values are transcribed from NASA's reference output - they are not produced by BurnSim and then blessed.
| Case | What it is | Why this one |
|---|---|---|
| Example 1 | Hydrogen burned in air at an equivalence ratio of 1 | The plainest possible equilibrium solve - if this disagrees, nothing else is worth looking at. |
| Example 3 | Toluene and n-octane burned in air preheated to 700 K | A lean, nitrogen-dominated flame at around 2400 K whose interesting products are the nitrogen oxides. No rocket propellant looks like this, which is the point: a solver accidentally tuned to propellant chemistry would fail here. |
| Example 5 | Adiabatic combustion of a real solid propellant | The case closest to what BurnSim is actually for. |
| Example 8 | Liquid hydrogen and liquid oxygen expanded through a nozzle | Validates the rocket driver rather than the equilibrium solve. The throat is found by a search, the area ratios by a second search on top of it, and C* ties them together - a sign error anywhere in that still produces a table of plausible-looking numbers. |
| Example 12 | Monomethylhydrazine and nitrogen tetroxide | A storable bipropellant, well away from the chemistry of the other cases. |
| Example 13 | An expansion that stalls on a melting point | A product that changes phase partway down the nozzle, which is a case naive implementations get wrong silently. |
| Example 14 | Hydrogen and oxygen cooled through the point where the steam condenses | NASA wrote this one "to illustrate the effect of condensed species on volume and molecular weight", and below 304.3 K two thirds of the moles are liquid water. It is the condensed-phase bookkeeping itself under test - the same bookkeeping that decides what the condensed aluminum oxide in a metallized propellant does to flame temperature and gas properties, which example 5 then exercises on a real propellant. |
How close is "agrees"?
Close enough that the tolerances are worth quoting. On example 8, BurnSim is required to match NASA's reference output to within:
- 0.5 K on a chamber flame temperature of 3383.8 K - about 0.015%
- 1 m/s on a characteristic velocity (C*) of 2332.3 m/s - about 0.04%
- 0.0001 on the isentropic exponent
- 0.01 bar on a throat pressure of 30.66 bar
If any of those drift, the build fails. Agreement at this level is what distinguishes an implementation of the algorithm from an approximation of it.
How BurnSim compares to ProPEP 3
Many people arrive at BurnSim already using ProPep3, so the practical question is how the two compare on the same formulation.
Expect close agreement, not identical numbers, and a percent-level difference in C* is normal. The two use different thermodynamic data of different vintages: ProPEP's was last updated in 1986, while BurnSim uses NASA's TP-2002-211556 library. Neither is "wrong" because of the other, and a small difference is not a bug in either one.
What would be a real disagreement, and worth reporting, is a qualitative one: a flame temperature off by hundreds of degrees, the wrong product species, or aluminum oxide missing entirely from a metallized mix. Those indicate an error rather than a data vintage.
One difference trips people up often enough to repeat here: ProPEP's Isp* and an expanded Isp are not the same quantity, and comparing one against the other makes the two programs look badly out of agreement when they are not - roughly 115 s against 153 s for KNSB at 1000 psi. Propellant Thermochemistry explains which is which.
The ingredient table
The recipe you enter is only as good as the ingredient data behind it, so every value in BurnSim's built-in ingredient table has been checked against a published second source, and each entry records where its numbers came from. You can audit any of them rather than taking them on trust.
That checking caught real problems rather than merely confirming what was already there: several substances exist in three or four solid forms whose heats of formation are tens of kJ/mol apart, which is the kind of error that produces a confidently wrong flame temperature. Ingredients are picked from a list rather than typed, so a misspelled name cannot silently produce a wrong analysis.
If you add your own ingredients, or import them from ProPEP's PEPCODED.DAF (see Importing ingredients from ProPEP), those values are yours and are not second-sourced by anyone - the audit trail above covers the built-in table.
The ballistic simulation
The simulation steps through the burn, by default every 0.01 s. At each step it works out how much propellant is burning, the chamber pressure that balances the gas made against the gas the nozzle passes, and the thrust that pressure produces. Each piece is a standard relation, and each is checked a different way.
| Calculation | What BurnSim does | How it is checked |
|---|---|---|
| Burning surface | The grain's cross-section is burnt back on a fine raster (a distance transform), so any shape, including imported and custom ones, burns the same way. Simple grains can use exact geometry instead (Use Eroder for Surface Area off). | Where a grain has both, the setting lets you compare the two on your own grain. A raster is an approximation of a curve, so expect small differences, mostly near burnout. |
| Burn rate | Saint-Robert's law, r = aPn, with your a and n, or the pressure band the chamber is in. Optionally raised locally by an erosive burning correlation. | The law is the definition of a and n, so there is nothing to validate but your numbers. The three erosive correlations (Lenoir-Robillard, Mukunda-Paul, Ma 2020) are each checked against values hand-solved from the published equations, for the formula and its units. That shows the equations are implemented as published. It does not show any of them predicts your motor. |
| Chamber pressure | The equilibrium of gas generated and gas discharged through a choked throat: P = (Kn·a·ρ·C*/g)1/(1−n), with Kn the burning area over the throat area, and C* scaled by C* efficiency. | A direct consequence of the mass balance, the same relation every hobby motor tool uses. Its accuracy is entirely that of C*, a, n and the burning area. |
| Thrust | F = Cf·P·At. Cf comes from the isentropic nozzle relations, with a momentum term and a pressure term, solved for the nozzle's actual expansion ratio. A divergence half-angle multiplies the momentum term by (1 + cos α)/2, and Other Cf losses scales it. | The solved exit pressure is put back through the standard area-Mach relation, a different formula from the one solved, for ratios of specific heats from 1.2 to 1.4 and expansion ratios from 1.05 to 60. The two agree. This check found and fixed an inherited rounding fault in 2026, which had treated every nozzle from an expansion ratio of 1.5 to 2.5 as the same nozzle. |
| After burnout | The chamber bleeds down through the nozzle as an isentropic blowdown of its free volume. | The standard choked-flow blowdown of a fixed volume. It changes only the tail after the last propellant is gone, and can be turned off (Bleed-off after burnout). |
Beyond the formula checks, 14 reference motors, covering most grain types, are each re-simulated on every build and compared, line by line, with its stored output. Those tests catch any change in results, intended or not. They do not prove the stored numbers are right: they are a guard against drift, not a validation.
Against real firings, the honest position is limited. A burn rate fitted to a firing reproduces that firing by construction, so a close match there is not evidence. What counts is a motor of a different design, or a different throat, simulated with a and n measured on other firings and then compared with its own static test. BurnSim's characterization tools exist so that you can do that check for your own propellant, which is the only one that matters for your motor. The experimental Ignition tab was compared with a measured 54 mm static firing. Its rise depends on how much of the grain you say is alight at the start, which is an input, not a prediction.
The case strength check
The case strength check is hand calculation, not simulation and not a safety assessment. Its tube formulas (Barlow on the outside diameter, Lamé with Tresca, and Nakka's burst-factor fit) reproduce Richard Nakka's CASING.XLS. Its snap ring checks reproduce the spreadsheet built on it that its author uses, and both are pinned by automated tests to the psi: a 2.125 × 0.100 in 6061-T6 tube at 1,000 psi gives a design pressure of 1,893 psi and a burst pressure of 3,956 psi in both. The check uses only the numbers entered on the Case tab; the drawn hardware never feeds it.
The thread and radial-bolt checks use standard joint formulas from Machinery's Handbook, FED-STD-H28, ASME B1.1, Shigley and Bruhn. Each is hand-worked in the tests. No published worked example has yet been found to check them against, so treat them as one step less checked than the tube. Every formula, input and source, and the list of what is not checked at all, is on Case Strength Check.
The material strengths it ships are typical values, not guaranteed minimums. The check knows nothing about your actual tube, machining, seals or welds. Testing is what tells you whether a case holds.
What BurnSim cannot check for you
This is the part to read carefully.
- Burn rate (a and n) requires real test data. No thermochemical calculation predicts how fast a propellant burns. BurnSim computes C*, specific heat ratio and molar mass from a recipe; a and n come from firing motors and measuring, which is what Propellant Characterization is about. A simulation built on guessed burn-rate coefficients is a guess regardless of how good the thermochemistry is.
- Density is yours too. It comes from the formulation's theoretical or measured value, not from the analysis.
- The ballistic simulation is quasi-steady. Each step solves for the equilibrium chamber pressure, so it does not model the chamber filling at ignition. The end of the burn is now modeled: since 4.0.0.24 the chamber bleeds off through the nozzle after burnout instead of dropping to zero in one step (Bleed-off after burnout on the graph). The ignition end is covered only by the experimental Ignition tab, which is reported separately and does not change the main curves.
- A nozzle with no exit diameter is a bare throat, and a poor nozzle. If Exit dia is left blank (or no larger than the throat), BurnSim treats it as a real nozzle with an expansion ratio of 1. Before 4.0.0.24 it understated even that, simulating such a motor at a Cf of about 0.69 instead of about 1.2; if you see a bare-throat motor's thrust and impulse jump by roughly 76% after upgrading, that is the correction. Enter the exit diameter you actually have.
- Erosive burning is modeled but off by default. In motors with high length-to-diameter ratios, crossflow near the nozzle end can raise burn rate and chamber pressure substantially above a steady-state prediction. BurnSim 4 can model this (Erosive Burning, with the Lenoir-Robillard, Mukunda-Paul or Ma (2020) correlations) but it is not enabled unless you enable it. These are empirical correlations, and they disagree with each other - which is itself informative, and a reason to run more than one.
- Your own measurements outrank all of it. If you have characterized a propellant against real test data and BurnSim's computed numbers disagree with yours, prefer yours. BurnSim asks before overwriting a value you entered by hand for exactly this reason.
Reproducing this yourself
The validation is not a claim you have to take on faith. The reference cases are NASA's, published in RP-1311 and shipped with CEA, and the expected values are in CEA's own reference_output files. If you run the same case through CEA and through BurnSim, you should get the same answer to the tolerances above - and if you do not, that is a bug report we want.
See also
- Propellant Thermochemistry - computing C*, specific heat ratio and molar mass from an ingredient recipe
- Propellant Characterization - measuring burn rate from real test data
- Case Strength Check - every formula behind the Case tab
- Characterization Motor - a test motor for measuring your own propellant
- Erosive Burning - crossflow-augmented burn rate
- Characterization Motor - designing a motor for gathering burn-rate data