{"id":51635,"date":"2026-04-17T21:51:16","date_gmt":"2026-04-17T20:51:16","guid":{"rendered":"https:\/\/maritimehub.co.uk\/?p=51635"},"modified":"2026-04-17T21:51:16","modified_gmt":"2026-04-17T20:51:16","slug":"navtex-msi-and-navigational-warnings","status":"publish","type":"post","link":"https:\/\/maritimehub.co.uk\/navtex-msi-and-navigational-warnings\/","title":{"rendered":"NAVTEX, MSI and Navigational Warnings"},"content":{"rendered":"
\n

BRIDGE \u2192 ECDIS & Charts<\/strong><\/p>\n

Position on the Bridge<\/strong><\/p>\n

System Group:<\/strong> Navigation \/ Situational Awareness \/ MSI Reception<\/p>\n

Primary Role:<\/strong> Reception, assessment and integration of Marine Safety Information into the active passage plan<\/p>\n

Interfaces:<\/strong> ECDIS, paper charts, passage plan, watchkeeping officer, company SMS, GMDSS log<\/p>\n

Operational Criticality:<\/strong> Absolute \u2014 navigational warnings describe real-world changes that override charted data<\/p>\n

Failure Consequence:<\/strong> Vessel proceeds on a passage plan referencing charted reality that no longer exists \u2014 unlit buoys, shifted wrecks, closed TSS lanes, active military exercise areas, unreported shoaling<\/p>\n<\/div>\n

A NAVTEX receiver printing messages is not a warning system working.
It is a warning system receiving. The system only works when a navigator acts.<\/em><\/p>\n

Introduction<\/h2>\n

Marine Safety Information is not a radio service. It is the formal mechanism by which the real state of the sea and its hazards is communicated to vessels in time to alter their behaviour. When a buoy drags off station at 0200, when a submarine exercise closes a corridor, when new hydrographic data reveals a shoal that predates the last survey by a century but was only just found \u2014 the path from that discovery to the navigator on watch runs through MSI. There is no other path.<\/p>\n

NAVTEX is the primary delivery mechanism for coastal waters. SafetyNET covers the ocean. NAVAREA warnings sit above both, handling the high-seas picture. These are not parallel redundant systems performing the same function. Each occupies a defined layer of the geographic hierarchy, and a vessel transiting from ocean to coast passes through all of them. Missing any layer is not a minor gap in situational awareness. It is a gap in the navigational picture on which collision avoidance and grounding avoidance depend.<\/p>\n

The problem aboard most vessels is not equipment failure. NAVTEX receivers print. SafetyNET terminals receive. The GMDSS log gets signed. The procedural paperwork looks correct. The failure happens at the translation step \u2014 between the message that has been received and the chart or ECDIS overlay that should, as a result, look different. That translation step requires a human decision, and it is the step most frequently skipped.<\/p>\n

This article addresses the architecture of MSI delivery, the mechanics of NAVTEX and SafetyNET, and the specific failure modes that leave vessels navigating on an outdated picture while believing their MSI regime is compliant.<\/p>\n

Contents<\/h2>\n
    \n
  • 1. The MSI Chain: From Source to Ship<\/li>\n
  • 2. NAVTEX: Frequencies, Stations and the Geographic Logic<\/li>\n
  • 3. Message Categories and the Non-Deselectable Ones<\/li>\n
  • 4. SafetyNET and the Ocean Gap<\/li>\n
  • 5. NAVAREA, Subarea and Coastal Warning Architecture<\/li>\n
  • 6. Integration with ECDIS: Where the System Typically Breaks<\/li>\n
  • 7. The Difference Between a Read Message and an Actioned Message<\/li>\n
  • 8. Common Failure Modes<\/li>\n
  • 9. Closing Reality<\/li>\n<\/ul>\n

    1. The MSI Chain: From Source to Ship<\/h2>\n

    MSI originates from a defined set of sources: hydrographic offices, coast guards, naval authorities, port authorities, and IALA. The IMO and IHO have structured this through the GMDSS framework, with the World-Wide Navigational Warning Service coordinating the global picture. That coordination matters because maritime hazards do not respect the administrative boundaries of the organisations that report them.<\/p>\n

    At the top of the hierarchy sit the sixteen NAVAREA coordinators, each responsible for a defined ocean zone. Below them, national coordinators manage subarea warnings covering their coastal waters. Below that, coastal NAVTEX transmitter stations handle the local picture \u2014 buoys, wrecks, port approaches, local TSS changes \u2014 within their roughly 400-nautical-mile broadcast radius.<\/p>\n

    The chain is designed to be complete. A vessel on a North Atlantic passage should receive relevant ocean-level warnings via SafetyNET from the NAVAREA coordinator, transition into coastal coverage via NAVTEX as it approaches, and receive port-level notices via local NAVTEX and NOTAM-equivalent port notices. In practice, the completeness of that chain depends entirely on whether the vessel’s receiving equipment is configured correctly for each phase of the voyage.<\/p>\n

    Reconfiguration does not happen automatically. Someone has to do it, and that someone needs to understand why.<\/p>\n

    2. NAVTEX: Frequencies, Stations and the Geographic Logic<\/h2>\n

    NAVTEX operates on three frequencies. 518 kHz is the international frequency, carrying English-language broadcasts and forming the primary layer of coastal MSI delivery worldwide. 490 kHz is the national frequency, used for broadcasts in local languages and, in some regions, supplementary English-language content. 4209.5 kHz is the high-frequency channel, providing extended range where coastal coverage on MF is insufficient \u2014 notably in Arctic and Antarctic waters and parts of the Pacific.<\/p>\n

    Each transmitter station is assigned a single-letter identifier, A through Z (excluding Q and some regionally assigned letters). No two stations on the same frequency within mutual interference range share the same identifier. Broadcasts are scheduled to avoid overlap, typically in 10-minute slots on a rotating basis. The receiver uses the station identifier to avoid printing duplicate messages \u2014 a message received from station identifier O will not be reprinted if that exact message (same station, same message number) arrives again.<\/p>\n

    This deduplication logic is important. If a vessel is in the overlap zone of two adjacent stations, it will receive the same regional warning from both. The receiver suppresses the duplicate. That is correct behaviour. The risk is that navigators occasionally mistake this suppression for a filtering decision they control, when in fact it is an automatic function of the receiver’s memory management.<\/p>\n

    Coverage planning is not optional. Before departure, and at each phase change of a passage, the appropriate stations for the next 24 to 48 hours should be confirmed active and selected. Harbour authorities and hydrographic offices publish station schedules. The assumption that the receiver will self-configure for a new region is wrong.<\/p>\n

    3. Message Categories and the Non-Deselectable Ones<\/h2>\n

    NAVTEX messages are categorised A through Z, with each letter designating a subject type. The categories most routinely encountered include:<\/p>\n

      \n
    • A<\/strong> \u2014 Navigational warnings<\/li>\n
    • B<\/strong> \u2014 Meteorological warnings<\/li>\n
    • C<\/strong> \u2014 Ice reports<\/li>\n
    • D<\/strong> \u2014 Search and rescue information<\/li>\n
    • E<\/strong> \u2014 Meteorological forecasts<\/li>\n
    • F<\/strong> \u2014 Pilot service messages<\/li>\n
    • G<\/strong> \u2014 AIS messages<\/li>\n
    • H<\/strong> \u2014 LORAN messages (largely obsolete but category retained)<\/li>\n
    • L<\/strong> \u2014 Subfacts and navigational warnings (submarine exercise areas, used in UK and some other regions)<\/li>\n
    • W, X, Y, Z<\/strong> \u2014 Allocated for special services by regional coordinators<\/li>\n<\/ul>\n

      Categories A, B, D and L cannot be deselected on a compliant NAVTEX receiver. This is a SOLAS requirement, not a manufacturer preference. The rationale is straightforward: navigational warnings, meteorological warnings, SAR information and submarine exercise area warnings represent minimum safety thresholds below which a vessel should never operate, regardless of how irrelevant the navigator believes them to be for a particular passage.<\/p>\n

      The temptation to manage message volume by aggressive category deselection is understandable on a busy passage when the printer produces pages of apparently irrelevant information. It is also a direct path to missing something that matters.<\/p>\n

      Category volume is not a reason to deselect. It is a reason to read faster and filter with judgement rather than with the receiver’s category buttons.<\/p>\n

      4. SafetyNET and the Ocean Gap<\/h2>\n

      NAVTEX MF coverage ends roughly 400 nautical miles offshore. For ocean passages, MSI delivery transfers to SafetyNET, the Inmarsat-C broadcast service carrying Enhanced Group Calling (EGC) messages. SafetyNET is mandatory GMDSS equipment for vessels operating in sea areas A3 and A4.<\/p>\n

      SafetyNET messages are addressed geographically using rectangular or circular areas, or by NAVAREA designation. The Inmarsat terminal receives messages addressed to the ocean region the vessel is currently in, filtered against the geographic areas the officer has programmed. This programming step is where ocean-passage MSI reception most commonly fails.<\/p>\n

      A vessel’s Inmarsat-C EGC receiver must be configured with the correct ocean region satellite, and the geographic filter must encompass the vessel’s current and immediate future position. Neither of these configurations survives a satellite handover automatically in all installations. After crossing between ocean regions \u2014 Atlantic to Indian Ocean, for example \u2014 the receiving configuration must be verified, not assumed.<\/p>\n

      NAVAREA warnings received via SafetyNET carry the same operational weight as a NAVTEX coastal warning. The difference in delivery medium does not change the obligation to assess and action them. The bridge team that treats SafetyNET messages as background traffic on a long ocean passage is operating on an increasingly stale navigational picture.<\/p>\n

      Quiet ocean passages generate complacency. The absence of warnings is not evidence that no warnings have been issued.<\/p>\n

      5. NAVAREA, Subarea and Coastal Warning Architecture<\/h2>\n

      The World-Wide Navigational Warning Service divides the global ocean into sixteen NAVAREAs, each with a designated coordinator. NAVAREA warnings cover large-scale hazards \u2014 newly reported wrecks in international waters, military exercise zones, unreported floating dangers, significant light changes on major aids to navigation. They are transmitted via SafetyNET and, for some areas, via HF radio facsimile and voice.<\/p>\n

      Below NAVAREA level sit subarea warnings, managed by national coordinators. These cover hazards that are regional rather than ocean-wide \u2014 changes to traffic separation schemes, significant buoy-watching failures, temporary obstructions to coastal shipping lanes. In UK waters, UKHO manages this through the Hydrographic Office’s Notice to Mariners system, with urgent notices transmitted via NAVTEX.<\/p>\n

      Coastal NAVTEX warnings are the most granular level. These cover port approach changes, local buoyage problems, specific wrecks or obstructions in defined positions, and temporary prohibited areas. They have the shortest geographic scope and typically the highest operational immediacy for coastal passages.<\/p>\n

      The hierarchy matters for passage planning. A vessel departing UK waters for the Arabian Gulf will transition through NAVAREA I (Eastern Atlantic), NAVAREA II (Mediterranean), NAVAREA IX (Arabian Sea) and multiple subarea warning regimes. The passage plan should document which NAVAREA the vessel is in at each stage, which SafetyNET or NAVTEX configuration applies, and who is responsible for verifying that configuration is correct before each transition.<\/p>\n

      Most passage plans do not contain this information. Most passage plan audits do not check for it.<\/p>\n

      6. Integration with ECDIS: Where the System Typically Breaks<\/h2>\n

      ECDIS does not receive NAVTEX or SafetyNET messages. This is the fact that the marketing around integrated bridge systems quietly glosses over. Some manufacturers offer data links that can import MSI data into the ECDIS as manual annotations or temporary chart objects, but this requires active operator input. The ECDIS does not know what the NAVTEX printer said this morning.<\/p>\n

      The integration that does exist is weak: some systems allow manual entry of temporary and preliminary notices to mariners as chart corrections, some allow drawing of user-defined areas or points. None of this happens automatically. Each step requires a navigator to read a warning, assess its geographic scope, determine whether the vessel’s route passes through or near it, and then make a manual entry on the chart or ECDIS.<\/p>\n

      When that step is performed correctly, the ECDIS shows a picture that reflects current reality. When it is skipped \u2014 and it is frequently skipped \u2014 the ECDIS shows a picture that reflects the state of the sea at the time the chart cells were last updated, which may be months prior.<\/p>\n

      A chart displaying a lit buoy that has been unlit for three weeks, because the NAVTEX warning was filed without annotation, is not a navigation aid. It is a confidence trap.<\/p>\n

      There is active development in the MSI-to-ECDIS integration space. S-124 is the IHO standard for digital navigational warnings, designed to allow warnings to be encoded as geometric objects with defined validity periods and imported directly into S-100 compliant ECDIS systems. Adoption is growing, but coverage remains incomplete. Until it is universal, the manual translation step remains the navigator’s responsibility.<\/p>\n

      7. The Difference Between a Read Message and an Actioned Message<\/h2>\n

      This is where compliance culture and actual safety diverge most visibly.<\/p>\n

      A NAVTEX message is considered received when the printer produces it. It is considered read when an officer tears it off and signs the GMDSS log. Under most SMS regimes and port state control interpretations, that is where the audit trail ends. The message has been received. The log is signed. The box is ticked.<\/p>\n

      None of that constitutes actioning the message.<\/p>\n

      Actioning a navigational warning means: determining its geographic position, comparing that position to the vessel’s planned track and planned timing, assessing whether the hazard described is relevant at the predicted time of nearest approach, and then either amending the passage plan or recording a documented decision that no amendment is required and why. It also means updating the ECDIS or chart to reflect the warning, regardless of whether the route passes through it, if there is any reasonable possibility of the vessel entering the affected area.<\/p>\n

      This is the process that distinguishes a vessel with a functioning MSI regime from a vessel that prints NAVTEX messages and files them. The distinction is not visible in the GMDSS log. It is only visible when something goes wrong and the question becomes: did anyone actually plot that warning?<\/p>\n

      On many vessels, no one did.<\/p>\n

      8. Common Failure Modes<\/h2>\n

      The failure modes in MSI handling are well-established and recur across incident investigations with depressing consistency.<\/p>\n

      Stacked Unread Messages<\/h3>\n

      NAVTEX printers produce output continuously. On vessels where no one is assigned primary responsibility for clearing and assessing the messages, the output accumulates. By the time anyone reads the stack, the early messages may describe hazards the vessel has already passed through. Or navigated past without knowing the hazard was there. Stacked unread messages represent the period during which the vessel was effectively blind to MSI despite the equipment functioning correctly.<\/p>\n

      Messages Filed Without Chart Annotation<\/h3>\n

      The GMDSS log shows every message signed as read. The chart and ECDIS show nothing. This is the most common failure mode and the one with the highest potential consequence. It is also the one most likely to satisfy a routine port state control inspection, because the paper trail looks complete.<\/p>\n

      Compliance and safety are not the same thing. The log entry proves the message arrived. It proves nothing about what the navigator did with it.<\/p>\n

      Aggressive Station or Category Deselection<\/h3>\n

      Filtering out stations because their coverage area is deemed irrelevant to the current passage is a judgement call that frequently proves wrong. Passage plans change. Weather diversions happen. A vessel that has filtered out the NAVTEX station covering its diversion route because that route was not anticipated will not receive warnings for the waters it now actually occupies.<\/p>\n

      Category deselection beyond the mandatory minimum amplifies this. The argument that certain categories produce irrelevant message volume is an argument for better assessment procedures, not for switching off the receiver’s categories.<\/p>\n

      SafetyNET Configuration Not Updated After Satellite Handover<\/h3>\n

      Ocean passage MSI reception requires active management across satellite region boundaries. The assumption that the Inmarsat-C terminal is correctly configured because it was correctly configured at departure is wrong once the vessel has crossed an ocean region boundary. Verification must be explicit, logged and assigned to a named officer.<\/p>\n

      ECDIS Operator Confidence in Uncorrected Cells<\/h3>\n

      ECDIS systems display dates of latest Notice to Mariners application. Officers who rely on this date as a proxy for chart currency are not accounting for the gap that exists between the weekly NtM cycle and the real-time MSI broadcast system. A chart corrected to last week’s NtM may not reflect a NAVTEX warning broadcast yesterday. Those are different layers of the same picture, and both must be current.<\/p>\n

      The ECDIS does not know about the NAVTEX printer. The navigator must hold both pictures simultaneously and reconcile them actively.<\/p>\n

      9. Closing Reality<\/h2>\n

      MSI systems work. The chain from hazard discovery to shipboard receipt is well-designed, globally coordinated, and, for most coastal and ocean areas, genuinely comprehensive. The equipment on fitted vessels receives what it is supposed to receive.<\/p>\n

      The failure point is the last metre \u2014 the distance between the NAVTEX printer and the chart table, or the ECDIS keyboard.<\/p>\n

      A navigational warning that has been received, printed, signed for, filed and not plotted has not been used. The vessel is still navigating without that information. The GMDSS log says otherwise, but the GMDSS log is a receipt, not a safety record.<\/p>\n

      Every passage plan should contain a documented MSI assessment, station by station and NAVAREA by NAVAREA, for each phase of the voyage. Every watch handover should include the status of outstanding navigational warnings. Every significant warning should have a corresponding annotation on the active chart or ECDIS before the vessel enters the relevant area.<\/p>\n

      These are not aspirational standards. They are the minimum that the purpose of the MSI system demands.<\/p>\n

      The sea does not wait for the message to be actioned.<\/p>\n","protected":false},"excerpt":{"rendered":"

      How Marine Safety Information is generated, transmitted and \u2014 critically \u2014 how it must be actioned against the passage plan, not merely read.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"fifu_image_url":"","fifu_image_alt":"","c2c-post-author-ip":"2a02:c7c:2ef8:2400:931:afb1:9971:4a62","footnotes":""},"categories":[10,1],"tags":[8949,9124,9192,9195,9193,9185,8959,9194],"class_list":["post-51635","post","type-post","status-publish","format-standard","hentry","category-bridge","category-latest","tag-ecdis","tag-gmdss","tag-msi","tag-navarea","tag-navigational-warnings","tag-navtex","tag-passage-planning","tag-safetynet"],"acf":[],"_links":{"self":[{"href":"https:\/\/maritimehub.co.uk\/?rest_route=\/wp\/v2\/posts\/51635","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/maritimehub.co.uk\/?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/maritimehub.co.uk\/?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/maritimehub.co.uk\/?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/maritimehub.co.uk\/?rest_route=%2Fwp%2Fv2%2Fcomments&post=51635"}],"version-history":[{"count":1,"href":"https:\/\/maritimehub.co.uk\/?rest_route=\/wp\/v2\/posts\/51635\/revisions"}],"predecessor-version":[{"id":51642,"href":"https:\/\/maritimehub.co.uk\/?rest_route=\/wp\/v2\/posts\/51635\/revisions\/51642"}],"wp:attachment":[{"href":"https:\/\/maritimehub.co.uk\/?rest_route=%2Fwp%2Fv2%2Fmedia&parent=51635"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/maritimehub.co.uk\/?rest_route=%2Fwp%2Fv2%2Fcategories&post=51635"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/maritimehub.co.uk\/?rest_route=%2Fwp%2Fv2%2Ftags&post=51635"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}