SAR coordinator study works best when you treat datum, probability of containment, probability of detection, pattern selection, and reporting as one linked decision chain rather than separate topics to memorize. The practical method is scenario cycling: take a written distress case, compute a datum from the reported position and drift inputs, choose and justify a pattern, decide when a negative search means re-datum rather than repetition, and write the coordination reports you would send. This guide builds that chain step by step, with two worked scenarios and a self-check rubric. For administrative questions such as scheduling, consult the relevant authority directly; the international SAR framework itself is maintained through the jointly produced IAMSAR Manual by IMO and ICAO.
Why the datum, not the last known position, anchors your search plan
A datum is your best estimate of where the casualty is now, not where it was reported. The last known position starts the calculation; current, wind leeway, and elapsed time move the estimated search center away from it.
In a simplified maritime practice example, a vessel reported a position fix, and the search planner must account for total drift: sea current, tidal current, and wind-driven leeway acting on the casualty. If the combined drift is roughly 1.5 knots and three hours have elapsed, the datum sits about 4.5 nautical miles from the reported fix, in the direction of the net drift vector. Learning to name each drift component separately matters because a plan built on the reported fix alone can center the search on water the casualty left hours ago.
The conceptual trap is treating the datum as a fixed point you compute once. A datum is a function of time: every additional hour of elapsed time shifts it, so a well-written plan states the datum as a position at a stated time. When you practice, compute the datum at two or three different elapsed times from the same report and watch the search center move. Building that habit makes later decisions — widening an area, re-datuming after a negative search — feel like natural extensions of the same arithmetic rather than new topics.
How POC, POD, and POS connect — and which one you can actually control
Probability of containment asks whether the casualty is inside your search area; probability of detection asks whether your sweeps would find it there; probability of success combines them. In simplified planning terms, POS behaves like POC multiplied by POD.
These three quantities answer different questions, and confusing them leads to poor decisions. A large search area centered on an uncertain datum can achieve high probability of containment, yet a single quick sweep of that area yields low probability of detection because coverage is thin. Conversely, a tiny, tightly covered area can have excellent detection probability while containing almost no chance the casualty is actually there. Naming which quantity you are improving is the discipline: expanding the area works on containment; re-sweeping or slowing down works on detection.
For coordinator practice, the useful exercise is a trade-off table you build yourself: for a given scenario, sketch three options (small area, thorough coverage; large area, thin coverage; moderate area with a planned second sweep) and estimate in words which raises containment and which raises detection. The point is not to produce exact figures — real sweep-width estimation depends on weather, target type, and sensor performance — but to internalize that effort spent on the wrong quantity produces a confident plan that searches the wrong water or misses what it covers.
Choosing between expanding square, parallel track, sector, and contour searches
Pattern choice follows from how confident you are in the datum and what constrains your search units. A tight datum supports an expanding square or sector; a broad or elongated area favors parallel track; variable terrain favors contour searches.
An expanding square search starts at the datum and spirals outward, which suits a single unit working a datum you trust, such as a recent person-in-water report. A sector search concentrates effort around the datum with repeated radial legs, fitting small search objects and short elapsed times. Parallel track sweeps cover long, uniform areas efficiently with one or more units, fitting a drifting target over a broad region or a second, wider phase of search. Contour searches follow a depth line or terrain feature when the casualty is likely on or near it.
Do not learn these patterns as an isolated list; learn each with its failure condition. An expanding square grows inefficient when the datum is poor, because most early effort lands near a wrong center. Parallel track wastes coverage on a very small, well-defined datum. A sector search assumes the search unit can repeatedly pass close to the datum, which traffic or sea state may prevent. When studying, state for each pattern the datum confidence, unit count, and object size under which it makes sense — that conditional reasoning is what scenario questions are built to reveal.
| Pattern | Best datum condition | Key limitation |
|---|---|---|
| Expanding square | Trusted datum, single unit, recent casualty | Effort concentrates near a possibly wrong center if datum confidence is low |
| Sector search | Very tight datum, small target, short elapsed time | Requires repeated passes near the datum; impractical for large areas |
| Parallel track | Broad or elongated area, datum spread along a line | Thin coverage if forced onto too large an area with too few units |
| Contour search | Casualty likely near a depth line, shoreline, or terrain feature | Only as good as the assumption that ties the casualty to that feature |
Worked scenario 1: turning a distress report into a search action plan
A search action plan converts the report into a timed datum, a bounded area, an assigned pattern, and reporting instructions. The classic planning mistake is anchoring the search on the reported position instead of the computed datum.
Scenario: a fishing vessel reports taking water and gives a position fix, then its radio fails. A planner under time pressure centers an expanding square search on the reported fix. In this simplified practice example, the vessel has been drifting with a net current of about 1.5 knots for three hours, so the search center is roughly 4.5 nautical miles wrong before the first unit arrives — and every further hour of delay widens that gap. The mistake is not arithmetic; it is treating the report as the target rather than the input.
The better decision is to compute the datum at the planned commencement time, state it as a position at that time, then bound a search area around it sized to the drift uncertainty, assign a pattern suited to that datum confidence, and note in the plan that the datum will be recomputed if the search is delayed. This matters because the search action plan is the document other units act on: if the plan embeds the wrong center, every unit inherits the error, and later analysis cannot tell whether the casualty was missed or was never inside the searched water at all.
Worked scenario 2: when a search finds nothing — re-datum, repeat, or widen?
A negative search is information, not just a disappointment. The decision to repeat coverage, re-datum with updated inputs, or widen the area should follow from what the negative result tells you about containment and detection.
Scenario: after several hours of expanding square coverage around the datum, units report nothing. A plausible mistake is to keep re-running the same square indefinitely, or to abandon the area on instinct and start a random new one. The first error spends effort re-covering water already searched without improving much, since detection probability rises only with meaningful additional coverage. The second discards your best available estimate without justification. Both stem from not asking which quantity — containment or detection — the negative result has changed.
The better decision sequence is to re-datum first: update elapsed time, revised current estimates, and any new information such as debris sightings, producing a fresh datum at the current time. Compare it with the searched area; if the new datum has drifted outside well-covered water, shift the area. If the datum has not moved much, plan a second sweep of the existing area to raise detection probability, and reconsider target assumptions such as leeway behavior. Report negative coverage and the revised plan to the coordinating level so the wider effort adjusts with you. Practicing this fork — shift, repeat, or widen, each with a stated reason — is one of the highest-value exercises in SAR coordinator preparation.
Dividing the work: coordinator, on-scene coordinator, and the reporting loop
The SAR mission coordinator plans and assigns; the on-scene coordinator directs units at the scene; unit commanders execute and report. The system functions through a continuous loop of situation reports, achieved-coverage updates, and plan revisions.
Study these roles as a division of decisions, not a list of titles. The coordinator level owns the overall plan: datum, area, pattern assignment, and decisions about re-datuming or widening, informed by reports from the scene. The on-scene coordinator translates that plan into concrete unit tasking, manages spacing and safety between units, and consolidates what has actually been searched. Individual rescue unit commanders own execution details the plan cannot foresee, such as pausing for visibility or sea state. Exam-style scenarios often describe friction at exactly these seams — a unit deviating from its assigned leg, or a scene report contradicting the plan — so learn which role is entitled to make which call.
The reporting loop is what keeps the plan honest. Coverage achieved rarely matches coverage planned: units miss legs, weather closes in, and the effective sweep differs from the intended one. Practice writing a short situation report that states position, what was actually searched and when, conditions observed, and any deviation from the assigned pattern. Then practice receiving one and asking what it changes about your containment and detection estimates. A coordinator who can convert a messy field report into a concrete plan revision — and document why — demonstrates the applied decision-making that scenario assessments are designed to observe.
A preparation sequence and self-check rubric for scenario practice
Build your study in five passes: definitions and roles, datum arithmetic on paper, pattern-selection drills, full scenario write-ups, then timed case analysis with reports. Grade your own work against stated observations, treating scores as learning milestones only.
A realistic sequence: first, map the SAR system — roles, definitions, and the coordination chain — until you can explain who decides what. Second, drill datum computation by hand from written inputs: given a reported position, drift components, and elapsed time, produce a datum stated with its time, and repeat at two different elapsed times. Third, do pattern-selection drills where the only task is choosing and justifying a pattern from datum confidence, unit count, and target description. Fourth, write complete search action plans for full scenarios, including what you would do if the search returns nothing. Fifth, run timed case analyses that end with a situation report, because time pressure changes how carefully people reason.
Use this self-check rubric on each full scenario: your datum is stated as a position at a named time; your search area is bounded and its size is justified against drift uncertainty; your pattern choice names the datum confidence and constraints behind it; your negative-search paragraph says whether you would repeat, re-datum, or widen, and why; your situation report states achieved versus planned coverage. A useful milestone is scoring all five items correctly on two consecutive scenarios; that signals the decision chain is reliable, not that any particular exam outcome is guaranteed. Treat misses as specific topics to re-drill rather than a general verdict on your readiness.
- Readiness check 1: you can compute and re-state a datum at a new time without re-deriving everything from scratch.
- Readiness check 2: for any pattern, you can state its best-use condition and its failure condition in one sentence each.
- Readiness check 3: given a negative-search scenario, you name which probability quantity your next action targets and why.
- Readiness check 4: your written plan and report would let another reader reconstruct what was searched, when, and under what assumptions.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.