How many frames does a typical search sortie produce?

Ask this before the first sortie of the day, not after the SD card comes back full. A typical sortie produces far more frames than most people guess, and that gap between expectation and what lands on the debrief table is where a lot of the lost time happens.

The rough math

A drone flying a search sector at 10 cm GSD or better, with standard forward and side overlap for photogrammetry (usually 70-80% forward, 60-70% side), is capturing a new frame every second or two depending on ground speed and altitude. A 20-minute sortie at that cadence lands somewhere in the range of 800 to 1,500 individual frames, sometimes more if the aircraft is working a tight grid pattern with a lot of turns.

Stack a few sorties over a shift, across multiple sectors, and a coordinator can be looking at five, ten, fifteen thousand frames by the time the last bird lands. Crewed aircraft running a wider swath at lower resolution produce fewer frames per minute of flight time, but longer loiter times on a search leg close that gap fast.

None of this is a defect in the mission plan. Overlap exists so nothing in the sector falls between two frames unseen. The frame count is a byproduct of doing the coverage right, not a sign something went wrong with the flight.

Why the number matters at debrief

The planning side of a sortie gets a lot of attention: sector boundaries, altitude, overlap percentage, battery budget. The debrief side gets less, and it's where the frame count actually does the most damage. Someone has to look at every one of those frames, or at least enough of them to be confident nothing was missed, and do it fast enough that a credible lead doesn't sit untouched for an hour while the crew reloads batteries for the next leg.

Scrolling a folder of 1,200 images frame by frame, even at a brisk pace, eats the exact window where a coordinator needs to be deciding where to send the next sortie, not squinting at thumbnails. It's also where fatigue shows up. Frame 40 gets real scrutiny. Frame 900 gets a glance, because the person reviewing it has been at this for two hours and the light is starting to go.

This is the real cost of a high frame count. It's the human hours standing between imagery captured and a decision made. A sortie that looked clean on paper, full coverage, no gaps, good overlap, can still fail at debrief if nobody has time to go through all of it properly before conditions change or the search window closes.

What a coordinator can do about it

Flying tighter overlap to cut the frame count usually isn't worth the tradeoff. Loosening overlap to save review time risks leaving gaps in coverage, which defeats the purpose of flying the sector in the first place. The frame count is a fixed cost of thorough coverage.

What's variable is how the frames get reviewed. A sortie's worth of imagery doesn't need a person opening every file in sequence. Search & Rescue Imagery runs detection across the full set and returns a short, ranked list, thumbnails, coordinates, a similarity score against any confirmed hit, so the coordinator's attention goes to the handful of frames worth a second look instead of the thousand that aren't.

That's the real answer to "how many frames does a sortie produce." The number tells you how much review time to plan for, and how much of that time a coordinator can get back by not scrolling through all of it by hand. Run your next sortie's imagery through a candidate list instead of a folder, and see how much of that debrief window you get back.