PHYSICS-BASED ASCENT & ORBITAL-STATE ANALYSIS

Launch Vehicle
Analyzer

A transparent framework for modeling launch vehicle ascent from the lower atmosphere to final orbital-state analysis, with assumptions, equations, and model boundaries kept visible.

Dynamics
2D
Atmosphere
Lower model
Integrator
RK4
Staging
Serial
Orbit
Planar 2-body
Illustrative launch trajectory A launch vehicle rises from Earth, passes Max-Q and a stage separation event, and approaches orbital-state analysis. MAX-QPeak dynamic pressure STAGE 1 SEPARATIONDiscrete mass event ORBITAL STATEr + v → orbit analysis

02 / SYSTEM

HOW THE SIMULATION WORKS

A launch is a coupled physical system.

The vehicle state is propagated through interacting environment, force, guidance, numerical integration, staging, and orbital-analysis models.

03 / FLIGHT

FOLLOW THE VEHICLE

From dense atmosphere to orbital state.

01 / LIFTOFF

Propulsion begins changing the vehicle state.

Gravity, thrust, mass flow, and the lower atmosphere immediately interact.

  • propulsion
  • gravity
  • atmosphere
02 / ATMOSPHERIC FLIGHT

Density and Mach shape aerodynamic loading.

Relative airspeed, speed of sound, dynamic pressure, and Cd determine drag.

  • atmosphere
  • aerodynamics
  • guidance
03 / STAGE EVENT

Continuous integration meets a discrete event.

Burnout is detected, the step is split safely, and discarded stage mass is removed.

  • integrator
  • staging
  • dynamics
04 / ORBITAL STATE

Position and velocity determine the resulting orbit.

Energy, angular momentum, eccentricity, periapsis, and apoapsis describe the final state.

  • orbit
  • state analysis

04 / PHYSICS

INSIDE THE PHYSICS ENGINE

Model scope, without pretending at false precision.

Select a model to inspect what it receives, what it computes, and where its assumptions stop.

01

GRAVITY MODEL

Central spherical-Earth gravity

IMPLEMENTED
Relation
g = μ / r²
Input
Earth-centred position
Output
Acceleration vector
Module
gravity.js
MODEL BOUNDARY

J2, oblateness, third-body gravity, and local terrain effects are not modeled.

05 / TRACEABILITY

TRANSPARENT BY DESIGN

A value should never enter the model anonymously.

Vehicle data can distinguish published, derived, estimated, and assumed values, with confidence recorded separately.

VALUEVacuum thrustVehicle input
ORIGINPublishedConfidence recorded
MODELpropulsion.jsPressure interpolation
PROPAGATES TOTrajectory stateThrust → acceleration → orbit
Published

Directly sourced value.

Derived

Computed from other values.

Estimated

Approximation from available evidence.

Assumed

Explicit modeling assumption.

06 / ARCHITECTURE

MODULAR BY RESPONSIBILITY

The numerical integrator does not know it is flying a rocket.

Physics remains replaceable and inspectable; continuous state propagation stays separate from discrete stage events.

NEXT SYSTEM

From physical assumptions to orbital state.

The analyzer interface connects vehicle definition, trajectory telemetry, staging events, and final orbital analysis.

Open analyzer