Communication

Part of the Day Skipper Notes series.

Communication was the module I expected to find the least interesting, and it ended up being one of the more useful reframes in the whole course — because almost everything it teaches is a deliberate rejection of natural, conversational language in favour of rigid, disambiguated format, for reasons that only became obvious once I thought about the conditions it’s designed for.

VHF radio: format over fluency

Marine VHF procedure isn’t really about operating a radio — it’s about a strict calling and message format designed to work over poor audio quality, background engine noise, and multiple stations potentially trying to talk at once. A routine call follows a fixed shape: the called vessel’s name (spoken up to three times), “this is,” your own vessel’s name, over. Nothing is assumed or inferred; every exchange explicitly identifies who’s talking to whom, and explicitly hands the conversation back with “over,” precisely because informal conversational cues (tone, pause, inflection) that work face-to-face don’t survive a noisy radio channel.

Channel 16 is the international calling and distress channel — monitored by convention, used to initiate contact or raise an alarm, then routine traffic is expected to move off to a working channel so 16 stays clear for anyone who might need it for an actual emergency. That discipline (get off the distress channel once you don’t need it) is itself a form of communication courtesy the course treats as a hard rule, not a suggestion.

The phonetic alphabet exists because letters get misheard

Spelling out a vessel name or a position reference over a noisy channel using plain letters is genuinely unreliable — “B” and “D” and “E” sound alike under poor signal. The NATO phonetic alphabet (Alpha, Bravo, Charlie…) exists purely to make single letters acoustically distinct from each other even under bad conditions. It’s a small thing to memorize but it’s a direct engineering response to a real failure mode, not tradition for its own sake.

Sound and light signals: communication without radio at all

Before or alongside radio, vessels communicate collision-avoidance intent with sound signals (short and long blasts, with specific meanings — for example one short blast meaning “I am altering course to starboard”) and, in reduced visibility, dedicated sound signals for vessels underway, at anchor, or not under command. Navigation lights (the specific combination and colour of lights a vessel shows at night) communicate a vessel’s type, size, and heading to anyone who can read them, without either party saying a word.

The common thread with VHF procedure is the same: a small, standardized vocabulary that removes ambiguity, because the alternative — improvised signals interpreted differently by different people — is exactly how collisions and misunderstandings happen in exactly the conditions (dark, poor visibility, multiple vessels) where a misunderstanding is most costly.

Distress and urgency calls: the same discipline, higher stakes

This ties directly back to the emergency module: Mayday and Pan-Pan calls use the same fixed-format instinct taken to its logical extreme — a fixed sequence of vessel name, position, nature of distress, assistance needed, persons aboard, repeated for clarity, precisely because a distress call is the worst possible moment to be improvising sentence structure under stress.

The pattern underneath the whole module

Every piece of this module — VHF format, the phonetic alphabet, sound signals, navigation lights — is solving the same problem: making intent understandable when normal conversational communication (tone, context, follow-up questions) isn’t reliably available. Once I saw that pattern, the seemingly arbitrary rigidity of marine radio procedure stopped feeling like bureaucracy and started feeling like the correct engineering response to a genuinely noisy channel — literally and figuratively.