This guide organizes NFPA 1006 Dive Rescue Technician study around decisions rather than definitions: naming rescue versus recovery mode before any deployment, treating the tender and diver as one working unit, and matching a search pattern to the evidence you actually hold. Two worked scenarios show how a defensible-looking choice can be the weaker one, and a tabletop drill with a self-check rubric lets you rehearse the whole chain without open water. Study each section's decision first, then attach the vocabulary that supports it, so case scenarios read as choices instead of trivia.
Rescue Mode vs. Recovery Mode: The Decision That Changes Every Task
Rescue mode assumes a savable victim and justifies speed and aggressive risk; recovery mode assumes time has passed and shifts weight toward diver protection. Naming the mode out loud is the first call on any dive scene.
In a training framework, rescue mode compresses everything: fewer divers in the water at a time, a rapid search anchored to the point last seen, and a surface team staged for immediate support. Recovery mode stretches the timeline, allowing fuller search patterns, more redundancy, and stricter exposure limits. The technician's job is to justify the mode from evidence — a credible witness and a recent submersion support rescue; a cold case with no witness supports recovery. Everything downstream inherits that call.
Worked scenario: a car is submerged in a pond, and a bystander reports the occupant surfaced once about eight minutes ago before going under. A plausible mistake is treating this as a routine vehicle recovery and planning a full-grid sweep with multiple teams. The stronger decision is rescue mode: one tender-controlled diver sent directly on a tether to the witnessed point, with a backup diver suited and staged. It matters because the mode drives pattern, staffing, and risk tolerance — mislabeling it burns the survivable window in the drill and, in the field, the real one.
Why the Tender, Not the Diver, Owns Navigation Underwater
In zero-visibility water a diver's bearings are unreliable, so navigation is tender-controlled: the tender holds tether tension, tracks the diver's heading, and moves the diver around the search point sector by sector.
The tether is a control line, not just a safety line. A standard training rhythm has the tender directing each movement, the diver acknowledging with a pull, and the tender logging headings so the arc stays true. Signal sets vary between agencies and instructors, so treat any published code as an example rather than a universal standard — the durable skill is the principle: one party owns direction, the other confirms, and every command produces an acknowledgeable action.
The classic breakdown is a diver who navigates independently: the line goes slack, the arc drifts, and the tender loses the diver's position entirely — the same slack that invites entanglement. The corrective habit is bidirectional tension: the tender keeps light, consistent tension, the diver keeps a hand on the line, and any interruption triggers a stop-and-confirm exchange. Audit your tabletop work the same way — every diver movement on your diagram should trace back to a logged tender instruction.
Choosing a Search Pattern: Matching the Pattern to the Evidence
Pattern choice follows two questions: do you have a point last seen, and how large is the area? A witness-anchored arc, a jackstay grid, and a free swim solve different problems and fail in different ways.
When a witness can point, the tender-controlled arc is the default training answer because it concentrates effort where the victim most likely is. The tender rotates the diver through heading sectors from a fixed shore point, overlapping each pass. The scenario that punishes arc habit is the vague report — somewhere off the dock — where an unverified point can absorb hours of precise, well-executed searching of the wrong water. Verify the point before committing the pattern to it.
Without a usable point, the jackstay grid replaces guesswork with lanes: a baseline line is set, and the diver sweeps parallel tracks between anchors, so any missed gap is identifiable rather than invisible. It costs setup time and equipment, which is why rescue-mode scenes rarely open with it. Practice articulating the trade cleanly: arcs buy speed but depend on point accuracy; grids buy completeness at a time cost. In case-analysis work, state the dependency instead of just naming a pattern.
| Pattern | Best fit | Strength | Main weakness |
|---|---|---|---|
| Tender-controlled arc | Credible point last seen, small area | Fast, simple, focused on the likeliest spot | Coverage collapses if the witness point is wrong |
| Jackstay / grid | No reliable point; large or featureless area | Systematic, complete, verifiable lanes | Slow setup; more line and staffing |
| Free swim | Emergencies, short-distance checks | Fastest to deploy | Poor accountability in zero visibility; easy to lose bearings |
Scenario Drill: The Fuel Sheen That Should Have Stopped the Dive
Contaminated water changes the mission from search to exposure management. This scenario turns on reading environmental evidence early and treating an abort as a competent decision, not a failure of nerve.
Worked scenario: your team is dispatched to a flooded quarry where a vehicle went off the ramp overnight. On arrival, a rainbow sheen films the surface and you smell fuel. A plausible mistake is launching anyway because the sheen looks minor and the diver is suited. The stronger decision is to hold the dive, reassess the operation toward a recovery posture, and require upgraded exposure protection plus a decontamination corridor before any entry. It matters because contaminated-water exposure is an injury pathway that early reading of surface evidence can catch.
Build this as a trigger list you rehearse until it fires automatically: sheen or odor, dead fish, outfalls or industrial runoff, ice, visible current, and submerged entanglement sources such as cables and fences. Each trigger has a different response — some upgrade PPE, some move you to recovery posture, some end the dive until specialized support arrives. When you narrate scenarios to yourself, force the abort option to compete: state what evidence would justify continuing and what would end the dive.
Pre-Dive Risk Assessment: Turning a Hazard List into a Go/No-Go Call
A risk assessment is only useful when each hazard maps to a named control: a PPE change, a posture change, a staffing change, or an abort. Practice producing that mapping in one breath for any scenario you study.
Group public safety diving hazards into families you can scan quickly: environmental (current, ice, temperature, weather), contamination (chemical, biological, sewage), physical (entanglement, submerged structures, boat traffic), and physiological demands such as thermal stress and workload in heavy suits. Scanning by family prevents tunnel vision on the hazard that is most visible — a strong current — while the quiet one, a submerged fence line, goes unaddressed.
Then convert each identified hazard into exactly one named control, and let the pattern of controls drive the call. Fuel odor maps to exposure protection and decontamination; current maps to tender positioning and tether management; entanglement sources map to line discipline and cutting-tool accessibility. A go decision you cannot state as a hazard-control pair is not yet a decision. That identify-control-decide-document chain is the structure to rehearse for case-analysis work.
Tabletop Exercise: Last-Seen-Point Drill with a Self-Check Rubric
Run a paper drill: convert a witness statement into a point last seen, run a tender-controlled arc on paper, and grade yourself against a rubric that mirrors the full decision chain, including abort criteria.
Setup: sketch a pond with a dock. The witness says the swimmer surfaced roughly 20 feet off the dock's end, then submerged. Mark the point last seen, place the tender at the water's edge nearest to it, and draw the arc sectors a single tethered diver would sweep at a stated radius, logging a heading change every quarter turn. Expected observations: the arc is centered on the witnessed point, sectors overlap slightly, and headings are recorded rather than guessed.
Grade honestly against the rubric below; these are learning milestones, not passing predictions. If you missed the mode call, redo the drill with three different dispatch scripts until naming the mode is automatic. If your headings wandered, shrink the sector size on paper. When you can complete the whole drill, abort criteria included, in a few minutes without notes, the same chain will hold up under exam-style case questions.
- Named rescue or recovery mode before any deployment, with one sentence of justification
- Converted the witness statement into a marked point last seen on the sketch
- Chose the arc pattern and can state its dependency on the witness point's accuracy
- Logged headings and acknowledged every tender instruction during the drill
- Stated at least two abort criteria before starting the dive
A Five-Step Preparation Sequence and Concrete Readiness Checks
Sequence your study from decisions to speed: master the mode distinction, drill patterns on paper, rehearse tender-diver communication, run mixed scenarios, then compress your decision narration until it is fast and complete.
Order matters because each step reuses the previous one: pattern drills make sense only once mode is settled, and communication drills only matter inside a pattern. Working on paper first is not a limitation — it isolates the decision skills that underwater time cannot teach efficiently, and it lets you repeat a scenario until the chain is automatic. Keep every drill written or spoken, because silent reading hides the gaps the rubric exposes.
Treat these as readiness checks: you can justify a mode call in one sentence; you can convert any witness phrasing into a marked point and state the pattern's dependency on it; you can name a specific control for each hazard family; and you can complete the full decision narration, abort criteria included, without notes. If any check wobbles, loop back to its step rather than rereading everything — the sequence is built for that.
- Step 1: Build a two-column rescue/recovery comparison from your own notes and say the justification aloud for five sample dispatches.
- Step 2: Draw all three patterns from memory and write one sentence on when each is the wrong choice.
- Step 3: Rehearse a line-signal exchange with a partner, alternating tender and diver roles, and log headings for a full arc.
- Step 4: Run mixed tabletop scenarios — witnessed rescue, unwitnessed recovery, contaminated site — and force the abort option to compete in each.
- Step 5: Timed closing drill: narrate mode, point last seen, pattern, controls, and abort criteria in under two minutes per scenario.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.