1. Problem Statement

Can planetary motion be simulated using only fundamental quantities such as:

• Position (x)

• Velocity (v)

• Mass (m)

without explicitly using force equations?

This post presents a computational implementation of the NKTg model, where orbital velocity is derived from a target constant:

NKTg₁ = x × p
where p = m × v

The model is validated using publicly available data from NASA JPL Horizons for Mercury.

2. Reference Dataset (NASA 2024)

Actual orbital data of Mercury in 2024:

From this dataset, the target constant is established:

NKTg₁ = 8.90E+38 NKTm

3. Model Definition

Given:

• x (orbital position)

• m (mass)

• Target constant NKTg₁

We compute:

p=NKTg1xp = \frac{NKTg₁}{x}p=xNKTg1​​v=pmv = \frac{p}{m}v=mp​

No force expressions are used in the computation.

The model also integrates mass variation:

dm/dt = -0.5 kg/s

This produces:

NKTg2=(dm/dt)×pNKTg₂ = (dm/dt) × pNKTg2​=(dm/dt)×p

which remains negative throughout the orbit.

4. 2025 Simulation (NKTg Model)

5. Actual NASA Data (2025)

6. Numerical Comparison

Average relative error: 1.3%

7. Observations from a Computational Perspective

• The system is fully defined by interaction between x, v, and m.

• No force expressions are required in the computation process.

• The model is deterministic and reproducible across platforms.

• Error remains within ~1.3% compared to NASA JPL data.

8. Discussion

From a software engineering perspective, this approach represents:

• A constant-driven orbital simulation model.

• A reduced-parameter dynamical system.

• A reproducible computational experiment based on publicly available data.

The implementation can be reproduced in any language supporting floating-point arithmetic.

If anyone is interested, I can share a minimal reproducible implementation (Python / C++ / Go) for benchmarking and independent validation.