Skip to main content
Calcimator

Constellation Design Calculator

Satellite count for global coverage from altitude and inclination.

About this calculator

This calculator sizes a Walker-style satellite constellation for continuous coverage using simplified spherical geometry rather than a full orbital-mechanics simulation. It starts from Earth's angular radius as seen from orbit — a function purely of altitude, since a satellite farther out sees a smaller slice of Earth's disk — and combines that with your minimum usable elevation angle (how high above the local horizon a satellite must sit before its signal counts as usable) to derive a half-swath coverage angle on the ground. Satellites-per-plane and number-of-planes are then back-calculated so each satellite's ground footprint just overlaps the next, closing gaps along both the along-track and cross-track directions; the coverage-overlap-margin input deliberately shrinks the usable swath to build in redundancy against an unplanned satellite loss. Orbital inclination sets the maximum latitude actually covered — a 53° inclination, similar to much of Starlink's constellation, reaches mid-latitudes but leaves the poles dark, while a 90° polar inclination is needed to reach the poles at all.

Note that this model's plane count and satellites-per-plane come entirely from altitude, minimum elevation, and overlap margin — inclination only determines which latitudes get covered, not how many planes the swath math calls for, so a polar and a mid-inclination constellation at the same altitude come out needing the same plane count here. The calculator's own documentation flags its key limitation plainly: it uses idealized spherical trigonometry and ignores both J2 perturbation (the orbital drift real satellites experience from Earth's oblateness) and the phasing optimization real constellation designers rely on to minimize satellite count — so treat the total-satellites figure as a first-order sizing estimate for early trade studies, not a final architecture. Raising altitude shrinks the required constellation size but raises both launch cost and per-satellite link complexity, a trade every constellation designer has to weigh.

Inputs

%

Results

Satellites per plane

4

Number of planes

2

Total satellites

8

Coverage half-angle (deg)53.61
Orbital period (min)95.5
Orbital velocity (km/s)7.59
Max latitude covered (deg)53
Cos Lambda Plus Elev0.4
How to Use This Calculator
  1. Enter orbital altitude (km) and minimum elevation angle (degrees) for acceptable coverage.
  2. Set orbital inclination (degrees) and coverage overlap margin (%) for redundancy.
  3. Review coverage half-angle, satellites per orbital plane, number of planes, and total satellite count.
  4. Use orbital period and revisit interval to verify coverage continuity meets mission requirements.
  5. Increasing altitude reduces satellite count but increases launch cost and coverage latency.

How the result changes with Min elevation angle (deg)

Min elevation angle (deg)Satellites per planeNumber of planesTotal satellites
5326
7.5428
156318
2535017561,250

What each input means

Orbital altitude (km)
Circular orbit altitude above Earth's surface. LEO: 200-2000 km, MEO: 2000-35786 km.
Min elevation angle (deg)
Minimum elevation above horizon for usable signal. Lower = wider coverage but weaker link. Typical: 5-25 deg.
Orbital inclination (deg)
Orbit inclination. 53 deg covers most populated areas. 90 deg (polar) for global coverage including poles.
Coverage overlap margin (%)
Extra overlap between adjacent coverage footprints to ensure seamless handoff.

What each result means

Coverage half-angle (deg)
Ground footprint half-angle from the sub-satellite point.
Satellites per plane
Minimum satellites in each orbital plane for along-track coverage.
Number of planes
Minimum orbital planes for cross-track coverage.
Total satellites
Total constellation size (planes x satellites per plane).
Orbital period (min)
Time for one complete orbit.
Orbital velocity (km/s)
Spacecraft speed in circular orbit.
Max latitude covered (deg)
Highest latitude that receives coverage (equals inclination for prograde orbits).

How this is calculated

Worked example, using the default values

  1. Identify Input Parameters
    4 parameters
    Orbital altitude (km) = 550, Min elevation angle (deg) = 10, Orbital inclination (deg) = 53, Coverage overlap margin (%) = 10 = 4 input(s) provided
  2. Calculate Satellites per plane
    Satellites per plane
    4 = 4
  3. Calculate Number of planes
    Number of planes
    2 = 2
  4. Calculate Total satellites
    Total satellites
    8 = 8
  5. Calculate Coverage half-angle
    Coverage half-angle = lambdaRad * RAD2DEG
    53.61 = 53.61
  6. Calculate Orbital period
    Orbital period = periodSec / 60
    95.5 = 95.5

Engine last updated . Checked against 2 independently-derived tests — how we verify calculators. Built by Paul Gunder, a software engineer, not a licensed financial, medical, or legal professional.

Frequently Asked Questions

Why does raising the minimum elevation angle increase the number of satellites needed?

A higher minimum elevation angle means a ground user must see a satellite riding higher above the local horizon before its link counts as usable, which shrinks the half-swath angle (lambda) each satellite can cover. Since satellites-per-plane and number-of-planes are both computed as pi divided by that angle, a smaller lambda directly increases both figures — trading link quality for constellation size.

Why doesn't changing inclination change the total satellite count in this calculator?

In this model, satellites-per-plane and number-of-planes are derived entirely from altitude, minimum elevation, and overlap margin through the coverage half-angle; inclination only sets which latitudes actually receive coverage, via the maxLatCovered output. So a 53-degree and a 90-degree (polar) constellation at the same altitude and elevation requirement come out needing the identical plane count here, even though the polar case reaches the poles and the 53-degree case doesn't.

What does the coverage overlap margin actually do to the result?

The overlap margin percentage shrinks the usable half-swath angle before it's used to size the constellation — a 10% margin means each satellite's effective coverage footprint is treated as 10% smaller than its raw geometric swath. That deliberately builds in redundancy so adjacent satellites' footprints overlap rather than just touching edge-to-edge, protecting against gaps if one satellite is lost or a handoff is imperfect.

How reliable is the total-satellites figure for an actual mission design?

The calculator uses idealized spherical trigonometry and explicitly ignores J2 perturbation (orbital drift from Earth's oblateness) and the phasing optimization real constellation designers use to trim satellite count, so treat the total as a first-order sizing estimate for early trade studies. A detailed design pass with orbital propagation and phasing optimization will typically arrive at a different, usually more efficient, satellite count for the same coverage requirement.

The questions that sit next to this one — chosen by subject, including calculators filed under a different category.

More in Science & Physics.