Real missions.
Put LOTUS to the test.

Compare LOTUS plugin trajectories with NASA/JPL flight references. Inspect the path, the difference and the physics behind each result.

Design your own mission

NASA/JPL reference compared with LOTUS plugin solve

BepiColombo: JPL reference and LOTUS plugin solutionThe blue trajectory shows the agency mission reference. A plugin solution with its validation record has not loaded. Oblique ecliptic projection; Sun-centered distances are shown in astronomical units.0.25 au0.5 au1 au2 au3 auSunEarth orbitVenus orbitMercury orbit0.43 auSun-centered · Ecliptic J2000 · Oblique view
Full mission reference20 Oct 2018 — 22 Oct 2026

The encounters that shape the journey

Select a flyby to locate it on the path

One Earth flyby, two at Venus and six at Mercury progressively reshape the transfer.

How this comparison was made Sources, assumptions and study files

Plugin solution and JPL reference

The blue mission reference is drawn from NASA/JPL Horizons geometric spacecraft states. A gold solution is displayed only with a genuine plugin run and its independent validation record.

Plugin solve not loaded.

The overview includes all nine flybys and flown cruise through 22 October 2026. Mercury capture is outside this study.

The overview stops at the source fit cutoff: 22 October 2026 for BepiColombo and 27 October 2026 for Psyche. Reference interpolation precision is distinct from solver accuracy. Both paths use the same coordinates, projection and physical scale.

Inspect the evidence

Read the comparison methodologyRead the sourced mission report

The solver request records the exact inputs used for this run. Mission encounter constraints do not supply the spacecraft’s actual thrust history or guarantee a feasible mission solution.

Decompress the plugin run to inspect its original .lotus_analysis file.

Your mission has
a path worth exploring.

Connect the encounters. Inspect the trajectory.
Build the spacecraft around the journey.

Start designing with LOTUS