Orbit
Sun & storms
Spacecraft
Area is the cross-section facing the flow (a tumbling 3U averages about 0.03 m²). CD ≈ 2.2 is the usual first guess for a compact satellite.
Loading 3D…
Density along one orbit · the white dot is your satellite
Results
Altitude loss and lifetime always use the mean density along your orbit.
Density vs altitude
Replay a real event: the Starlink storm, February 2022
On 3 February 2022 a Falcon 9 put 49 new Starlink satellites into a low checkout orbit (about 210 by 335 km). A moderate geomagnetic storm arrived the next day. SpaceX said onboard GPS showed drag “up to 50 percent higher than during previous launches”. The satellites couldn't climb out, and 38 of the 49 burned up. Here is the same week, flown again with real space-weather data.
Altitude, day by day · lines = simulation, dots = real re-entries (hollow = estimated date)
Now
Area facing the air
The one number nobody outside SpaceX knows. Flying "edge-on, like a sheet of paper" (SpaceX's safe mode) shrinks it; a tumbling or flat satellite shows much more. Mass 297 kg and size from McDowell's catalogue; CD 2.2.
When does it come down? · same satellite, same week, four versions of the air
What would have happened
SpaceX launches low on purpose: a satellite that fails its checkout falls out of the sky within days instead of becoming debris. Healthy ones fire their thrusters and climb. So at 210 km every line above comes down within days unless the thrusters win. The question that February was whether they could win against the air the storm added. The blue line is the same week with a quiet Sun. The gap between it and the others is time the satellites lost, inside a window that was already short.
This replay has no thrust in it. It shows the air the satellites were fighting, not SpaceX's manoeuvres.
Working it backwards: does the simulation match reality?
Partly, and the parts that don't match are the point.
- The dates line up. With the area set between about 2 and 12 m², the simulated re-entries fall between 5 and 13 February, the same window as the catalogue's 38 dates. Satellites in different attitudes would spread out just like that.
- The standard model barely saw the storm. Fed the real storm index, the empirical model added about to the density at 210 km. SpaceX's own GPS showed up to 50% more drag. Fang et al. (2022), with SpaceX Starlink staff among the authors, ran a physics model and found at least 50% in most regions at 210 km, and more than 100% in some.
- That gap is the problem. An operator planning with the standard model would have expected a storm worth a few hours. The real air took days. Nobody measures the density at 210 km directly; the number arrives later, worked out from how fast satellites fell.
The uncertainty view: the Sun moves the air more than anything you control
How many times denser at solar max than at solar min
Ratio of orbit-average density, F10.7 200/Ap 15 over F10.7 70/Ap 4. At your altitude: . The shaded band is ±30%, the size of the typical disagreement between good density models.
Monte Carlo lifetime uncertainty
Real lifetimes depend on things nobody knows in advance. Each run draws a random future: where we are in the 11-year solar cycle and how strong it is, the storm level, your CD (2.0–2.6), your average area (±20% for tumbling) and a ±25% model error. Then it flies the satellite down to re-entry.
How long satellites last, and how fast a prediction drifts
Lifetime vs starting altitude · your spacecraft, Sun held fixed
Prediction drift from a density error
Δa is the drag the model misses: the error times the drag on your spacecraft. Extra drag lowers the orbit, and a lower orbit moves faster, so the satellite runs ahead of its prediction three times faster than simple kinematics suggests (the secular along-track term of the Hill/Clohessy-Wiltshire equations). Across 151 storms, MSIS models underestimated density by about 20 to 30% (Wang et al. 2026). Both lines assume the error stays constant and nobody re-tracks the satellite.
The physics, in plain words
1. The drag equation
A satellite in low orbit moves at about 7.7 km/s through very thin air. Each second it sweeps up the air in a tube the size of its cross-section. Pushing that air out of the way costs momentum:
ρ is the air density, v the speed, A the area facing the flow, and CD a number near 2 that captures how molecules bounce off the surface. Divide by mass to get the deceleration. The speed is fixed by the orbit and the shape by your design, so the density is the term that swings.
2. Losing height
Drag takes energy out of the orbit, and the orbit shrinks a little each revolution. For a circular orbit of radius a:
Lower orbits mean thicker air and faster decay, so the fall speeds up. The lifetime is the time to integrate that equation down to about 150 km, where the satellite burns up within hours. A heavy, compact satellite (high m/CDA) lasts longer.
3. Why density swings with the Sun
Above about 120 km the air is heated mostly by the Sun's extreme ultraviolet light. We track that with the 10.7 cm radio flux (F10.7), which follows the 11-year cycle from about 70 to above 200. A hotter thermosphere puffs up, so at a fixed altitude you sit in denser air: roughly 10 times denser at 400 km at solar max, and up to 30 times at 700 km.
Geomagnetic storms (high Ap) dump extra energy at high latitudes within hours. The day side, around 2 pm local time, is hotter than the night side. Switch to "one point" above to see the day/night bulge.
4. The model behind this page
Each gas (N₂, O, O₂, Ar, He) settles in its own layer, with lighter gases thinning out more slowly. That's why atomic oxygen dominates at 400 km and helium takes over higher up at solar minimum. We solve that layering in closed form (Bates' temperature profile and diffusive equilibrium) from a 120 km starting point taken from the U.S. Standard Atmosphere. The top-of-atmosphere temperature follows Jacchia's published formulas for F10.7, Ap, latitude and local time. It's about 100 lines of JavaScript (model.js).
How the simulation was built, and cross-checked
- Start from the requirement, not the tool. What does an operator need to know, and how well? That sets the error budget.
- Model the physics. Density, drag, flow into a sensor, using a reference atmosphere as the "truth".
- Monte Carlo the unknowns. Instead of one best guess, run hundreds of randomized cases (solar cycle, storms, instrument errors, attitude) and look at the spread. The histogram above is the same idea.
- Build an error budget. List each error source, size it, combine them (root-sum-square) and see which one dominates. You fix the biggest one first.
- Tag every number by evidence. Computed, simulated, from a datasheet, or measured. A simulated number never gets to pose as a measured one.
- Cross-check with an independent model. Two different implementations have to agree before a claim ships.
An AI engineering team did the heavy lifting
We developed this work during our entry to NASA TechLeap's Orbital Clarity Challenge. Two independent AI agent teams, one built on Claude and one on Grok, worked from the same requirements under one human engineer. Each team had roles like a small company: systems engineer, space-environment analyst, hardware lead, proposal writer and an independent judge that red-teams the others.
The two teams built separate simulations and then checked them against each other. Where they disagreed, we dug in, and that's how overclaims got caught before they shipped. The human set the direction and made the calls. The agents wrote the code, ran the cases, checked sources and argued.
Who built this page. Both teams, on purpose. The 3D scene and camera views started in the Claude team's viewer. The Grok team built the open density model, the drag and lifetime physics, the Monte Carlo and this simulator around it. The Claude team added the February 2022 replay (the open model driven by the real storm data, flown on a full orbit and checked against the real re-entry dates), the lifetime-vs-altitude chart and the prediction-drift chart. Goncalo Esteves directed both and asked for the two pages to become one.
This page is an example. An agent rebuilt the density model from published physics, checked it against reference models, and wrote and tested this simulator in a single afternoon. Not long ago this would have been a semester-long student project.
Satellite operators: use this, and talk to us
Use it for quick lifetime checks against the FCC 5-year post-mission disposal rule, for drag sanity checks in mission design, or to show your team why the solar cycle matters. It's free, and everything runs in the browser. If you fly in low orbit and care about density (conjunctions, re-entry, station-keeping), we'd like to hear what you need measured.
Honest limits
- This is an educational, first-order tool. It isn't for operational conjunction or re-entry decisions.
- Compared with NRLMSIS 2.0 (U.S. Naval Research Laboratory), the orbit-average density here agrees within about ±30% from 200 to 700 km for solar min, moderate and max. It runs up to about 30% high below 300 km at low and moderate activity. Both models underpredict the short, sharp density spikes of storms.
- Ignored here: seasonal and semiannual variation (we assume equinox), hydrogen above about 600 km, atmospheric co-rotation (a few % on drag), eccentric orbits, lift and attitude changes, and the slow drift of the orbit plane relative to the Sun (J2 precession). In the 3D view the orbit plane stays fixed against the Sun, so a non-sun-synchronous orbit samples one set of local times instead of sweeping through them over weeks.
- The 3D satellite is a generic box with a marked sensor port, not any specific design, and not to scale. The density shell is our open model, not a measurement or a forecast.
- "Lifetime, Sun held fixed" freezes today's F10.7 and Ap. Real lifetimes cross the solar cycle, so use the Monte Carlo for a range.
- The February 2022 replay flies one satellite at a time through this page's open density model along a two-body orbit with drag (rotating atmosphere, real latitude and local time), with the 3-hourly ap lagged 6.7 h, starting at 209 by 334 km, 53.2°, two hours after launch, using the real 3-hourly Ap and daily F10.7. It has no thrust, no attitude history and a constant area per run. The +50% and +100% cases raise the density only during the storm window (3 Feb 18:00 to 5 Feb 06:00 UT); they stand in for what SpaceX and Fang et al. reported, they are not a model of their own. 32 of the 38 observed re-entry dates are estimates in the catalogue. The replay is a reconstruction, not a reproduction of SpaceX's data.