How often do commercial satellites revisit a military airfield?

A satellite with extended solar panels in orbit, Earth's curved surface and cloud cover visible below.

"Daily revisit" gets thrown around like a fixed property of the satellite. The real number depends on constellation size, the sensor's off-nadir slew range, your tasking priority against everyone else's, which constellation you're pulling from, and how much cloud sat over the field that morning.

Revisit rate vs. tasking cadence

Revisit rate is the theoretical interval between opportunities to image a given point. For a large VHR constellation with wide off-nadir pointing, that can be sub-daily at mid-latitudes, meaning more than one look in a 24-hour window is physically possible. For a smaller constellation or one with narrower swath, the honest number is closer to every few days before you get a usable look straight down or close to it.

Tasking cadence is the different question, and it's the one that governs your workflow: how often a frame from that revisit window actually lands in your hands, at usable quality, pointed at the field you care about. A satellite can pass overhead daily and still give you nothing useful for a week if the pass is 40 degrees off-nadir and the hangar roofline is hiding the apron, or if the tasking request sat behind someone else's priority target. Revisit rate is a catalog spec. Tasking cadence is what shows up in your archive.

For a named airbase that matters to a desk, the two numbers that count are: how many usable (low-obliquity, low-cloud) frames land per week, and how consistent that cadence is month to month. A field under a seasonal cloud band in one hemisphere's winter will show a worse real-world cadence than the constellation's marketing page implies, even with the same tasking priority.

What daily pass satellite imagery looks like on the ground

"Daily pass" sounds like a clean, metronomic thing. In practice it's lumpier. You might get three usable frames in four days, then a six-day gap from weather or tasking contention, then two frames in one day because two different sensors happened to line up. If you're watching for aircraft turnover, revetment occupancy, or new construction at a dispersal site, that lumpiness is the operating environment, not an edge case.

This is why a revisit-rate number by itself doesn't tell you much about detection latency, the time between something changing on the ground and you noticing it in the archive. A field with a nominal daily revisit but poor real-world cadence over the last month can still have a detection latency of four or five days for a single aircraft move. A field with a less impressive catalog number but consistent tasking priority can beat it.

If you're building a watch routine around a specific airfield, the question worth asking isn't "what's the revisit rate for this constellation." It's "what's the real gap between usable frames at this field, this season, and is anyone narrowing that gap by keeping it tasked." Archive density for your specific target matters more than a constellation-wide average.

Analysts tracking a shortlist of fields day to day stop re-deriving frame cadence by hand each morning and keep a running log per airfield instead, so the gap between frames is visible rather than reconstructed from memory. That's what Airfield Activity keeps: a daily-cadence log of aircraft counts by type, apron and revetment occupancy, and tracked construction at a named field, with side-by-side imagery so you can see exactly what changed between the frames you've got instead of guessing what happened in the gap.

The short version

Revisit rate tells you what's theoretically possible. Tasking cadence tells you what lands. For any field you're tracking day to day, build your expectations around the second number, and keep a log that shows you the real gaps instead of the catalog promise.

Get started

← Back to the blog