Satellite Orbit Simulator Back
Orbital Mechanics

Satellite Orbit Ops — RAAN, Coverage Radius, Eclipse Fraction

An operations-design tool for satellite engineers. Manipulate altitude h, inclination i and RAAN to estimate coverage and eclipse fraction for LEO/GEO assessment, ground-station access timing, and power-budget preparation. For three-orbital-element basics use Orbital Mechanics Basics; for power budget use Satellite Power; for thermal use Satellite Thermal.

Orbital Parameters
Altitude h (km)
km
Inclination i (°)
°
RAAN Ω (°)
°
True Anomaly ν (°)
°
Results
Period T (min)
Velocity v (km/s)
Coverage R (km)
Eclipse (%)
Orbit

Blue: orbital plane  ●: satellite at true anomaly ν  Dashed: ground track

Theory & Key Formulas
Period: $T = 2\pi\sqrt{\dfrac{(R_e+h)^3}{\mu}}$
Velocity: $v = \sqrt{\dfrac{\mu}{R_e+h}}$
$\mu = 3.986\times10^{14}$ m³/s², $R_e = 6371$ km

What is a Satellite Orbit?

🙋
What exactly is the difference between LEO and GEO? They just look like circles on the simulator.
🎓
Basically, it's all about altitude and speed. LEO (Low Earth Orbit) is close, typically 200-2000 km up. GEO (Geostationary Orbit) is way out at about 35,786 km. Try moving the altitude slider in the simulator from 500 km to 35,786 km. See how the satellite slows down dramatically? That's because orbital velocity decreases with altitude.
🙋
Wait, really? So a GEO satellite is slower? Why does it seem to hover over one spot on Earth then?
🎓
Great observation! It is slower, but the circle it has to travel is much bigger. The key is its orbital period—the time for one lap. At exactly 35,786 km, the period is 24 hours, matching Earth's rotation. So, if you also set the inclination to 0° in the simulator, it will appear fixed in the sky. A common case is TV broadcast satellites.
🙋
What about the other parameters, like RAAN and inclination? They seem to tilt and rotate the orbit.
🎓
Exactly. Inclination tilts the orbital plane relative to the equator. Set it to 90° in the simulator—you get a polar orbit that passes over the poles, great for Earth observation. RAAN (Right Ascension of Ascending Node) rotates that tilted plane around the Earth. For instance, a satellite constellation like Starlink uses specific RAAN values to space out its orbital planes for global coverage.

Physical Model & Key Equations

The orbit is governed by balancing the satellite's inertia with Earth's gravity. The key relationship gives the orbital period, which you see calculated automatically in the simulator.

$$T = 2\pi\sqrt{\dfrac{(R_e+h)^3}{\mu}}$$

Here, $T$ is the orbital period (seconds), $R_e = 6371$ km is Earth's radius, $h$ is the altitude above Earth (km), and $\mu = 3.986\times10^{14}$ m³/s² is Earth's standard gravitational parameter.

The satellite's orbital velocity, also displayed, is derived from the same principles. A higher orbit means a longer path but a slower speed.

$$v = \sqrt{\dfrac{\mu}{R_e+h}}$$

Here, $v$ is the orbital velocity (m/s). This is the speed needed to maintain a circular orbit at altitude $h$. Notice in the simulator: LEO satellites zip around at ~7.8 km/s, while GEO satellites cruise at ~3.1 km/s.

Real-World Applications

Earth Observation & Weather Satellites: These often use Sun-synchronous orbits, a special type of LEO with high inclination. By adjusting RAAN and inclination precisely, the satellite passes over the same location at the same local solar time every day, ensuring consistent lighting for images. The simulator shows how changing inclination alters ground coverage.

Global Communications (GEO): Television and weather broadcast satellites use Geostationary orbit. As shown when you set altitude to ~35,786 km and inclination to 0°, the satellite stays over a fixed longitude, providing continuous coverage to nearly a third of the Earth's surface with a single satellite.

Satellite Constellations (LEO): Systems like Starlink or GPS use many satellites in lower orbits. In the simulator, see how a LEO satellite has a short period (~90 minutes). Multiple satellites in different orbital planes (set by varying RAAN and true anomaly) are needed to ensure at least one is always in view from any point on Earth.

Space Station & Crewed Missions: The International Space Station orbits in LEO at about 400 km altitude. At this height, you can see the high orbital velocity in the simulator. This low altitude reduces the energy required for crew and cargo launches but means the station experiences atmospheric drag and requires periodic re-boosts.

Common Misconceptions and Points to Note

There are several key points you should be especially mindful of when starting to use the simulator. First is the assumption of "perfectly circular orbits." This tool calculates using circular orbits for simplicity, but in reality, most satellite orbits are elliptical. For instance, an Earth observation satellite can have an altitude difference of hundreds of kilometers between its perigee (closest point to Earth) and apogee. While circular orbit calculations are excellent as a first approximation, actual designs must always consider elliptical orbit parameters (eccentricity).

Next is overlooking dependencies between parameters. For example, you might memorize that "Geostationary Orbit (GEO) is at an altitude of about 36,000 km with 0-degree inclination," but this is true only for an ideal case where Earth is a perfect sphere and there is no gravitational influence from other celestial bodies (perturbations). In reality, Earth is slightly flattened (an oblate spheroid), so to strictly maintain a 0-degree inclination, a satellite will gradually drift on its own. Preventing this requires regular orbital control maneuvers (thruster firings). When adjusting parameters in the simulator, get into the habit of asking, "If I change this value, which other values will be affected?"

Finally, the interpretation of "coverage radius." The tool calculates the "area of Earth's surface visible from the satellite" geometrically. However, in practical communication or observation operations, this entire area is not uniformly usable. For example, near the edge of the horizon, radio signals can be attenuated by the atmosphere or experience significant delays. Keep in mind that the practical service area is often considerably smaller than the calculated coverage radius.

How to Use

  1. Enter altitude h in kilometers (300–36000 km typical range). LEO constellation design often uses 550–800 km; GEO requires 35786 km.
  2. Set inclination i in degrees (0° equatorial, 90° polar). Polar missions use i=98°; geostationary requires i≈0°.
  3. Input Right Ascension of Ascending Node (RAAN) in degrees to orient the orbital plane. Adjust RAAN to shift ground track east or west.
  4. Read outputs: orbital period T (minutes), velocity v (km/s), nadir coverage radius R (km), and eclipse fraction (%) for eclipse season analysis.

Worked Example

Design a Sun-synchronous Earth observation satellite: h=705 km, i=98.13° (SSO condition), RAAN=0°. Simulator yields T≈98.7 min, v≈7.53 km/s, coverage R≈1247 km (approx. 2.5° half-angle swath for nadir sensor), eclipse fraction≈35% at equinox. This configuration gives ~14 orbits/day with predictable lighting geometry, ideal for Landsat-class missions.

Practical Notes

  1. RAAN precession: J₂ perturbation causes nodal regression (~0.98°/day for SSO). Use RAAN inputs to pre-plan seasonal drift and maintain frozen-orbit conditions.
  2. Eclipse fraction peaks near equinoxes and varies with h and i. At h=550 km, expect 30–38% eclipse; geostationary satellites see zero eclipse.
  3. Coverage radius R assumes hemispherical visibility (horizon-limited, ~81° elevation mask typical). Increase h to expand ground footprint; reduce i for equatorial coverage density.
  4. Velocity trades: lower altitude increases v and T shortens (e.g., 400 km LEO: v≈7.67 km/s, T≈92 min); higher altitude reduces atmospheric drag for station-keeping accuracy.