1The lesson in plain words
In one sentence…
A useful radio log keeps traceable facts: UTC time, identity, equipment, result, defects, actions, and corrections.
What do you keep available?
Keep the station licence and certificates, equipment manuals, and required current service publications available.
What do you record?
So another operator can reconstruct the event, record UTC date and time, identity, channel or equipment, event or test, and result.
How do you handle a fault?
Add the defect or corrective action, state who was responsible, and record the assigned follow-up.
What can you not conclude?
A neat example does not prove a real call. A self-test shows only what it observed; it does not establish coverage, compliance, or RCC status. Keep observation and inference separate.
2Step by step
Traceable radio-log entry
- 1
Identify the relevant station, equipment, service, and identity.
You link the record to the station or service involved.
- 2
Record the UTC date and time and describe the event.
UTC orders events consistently.
- 3
Record the observed result, including any failure.
You preserve what the test or event showed.
- 4
Record who was responsible and what follow-up was assigned.
The log shows who responds and what remains outstanding.
- 5
Preserve the original and make corrections auditable.
Traceability prevents an example being presented as a real event.
3Key data
- Station licence
- Available
- Operator certificates
- Applicable and available
- Equipment instructions
- Available
- Service publications
- Current and required
- Log time
- UTC
- Normal ship MMSI
- MIDxxxxxx
- Ship group identity
- Starts with 0
- Coast station identity
- Starts with 00
4Key points
- 1.
UTC time, identity, channel/equipment, result, defect, action, and responsible operator.
- 2.
Correct without erasing the original; preserve traceability.
- 3.
The flag administration sets many equipment, publication, and retention details.
- 4.
An example or self-test proves neither a real event, coverage, nor compliance.
5Frequent mistakes
Wrong: "This sample log proves that the call happened."
Right: A neat example does not prove a real call; keep it identified as fictional.
Wrong: "MCA daily, weekly, and monthly tests apply to every flag."
Right: They are evidence for UK ships, not universal requirements.
Wrong: "If the self-test responds, I know the coverage and RCC status."
Right: A self-test proves only what it observed; coverage and RCC need additional evidence.
6Practice case & exam keys
Situation
A fictional weekly DSC test responds locally, but the exercise has no coast-station receipt. The learner must complete a sample record.
What may the record claim?
Show the answer →
It may claim that the local test response was observed at the stated UTC time; it must not claim coast-station receipt.
Why: The observation and the inference require different evidence. A traceable log helps the next operator investigate without overstating what the equipment test established.
Exam keys
If you see «time», look for «UTC»: it is the log's time basis.
If you see «MMSI pattern», remember: a pattern does not authorise inventing a real identity.
If you see «local test», do not conclude «received by the coast station»: evidence is missing.
How to read it
Think of the log as an evidence chain: another operator should reconstruct what happened and what follow-up was assigned.
Separate observation from conclusion: a traceable correction improves the record, but an available document is not proven current for this ship or voyage.
7Full lesson & sources
Open the full lesson (diagrams and official references)
Keep the ship station licence, applicable operator certificates, equipment instructions and required current service publications available. Exact carriage, display and retention requirements depend on the applicable rules and flag administration; the entire IMO reading list for an RCC is not automatically mandatory aboard every ship. Consult current GMDSS Master Plan and radio-service information before the voyage.
Record safety-significant communications, tests, false alerts and cancellations, equipment defects and corrective action with UTC date/time, relevant identities, channel or equipment, outcome and responsible operator. Keep corrections traceable. A normal ship MMSI is MIDxxxxxx; group ship identities start with 0 and coast station identities with 00. Do not invent station identities for real test calls or present example records as actual events.
A station is a controlled record
Radio-station management joins identity, authorisation, equipment instructions, current service information, and traceable records. The exact carriage and retention rules come from SOLAS and the flag administration. A learner can build a reliable record without pretending that one national checklist applies everywhere.
What a useful log entry contains
For study purposes, a safety-significant entry should let another operator reconstruct what happened. Include UTC date and time, the relevant identity, channel or equipment, event or test, result, defect or corrective action, and responsible operator where the applicable log requires it. Corrections should remain traceable. A neat example is not evidence that a real call occurred.
- 1Identify the station, equipment, or service involved.
- 2Record the event time in UTC and describe the event.
- 3Record the observed result, including any failure.
- 4Record who was responsible and what follow-up was assigned.
- 5Preserve the original entry and make corrections auditable.
| Record field | Why it helps | Typical uncertainty |
|---|---|---|
| UTC date/time | Orders events consistently | Clock accuracy and local log rules |
| Identity | Links event to station or service | Allocation and registration are external |
| Test/result | Shows what was observed | A local test may not prove end-to-end service |
| Defect/action | Supports follow-up | Repair acceptance belongs to responsible authority |
Identity without invention
ITU Radio Regulations Article 32.5A requires administrations to arrange assignment and registration of GMDSS ship identities and to make registration information available to rescue coordination centres continuously. That does not allow a learner to infer a real identity from a pattern alone. Use fictional values in a worksheet and label them as examples. Never make a real test call with invented data.
The station licence, operator certificates, equipment manuals, current GMDSS Master Plan material, and radio-service information each answer different questions. Availability of a document does not prove that it is the current document for this ship or voyage. A source shelf is a control, not a compliance certificate.
UTC versus inference
UTC is the timestamp convention used by the radio record in this lesson. It is a fact to record, while “the test proves the coast station received us” is an inference that needs separate evidence. Similarly, an equipment self-test can show the facility responded; it does not establish current coverage, legal carriage, or an RCC's operational status.
This distinction makes a study log useful without turning it into a false official record.
Sources: ITU RR 2024, Article 32.5A; MCA Master's Guide, GMDSS Log Book §§5.1–5.3; IMO GMDSS circular index.
Official references · 2026-09-09
8Test your knowledge
What should a useful log entry contain?
Keep studying…
Last reviewed: