How to brief an aircrew before a search sortie

Every sortie brief has to solve the same five problems before the aircraft leaves the ramp: where to look, how to look there, what to do if something turns up, what to do if nothing does, and how to get everyone back safely. Skip one and you find out about it mid-flight, usually at the worst time.

A good brief is a short list of facts the crew needs once, right before they need them, in the order they'll use them, not a speech.

What the crew actually needs before engine start

Cover these, in this order, and move on:

• The sector. Boundaries by lat/long or named features, not "the area north of the lake." Hand them the sector on paper or on the tablet, not just a verbal description.
• The pattern. Track spacing, altitude, direction of first leg. If it's a creeping line ahead or an expanding square, say so and say why.
• The subject description. Clothing color, last known heading, mobility, anything from the PLS/LKP interview that changes what a hit looks like from altitude.
• Comms plan. Primary and backup frequency, check-in interval, and what "lost comms" means for this sortie specifically, not the generic SOP.
• Weather and light. Ceiling, visibility, and when the sun angle turns the sector into glare on the return leg.
• Fuel and bingo. When they turn for home regardless of what's happening in the sector.
• What to do on a find. Mark the GPS point, don't orbit low enough to spook anything, call it in, keep flying the plan unless told otherwise.

That's the brief. If you're adding more than that, you're probably briefing the whole op order instead of the sortie.

Where the rushed brief costs you later

The sortie that gets the thinnest brief is usually the third or fourth of the day, when everyone's tired and the coordinator is juggling two more crews waiting on the ramp. That's exactly when a vague sector boundary or a skipped comms check turns into overlap with the previous sortie, or a crew flying a pattern nobody else can reconstruct at debrief.

That reconstruction problem shows up again an hour later, when the aircraft is back and someone has to go through however many thousand frames it shot looking for anything that matches the description from the brief. If the tasking brief was specific, that review goes fast: the sector's known, the subject description is known, and you're checking a short list against both. If the brief was loose, the review turns into a second search, this time through imagery instead of terrain.

Search & Rescue Imagery was built for that second half of the job. It runs detection and similarity matching over a flown sector and hands the coordinator a ranked list of candidate frames, thumbnails and coordinates and a score against any confirmed hit, instead of a raw folder with no good way to tell what's worth a second look. The tighter the brief going out, the sharper that candidate list coming back. If the debrief after your next sortie is eating the hour you don't have, see what reviewing a flown sector looks like as a ranked candidate list instead of a frame-by-frame scroll.

A one-page version for the clipboard

If you need something you can laminate: sector (drawn, not described), pattern and altitude, subject description, comms and lost-comms procedure, bingo fuel, find procedure. Six lines. Everything else is useful to know but doesn't belong between the crew and the aircraft door.

Write it the same way every time, even on sortie four of the day. A crew that gets a consistent brief flies a more consistent pattern, and a consistent pattern is what makes the imagery worth reviewing afterward instead of just filed away. Worth testing on your next flown sector.