
derive orbital speed and period from Newton’s laws, use them to predict the ISS, GPS and geostationary orbits, and test Kepler’s third law with NASA planetary data in a spreadsheet model.
Phase 3: Make Sense
Do Now. A satellite moves to a higher orbit. Predict: does it move faster or slower, and does its period get longer or shorter? Write one reason.
Which moves faster around Earth: the ISS, about 420 km up, or a GPS satellite, about 20,200 km up?
Orbital speed from two laws. For a satellite in a circular orbit, gravity supplies the centripetal force: GMm/r2 = mv2/r. The satellite’s mass cancels, leaving
v = √(GM/r) and T = 2πr/v = 2π√(r3/GM)
For Earth, GM = (6.674 × 10−11)(5.972 × 1024) = 3.986 × 1014 m3/s2. Every satellite at the same radius has the same speed, whatever its mass: a bolt and a space station share an orbit. This is Newton’s second law at work: the net force per kilogram, GM/r2, equals the acceleration v2/r.
Worked example 1: three orbits.
Worked example 2: Kepler’s third law. Squaring the period formula gives T2/r3 = 4π2/GM: the same constant for everything orbiting the same body. For Earth’s satellites it is 9.90 × 10−14 s2/m3. Kepler found the pattern for the planets in 1619 from observations, decades before Newton explained it. With periods in years and orbit sizes in astronomical units (AU), the Sun’s constant is 1. NASA’s planetary fact sheet data:
| Planet | Semimajor axis (106 km) | Period (days) | a (AU) | T (years) | T2/a3 |
|---|---|---|---|---|---|
| Mercury | 57.9 | 88.0 | 0.387 | 0.241 | 1.002 |
| Venus | 108.2 | 224.7 | 0.723 | 0.615 | 1.001 |
| Earth | 149.6 | 365.2 | 1.000 | 1.000 | 1.000 |
| Mars | 228.0 | 687.0 | 1.524 | 1.881 | 1.000 |
| Jupiter | 778.5 | 4,331.0 | 5.204 | 11.859 | 0.998 |
| Saturn | 1,432.0 | 10,747.0 | 9.572 | 29.428 | 0.987 |
The ratio stays within about 1.5% of 1.000 from Mercury to Saturn, across a factor of 25 in distance. That is strong evidence for a single inverse-square force from the Sun.
A computational model. In a spreadsheet, put altitudes from 200 km to 40,000 km in column A. Compute r, v, T, orbits per day and g(r) in the next columns and graph T against altitude. This is the simulation you described in 4.02: altitude is the input you choose; Newton’s laws are the relationships inside it. Check it against the three worked examples first: if your ISS period is not about 92.8 min, find the error before you trust any other row.
Know the model’s limits. Our model assumes circular orbits, a perfectly round Earth, no air drag, no pull from the Moon or Sun, and no Earth rotation beneath the orbit. Real low orbits slowly lose height to drag, and the ground track shifts west each orbit because Earth turns underneath.
Misconceptions. (1) “Higher satellites move faster.” They move slower: v falls as 1/√r. (2) “A heavier satellite needs a faster orbit.” Mass cancels. (3) “A geostationary satellite can sit directly above a mid-latitude forest.” A geostationary orbit must be over the equator; from there it views mid-latitude regions at a slant.
Build the spreadsheet first, then answer.
Extend the model for the client.
Add a column for “orbits per day” and another for the time between passes if four satellites share one orbit. Choose realistic inputs (altitudes from 400 to 1,000 km and 35,786 km), and compare what you expected with what the model shows.
We have a working, checked orbit model. Next, we compare gravity with the other inverse-square force and brainstorm orbit designs.
Exit ticket: name one prediction from your model that matched a published value, and one assumption that could make it wrong for a real satellite.
How confident are you that you can I can derive and use v = √(GM/r) and Kepler's third law in a spreadsheet model of real satellite orbits.
Timing: Poly ran this as 2 × 50 min. Period 1: derivation and worked examples; period 2: building and checking the spreadsheet.
Materials: devices with a free spreadsheet, or calculators and a printed 8-row table; a NASA planetary fact sheet.
Listen for: altitude used as r; “heavier satellites go faster”; trusting the model before checking it.
Support / stretch: provide a spreadsheet with the r column built. Stretch: add a drag warning column that flags altitudes below about 400 km, and explain why the model cannot compute drag on its own.
Reading: OpenStax Physics (high school), chapter 6; OpenStax College Physics 2e, chapter 6.