South Africa Pre-Arrival Notice Requirements: The Complete SAMSA ISPS Filing Guide

Filing a pre-arrival notice for a South African port call sounds procedural. It is also the step that — when missed or done wrong — can convert a routine port call into a week-long detention with six-figure off-hire losses. The South African Maritime Safety Authority's pre-arrival ISPS notification requirement under Marine Notice 12 of 2008 operates on a strict 96-hour window, requires nine defined fields, and feeds directly into the IOMOU port state control targeting algorithm that determines whether your vessel gets a concentrated inspection or a wave-through.

This guide covers the full filing procedure for vessels calling at any South African port — Durban, Cape Town, Richards Bay, or Port Elizabeth. It covers what goes in each required field, the port-by-port PFSO contact workflow, the compliance pitfalls that trip up vessels newly routing via the Cape, and what PSC inspectors do when the filing triggers their attention. By the end, you will have a repeatable checklist your operations team can run before every South African port call.

The Legal Framework: SAMSA Marine Notice 12 of 2008

South Africa ratified SOLAS and adopted the ISPS Code under the South African Ship Safety Act (No. 5 of 1998) and its subsequent amendments. SAMSA Marine Notice 12 of 2008 is the implementing instrument that specifies the exact pre-arrival notification requirements for South African ports. It gives effect to SOLAS Chapter XI-2, Regulation 9 — which requires ships to provide information to port states prior to entry into port — and translates the regulation's general language into the specific timing, format, and content requirements that apply at South African facilities.

The notice is not optional and does not distinguish between vessel types, flag states, or trade routes. Any vessel of 500 gross tons or more engaged on an international voyage that intends to call at a South African port or anchorage is subject to the requirement. This includes vessels on their first-ever South African call, vessels in transit that seek bunkering or provisions, and vessels calling at offshore supply bases or ship repair yards that are designated port facilities under the ISPS Code.

How It Differs from Other Pre-Arrival Notices

South African ports require multiple pre-arrival notifications that operate on different timelines and go to different recipients. Operators unfamiliar with the South African port system sometimes conflate these, treating a single pre-arrival submission as satisfying all requirements. It does not. The key notices and their relationships:

The SAMSA ISPS message operates on the longest lead time by design. The 96-hour window gives the PFSO time to review the vessel's security history, consult IOMOU records, and coordinate with PSC authorities if the submission raises questions. A 24-hour submission window — the minimum in many other jurisdictions — would not allow meaningful review. For vessels arriving on short inter-port runs where the 96-hour window cannot be achieved, the guidance is to submit as early as possible and notify the PFSO of the reason the full window cannot be met.

Step-by-Step: Filing the SAMSA ISPS Pre-Arrival Message

The following steps reflect the actual filing workflow for a vessel calling at a South African port. Each step maps to one or more required fields in the Marine Notice 12 submission.

Step 1: Establish ETA and Calculate the Filing Deadline

The 96-hour window is calculated from estimated time of arrival at the berth or anchorage, not at the pilot station or port approaches. Use the port's published ETA definition — most South African ports count ETA from the pilot boarding ground. Count back 96 hours from that point to find the latest filing moment.

Build a buffer. ETA estimates change, especially on long-haul passages from Asia, the Americas, or Northern Europe. A vessel that expects to arrive in 102 hours at the time of filing may encounter weather that extends the passage to 90 hours after filing — putting the arrival ahead of the 96-hour window calculated from the original ETA. File when 96 hours remain on the current ETA estimate, not on the initial voyage plan ETA. If ETA changes significantly after filing, notify the PFSO of the revised ETA as soon as the change is known.

Step 2: Compile the Last 10 Port Calls Record

This is the most operationally demanding field and the one most commonly incomplete. The required data for each of the 10 preceding port calls:

• Port name — full official port name, not abbreviation
• Country — ISO country name
• Date of arrival — UTC date
• Date of departure — UTC date
• ISPS security level maintained at that port — 1, 2, or 3; must reflect the actual level maintained, not a default assumption

The security level field trips operators who assume their vessel has always been at Security Level 1. Vessels trading through the Gulf of Aden, West African offshore areas, certain Indonesian straits, or other elevated-threat regions may have operated at Security Level 2 on parts of those voyages. If those periods are within the last 10 port calls, the elevated security level must be declared. Declaring Security Level 1 when the vessel's own records show Security Level 2 at a prior port is a material misstatement. PFSO staff cross-check port call records against commercial vessel tracking databases and IOMOU shared records.

Step 3: Verify ISSC Certificate Details

Pull the current International Ship Security Certificate and confirm:

• Certificate number — as it appears on the certificate face
• Expiry date — the certificate must be valid through the date of the South African port call, not just through the filing date
• Issuing Recognized Security Organization (RSO) — the full name of the organization that issued the certificate on the flag state's behalf

Certificates expiring within 30 days of the planned arrival date are flagged for heightened PFSO attention even if technically still valid. If your ISSC expires within 30 days of a planned South African call, initiate renewal before the voyage departs. RSOs can issue an interim ISSC valid for up to five months while the full renewal audit is scheduled; this is the appropriate tool for a vessel that is at sea when a scheduled renewal approaches.

Step 4: Identify the Ship Security Officer

The SSO named in the filing must be the individual currently serving on board at the time of the filing, not a shore-based fleet security manager. Provide:

• Full name — exactly as it appears on the SSO's STCW certificate
• 24-hour contact details — at minimum, a satellite phone number or ship's INMARSAT number; an email address is also recommended

The SSO must hold a valid certificate issued under STCW Regulation VI/5, which was introduced in the 2010 Manila Amendments. Certificates issued under earlier national frameworks may not satisfy this requirement depending on the flag state's implementation timeline. If there is any uncertainty about the current SSO's certificate status, verify with the flag state or RSO before the voyage departs for South Africa.

Step 5: Complete the Security Incident Declaration

The filing must declare any security incidents involving the vessel in the preceding 12 months. A security incident for ISPS purposes includes piracy attacks, attempted unauthorized boarding, security threats received, and any event that required the vessel to escalate from Security Level 1. A nil declaration — confirming no incidents occurred — is required and valid if no incidents took place. Do not leave this field blank; an omitted security incident field is treated as an incomplete submission, not an implied nil.

Step 6: State the Current ISPS Security Level

Declare the vessel's current security level at the time of filing. For most vessels on most voyages, this will be Security Level 1. If the vessel is at Security Level 2 or 3 at the time of filing, this must be declared and the reason noted. A change in security level between the time of filing and the time of arrival must be communicated to the PFSO immediately upon the change occurring.

Step 7: Transmit to the Port Facility Security Officer

The completed message is transmitted to the PFSO at the destination port facility. Each major South African port has a designated PFSO contact:

Transmit via the officially designated channel for the port — most filings go through the vessel's appointed South African port agent, who has established PFSO contacts and can confirm receipt. If filing directly (without an agent), use the Transnet National Ports Authority electronic submission channel and retain a timestamped confirmation. If no acknowledgement of receipt is received within 24 hours of submission, follow up directly with the PFSO. A submission that leaves no traceable receipt record is not a completed filing.

Port-by-Port Context: What Each South African Port Inspects

While the SAMSA ISPS filing requirement is uniform across all South African ports, the PSC inspection environment varies by port in ways that affect how operators should prioritize their pre-arrival compliance review.

Durban: The Highest-Inspection Port in the IOMOU Region

Durban is South Africa's largest commercial port and the highest-volume PSC inspection port in the entire Indian Ocean MOU network. The port sees a diverse vessel population — container ships, bulk carriers, tankers, car carriers, general cargo vessels — and IOMOU inspectors are present on a daily basis. The targeting algorithm that drives inspection selection weighs flag state performance (some flags receive automatic concentrated inspections), vessel age, time since last PSC inspection, and pre-arrival compliance status.

Since the Cape re-routing traffic surge began in 2024, Durban has seen an influx of vessel types that were not historically regular callers: container ships from liner services that previously transited Suez, and tankers re-routed away from the Red Sea. These vessels are less familiar to Durban PSC staff and carry a higher inspection probability simply because they are newer faces in the port. Combined with any pre-arrival compliance gaps, the inspection risk for re-routed vessels at Durban is meaningfully elevated.

Cape Town: Gateway Traffic and Growing Inspection Activity

Cape Town handles the bulk of the rounding-Cape transit traffic — it is the last major South African port before the Southern Ocean, and many vessels call for fuel, provisions, crew changes, or emergency repairs on Cape passages. PSC inspections at Cape Town increased noticeably in 2025 as vessel traffic volumes grew. The port's ship repair and dry dock facilities also attract vessels that may be calling specifically because they have a technical condition to address — which is itself a PSC inspection trigger.

Richards Bay: Bulk Commodity Focus

Richards Bay is South Africa's primary bulk export terminal — coal, ferrochrome, timber, and other dry bulk commodities. The vessel population is dominated by bulk carriers on established commodity trade routes. PSC inspection patterns here reflect the IOMOU targeting priorities for dry bulk vessels — fire safety systems (particularly in cargo holds), ISM documentation, and STCW certifications for cargo handling operations are common focus areas.

Port Elizabeth (Gqeberha): Automotive and General

Port Elizabeth, now officially named Gqeberha, is South Africa's primary automotive port, handling the majority of new vehicle exports and imports. Vehicle carrier (PCTC) operators are frequent callers. PSC inspections here follow general IOMOU protocols; the port is an active inspection site and shares all deficiency records with the IOMOU database.

After Filing: What Happens to Your Submission

Once the SAMSA ISPS pre-arrival message is received by the PFSO, the following sequence typically occurs:

1. Receipt acknowledgement — the PFSO confirms receipt, typically within 24 hours of submission. Absence of acknowledgement should prompt a follow-up.
2. IOMOU record check — the PFSO's office queries the vessel's IOMOU database record for prior deficiencies, detentions, and inspection history across all 18 member state ports.
3. Targeting assessment — based on the filing content, flag state risk profile, vessel history, and IOMOU records, the vessel is assigned an inspection priority. High-priority vessels receive a concentrated inspection; lower-priority vessels may receive a more limited review or no inspection at that call.
4. Inspection scheduling — if the vessel is selected for inspection, PSC officers coordinate with the berth schedule to conduct the inspection after arrival and before cargo operations begin.
5. Inspection outcome — inspectors issue a report noting deficiencies (if any). Detainable deficiencies halt departure until rectified; non-detainable deficiencies are noted in the IOMOU database and follow the vessel to subsequent calls.

The most important thing operators can do after filing is confirm receipt and monitor for any PFSO queries. A PFSO who has questions about the port call history data or the ISSC details will often contact the vessel or agent for clarification before the vessel arrives. Responding promptly to these queries — and providing correct information — can deflect an inspection that the ambiguous data would otherwise have triggered.

Special Situations: Short Inter-Port Runs and Emergency Calls

Runs Shorter Than 96 Hours

Vessels trading between South African ports — Durban to Cape Town, Richards Bay to Port Elizabeth — face a structural challenge with the 96-hour requirement: the voyage is shorter than the filing window. SAMSA's guidance is that operators should file as early as possible and notify the PFSO explicitly that the full 96-hour window is not achievable due to the inter-port distance. A filing submitted at departure from the previous South African port, with notification to the PFSO of the reason for the compressed window, is treated differently from a simple late filing with no explanation. Document the notification and retain confirmation.

Emergency and Refuge Calls

A vessel in distress or seeking emergency refuge at a South African port must notify the PFSO as soon as the decision to call is made. Emergency situations do not eliminate the ISPS notification obligation — they compress it to the shortest practicable window. The PFSO notification in an emergency call should include the vessel's distress or emergency status, the reason for the call, and all available ISPS data. The PFSO will coordinate with the port captain, MRCC SAMSA (Maritime Rescue Coordination Centre), and PSC authorities to manage the arrival appropriately.

The Broader Compliance Picture: SAMSA ISPS and Your IOMOU Profile

Every South African PSC inspection result, every SAMSA ISPS filing, and every deficiency record is entered into the IOMOU shared database. For operators who route via the Cape on a regular basis — whether by established trade pattern or as a result of ongoing Red Sea disruption — building a clean IOMOU record is not just about avoiding immediate detention. It is about managing the cumulative targeting weight that follows the vessel across 18 member state ports.

A vessel with a clean IOMOU record — no recent deficiencies, current certificates, timely filings — is a lower targeting priority at every subsequent port call. The inspection it avoids in Colombo because of a clean Durban record, and the inspection it avoids in Mumbai because of a clean Colombo record, are invisible cost savings. The value of compliance is not only in avoiding the detention you can see; it is in the inspections you do not get because your record says you do not need one.

The CanalClear Cape of Good Hope compliance module tracks ISSC expiry dates, validates SAMSA ISPS message fields against Marine Notice 12 of 2008 requirements, and maintains a running port call log in the correct format for pre-arrival submissions. For operators building a Cape filing workflow for the first time, the Cape Compliance Guide provides field-by-field examples drawn from actual SAMSA submission practice. And for operators thinking through the full cost of a compliance miss, our analysis of maritime non-compliance costs puts the Sea Lord detention and similar cases in the broader context of what PSC exposure actually costs a fleet.

Related Reading

• SAMSA ISPS Requirements for Cape of Good Hope Transits: A Ship Operator's Guide
• Cape of Good Hope Compliance Module
• Cape Compliance Guide (Free PDF)
• What Is Port State Control? A Ship Operator's Introduction
• Suez Canal ISPS Compliance Guide
• The True Cost of Maritime Non-Compliance
• All CanalClear Blog Posts
• 🚀 Try the Live Demo — validate your vessel's compliance in 90 seconds, no account required