Treat radar interpretation as a frame-selection problem, not a button-pressing problem. Readiness checks: (1) hand-plot a two-fix problem and report CPA, TCPA, and relative speed within your own tolerance; (2) explain in two sentences how sea and ground stabilization differ and what each distorts; (3) read target aspect from the heading marker, not the vector; (4) predict how a stated alteration changes CPA before describing the maneuver. Administrative matters such as eligibility and approved training sit with the U.S. Coast Guard National Maritime Center; confirm them there.
Reading bearing drift and range rate before trusting any vector
Before drawing anything, quantify two raw observations: how fast the bearing changes and how fast range closes. These numbers alone bound the problem and expose unreliable first impressions that a plotted or computed vector might otherwise overwrite.
Bearing drift and range rate are the two primitive measurements from which everything else follows. A bearing that barely moves while range steadily shrinks describes a target converging on your position; a bearing swinging rapidly through the bow or quarter with moderate range change describes a passing target. Committing to a vector before stating these two rates means committing before you have evidence.
Make it a habit to verbalize both numbers aloud on every contact: 'bearing drifting two degrees in six minutes, range closing one point four miles.' This habit matters most when the display is misconfigured or ambiguous, because the raw rates come from the history of the blip itself and do not depend on which vector mode is active. When a vector looks surprising, return to the raw rates and ask whether the vector can reproduce them; if it cannot, the setup, not the target, is the problem.
Relative vector versus true vector: two different questions
The relative vector answers how the target will move across your screen; the true vector answers what the target is actually doing through the water. Each is correct for its own question, and mixing their answers produces wrong decisions.
The relative vector, extended from the target blip, ends at the point of closest approach; its length and direction encode the combined motion of both vessels. The true vector instead shows the target's own course and speed. A target that is nearly stopped relative to your ship shows a short relative vector but may display a long true vector; a fast vessel moving nearly parallel to you can show a long true vector but a modest relative drift across the screen. Neither vector is 'more true' — they encode different frames.
The practical rule is to decide the question first, then choose the vector. For collision risk and CPA, work with the relative picture, whether as a vector or a manual plot on the history of the blip. For understanding what the other ship is doing — is she anchored, drifting, heading out at speed, matching your course — the true vector is the tool. In exam-style scenarios, check that each conclusion you state is being answered by the vector that can actually answer it; a conclusion about the target's route drawn from a relative vector is a frame mismatch, not an observation.
- Relative vector: ends at the closest point of approach; use for CPA, TCPA, and risk assessment.
- True vector: shows target course and speed through its frame of reference; use for intent and classification.
- A short relative vector does not mean a slow target, and a long true vector does not mean an inbound one.
Sea stabilization versus ground stabilization and the drift-angle trap
Sea stabilization references motion to the water; ground stabilization references it to the seabed. When current is present, the same traffic picture reads differently in each, and the drift angle between heading and track is the trap.
In ground stabilization, target vectors are referenced to the seabed, so a vessel making way through the water also displays the current she is in; her displayed track may differ noticeably from her heading. In sea stabilization, vectors are referenced to the water mass, so a vessel's vector approximates her course and speed through the water, which is the frame in which her maneuvering and her aspect are naturally described. When all vessels share the same current field, the relative geometry — CPA, TCPA, relative bearing drift — is the same in both modes; what changes is how individual vectors and headings read.
This is why stabilization choice changes interpretation rather than the underlying risk. A ground-stabilized vector that angles away from its heading marker is usually showing drift, not a vessel steering an odd course. Conversely, a sea-stabilized display will not show you where a drifting or anchored object sits relative to the seabed, which is exactly what ground stabilization is for. Condition your claims accordingly: a vector statement about where a target is going over the ground is valid in ground stabilization, while a statement about her course through the water needs the water frame or an explicit drift correction.
| Feature | Sea stabilization (water reference) | Ground stabilization (seabed reference) |
|---|---|---|
| Reference frame | Water mass; speed through water | Seabed; speed over ground |
| Own ship on screen | Holds course and speed through water | Shows set and drift with the current |
| Target vectors show | Course and speed through the water | Track over the ground, including current |
| Heading versus vector | Typically aligned when steaming straight | Diverge by the drift angle when current is present |
| Natural use | Aspect, maneuvering, and water-frame prediction | Fixed-object monitoring, drift, anchorage, pilotage |
Aspect: why the heading marker, not the vector, classifies a target
Aspect describes where a target's bow points relative to your line of sight, and it comes from her heading. Her course over the ground is a different quantity, and using it as a substitute misclassifies the encounter.
Aspect is the angle between the target's heading and the bearing line from you to her; it tells you how much of her bow or stern you are looking at. It is read from the target's heading marker combined with the bearing, and it is what determines, for example, whether you are looking at a bow-on presentation or a broad quarter. The target's true vector tells you her motion, not her orientation; in current, the two can differ by the drift angle, sometimes by many degrees.
Build a drill around this: for each contact, state heading, vector direction, and computed aspect, and note when they disagree. Any disagreement is information about current, wind leeway, or shallow-water effects — or about your own display configuration. In exam-style scenarios, a described target whose track is wide of her heading is inviting exactly this check: classify her by heading, describe her motion by vector, and keep the two statements explicitly separate in your answer. Collapsing them into a single 'the target is heading such-and-such' claim is the specific error this concept exists to prevent.
Worked scenario: two fixes, one plot, a quantified decision
Given two radar fixes of the same target, a manual relative-motion plot converts raw observations into CPA, TCPA, and relative speed — numbers you can decide with, instead of an impression of the bearing.
Setup: own ship on 000 degrees at 12 knots. At the first observation the target bears 040 degrees relative at 8.0 miles; six minutes later she bears 038 degrees at 6.6 miles. The tempting shortcut is to see the bearing easing a couple of degrees and assume she will pass ahead clear. Plot instead: the range closed 1.4 miles in six minutes, so relative speed is about 14 knots, and the bearing drift is only about 2 degrees for that much closure — far too slow for a comfortable bow crossing. Extending the relative motion line gives a CPA of roughly 1.3 miles and a TCPA of roughly 27 minutes from the second fix (about 33 minutes measured from the first fix).
Why it matters: at 14 knots of relative speed, 1.3 miles of passing distance is consumed in under six minutes on either side of the closest point, and the 2-degree bearing drift would have looked like 'passing ahead' right up until it stopped looking like it. The mistake was treating a slow-bearing-change impression as a passing assessment. The better decision sequence is: quantify the rates, extend the relative motion line, then choose an early, generous alteration and verify afterward that the plotted CPA has opened as intended. The lesson is not that this particular geometry is dangerous in general; it is that the plot converts a feeling into a number before time runs out.
Worked scenario: stabilization mode and a misread crossing geometry
A ground-stabilized vector can point far from a target's heading when current is present. Reading course, aspect, and maneuver predictions from the wrong frame misclassifies the encounter and distorts maneuver planning.
Setup: your display is ground-stabilized with satellite-derived speed over ground. A target on your starboard bow shows a true vector angled well to the right of her heading marker; her vector track suggests she will pass broadly astern. The mistake is reading that vector as the course she is steering. Suppose she is heading 090 at 10 knots through the water while a current sets her toward the south: her ground track angles away from her bow by the drift angle, and her aspect as seen from your position is a bow presentation, not the broad-off track the vector suggests. Because her heading — not her drift — governs how the encounter presents, the geometry you assumed from the vector is the wrong one.
The better decision: check the divergence between heading marker and vector on every true-vector contact, and when current is a factor, switch to a sea-stabilized display — or correct for drift explicitly — before judging aspect and before running a predicted maneuver. Predicted alterations are computed in the selected frame, so a prediction made about a drifting vector answers a question about ground track, not about how your turn changes the meeting in the water frame. The conditional to keep in mind: when both vessels sit in the same current, CPA and TCPA are unchanged between modes — what changes is interpretation, classification, and how your own maneuver will read afterward. Verify with the other ship's heading data, not with assumption, whenever the divergence is significant.
A plotting exercise with a self-check rubric and preparation sequence
Rebuild scenario skills by hand: plot two fixes, extract CPA, TCPA, and relative speed, then grade yourself against stated tolerances and a fixed sequence of interpretation checks.
Exercise: own ship on 090 degrees at 15 knots. First fix: target bears 020 degrees relative, range 9.0 miles. Twelve minutes later: bearing 019 degrees, range 6.6 miles. Plot the relative motion line, extend it, and report CPA, TCPA, and relative speed. Expected observations: range closed 2.4 miles in 12 minutes, so relative speed is about 12 knots; the extended relative motion line gives a CPA of roughly 0.4 miles and a TCPA of roughly 33 minutes from the second fix (about 45 minutes measured from the first fix). Then answer the interpretive question: which single alteration of your own course would open this CPA fastest, and how would you verify on the next fix that it worked? Repeat the exercise with the same fixes but a deliberately rotated own-ship course to confirm your construction, not your memory, is doing the work.
Self-check rubric — learning milestones, not passing predictions: CPA within about 0.3 miles of a careful construction; TCPA within about 5 minutes; relative speed within about 1 knot; a one-sentence statement of which frame each reported quantity belongs to; and a stated verification step for any proposed maneuver. A realistic preparation sequence you can adapt: first week, relative-motion construction fundamentals on plain paper until two-fix problems are mechanical; second week, frame drills — converting between relative and true vectors, and identifying heading versus track divergence; third week, timed scenario sets that force stabilization-mode switches and aspect calls; final phase, full mock sessions followed by a written self-debrief against the rubric, with extra sets targeted at whichever check you missed. You are ready to sit a practice session when every rubric line is met on consecutive attempts, not on a single lucky plot.
- Milestone 1: two-fix CPA/TCPA construction accurate to the stated tolerances.
- Milestone 2: correct frame named for every reported quantity (relative, water, ground).
- Milestone 3: aspect stated from heading, with drift angle identified separately.
- Milestone 4: maneuver stated with its predicted effect on CPA before execution.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.