What is sweep width in search and rescue planning?

If you've sat through a SAR planning course, you've seen the term thrown around like everyone already knows what it means. Sweep width (W) is the measure of how wide a strip of ocean, water, or terrain a given sensor and searcher combination can effectively cover while moving along a track line, accounting for the fact that detection probability doesn't drop off at a clean edge. It fades.

Here's the plain version: picture a searcher flying a straight line. Directly under the track, they'll spot almost anything that's there. A hundred meters off to the side, detection odds drop. Three hundred meters off, they're low but not zero. Sweep width is the width of a hypothetical corridor where everything inside gets detected and everything outside doesn't, chosen so the math works out the same as the real, fuzzy detection curve. It's a planning shortcut, not a physical boundary you'd ever see from the cockpit.

Why this number matters for coordinators

Sweep width feeds directly into track spacing, which feeds directly into how many legs you need to fly to cover a sector at a given probability of detection (POD). Get the sweep width wrong and you either fly tracks too far apart, leaving gaps between passes, or too close together, burning fuel and crew hours covering ground twice.

The National Search and Rescue Supplement (NSS) publishes sweep width tables for different search object types, cross-referenced against sensor (visual, radar, IR), platform, and environmental conditions like sea state, visibility, and light. A life raft in calm water with good visibility has a very different sweep width than a person in the water during marginal visibility or rough seas. Coordinators pull the row that matches their conditions, plug it into the track spacing formula alongside the target POD, and get a leg spacing for the search plan.

The practical wrinkle: those tables assume a trained observer scanning under reasonable workload. Fatigue, glare, sensor degradation, and a search object that doesn't match the assumed profile (wrong color, partially submerged, obscured by debris) all push the effective sweep width down from the table value. Effective sweep width is the number you should be planning against: the published figure adjusted for what's really happening on this sortie, not the textbook case.

Detection range measures something else

Detection range for air search is the distance at which a crew member can first pick out a target under ideal, focused-attention conditions, essentially a single-point measurement taken in good viewing conditions dead ahead. Sweep width is built differently. It's an integrated quantity, detection probability summed across the whole lateral range left and right of the track, averaged over a realistic scan pattern as the aircraft moves. A bright orange raft might have a strong detection range on a clear day, and the sweep width for that same sortie can still come in lower once you account for the observer splitting attention across both sides of the aircraft at a scan rate that's high relative to groundspeed.

This distinction matters at debrief as much as at planning. If a sector gets searched and the POD was computed off a sweep width that didn't hold up (haze rolled in, the swell built, the spotter was on their third sortie of the day), that sector's coverage was lower than the plan assumed. Knowing that changes whether you reassign the sector for a re-fly or move the search area based on drift.

Where the review backlog comes in

None of the sweep width math changes what happens after the aircraft lands with a card full of imagery. A flown sector at sub-10 cm GSD still produces thousands of frames, and the planning number that got you good coverage doesn't help a coordinator review it fast. Search & Rescue Imagery runs detection and similarity search over that sortie's imagery and hands back a ranked candidate list, thumbnails, coordinates, a similarity score against any confirmed hit, instead of a scroll-through. You can see how it fits into a debrief on the Search & Rescue Imagery landing page.

Get your sweep width right at the planning table, and let the review of what the aircraft actually brought back move at the same pace your sortie did.