Field notes: the six hours between the strike and the pass that mattered

There's a particular kind of quiet that settles over a planning cell after a strike package reports weapons away. The target's hit. The jets are feet wet or already turning for the barn. And now everyone in the room is staring at a clock instead of a screen, because the thing they actually need, the thing a re-strike recommendation hangs on, hasn't arrived yet.

I've sat through that wait more times than I can count, and it's never the same length twice. Sometimes it's forty minutes. Sometimes it's most of a shift. What varies is whichever platform flies overhead next with a clean look at the ground, and whether that pass lines up with the window you need it in.

One night that's stuck with me: a structure went down clean, secondary explosion and everything, the kind of result that looks decisive on the radio. But "looks decisive on the radio" isn't a BDA call, and the duty officer knew it. So we waited. The next usable pass wasn't for six hours. Six hours is nothing in the context of a campaign, and it's an eternity when a re-strike tasking is sitting on a shelf waiting on a yes or no, and the window on the target might not hold.

What happened during that six hours is what made it worth writing down. Half the room assumed the structure was a total loss and started drafting the next tasking order on that assumption. The other half wanted to hold everything until the imagery landed. Both positions were reasonable. Neither was based on anything you could put your name next to. The gap costs more than its hours; it costs the decisions that get made, deferred, or half-made while everyone's working off the audio and the aircrew's read of their own smoke.

When the pass finally came in, the picture told a quieter story than the radio call. The main structure was down. An adjacent one, which nobody had been watching closely, had taken enough blast damage that it needed its own line on the assessment. That's the value of a per-structure look over a single damage call: it catches the stuff next door that the strike package wasn't tasked to care about but the re-strike decision has to.

I don't think the fix is faster satellites, exactly, though that helps. It's treating the imagery tasking itself as part of the strike, not an afterthought that gets queued once someone remembers to queue it. A tasking that's already waiting for the next viable pass the moment weapons go away closes more of that gap than any amount of hustling after the fact. The hours between the strike and the pass that matters don't shrink because people want them to. They shrink because someone set the collection in motion before the smoke cleared.

The other thing I've come around to: the assessment that comes out the other end needs to be dated and itemised, structure by structure, not a single verbal "effective" or "ineffective" stapled to the target as a whole. A commander deciding whether to spend another sortie on the same aim point needs to know which parts of it are still standing, structure by structure, and when that picture was taken. That's the whole case for building the BDA workflow around before/after optical imagery that triggers the moment a strike happens, rather than bolting assessment onto the schedule a sensor happened to be running already.

Six hours doesn't sound like much until it's the six hours your re-strike window needed. If that gap is the one you're fighting right now, Battle Damage Assessment is built for exactly that window.