WPC GMDSS GOC Exam (India) common mistakes
WPC GMDSS GOC Exam (India) · Understand the traps and how to avoid them.
When writing a DSC distress alert, the candidate selects the correct distress nature (e.g., 'Fire/Explosion') but omits or fumbles the position/time field, or transmits the alert on a routine/ship-to-ship call instead of the designated distress button sequence, then cannot state what happens next (auto-retransmission of the distress alert by the coast station, wait for acknowledgement, or 5-minute retransmit rule).
Candidates memorise the 'red button' and the menu tree in isolation from the underlying logic: DSC distress alerts are sent on 2187.5 kHz (MF) or Channel 70 (VHF) as an all-ships distress call with a mandatory position/time and nature-of-distress, and the operator must know the acknowledgement and confirmation-of-distress flow. Practising only the button press, without rehearsing the full alert-to-SAR-coordination sequence, leaves the procedural reasoning untested.
What to do instead
Rehearse the full sequence aloud for both MF/HF and VHF: press distress for 5 s, confirm the nature of distress, confirm position and UTC time (updated from GPS), transmit, then monitor the distress frequency for acknowledgement for at least 5 minutes before any retransmission. Practise writing out the DSC message fields (format specifier, address, category, nature, position, time, subsequent communication) on paper and check each field against the ITU Radio Regulations Article 32/33 requirements.
In a distress, urgency, or safety radiotelephony call, the candidate uses the wrong priority word or misplaces it: saying 'MAYDAY' where 'PAN PAN' is correct (or vice versa), repeating the priority word three times when the procedure calls for a different pattern, or inserting the priority word after the station identity instead of before it.
The three priority signals (MAYDAY, PAN PAN, SECURITE) look similar in drills, and candidates practise the distress call most often, so the urgency and safety formats get less rehearsal. Under exam pressure the candidate defaults to the most familiar word, and the fixed order of the call (priority signal x3, THIS IS, station identity x3, call sign, position, nature, assistance required, etc.) is recalled as a loose list rather than a template.
What to do instead
Build a one-page template for each of the three calls with the exact word order and repetition pattern, and drill them by writing out and then speaking five examples each, including a MAYDAY RELAY and a distress acknowledgement. Deliberately practise the 'wrong' cases: a vessel in urgent but non-distress need (PAN PAN) and a navigational safety broadcast (SECURITE), so the discriminator is the situation, not the word.
On Inmarsat/satellite questions, the candidate confuses which service or terminal handles which function: mixing up Fleet/FBB vs Fleet 77/Inmarsat-C vs Mini-C, or stating that Inmarsat-C provides voice distress, or naming the wrong ocean region/LES for a given service, or forgetting that the Inmarsat-C distress alert is a two-stage (send alert then confirm) procedure requiring the correct LES and a position update.
Inmarsat product families have overlapping names and changing generations (Inmarsat-C, Fleet 77, FleetBroadband, and the newer Fleet Xpress), and candidates study from mixed-generation notes. The distinctions between store-and-forward messaging (Inmarsat-C), voice (Fleet), and GMDSS distress priority are abstract unless tied to a terminal the candidate has seen.
What to do instead
Make a comparison table with columns: terminal, service type (voice/data/store-and-forward), GMDSS role (distress alerting, MSI reception via SafetyNET, general comms), and the exact distress activation steps. Learn the Inmarsat-C distress alert as a numbered procedure (select distress, confirm LES, confirm position, press send, await confirmation) and test yourself by covering one column at a time.
On EPIRB and SART questions, the candidate gives the wrong activation method or the wrong operational behaviour: stating a SART shows a continuous solid line on the radar screen instead of a line of 12 dots, or claiming a SART works at long range, or describing an EPIRB as transmitting on VHF Channel 16, or not knowing the 406 MHz COSPAS-SARSAT function versus the 121.5 MHz homing signal.
The two devices are studied together as 'distress beacons', so their distinct technologies blur: EPIRB = 406 MHz satellite alert plus 121.5 MHz homing; SART = 9 GHz radar transponder giving a 12-dot line at short range. Candidates also recall the older 121.5 MHz-only EPIRB era and mix it with current 406 MHz operation, and the SART's dot pattern is often remembered as a 'blip' or 'line'.
What to do instead
Learn each device by its physics: EPIRB transmits a coded 406 MHz burst to COSPAS-SARSAT (with 121.5 MHz for local homing), SART responds to 9 GHz radar with a swept-frequency reply giving 12 equidistant dots on the PPI out to roughly the radar horizon. Draw the radar screen from memory, and state the range, frequency, and activation method (manual/water-activated) for each device in a three-line summary you can reproduce.
On NAVTEX and MSI questions, the candidate cannot state the NAVTEX frequency (518 kHz international, 490 kHz national, 4209.5 kHz), the meaning of the B1/B2/B3/B4 message structure, or the difference between NAVTEX and SafetyNET/Inmarsat MSI. They also fail to explain what to do when a NAVTEX message is received with an error or is not addressed to their station, or how the 518 kHz transmission schedule and range (about 200-400 nm) affect reception.
NAVTEX is taught as a list of frequencies and message types without the message-structure logic, so candidates cannot reason about which station, which message type, or which frequency applies. The relationship between NAVTEX (MF/HF broadcast, coastal), SafetyNET (Inmarsat EGC, global), and HF NBDP MSI is rarely consolidated, and the receiver's automatic rejection of already-received or non-addressed messages is not linked to the B1-B4 header.
What to do instead
Memorise the NAVTEX message format as B1 (station ID) B2 (message type A-Z) B3 (message number) B4 (time of origin), and learn the frequencies as a set: 518 kHz international English, 490 kHz national language, 4209.5 kHz for tropical/remote areas. Build a table comparing NAVTEX, SafetyNET, and HF NBDP on coverage, frequency, and who transmits, then practise decoding a sample NAVTEX header field by field.
On licensing and frequency-management questions, the candidate cannot distinguish the station licence, the operator's GOC certificate, and the ship's radio log requirements, or states the wrong validity/renewal period, the wrong authority (e.g., naming a commercial body instead of the national administration/WPC wing), or the wrong rule on keeping a radio log and when entries must be made and signed.
Regulatory content is memorised as isolated facts (certificate names, periods) without a framework of who authorises what. Candidates also confuse the ITU Radio Regulations with national licensing rules, and the GOC's relationship to the ship station licence and to watchkeeping duties is not clearly mapped.
What to do instead
Draw a three-layer diagram: ITU Radio Regulations (international framework) -> national administration licence (ship station licence, callsign, MMSI) -> operator certificate (GOC) and logbook duties. Attach each fact (validity, renewal, log entries, who may operate) to the correct layer, and verify current Indian licensing details against the latest WPC/administration guidance rather than older notes, flagging anything uncertain for review.
On watchkeeping questions, the candidate cannot state the GMDSS radio watch requirements correctly: which frequencies/channels must be watched continuously (VHF Ch 70 DSC, MF 2187.5 kHz DSC, and where fitted HF DSC and Inmarsat), the difference between continuous watch and periodic watch, and the requirement to maintain a listening watch on VHF Ch 16 and the distress/safety frequencies. They also fail to explain what to do when leaving the bridge or during an emergency.
Watchkeeping is treated as a list of frequencies rather than a set of duties tied to the vessel's area (A1-A4) and equipment fit. Candidates memorise 'listen on 16' and miss the DSC continuous-watch obligations, the sea-area equipment logic, and the requirement to keep the radio log and to arrange relief or a designated operator when absent.
What to do instead
Learn the sea areas A1-A4 with the minimum equipment for each, then derive the watch requirements from the fitted equipment: continuous DSC watch on VHF 70, MF 2187.5 kHz, and HF DSC as fitted, plus Ch 16 listening watch. Write a one-page 'watch handover' checklist (frequencies monitored, log entries, battery/equipment status, outstanding MSI) and practise explaining what changes when the vessel moves between sea areas.
On battery and maintenance questions, the candidate cannot state the GMDSS battery requirements or the correct testing/maintenance routine: the required capacity and duration (e.g., 1 hour for emergency/standby arrangements, or the specified reserve for the fitted equipment), the specific gravity and voltage checks for lead-acid versus the checks for sealed batteries, and the periodic test intervals and log entries. They also misdiagnose simple faults (e.g., no transmit power, high VSWR, antenna fault) as equipment failure without checking supply, fuse, antenna, or earthing first.
Battery and fault-finding content is formulaic and candidates memorise numbers without the purpose behind them (reserve capacity to keep distress communications alive). Practical fault diagnosis is rarely rehearsed, so candidates jump to 'replace the unit' instead of following a supply-antenna-earth-signal chain, and they confuse battery types and their maintenance needs.
What to do instead
Learn the battery requirement as a reserve-capacity calculation: what must run, for how long, and at what current, then check the arithmetic. Build a fault-diagnosis flowchart (power supply -> fuse/breaker -> antenna and feeder -> VSWR -> equipment self-test -> log and report) and apply it to three worked examples. For batteries, make a table of type, specific gravity/voltage check, topping-up, and test interval, and record each check in the radio log.
In distress/urgency/safety procedure questions, the candidate mishandles the 'silence' and control procedures: failing to impose radio silence (MAYDAY, spoken as 'SEELONCE MAYDAY') when required, not knowing who may impose it (the station in distress or the SAR/coast station controlling the incident), or not knowing how to lift it (SEELONCE FEENEE), and confusing the distress acknowledgement, distress relay, and distress traffic procedures.
The control procedures are rarely used in peacetime drills, so candidates learn the words without the authority structure. They conflate the distress acknowledgement (by a coast station or SAR authority) with the distress relay (by a station not in distress), and they do not know that only the controlling station or the station in distress can impose or cancel silence.
What to do instead
Map the incident as a role-play: station in distress, coast station/SAR controller, assisting ship, and other stations. For each role, write the exact transmissions and who is authorised to send them, including MAYDAY, MAYDAY RELAY, distress acknowledgement, SEELONCE MAYDAY, and SEELONCE FEENEE. Practise the sequence end-to-end so the authority for each message is explicit.
On radiotelephony and DSC phonetic/identification questions, the candidate misspells or misapplies the ITU phonetic alphabet and figure code, or gives the wrong MMSI structure (e.g., cannot explain the MID, the leading digits for ship/coast/group/SART/AIS, or how the MMSI relates to the callsign and DSC addressing), leading to wrong addressing and wrong spoken identification in the exam.
The phonetic alphabet and MMSI are learned as lists without the underlying structure, so under time pressure the candidate substitutes similar-sounding words or guesses MMSI prefixes. The MID (Maritime Identification Digits) concept and the leading-digit conventions for different station types are not connected to how DSC actually addresses a station.
What to do instead
Drill the ITU phonetic alphabet and figure code daily until recall is automatic, including the standard pronunciations. Then learn MMSI by structure: MID identifies the administration, and the leading digits distinguish ship stations, coast stations, groups, SAR aircraft, AIS-SART, and craft associated with a parent ship. Practise constructing and reading back five MMSIs and explaining each part.