SAR vs optical imagery for airfield monitoring through cloud cover

A satellite in orbit above Earth, with layered cloud formations covering the surface below.

If you've tasked a watch on a named airfield for more than a few weeks, you've hit this problem: three days of solid cloud over the base, and your running log has a gap exactly where the interesting thing probably happened. The question of SAR versus optical for airbase monitoring usually comes up right at that moment, not as an abstract collection-planning exercise.

Here's the honest version of the tradeoff, not the vendor-brochure one.

What SAR buys you

Synthetic aperture radar doesn't care about cloud, haze, or darkness. It images at night, through overcast, through the kind of weather that would blank out an optical pass for a week. For a desk watching an airfield in a region with persistent cloud cover, that's the real appeal: SAR keeps collecting when optical can't.

What it doesn't buy you is easy interpretation. Reading SAR imagery well enough to call "that's a Flanker, not a Fencer" or to count aircraft reliably in a cluttered revetment takes training most desks don't have in-house, and even trained interpreters will tell you radar backscatter from a parked aircraft, a fuel bowser, and a generator trailer can look uncomfortably similar at the resolutions most commercial SAR constellations fly. You get coverage. You don't automatically get a clean count.

What optical gets right, and where it falls down

VHR optical is the opposite trade. At sub-meter resolution, aircraft type is usually legible without specialist training; you can tell a transport from a fighter from a helicopter at a glance, which matters a lot if the "so what" of your reporting has to survive a skeptical reader. Shelter construction, apron resurfacing, new hardstand, all of it shows up as a visual change a non-imagery-specialist can understand.

The catch is the one everyone already knows: no imagery when there's cloud in the way. A persistent weather system over a base in, say, the Baltic or parts of South Asia can mean days or weeks of nothing from an optical constellation, and that's exactly the stretch when something could move without you seeing it.

So which one, for daily change tracking

In practice, most OSINT desks don't get to pick one system and commit. You work with what tasks and what's affordable, and for the specific job of "did the order of battle at this base change since yesterday," optical VHR is still the workhorse, because the output is countable and defensible without a radar specialist checking your homework. The cloud-cover problem doesn't go away, but it becomes a known gap instead of a silent one: you know which days you have imagery and which days you don't, and you report the gap as a gap rather than guessing at continuity across it.

That's a different posture than trying to paper over the gap with inference, and it's worth being explicit about in your own reporting chain. A log that says "no imagery October 14-17, cloud cover" is more useful to whoever reads your product than one that just skips those dates silently or, worse, assumes nothing changed.

If SAR tasking is available to you for the same target, the two sources genuinely complement each other: SAR carries you through the weather window, optical gives you the type-level counts and the clean before/after comparison once skies clear. Few individual analysts have both on tap for every base they watch, but it's worth knowing which gaps your current source leaves and planning collection or at least documentation around them.

Airfield Activity runs on VHR optical and builds the daily-cadence log and the side-by-side comparison that let you see at a glance what changed at a named airfield, cloud-cover gaps included rather than hidden, which is a different job than trying to stitch together a continuous all-weather feed, and a more honest one for the kind of reporting most desks have to stand behind.

Worth a look at what a daily airfield log actually tracks if you're building this watch for the first time.

Get started

← Back to the blog