Past lunar mission

Artemis II

Artemis II is a past Moon mission entry covering launch, transfer, lunar operations, and engineering context.

Animated launch, translunar trajectory, lunar operations, and return or descent path.

Mission facts

Launch and expedition data

Status
Past
Agency
United States / international partners
Launch
2026
Vehicle
Space Launch System
Destination
Crewed lunar flyby
Mission class
Crewed Orion test

Trajectory and outcome

Flight sequence

Trajectory
High-energy translunar flyby and Earth return
Expedition
Crewed systems validation before the next Artemis campaign steps
Outcome
Completed crewed lunar flyby and Earth return in April 2026

Detailed notes

What this mission teaches

  • Mission class: Crewed Orion test.
  • Transfer profile: High-energy translunar flyby and Earth return.
  • Lunar work: Crewed systems validation before the next Artemis campaign steps.
  • Result or planning state: Completed crewed lunar flyby and Earth return in April 2026.
Artemis II project-local lunar mission visual

Technical Review

What to compare against other lunar missions

Launch energy

Compare direct translunar injection, Earth-orbit phasing, low-energy transfer, and rideshare constraints.

Navigation

Flybys and orbiters stress tracking and burn accuracy; landers add powered descent, hazard detection, and autonomous terminal guidance.

Surface operations

Rovers, landers, and crewed missions have very different thermal, dust, communications, and power constraints.

Return path

Sample-return and crewed missions add ascent, rendezvous, entry interface, heat shield, and recovery risk.

Mathematical model

Mission trajectory and spacecraft model

Mission visuals combine catalog dates, distance vectors, speed estimates, and schematic spacecraft geometry. They are not CAD-certified vehicle meshes unless a source model is explicitly loaded.

Vector propagation

\[\mathbf{r}(t)=\mathbf{r}_0+\mathbf{v}(t-t_0)\]

For live-distance spacecraft pages, current position is propagated from epoch vector and velocity when high-precision ephemerides are not bundled.

Transfer curve

\[\mathbf{r}_{\mathrm{curve}}(u)=\operatorname{Bezier}\!\left(\mathbf{r}_{\mathrm{launch}},\mathbf{r}_{\mathrm{mid}},\mathbf{r}_{\mathrm{target}}\right)\]

Mission path arcs are schematic transfer curves anchored at meaningful endpoints, not claims of exact reconstructed trajectories.

Dimensional hierarchy

\[T_{\mathrm{world}}=T_{\mathrm{parent}}RS\]

Spacecraft parts are placed with transformation matrices. This proves the generated geometry is internally consistent even when simplified.

Verification standard: the rendered object must be reproducible from stated equations, catalog parameters, or explicit geometric transforms. Visual reference images may inform presentation only; they are not the source of orbital positions, field vectors, accretion-disk gradients, timing, or engineering layout.

Limitations: browser scenes may use bounded scale, compressed distances, simplified two-body dynamics, schematic transfer curves, or educational approximations where full numerical ephemerides, CFD, finite-element models, or general-relativistic ray tracing are outside the page scope. Those simplifications are part of the model contract, not hidden image-based construction.

Open the full site-wide mathematical verification policy