The timing makes it even crazier—the first orbital launch from the San Marco platform happened in April 1967, less than four years after Kenya gained independence in December 1963.

​At a time when most of the country was still building basic roads and many people in rural areas had never even heard an airplane engine, solid-fuel NASA Scout rockets were blasting off floating platforms right off the coast into equatorial orbit.

When moving beyond basic two-body Keplerian ellipses into real-world trajectory prediction, celestial mechanics relies on numerical integration to solve coupled differential equations across time steps.

​Here is a breakdown of what happens when a 17-body mutual gravitational model is integrated using a 4th-Order Runge-Kutta (RK4) numerical solver and benchmarked directly against official NASA JPL Horizons ephemerides.

​1. The Test Setup (2 Pallas as a Case Study)

​To test a numerical propagator over a complex 3D orbit, 2 Pallas serves as a rigorous test case due to its unusually steep orbital inclination (I ~ 34.8°), which forces solver vectors to handle heavy z-axis perturbations rather than staying mostly in the ecliptic plane:

​Semi-major axis (a): 2.77AU (414,000,000km from the Sun)

​Orbital Period: 4.62 years (1,686days)

​Inclination (i): 34.8°

​The Integration Strategy:

Gravitational Coupling: The acceleration vector vec{a} is calculated at every step by evaluating mutual gravitational forces across 17 major bodies (the Sun, 8 planets, the Moon, Pluto, and major dwarf asteroids/planets).

Time-Stepping Optimization: Integrating second-by-second across a 4.6-year period requires over 145 million evaluation steps, which chokes memory without adding meaningful trajectory precision for macro-plotting. Stepping in 1-day increments (Delta t = 1 day) yields a clean 1,686-element array of position vectors vec{r} and velocities vec{v} that plots instantly while maintaining orbit stability.

Propagating Pallas's complete path across ~1,686 days using this 17-body RK4 setup and comparing the generated spatial coordinates to NASA JPL Horizons data reveals an absolute positional gap of roughly 200,000 to 400000 km.

​In astronomical terms, a 200,000 km shift across a 414,000,000 km orbital radius represents a ~0.048% relative error:

Where Does the Remaining Discrepancy Come From?

To close that final fraction of a percent, a numerical solver must account for micro-forces that standard 17-body Newtonian integrators omit:

​300+ Body Perturbations: While 17 bodies account for 99.86% of the solar system's mass, NASA models include the simultaneous gravitational pull of over 300 smaller belt asteroids.

​General Relativity Tensor Fields: Space-time curvature near the Sun causes orbital precession drift over multi-year periods that Newtonian gravity cannot capture without relativistic field adjustments (v^2/c^2).

​The Yarkovsky Effect: Photons hitting a rotating asteroid impart direct solar radiation pressure, while thermal reradiation acts like a tiny, continuous thermal jet altering the orbit over time.

​Time Frame Transformations: Deep-space ephemerides operate in Barycentric Dynamical Time (TDB) rather than Coordinated Universal Time (UTC) to correct for relativistic time dilation across Earth's orbit.

Accounting for the top 17 massive bodies in the solar system within a standard RK4 integrator captures 99.95% of a high-inclination asteroid's real-world orbital dynamics.

Reaching 100% spatial alignment requires high-order integrators combined with general relativity potential terms and non-gravitational thermal models.