<?xml version="1.0" encoding="UTF-8"?><urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://tasmanmaritime.com/</loc>
    <lastmod>2026-07-31</lastmod>
    <changefreq>monthly</changefreq>
    <priority>1.0</priority>
  </url>
  <url>
    <loc>https://tasmanmaritime.com/regions/new-zealand</loc>
    <lastmod>2026-07-31</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.9</priority>
  </url>
  <url>
    <loc>https://tasmanmaritime.com/regions/australia</loc>
    <lastmod>2026-07-31</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.9</priority>
  </url>
  <url>
    <loc>https://tasmanmaritime.com/regions/south-pacific</loc>
    <lastmod>2026-07-31</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.9</priority>
  </url>
  <url>
    <loc>https://tasmanmaritime.com/services/dpa-backup-dpa</loc>
    <lastmod>2026-07-31</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.9</priority>
  </url>
  <url>
    <loc>https://tasmanmaritime.com/services/cso</loc>
    <lastmod>2026-07-31</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.9</priority>
  </url>
  <url>
    <loc>https://tasmanmaritime.com/services/internal-auditor</loc>
    <lastmod>2026-07-31</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.9</priority>
  </url>
  <url>
    <loc>https://tasmanmaritime.com/services/lead-auditor</loc>
    <lastmod>2026-07-31</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.8</priority>
  </url>
  <url>
    <loc>https://tasmanmaritime.com/services/expedition-cruise</loc>
    <lastmod>2026-07-31</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.9</priority>
  </url>
  <url>
    <loc>https://tasmanmaritime.com/services/superyacht-compliance</loc>
    <lastmod>2026-07-31</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.9</priority>
  </url>
  <url>
    <loc>https://tasmanmaritime.com/flag-states</loc>
    <lastmod>2026-07-31</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.8</priority>
  </url>
  <url>
    <loc>https://tasmanmaritime.com/privacy-policy</loc>
    <lastmod>2026-07-31</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.3</priority>
  </url>
  <url>
    <loc>https://tasmanmaritime.com/quality-and-policies</loc>
    <lastmod>2026-07-31</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>https://tasmanmaritime.com/about</loc>
    <lastmod>2026-07-31</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.8</priority>
  </url>
  <url>
    <loc>https://tasmanmaritime.com/blog</loc>
    <lastmod>2026-07-31</lastmod>
    <changefreq>weekly</changefreq>
    <priority>0.8</priority>
  </url>
<!DOCTYPE html>
<html lang="en-NZ">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<!-- Preload critical above-fold assets -->
<link rel="preload" href="/assets/images/pacific-map.webp" as="image" type="image/webp">
<link rel="preload" href="/assets/images/logo-web.webp" as="image" type="image/webp">
<link rel="preload" href="/assets/css/style.min.css" as="style">
<link rel="dns-prefetch" href="//www.google-analytics.com">
<title>What is a Designated Person Ashore (DPA)? | Tasman Maritime Consulting</title>
<meta name="description" content="What is a Designated Person Ashore (DPA) under the ISM Code? What the role involves, who needs one, and how a contracted external DPA works for smaller operators and superyachts.">
<link rel="canonical" href="https://tasmanmaritime.com/blog/posts/dpa-designated-person-ashore-explained">
<meta name="robots" content="index, follow">

<meta property="og:type" content="website">
<meta property="og:title" content="What is a Designated Person Ashore (DPA)? | Tasman Maritime Consulting">
<meta property="og:description" content="What is a Designated Person Ashore (DPA) under the ISM Code? What the role involves, who needs one, and how a contracted external DPA works for smaller operators and superyachts.">
<meta property="og:url" content="https://tasmanmaritime.com/blog/posts/dpa-designated-person-ashore-explained">
<meta property="og:site_name" content="Tasman Maritime Consulting">
<meta property="og:image" content="https://tasmanmaritime.com/assets/images/logo.png">
<meta property="og:image:width" content="993">
<meta property="og:image:height" content="644">
<meta name="twitter:card" content="summary_large_image">
<meta name="twitter:image" content="https://tasmanmaritime.com/assets/images/logo.png">
<meta name="twitter:card" content="summary">

<link rel="icon" href="/assets/images/favicon.png" type="image/png">
<link rel="stylesheet" href="/assets/css/style.css">

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "ProfessionalService",
  "name": "Tasman Maritime Consulting",
  "description": "ISM/ISPS/MLC audit and DPA/CSO services for vessels operating in or planning operations in New Zealand, Australian, and South Pacific waters.",
  "url": "https://tasmanmaritime.com",
  "logo": "https://tasmanmaritime.com/assets/images/logo.png",
  "image": "https://tasmanmaritime.com/assets/images/logo.png",
  "telephone": "",
  "email": "enquiries@tasmanmaritime.com",
  "address": {
    "@type": "PostalAddress",
    "addressCountry": "NZ"
  },
  "areaServed": [
    {"@type": "Country", "name": "New Zealand"},
    {"@type": "Country", "name": "Australia"},
    {"@type": "GeoCircle", "geoMidpoint": {"@type": "GeoCoordinates", "latitude": -20, "longitude": 170}, "geoRadius": "3000000"}
  ],
  "knowsAbout": ["ISM Code", "ISPS Code", "MLC 2006", "Designated Person Ashore", "Company Security Officer", "Safety Management System", "Maritime compliance", "Internal audit", "Gap analysis", "Superyacht compliance", "Red Ensign Group", "Cook Islands flag", "New Zealand maritime", "AMSA", "Boatworks", "GCCM", "Rivergate", "Westhaven", "Norsand Boatyard"],
  "hasOfferCatalog": {
    "@type": "OfferCatalog",
    "name": "Maritime compliance services",
    "itemListElement": [
      {"@type": "Offer", "itemOffered": {"@type": "Service", "name": "ISM/ISPS/MLC Internal Audit"}},
      {"@type": "Offer", "itemOffered": {"@type": "Service", "name": "Designated Person Ashore (DPA)"}},
      {"@type": "Offer", "itemOffered": {"@type": "Service", "name": "Company Security Officer (CSO)"}},
      {"@type": "Offer", "itemOffered": {"@type": "Service", "name": "Pre-certification gap analysis"}}
    ]
  },
  "founder": {
    "@type": "Person",
    "name": "Craig Hopkins",
    "jobTitle": "Principal"
  },
  "sameAs": ["https://www.linkedin.com/company/tasmanmaritime/"]
  }
</script>

</head>
<body>

<header class="site-header">
  <div class="header-top">
        <a href="/" class="header-compact-logo">
      <picture>
        <source srcset="/assets/images/logo-web.webp" type="image/webp">
        <img src="/assets/images/logo-web.png"
             alt="Tasman Maritime Consulting"
             width="160" height="104"
             loading="eager" decoding="async">
      </picture>
    </a>
        <a href="/" class="brand brand--compact">
      <picture>
        <source srcset="/assets/images/logo-web.webp" type="image/webp">
        <img src="/assets/images/logo-web.png"
             alt="Tasman Maritime Consulting"
             class="brand__logo-img"
             width="160" height="104"
             loading="eager" decoding="async">
      </picture>
    </a>

    <div class="quick-actions quick-actions--mobile">

      <div class="quick-action quick-action--emergency">
        <button class="quick-action__btn" type="button" data-toggle="emergency-panel" aria-expanded="false" aria-controls="emergencyPanelMobile">
          <span class="quick-action__dot" aria-hidden="true"></span>
          Emergency 24-hour client contact
        </button>
        <div class="quick-action__panel emergency-gate" id="emergencyPanelMobile" hidden>
          <div class="emergency-gate__form" id="emergencyGateFormMobile">
            <p class="quick-action__panel-label">24-hour emergency line — existing clients and vessels in distress only.</p>
            <p class="emergency-gate__prompt">Please enter your vessel name to continue:</p>
            <input type="text" class="emergency-gate__input" id="emergencyVesselInputMobile" placeholder="Vessel name" autocomplete="off">
            <button type="button" class="emergency-gate__submit" id="emergencyGateSubmitMobile">Show number</button>
          </div>
          <div class="emergency-gate__number" id="emergencyNumberMobile" hidden>
            <p class="quick-action__panel-label">Call now, any time:</p>
            <a href="tel:+64273556673" class="quick-action__panel-phone">+64 (0)27 355 6673</a>
            <p class="emergency-gate__vessel" id="emergencyVesselConfirmMobile"></p>
          </div>
        </div>
      </div>

      <div class="quick-action quick-action--portal">
        <button class="quick-action__btn" type="button" data-toggle="portal-panel" aria-expanded="false" aria-controls="portalPanelMobile">
          Client login portal
        </button>
        <div class="quick-action__panel" id="portalPanelMobile" hidden>
          <p class="quick-action__panel-label">Vessel login &mdash; sign in as:</p>
          <a href="/portal/manager.php">Manager</a>
          <a href="/portal/captain.php">Captain</a>
          <a href="/portal/crew.php">Crew</a>
        </div>
      </div>

      <div class="quick-action quick-action--consult">
        <button class="quick-action__btn" type="button" data-toggle="consult-modal">
          Book a consultation
        </button>
      </div>

    </div>
  </div>

  <nav class="site-nav" aria-label="Primary">
    <div class="site-nav__inner">
      <button class="site-nav__toggle" id="navToggle" aria-expanded="false" aria-controls="siteNavList">
        <span></span><span></span><span></span>
        <span class="sr-only">Menu</span>
      </button>
      <ul class="site-nav__list" id="siteNavList">
        <li class="has-children">
          <a href="/#services">Services</a>
          <ul>
            <li><a href="/services/dpa-backup-dpa.php">DPA &amp; backup DPA</a></li>
            <li><a href="/services/cso.php">Company Security Officer</a></li>
            <li><a href="/services/internal-auditor.php">ISM/ISPS/MLC internal audits</a></li>
            <li><a href="/services/lead-auditor.php">ISM/ISPS/MLC lead audits</a></li>
            <li><a href="/services/expedition-cruise.php">Expedition &amp; small cruise operators</a></li>
            <li><a href="/services/superyacht-compliance.php">Superyacht &amp; large yacht compliance</a></li>
          </ul>
        </li>
        <li class="has-children">
          <a href="/#regions">Regions</a>
          <ul>
            <li><a href="/regions/new-zealand.php">New Zealand</a></li>
            <li><a href="/regions/australia.php">Australia</a></li>
            <li><a href="/regions/south-pacific.php">South Pacific</a></li>
          </ul>
        </li>
        <li><a href="/flag-states.php">Flag states</a></li>
        <li><a href="/blog">Insights</a></li>
        <li><a href="/about.php">About</a></li>
        <li>
          <a href="https://www.linkedin.com/company/tasmanmaritime/" target="_blank" rel="noopener" class="nav-linkedin" aria-label="Follow Tasman Maritime on LinkedIn">
            <svg width="17" height="17" viewBox="0 0 24 24" fill="currentColor" aria-hidden="true"><path d="M20.447 20.452h-3.554v-5.569c0-1.328-.027-3.037-1.852-3.037-1.853 0-2.136 1.445-2.136 2.939v5.667H9.351V9h3.414v1.561h.046c.477-.9 1.637-1.85 3.37-1.85 3.601 0 4.267 2.37 4.267 5.455v6.286zM5.337 7.433a2.062 2.062 0 01-2.063-2.065 2.064 2.064 0 112.063 2.065zm1.782 13.019H3.555V9h3.564v11.452zM22.225 0H1.771C.792 0 0 .774 0 1.729v20.542C0 23.227.792 24 1.771 24h20.451C23.2 24 24 23.227 24 22.271V1.729C24 .774 23.2 0 22.222 0h.003z"/></svg>
          </a>
        </li>
      </ul>
    </div>
  </nav>
</header>

<!-- Book a consultation modal — shared across every page -->
<div class="modal" id="consultModal" hidden>
  <div class="modal__overlay" data-close="consult-modal"></div>
  <div class="modal__dialog" role="dialog" aria-modal="true" aria-labelledby="consultModalTitle">
    <button class="modal__close" type="button" data-close="consult-modal" aria-label="Close">&times;</button>
    <h2 id="consultModalTitle">Book a consultation</h2>
    <p class="modal__sub">Send a quick note and I&rsquo;ll get back to you. Fields marked * are required.</p>

    <form id="consultForm" novalidate>
      <label class="field">
        <span>Name *</span>
        <input type="text" name="name" required>
      </label>
      <label class="field">
        <span>Company or vessel</span>
        <input type="text" name="company">
      </label>
      <label class="field">
        <span>Phone number</span>
        <input type="tel" name="phone">
      </label>
      <label class="field">
        <span>Email *</span>
        <input type="email" name="email" required>
      </label>
      <label class="field">
        <span>Message</span>
        <textarea name="message" rows="4" placeholder="What would you like to discuss?"></textarea>
      </label>

      <button type="submit" class="btn btn--primary" style="width:100%;">Send message</button>
      <p class="form__status" id="consultFormStatus" role="status" aria-live="polite"></p>
    </form>
  </div>
</div>

<div class="container">
  <p class="breadcrumb">
    <a href="/">Home</a><span class="breadcrumb__sep">/</span>
    <a href="/blog">Insights</a><span class="breadcrumb__sep">/</span>
          <a href="/blog?cat=DPA+%26+CSO">DPA &amp; CSO</a><span class="breadcrumb__sep">/</span>
        What is a Designated Person Ashore (DPA) — and do you need one?  </p>
</div>

<div class="article-wrap">
  <div class="container">
    <div class="article-layout">

      <article class="article-body">
                <span class="blog-card__cat" style="display:inline-block;margin-bottom:16px;">DPA &amp; CSO</span>
        
        <h1 class="article-title">What is a Designated Person Ashore (DPA) — and do you need one?</h1>

        <p class="article-meta">
          By <strong>Craig Hopkins</strong>
          &bull; 13 July 2026          &bull; 5 min read        </p>

        <div class="article-content">
<!-- ARTICLE BODY STARTS HERE -->

<p>If your vessel falls under the ISM Code, you need a Designated Person Ashore. Most operators know this. Fewer are clear on what the DPA role actually requires, what "reachable at all times" means in practice, and why having the right DPA in the right timezone matters more than most people appreciate until it doesn't.</p>

<h2>What the ISM Code says</h2>

<p>ISM Code Regulation 4 is unambiguous: <em>"To ensure the safe operation of each ship and to provide a link between the company and those on board, every company, as appropriate, should designate a person or persons ashore having direct access to the highest level of management."</em></p>

<p>The designated person's responsibilities include monitoring the safety and pollution-prevention aspects of each vessel, ensuring adequate resources and shore-based support are provided, and being available at all times as the point of contact between the vessel and the company's senior management. That last point — available at all times — is the one most frequently underestimated.</p>

<h2>What "available at all times" actually means</h2>

<p>It means what it says. A vessel does not stop operating at 0200. Emergencies do not wait for office hours. A vessel in distress in the South Pacific at 0200 UTC — the middle of the European night — cannot reach a DPA asleep in Monaco or Antibes. That same 0200 UTC is 1300 to 1500 the following afternoon in New Zealand. A NZ-based backup DPA is at their desk. The ISM Code requirement for 24-hour accessibility is either being met or it isn't — and a sleeping European DPA is not meeting it.</p>

<p>This is not a theoretical concern. Port state control officers ask to see evidence of DPA contact arrangements and will test whether the provided number is actually reachable. A non-functioning DPA is a documented deficiency.</p>

<h2>Who can be a DPA?</h2>

<p>The ISM Code sets out the functional requirements for the DPA role — direct access to senior management, understanding of safety management requirements, and 24-hour availability — but does not mandate a specific certificate by name. In practice however, flag states, Recognised Organisations, and port state control increasingly expect the DPA to demonstrate formal competence through a recognised DPA qualification — structured training in ISM Code requirements, emergency response, and the legal responsibilities of the role. Several classification societies and maritime training providers offer DPA certification programmes. In practice, a competent DPA should have:</p>

<ul>
  <li>The ISM Code and the company's SMS</li>
  <li>The types of vessels and operations involved</li>
  <li>Emergency response procedures and escalation paths</li>
  <li>The flag state's requirements and the Recognised Organisation involved</li>
</ul>

<p>For larger shipping companies, the DPA is typically a senior shore-side employee. For smaller operators, yacht management companies, and individual vessel owners, an external contracted DPA is a practical and commonly used alternative.</p>

<h2>The case for an external contracted DPA</h2>

<p>An external contracted DPA provides the same function as an in-house one — formal designation in the SMS, 24-hour reachability, direct access to management, oversight of compliance — without requiring the vessel owner or management company to employ a dedicated shore-side role.</p>

<p>For vessels with internationally based management and crews operating in the South Pacific, New Zealand, or Australian waters, there is an additional practical argument: timezone coverage. A primary DPA based in Antibes or Fort Lauderdale is available during European or Atlantic business hours — but unreachable in the middle of their night. New Zealand and Australia sit 11 to 13 hours ahead of Europe, meaning NZ/Australian business hours run directly across the European overnight. When it is 0200 UTC and the European DPA is asleep, it is already early afternoon in New Zealand — the backup DPA is working, reachable, and available.</p>

<blockquote>
  "The captain called at 0200 UTC — a crew welfare issue that needed shore-side escalation. In the south of France it was 0300 in the morning and the primary DPA was unreachable. In New Zealand it was early afternoon. The backup DPA took the call, escalated to management, and the issue was managed before it became a formal incident."
</blockquote>

<h2>What a contracted DPA arrangement looks like</h2>

<p>A contracted DPA arrangement typically involves a formal agreement between the DPA and the vessel's company that specifies:</p>

<ul>
  <li>The vessels covered and the SMS applicable to each</li>
  <li>Contact arrangements and response time expectations</li>
  <li>Escalation paths to the company's senior management</li>
  <li>Scope of involvement in audits, drills, and SMS reviews</li>
  <li>Handover procedures with the primary DPA where applicable</li>
</ul>

<p>The DPA is named in the SMS and their contact details are on board. They are not a silent contract — they are an active participant in the company's safety management, and their involvement needs to be genuine to satisfy port state control scrutiny.</p>

<h2>The DPA and the CSO — not the same role</h2>

<p>A common source of confusion: the DPA (ISM Code) and the Company Security Officer or CSO (ISPS Code) are different roles with different functions. The DPA covers safety management; the CSO covers security management. They can be — and in smaller operations, often are — the same person. But conflating the two roles without explicitly documenting that arrangement in both the SMS and the Ship Security Plan creates compliance gaps.</p>

<h2>Summary</h2>

<p>If your vessel needs a DPA under the ISM Code, the requirement is genuine and the consequences of a non-functioning arrangement are real — deficiency citations from PSC, potential detention, and a captain without the shore-side support they need when things go wrong. An external contracted DPA is a legitimate, commonly used solution, particularly for smaller operators and for vessels in time zones where European-based management teams are unavailable overnight.</p>

<p>For vessels operating in or heading to New Zealand, Australian, and South Pacific waters, timezone-appropriate DPA cover is worth specific attention before departure.</p>

<!-- ARTICLE BODY ENDS HERE -->
        </div><!-- /.article-content -->

        <div class="article-share">
          <p class="article-share__label">Share this article</p>
          <a href="https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Ftasmanmaritime.com%2Fblog%2Fposts%2F_article-footer" target="_blank" rel="noopener" class="article-share__btn article-share__btn--li">
            <svg width="16" height="16" viewBox="0 0 24 24" fill="currentColor" aria-hidden="true"><path d="M20.447 20.452h-3.554v-5.569c0-1.328-.027-3.037-1.852-3.037-1.853 0-2.136 1.445-2.136 2.939v5.667H9.351V9h3.414v1.561h.046c.477-.9 1.637-1.85 3.37-1.85 3.601 0 4.267 2.37 4.267 5.455v6.286zM5.337 7.433a2.062 2.062 0 01-2.063-2.065 2.064 2.064 0 112.063 2.065zm1.782 13.019H3.555V9h3.564v11.452zM22.225 0H1.771C.792 0 0 .774 0 1.729v20.542C0 23.227.792 24 1.771 24h20.451C23.2 24 24 23.227 24 22.271V1.729C24 .774 23.2 0 22.222 0h.003z"/></svg>
            Share on LinkedIn
          </a>
          <a href="mailto:?subject=What+is+a+Designated+Person+Ashore+%28DPA%29+%E2%80%94+and+do+you+need+one%3F&body=I+thought+you+might+find+this+article+useful%3A+https%3A%2F%2Ftasmanmaritime.com%2Fblog%2Fposts%2F_article-footer" class="article-share__btn">
            <svg width="16" height="16" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" aria-hidden="true"><path d="M4 4h16c1.1 0 2 .9 2 2v12c0 1.1-.9 2-2 2H4c-1.1 0-2-.9-2-2V6c0-1.1.9-2 2-2z"/><polyline points="22,6 12,13 2,6"/></svg>
            Share by email
          </a>
        </div>

        <div class="article-cta">
          <h3>Have a question about this topic?</h3>
          <p>Book a free 15-minute call with Craig Hopkins — practical answers, no jargon.</p>
          <button type="button" class="btn btn--primary" data-toggle="consult-modal">Book a free consultation</button>
        </div>

      </article>

      <aside class="article-sidebar">
        <div class="blog-sidebar__block">
          <p class="blog-sidebar__heading">About the author</p>
          <div style="display:flex;align-items:center;gap:12px;margin-bottom:12px;">
            <picture>
              <source srcset="/assets/images/craig.webp" type="image/webp">
              <img src="/assets/images/craig.jpg" alt="Craig Hopkins" style="width:56px;height:56px;border-radius:50%;object-fit:cover;object-position:center top;" loading="lazy">
            </picture>
            <div>
              <strong style="display:block;color:var(--navy);font-size:14px;">Craig Hopkins</strong>
              <span style="color:var(--slate);font-size:13px;">Founder &amp; Principal Consultant</span>
            </div>
          </div>
          <p style="font-size:13.5px;color:var(--slate);margin:0;">MCA Master 3000T. Two decades of worldwide command on commercially operated superyachts. Lloyd&rsquo;s Maritime Institute ISM/ISPS/MLC Internal Auditor and CSO certified.</p>
        </div>

        <div class="blog-sidebar__block">
          <p class="blog-sidebar__heading">More articles</p>
          
<p>If your vessel falls under the ISM Code, you need a Designated Person Ashore. Most operators know this. Fewer are clear on what the DPA role actually requires, what "reachable at all times" means in practice, and why having the right DPA in the right timezone matters more than most people appreciate until it doesn't.</p>

<h2>What the ISM Code says</h2>

<p>ISM Code Regulation 4 is unambiguous: <em>"To ensure the safe operation of each ship and to provide a link between the company and those on board, every company, as appropriate, should designate a person or persons ashore having direct access to the highest level of management."</em></p>

<p>The designated person's responsibilities include monitoring the safety and pollution-prevention aspects of each vessel, ensuring adequate resources and shore-based support are provided, and being available at all times as the point of contact between the vessel and the company's senior management. That last point — available at all times — is the one most frequently underestimated.</p>

<h2>What "available at all times" actually means</h2>

<p>It means what it says. A vessel does not stop operating at 0200. Emergencies do not wait for office hours. A vessel in distress in the South Pacific at 0200 UTC — the middle of the European night — cannot reach a DPA asleep in Monaco or Antibes. That same 0200 UTC is 1300 to 1500 the following afternoon in New Zealand. A NZ-based backup DPA is at their desk. The ISM Code requirement for 24-hour accessibility is either being met or it isn't — and a sleeping European DPA is not meeting it.</p>

<p>This is not a theoretical concern. Port state control officers ask to see evidence of DPA contact arrangements and will test whether the provided number is actually reachable. A non-functioning DPA is a documented deficiency.</p>

<h2>Who can be a DPA?</h2>

<p>The ISM Code sets out the functional requirements for the DPA role — direct access to senior management, understanding of safety management requirements, and 24-hour availability — but does not mandate a specific certificate by name. In practice however, flag states, Recognised Organisations, and port state control increasingly expect the DPA to demonstrate formal competence through a recognised DPA qualification — structured training in ISM Code requirements, emergency response, and the legal responsibilities of the role. Several classification societies and maritime training providers offer DPA certification programmes. In practice, a competent DPA should have:</p>

<ul>
  <li>The ISM Code and the company's SMS</li>
  <li>The types of vessels and operations involved</li>
  <li>Emergency response procedures and escalation paths</li>
  <li>The flag state's requirements and the Recognised Organisation involved</li>
</ul>

<p>For larger shipping companies, the DPA is typically a senior shore-side employee. For smaller operators, yacht management companies, and individual vessel owners, an external contracted DPA is a practical and commonly used alternative.</p>

<h2>The case for an external contracted DPA</h2>

<p>An external contracted DPA provides the same function as an in-house one — formal designation in the SMS, 24-hour reachability, direct access to management, oversight of compliance — without requiring the vessel owner or management company to employ a dedicated shore-side role.</p>

<p>For vessels with internationally based management and crews operating in the South Pacific, New Zealand, or Australian waters, there is an additional practical argument: timezone coverage. A primary DPA based in Antibes or Fort Lauderdale is available during European or Atlantic business hours — but unreachable in the middle of their night. New Zealand and Australia sit 11 to 13 hours ahead of Europe, meaning NZ/Australian business hours run directly across the European overnight. When it is 0200 UTC and the European DPA is asleep, it is already early afternoon in New Zealand — the backup DPA is working, reachable, and available.</p>

<blockquote>
  "The captain called at 0200 UTC — a crew welfare issue that needed shore-side escalation. In the south of France it was 0300 in the morning and the primary DPA was unreachable. In New Zealand it was early afternoon. The backup DPA took the call, escalated to management, and the issue was managed before it became a formal incident."
</blockquote>

<h2>What a contracted DPA arrangement looks like</h2>

<p>A contracted DPA arrangement typically involves a formal agreement between the DPA and the vessel's company that specifies:</p>

<ul>
  <li>The vessels covered and the SMS applicable to each</li>
  <li>Contact arrangements and response time expectations</li>
  <li>Escalation paths to the company's senior management</li>
  <li>Scope of involvement in audits, drills, and SMS reviews</li>
  <li>Handover procedures with the primary DPA where applicable</li>
</ul>

<p>The DPA is named in the SMS and their contact details are on board. They are not a silent contract — they are an active participant in the company's safety management, and their involvement needs to be genuine to satisfy port state control scrutiny.</p>

<h2>The DPA and the CSO — not the same role</h2>

<p>A common source of confusion: the DPA (ISM Code) and the Company Security Officer or CSO (ISPS Code) are different roles with different functions. The DPA covers safety management; the CSO covers security management. They can be — and in smaller operations, often are — the same person. But conflating the two roles without explicitly documenting that arrangement in both the SMS and the Ship Security Plan creates compliance gaps.</p>

<h2>Summary</h2>

<p>If your vessel needs a DPA under the ISM Code, the requirement is genuine and the consequences of a non-functioning arrangement are real — deficiency citations from PSC, potential detention, and a captain without the shore-side support they need when things go wrong. An external contracted DPA is a legitimate, commonly used solution, particularly for smaller operators and for vessels in time zones where European-based management teams are unavailable overnight.</p>

<p>For vessels operating in or heading to New Zealand, Australian, and South Pacific waters, timezone-appropriate DPA cover is worth specific attention before departure.</p>

<footer class="site-footer">
  <div class="site-footer__inner">

    <div class="site-footer__col">
      <a href="/" class="site-footer__logo-link">
        <picture>
          <source srcset="/assets/images/logo-web-white.webp" type="image/webp">
          <img src="/assets/images/logo-web-white.png"
               alt="Tasman Maritime Consulting"
               class="site-footer__logo"
               width="200" height="130"
               loading="lazy" decoding="async">
        </picture>
      </a>
      <p class="site-footer__tagline">ISM/ISPS/MLC audit and DPA/CSO services for vessels operating in or planning operations in New Zealand, Australian, and South Pacific waters.</p>
    </div>

    <div class="site-footer__col">
      <p class="site-footer__heading">Services</p>
      <ul>
        <li><a href="/services/dpa-backup-dpa.php">DPA &amp; backup DPA</a></li>
        <li><a href="/services/cso.php">Company Security Officer</a></li>
        <li><a href="/services/internal-auditor.php">Internal audits</a></li>
        <li><a href="/services/lead-auditor.php">Lead audits</a></li>
      </ul>
    </div>

    <div class="site-footer__col">
      <p class="site-footer__heading">Regions</p>
      <ul>
        <li><a href="/regions/new-zealand.php">New Zealand</a></li>
        <li><a href="/regions/australia.php">Australia</a></li>
        <li><a href="/regions/south-pacific.php">South Pacific</a></li>
        <li><a href="/flag-states.php">Flag states</a></li>
      </ul>
    </div>

    <div class="site-footer__col">
      <p class="site-footer__heading">Contact</p>
      <ul>
                        <li><a href="mailto:enquiries@tasmanmaritime.com">enquiries@tasmanmaritime.com</a></li>
        <li><a href="#" data-toggle="consult-modal">Book a free consultation</a></li>
        <li>
          <a href="https://www.linkedin.com/company/tasmanmaritime/" target="_blank" rel="noopener" class="footer-linkedin">
            <svg width="14" height="14" viewBox="0 0 24 24" fill="currentColor" aria-hidden="true" style="vertical-align:middle;margin-right:5px;"><path d="M20.447 20.452h-3.554v-5.569c0-1.328-.027-3.037-1.852-3.037-1.853 0-2.136 1.445-2.136 2.939v5.667H9.351V9h3.414v1.561h.046c.477-.9 1.637-1.85 3.37-1.85 3.601 0 4.267 2.37 4.267 5.455v6.286zM5.337 7.433a2.062 2.062 0 01-2.063-2.065 2.064 2.064 0 112.063 2.065zm1.782 13.019H3.555V9h3.564v11.452zM22.225 0H1.771C.792 0 0 .774 0 1.729v20.542C0 23.227.792 24 1.771 24h20.451C23.2 24 24 23.227 24 22.271V1.729C24 .774 23.2 0 22.222 0h.003z"/></svg>
            Follow on LinkedIn
          </a>
        </li>
      </ul>
    </div>

  </div>

  <div class="site-footer__legal">
    <p>&copy; 2026 Tasman Maritime Consulting. All rights reserved.</p>
    <ul>
      <li><a href="/sitemap.xml">Sitemap</a></li>
      <li><a href="/quality-and-policies">Quality &amp; policies</a></li>
      <li><a href="/privacy-policy">Privacy policy</a></li>
      <li><a href="/terms.php">Terms of use</a></li>
    </ul>
  </div>
</footer>

<script src="/assets/js/main.js" defer></script>
<div class="cookie-banner" id="cookieBanner" role="dialog" aria-labelledby="cookieBannerTitle" aria-describedby="cookieBannerDesc" hidden>
  <div class="cookie-banner__inner">
    <div class="cookie-banner__text">
      <p id="cookieBannerTitle"><strong>Cookie &amp; analytics notice</strong></p>
      <p id="cookieBannerDesc">This site uses Google Analytics to understand how visitors use it. No personal information is collected without your consent. See our <a href="/privacy-policy" class="cookie-banner__link">Privacy policy</a>.</p>
    </div>
    <div class="cookie-banner__actions">
      <button type="button" class="cookie-banner__accept" id="cookieAccept">Accept analytics</button>
      <button type="button" class="cookie-banner__decline" id="cookieDecline">No thanks</button>
    </div>
  </div>
</div>

<script>
(function() {
  var GA4_ID = 'G-W252M135WJ';
  var banner = document.getElementById('cookieBanner');
  var consent = localStorage.getItem('tm_cookie_consent');

  function loadGA4() {
    if (!GA4_ID) return;
    var s = document.createElement('script');
    s.async = true;
    s.src = 'https://www.googletagmanager.com/gtag/js?id=' + GA4_ID;
    document.head.appendChild(s);
    window.dataLayer = window.dataLayer || [];
    function gtag(){dataLayer.push(arguments);}
    gtag('js', new Date());
    gtag('config', GA4_ID, {anonymize_ip: true});
  }

  if (consent === 'accepted') {
    loadGA4();
  } else if (consent === null) {
    banner.hidden = false;
  }

  document.getElementById('cookieAccept').addEventListener('click', function() {
    localStorage.setItem('tm_cookie_consent', 'accepted');
    banner.hidden = true;
    loadGA4();
  });

  document.getElementById('cookieDecline').addEventListener('click', function() {
    localStorage.setItem('tm_cookie_consent', 'declined');
    banner.hidden = true;
  });
})();
</script>
</body>
</html>

<p>If you operate a commercial vessel and have encountered the ISM Code, you have probably also encountered conflicting advice about whether it applies to you, what it actually requires, and what happens if you get it wrong. This article offers a clear, practical explanation — written from the perspective of someone who has managed a Safety Management System at sea and audited them from the shore side.</p>

<h2>What the ISM Code is</h2>

<p>The International Safety Management Code — the ISM Code — is a mandatory IMO standard adopted under SOLAS Chapter IX. Its purpose is straightforward: to establish an international standard for the safe management and operation of ships and for pollution prevention.</p>

<p>In plain terms, the ISM Code requires a shipping company to have a documented <strong>Safety Management System (SMS)</strong> — a set of policies, procedures, and records that define how the vessel is operated safely. The SMS must cover everything from maintenance and emergency procedures to crew training, incident reporting, and the communication lines between ship and shore.</p>

<p>The Code also requires a company-level point of accountability ashore — the <strong>Designated Person Ashore (DPA)</strong> — who has direct access to the highest level of management and can be reached at all times when the vessel is operating.</p>

<h2>Which vessels does it apply to?</h2>

<p>The ISM Code applies to ships engaged in international voyages in the following categories:</p>

<ul>
  <li>Passenger ships, including high-speed passenger craft</li>
  <li>Oil tankers, chemical tankers, gas carriers, bulk carriers and cargo high-speed craft of 500 gross tonnage (GT) and above</li>
  <li>Other cargo ships and mobile offshore drilling units of 500 GT and above</li>
</ul>

<p>For commercially operated yachts and superyachts, the threshold matters: ISM applies to commercially operated passenger vessels on international voyages. A superyacht operating commercially under a Red Ensign Group flag (Isle of Man, Cayman Islands, Channel Islands) will generally fall within this requirement once it exceeds 500GT or carries passengers on international voyages. Smaller commercially operated yachts typically fall under the <strong>MCA Large Yacht Code (LY3)</strong>, which contains its own SMS requirements — but the principles of good safety management apply regardless of which framework governs your vessel.</p>

<h2>What does compliance actually look like?</h2>

<p>A company subject to the ISM Code must hold two certificates:</p>

<ul>
  <li>A <strong>Document of Compliance (DOC)</strong> — issued to the company, covering the types of ships it operates</li>
  <li>A <strong>Safety Management Certificate (SMC)</strong> — issued to each individual vessel</li>
</ul>

<p>Both are issued by a Recognised Organisation (a classification society authorised by the vessel's flag state — Lloyd's Register, DNV, Bureau Veritas, ABS, ClassNK, and others) or directly by the flag state administration. They follow a statutory audit, are renewed periodically, and verified through annual or intermediate audits.</p>

<p>What the certificates represent, though, is not the end of the story — they represent a point-in-time assessment. What happens between those statutory audits is where genuine compliance either exists or doesn't.</p>

<h2>The internal audit — and why independence matters</h2>

<p>ISM Code Clause 12.1 requires companies to carry out internal safety audits to verify that safety and pollution-prevention activities comply with the SMS. The Code specifically requires that auditors be independent of the activities being audited — meaning the engineer cannot audit his own maintenance records, and the captain cannot be the sole auditor of bridge procedures he has authored.</p>

<p>That requirement for independence from the activity is the floor, not the ceiling. The deeper value of internal audit comes from genuine objectivity — an assessor who brings no assumptions about how things are done, no loyalty to existing procedures, and no hesitation in recording what the evidence actually shows rather than what the SMS says should be happening.</p>

<p>This is where good audit methodology matters. A structured internal audit follows a consistent process: planning against defined criteria, gathering objective evidence, assessing findings impartially, and reporting clearly — including findings that are uncomfortable. These are not bureaucratic steps; they are what separates an audit that actually improves safety from one that confirms what everyone already believes.</p>

<blockquote>
The most common pattern in SMS audits: the system is well-written but not well-lived. The procedures exist on paper; the records tell a different story. A rigorous internal audit closes that gap — before a statutory auditor or port state control officer does it for you.
</blockquote>

<p>Critically, internal audit findings are confidential to the company — they exist to drive improvement, not to create a paper trail for regulators. That confidentiality is itself a cornerstone of effective auditing: it allows genuine findings to be reported and addressed without fear of external consequence.</p>

<h2>Evidence-based assessment — what auditors actually look at</h2>

<p>A well-conducted ISM internal audit is evidence-based. It does not rely on what crew members say should be happening — it examines what the records show actually happened. Drill logs, maintenance records, non-conformity reports, hours of rest records, safety committee minutes — these are the objective evidence against which the SMS is assessed.</p>

<p>An SMS with no non-conformity reports is almost always an SMS where the reporting culture hasn't taken hold, not one where nothing has gone wrong. Port state control officers in New Zealand and Australia know this — an empty NCR log is a finding in itself.</p>

<h2>Risk-based thinking throughout the SMS</h2>

<p>The ISM Code requires companies to identify risks and implement safeguards — but the Code itself doesn't prescribe exactly how. Good safety management means applying risk-based thinking proportionately: the hazards relevant to a 45-metre superyacht on a Pacific circuit are not the same as those for a bulk carrier on a fixed route, and the SMS should reflect that. A Safety Management System that has been lifted wholesale from a template and applied without adaptation to the specific vessel, its operations, and its trading areas is one that will struggle under scrutiny — both in an audit and at the quayside.</p>

<h2>What port state control checks in New Zealand and Australia</h2>

<p>Port state control in both New Zealand (Maritime NZ) and Australia (AMSA) actively checks ISM compliance for visiting foreign-flagged vessels. PSC officers can board your vessel, examine your SMS, check your certificates, and detain the vessel if serious deficiencies are found. A missing or expired SMC, an unreachable DPA, or an SMS that clearly does not reflect actual operations are all grounds for detention.</p>

<p>For vessels arriving in this region on a Pacific circuit — often after a long passage from French Polynesia or following a refit period — PSC attention at the first port of call is a real risk if compliance preparations have been deferred during the voyage. The time to close nonconformities is before you arrive, not after a PSC officer has recorded them.</p>

<h2>Summary</h2>

<p>The ISM Code requires commercially operated vessels above certain thresholds to have a documented Safety Management System, a company-level Document of Compliance, a vessel-level Safety Management Certificate, and a Designated Person Ashore available at all times. For vessels planning passages to New Zealand, Australia, or the Pacific, ensuring all of these are current and genuinely implemented — not just on paper — before arrival is the single most valuable compliance step you can take.</p>

<p>If you are unsure whether the ISM Code applies to your vessel or what your current compliance position looks like, a short initial conversation is usually all it takes to get clarity.</p>


<p>If you operate a commercial vessel and have encountered the ISM Code, you have probably also encountered conflicting advice about whether it applies to you, what it actually requires, and what happens if you get it wrong. This article offers a clear, practical explanation — written from the perspective of someone who has managed a Safety Management System at sea and audited them from the shore side.</p>

<h2>What the ISM Code is</h2>

<p>The International Safety Management Code — the ISM Code — is a mandatory IMO standard adopted under SOLAS Chapter IX. Its purpose is straightforward: to establish an international standard for the safe management and operation of ships and for pollution prevention.</p>

<p>In plain terms, the ISM Code requires a shipping company to have a documented <strong>Safety Management System (SMS)</strong> — a set of policies, procedures, and records that define how the vessel is operated safely. The SMS must cover everything from maintenance and emergency procedures to crew training, incident reporting, and the communication lines between ship and shore.</p>

<p>The Code also requires a company-level point of accountability ashore — the <strong>Designated Person Ashore (DPA)</strong> — who has direct access to the highest level of management and can be reached at all times when the vessel is operating.</p>

<h2>Which vessels does it apply to?</h2>

<p>The ISM Code applies to ships engaged in international voyages in the following categories:</p>

<ul>
  <li>Passenger ships, including high-speed passenger craft</li>
  <li>Oil tankers, chemical tankers, gas carriers, bulk carriers and cargo high-speed craft of 500 gross tonnage (GT) and above</li>
  <li>Other cargo ships and mobile offshore drilling units of 500 GT and above</li>
</ul>

<p>For commercially operated yachts and superyachts, the threshold matters: ISM applies to commercially operated passenger vessels on international voyages. A superyacht operating commercially under a Red Ensign Group flag (Isle of Man, Cayman Islands, Channel Islands) will generally fall within this requirement once it exceeds 500GT or carries passengers on international voyages. Smaller commercially operated yachts typically fall under the <strong>MCA Large Yacht Code (LY3)</strong>, which contains its own SMS requirements — but the principles of good safety management apply regardless of which framework governs your vessel.</p>

<h2>What does compliance actually look like?</h2>

<p>A company subject to the ISM Code must hold two certificates:</p>

<ul>
  <li>A <strong>Document of Compliance (DOC)</strong> — issued to the company, covering the types of ships it operates</li>
  <li>A <strong>Safety Management Certificate (SMC)</strong> — issued to each individual vessel</li>
</ul>

<p>Both are issued by a Recognised Organisation (a classification society authorised by the vessel's flag state — Lloyd's Register, DNV, Bureau Veritas, ABS, ClassNK, and others) or directly by the flag state administration. They follow a statutory audit, are renewed periodically, and verified through annual or intermediate audits.</p>

<p>What the certificates represent, though, is not the end of the story — they represent a point-in-time assessment. What happens between those statutory audits is where genuine compliance either exists or doesn't.</p>

<h2>The internal audit — and why independence matters</h2>

<p>ISM Code Clause 12.1 requires companies to carry out internal safety audits to verify that safety and pollution-prevention activities comply with the SMS. The Code specifically requires that auditors be independent of the activities being audited — meaning the engineer cannot audit his own maintenance records, and the captain cannot be the sole auditor of bridge procedures he has authored.</p>

<p>That requirement for independence from the activity is the floor, not the ceiling. The deeper value of internal audit comes from genuine objectivity — an assessor who brings no assumptions about how things are done, no loyalty to existing procedures, and no hesitation in recording what the evidence actually shows rather than what the SMS says should be happening.</p>

<p>This is where good audit methodology matters. A structured internal audit follows a consistent process: planning against defined criteria, gathering objective evidence, assessing findings impartially, and reporting clearly — including findings that are uncomfortable. These are not bureaucratic steps; they are what separates an audit that actually improves safety from one that confirms what everyone already believes.</p>

<blockquote>
The most common pattern in SMS audits: the system is well-written but not well-lived. The procedures exist on paper; the records tell a different story. A rigorous internal audit closes that gap — before a statutory auditor or port state control officer does it for you.
</blockquote>

<p>Critically, internal audit findings are confidential to the company — they exist to drive improvement, not to create a paper trail for regulators. That confidentiality is itself a cornerstone of effective auditing: it allows genuine findings to be reported and addressed without fear of external consequence.</p>

<h2>Evidence-based assessment — what auditors actually look at</h2>

<p>A well-conducted ISM internal audit is evidence-based. It does not rely on what crew members say should be happening — it examines what the records show actually happened. Drill logs, maintenance records, non-conformity reports, hours of rest records, safety committee minutes — these are the objective evidence against which the SMS is assessed.</p>

<p>An SMS with no non-conformity reports is almost always an SMS where the reporting culture hasn't taken hold, not one where nothing has gone wrong. Port state control officers in New Zealand and Australia know this — an empty NCR log is a finding in itself.</p>

<h2>Risk-based thinking throughout the SMS</h2>

<p>The ISM Code requires companies to identify risks and implement safeguards — but the Code itself doesn't prescribe exactly how. Good safety management means applying risk-based thinking proportionately: the hazards relevant to a 45-metre superyacht on a Pacific circuit are not the same as those for a bulk carrier on a fixed route, and the SMS should reflect that. A Safety Management System that has been lifted wholesale from a template and applied without adaptation to the specific vessel, its operations, and its trading areas is one that will struggle under scrutiny — both in an audit and at the quayside.</p>

<h2>What port state control checks in New Zealand and Australia</h2>

<p>Port state control in both New Zealand (Maritime NZ) and Australia (AMSA) actively checks ISM compliance for visiting foreign-flagged vessels. PSC officers can board your vessel, examine your SMS, check your certificates, and detain the vessel if serious deficiencies are found. A missing or expired SMC, an unreachable DPA, or an SMS that clearly does not reflect actual operations are all grounds for detention.</p>

<p>For vessels arriving in this region on a Pacific circuit — often after a long passage from French Polynesia or following a refit period — PSC attention at the first port of call is a real risk if compliance preparations have been deferred during the voyage. The time to close nonconformities is before you arrive, not after a PSC officer has recorded them.</p>

<h2>Summary</h2>

<p>The ISM Code requires commercially operated vessels above certain thresholds to have a documented Safety Management System, a company-level Document of Compliance, a vessel-level Safety Management Certificate, and a Designated Person Ashore available at all times. For vessels planning passages to New Zealand, Australia, or the Pacific, ensuring all of these are current and genuinely implemented — not just on paper — before arrival is the single most valuable compliance step you can take.</p>

<p>If you are unsure whether the ISM Code applies to your vessel or what your current compliance position looks like, a short initial conversation is usually all it takes to get clarity.</p>


<p>One of the most common areas of confusion in superyacht compliance is the relationship between the IMO ISM Code and the MCA Large Yacht Code (LY3). Both involve safety management requirements. Both apply to commercially operated yachts. But they do not apply to the same vessels in the same way, and conflating them leads to real compliance gaps.</p>

<p>This article explains the distinction clearly — from the perspective of someone who has operated commercially under both frameworks.</p>

<h2>The MCA Large Yacht Code (LY3)</h2>

<p>The MCA Large Yacht Code — currently in its third edition (LY3) — is a UK Maritime and Coastguard Agency standard that applies to <strong>commercially operated yachts of 24 metres in length and above</strong> that are flagged under Red Ensign Group registries (Isle of Man, Cayman Islands, Bermuda, Channel Islands, British Virgin Islands, and others).</p>

<p>LY3 is a comprehensive framework covering construction, stability, life-saving appliances, fire protection, crew certification, watchkeeping, and — critically for this discussion — operational requirements including a <strong>Safety Management System</strong>. The LY3 SMS requirements are derived from the ISM Code but adapted for the superyacht context.</p>

<p>For commercially operated yachts of 24m and above but <strong>under 500 gross tonnage</strong> operating under Red Ensign Group flags, LY3 is the primary compliance framework. The ISM Code, as an IMO instrument, does not formally apply to vessels below 500GT — LY3 is the applicable standard.</p>

<h2>The ISM Code</h2>

<p>The IMO ISM Code applies to ships engaged in international voyages, and for commercially operated passenger vessels and cargo ships, the threshold is <strong>500 gross tonnage</strong>. For a superyacht, this means:</p>

<ul>
  <li>A commercially operated yacht of 24m to approximately 500GT operating under a Red Ensign Group flag: <strong>LY3 applies</strong></li>
  <li>A commercially operated yacht over 500GT on international voyages: <strong>both LY3 and ISM Code requirements apply</strong></li>
  <li>A commercially operated passenger vessel on international voyages regardless of GT: <strong>SOLAS and ISM apply</strong></li>
</ul>

<p>In practice, this means that a well-run 45-metre superyacht under 500GT on a commercial charter operating under an IoM flag needs to comply with LY3 — including its SMS requirements — but does not formally require ISM certification (a DOC and SMC) in the way a 600GT vessel does.</p>

<h2>Where it gets complicated — flag state variations</h2>

<p>Flag states within the Red Ensign Group each maintain their own specific requirements, and the precise application of LY3 versus ISM can vary. The Isle of Man Ship Registry, Cayman Islands Shipping Registry, and Channel Islands registries all apply LY3 but may have specific additional requirements or interpretations. Your flag state and your Recognised Organisation (the classification society your flag state delegates survey authority to) are the definitive source for your specific vessel's obligations.</p>

<p>What is consistent across all of them is this: <strong>commercially operating without a functioning, documented SMS — whether under LY3 or ISM — is not an option</strong>. Both frameworks require it, and port state control in New Zealand, Australia, and across the Pacific actively checks that it exists and is genuinely implemented.</p>

<h2>ISPS — the other code that applies to both</h2>

<p>The ISPS Code (International Ship and Port Facility Security Code) applies to passenger vessels on international voyages regardless of the LY3/ISM distinction. If your superyacht is operating commercially and making international port calls — including the Pacific island states, PNG, or Indonesian ports — ISPS compliance is required. This means:</p>

<ul>
  <li>An approved Ship Security Plan (SSP)</li>
  <li>A Ship Security Officer (SSO) on board</li>
  <li>A <strong>Company Security Officer (CSO)</strong> ashore, reachable at all times</li>
  <li>Port-specific security measures documented and implemented before arrival</li>
</ul>

<h2>What this means practically for vessels approaching this region</h2>

<p>For a commercially operated superyacht on a Pacific circuit heading for New Zealand or Australia, the compliance picture typically looks like this:</p>

<ul>
  <li><strong>LY3 compliance</strong> — SMS, crew certificates, survey status current</li>
  <li><strong>ISM compliance (if over 500GT)</strong> — DOC and SMC current, DPA in place and reachable</li>
  <li><strong>ISPS compliance</strong> — SSP current, CSO in place and reachable, port-specific security measures ready</li>
</ul>

<p>Port state control officers in Auckland, Sydney, and Cairns are familiar with all three frameworks and will check them. A vessel arriving after a long Pacific passage with lapsed certificates, an unreachable DPA, or an SMS that clearly has not been maintained is a detention risk at exactly the point where the crew and owner least want the disruption.</p>

<h2>Summary</h2>

<p>For commercially operated superyachts under Red Ensign Group flags: LY3 is your primary framework if you are under 500GT; ISM applies additionally if you are over 500GT on international voyages. Both require a functioning SMS. ISPS applies on international voyages regardless of size. Know which framework applies to your vessel, ensure your certificates are current, and ensure your DPA and CSO are reachable in the timezone your vessel is actually operating in.</p>

<p>If you are heading to the South Pacific, New Zealand, or Australia and are uncertain about your compliance position, a pre-departure review is worth considerably more than the time it takes.</p>


<p>New Zealand and Australia are not the same as Tahiti or Fiji when it comes to port state control. Both are members of the Tokyo Memorandum of Understanding on Port State Control, both have professional and well-resourced PSC teams, and both are increasingly focused on commercially operated superyachts — a category that has historically received lighter scrutiny than commercial shipping but is no longer able to count on that.</p>

<p>If your vessel is arriving from the Pacific, this guide explains how PSC works in each country, what triggers a detailed inspection, and what the outcomes look like when things are not in order.</p>

<h2>How port state control works — the basics</h2>

<p>Port state control is the inspection of foreign-flagged vessels by the authorities of the country whose port the vessel has entered. The legal basis is a series of international conventions — SOLAS, MARPOL, STCW, MLC, ISPS — that member states have agreed to enforce on vessels in their waters, regardless of the vessel's flag.</p>

<p>In practical terms: when your vessel arrives at a New Zealand or Australian port, the PSC authority has the right to board and inspect. They are checking whether your vessel complies with the international conventions. If they find deficiencies, they can require them to be rectified before departure. If the deficiencies are serious enough, they can detain the vessel — preventing it from leaving until the issues are resolved.</p>

<h2>Maritime NZ — port state control in New Zealand</h2>

<p>In New Zealand, port state control is conducted by <strong>Maritime NZ</strong>. PSC officers are based primarily in Auckland, Tauranga, Wellington, Lyttelton, and Dunedin — though they can operate at any port where vessels arrive.</p>

<p>Maritime NZ targets vessels for inspection using a risk-based targeting system within the Tokyo MOU framework. Factors that increase your vessel's targeting priority include:</p>

<ul>
  <li>First visit to New Zealand waters</li>
  <li>Significant time since last PSC inspection</li>
  <li>Previous deficiency history in the Tokyo MOU region</li>
  <li>Flag state performance — vessels under flags with poor Tokyo MOU performance records receive more attention</li>
  <li>Vessel type and age</li>
</ul>

<p>A superyacht arriving in New Zealand for the first time, from a Pacific crossing, under a Red Ensign Group flag, with no recent PSC history in the region, is a moderate-to-high targeting priority. That does not mean an inspection is certain — but it means the probability is real enough to prepare for.</p>

<p><strong>Typical entry points in New Zealand:</strong> Whangarei (Marsden Cove, Norsand Boatyard) and Auckland (Viaduct Harbour, Westhaven) are the most common first ports of call for superyachts arriving from the Pacific. PSC inspections at these ports are routine.</p>

<h2>AMSA — port state control in Australia</h2>

<p>In Australia, port state control is conducted by the <strong>Australian Maritime Safety Authority (AMSA)</strong>. AMSA has a well-established reputation for thorough inspections and follows both the Tokyo MOU and, for some vessel categories, Paris MOU procedures.</p>

<p>AMSA PSC officers are active at all major Australian ports: Brisbane, Gold Coast, Sydney, Melbourne, Cairns, Darwin, Fremantle, and others. AMSA uses a similar risk-based targeting system to Maritime NZ, with comparable factors affecting inspection priority.</p>

<p>One distinction worth knowing: AMSA publishes its deficiency and detention records, and its PSC teams are known for detailed scrutiny of safety management systems — not just checking that the SMS exists, but testing whether it is genuinely implemented. This is an area where superyachts frequently fall short.</p>

<p><strong>Typical entry points in Australia:</strong> Cairns and Darwin are common first ports for vessels arriving from the Pacific or Southeast Asia. Brisbane, Sydney, and Melbourne are major refit destinations where PSC inspections occur regularly.</p>

<h2>What triggers a detailed inspection</h2>

<p>Not every arrival results in a detailed inspection. A PSC officer may conduct an initial check of certificates and overall condition and, if satisfied, issue a clearance without a full inspection. What triggers a move from initial check to detailed inspection:</p>

<ul>
  <li>Certificates not immediately available or visibly irregular</li>
  <li>Obvious deficiencies in condition observed during initial boarding</li>
  <li>Information from port agents, the crew, or other sources suggesting compliance issues</li>
  <li>High targeting priority based on the risk model</li>
  <li>Previous detention or significant deficiency history</li>
</ul>

<p>The best way to avoid triggering a detailed inspection is to present cleanly on the initial check — certificates in order, clearly maintained vessel, a captain who answers questions directly and confidently. A confident, well-prepared response to an initial check does not guarantee no inspection, but a flustered response almost always produces one.</p>

<h2>Deficiencies, rectification, and detention</h2>

<p>PSC deficiencies are categorised. Minor deficiencies that do not affect seaworthiness are typically noted and must be rectified by the next port or a specified date. More serious deficiencies — particularly those affecting safety equipment, certificates, or the functioning of the safety management system — require rectification before departure.</p>

<p>Detention occurs when deficiencies are serious enough that the vessel should not sail. Common grounds for detention of superyachts in the NZ/Australian region include:</p>

<ul>
  <li>Expired SMC or ISSC, or no DOC covering the vessel's operational category</li>
  <li>STCW crew certification deficiencies that leave the vessel undermanned for its operating area</li>
  <li>Fire detection or firefighting equipment deficiencies</li>
  <li>Life-saving appliance deficiencies — particularly life raft servicing</li>
  <li>No functioning DPA arrangement</li>
</ul>

<p>A detention means the vessel cannot depart until deficiencies are rectified and re-inspected. In Whangarei or Cairns, that may be manageable. In a remote port, it is a significant operational and financial event.</p>

<h2>Red Ensign Group vessels — specific considerations</h2>

<p>The majority of commercially operated superyachts in this region are registered under Red Ensign Group flags — Isle of Man, Cayman Islands, Channel Islands. PSC officers in New Zealand and Australia are familiar with these registries and know their survey and certification requirements well. A few specific points:</p>

<ul>
  <li>Red Ensign Group flags are generally well-regarded within the Tokyo MOU — vessels under IoM, Cayman, and Channel Islands flags are not automatically high-targeted on flag grounds alone</li>
  <li>However, the RO-issued certificates (DOC, SMC, ISSC) must be current and must reflect the vessel's actual operational category. A superyacht that has changed from private to commercial operation without updating its certification is a significant deficiency</li>
  <li>Flag state endorsements on crew STCW certificates are specifically checked — some Red Ensign Group registries require specific flag endorsements in addition to the STCW certificate</li>
</ul>

<h2>The case for a pre-arrival review</h2>

<p>Port state control officers have time, authority, and a checklist developed specifically to find the gaps that exist in the gap between what a vessel's SMS says and what its records demonstrate. The preparation window — while your vessel is still in the Pacific — is the best opportunity to find those gaps first.</p>

<p>A remote pre-arrival compliance review, completed in the weeks before arrival, covers the same ground a PSC officer covers: certificates, crew certification, SMS records, ISPS arrangements, safety equipment servicing. The difference is that the findings come to you, not to a PSC inspector, and you have time to act on them.</p>

<p>If your vessel is currently in the Pacific and arrival in New Zealand or Australia is planned between September and November, the window to complete this preparation is now.</p>


<p>New Zealand and Australia are not the same as Tahiti or Fiji when it comes to port state control. Both are members of the Tokyo Memorandum of Understanding on Port State Control, both have professional and well-resourced PSC teams, and both are increasingly focused on commercially operated superyachts — a category that has historically received lighter scrutiny than commercial shipping but is no longer able to count on that.</p>

<p>If your vessel is arriving from the Pacific, this guide explains how PSC works in each country, what triggers a detailed inspection, and what the outcomes look like when things are not in order.</p>

<h2>How port state control works — the basics</h2>

<p>Port state control is the inspection of foreign-flagged vessels by the authorities of the country whose port the vessel has entered. The legal basis is a series of international conventions — SOLAS, MARPOL, STCW, MLC, ISPS — that member states have agreed to enforce on vessels in their waters, regardless of the vessel's flag.</p>

<p>In practical terms: when your vessel arrives at a New Zealand or Australian port, the PSC authority has the right to board and inspect. They are checking whether your vessel complies with the international conventions. If they find deficiencies, they can require them to be rectified before departure. If the deficiencies are serious enough, they can detain the vessel — preventing it from leaving until the issues are resolved.</p>

<h2>Maritime NZ — port state control in New Zealand</h2>

<p>In New Zealand, port state control is conducted by <strong>Maritime NZ</strong>. PSC officers are based primarily in Auckland, Tauranga, Wellington, Lyttelton, and Dunedin — though they can operate at any port where vessels arrive.</p>

<p>Maritime NZ targets vessels for inspection using a risk-based targeting system within the Tokyo MOU framework. Factors that increase your vessel's targeting priority include:</p>

<ul>
  <li>First visit to New Zealand waters</li>
  <li>Significant time since last PSC inspection</li>
  <li>Previous deficiency history in the Tokyo MOU region</li>
  <li>Flag state performance — vessels under flags with poor Tokyo MOU performance records receive more attention</li>
  <li>Vessel type and age</li>
</ul>

<p>A superyacht arriving in New Zealand for the first time, from a Pacific crossing, under a Red Ensign Group flag, with no recent PSC history in the region, is a moderate-to-high targeting priority. That does not mean an inspection is certain — but it means the probability is real enough to prepare for.</p>

<p><strong>Typical entry points in New Zealand:</strong> Whangarei (Marsden Cove, Norsand Boatyard) and Auckland (Viaduct Harbour, Westhaven) are the most common first ports of call for superyachts arriving from the Pacific. PSC inspections at these ports are routine.</p>

<h2>AMSA — port state control in Australia</h2>

<p>In Australia, port state control is conducted by the <strong>Australian Maritime Safety Authority (AMSA)</strong>. AMSA has a well-established reputation for thorough inspections and follows both the Tokyo MOU and, for some vessel categories, Paris MOU procedures.</p>

<p>AMSA PSC officers are active at all major Australian ports: Brisbane, Gold Coast, Sydney, Melbourne, Cairns, Darwin, Fremantle, and others. AMSA uses a similar risk-based targeting system to Maritime NZ, with comparable factors affecting inspection priority.</p>

<p>One distinction worth knowing: AMSA publishes its deficiency and detention records, and its PSC teams are known for detailed scrutiny of safety management systems — not just checking that the SMS exists, but testing whether it is genuinely implemented. This is an area where superyachts frequently fall short.</p>

<p><strong>Typical entry points in Australia:</strong> Cairns and Darwin are common first ports for vessels arriving from the Pacific or Southeast Asia. Brisbane, Sydney, and Melbourne are major refit destinations where PSC inspections occur regularly.</p>

<h2>What triggers a detailed inspection</h2>

<p>Not every arrival results in a detailed inspection. A PSC officer may conduct an initial check of certificates and overall condition and, if satisfied, issue a clearance without a full inspection. What triggers a move from initial check to detailed inspection:</p>

<ul>
  <li>Certificates not immediately available or visibly irregular</li>
  <li>Obvious deficiencies in condition observed during initial boarding</li>
  <li>Information from port agents, the crew, or other sources suggesting compliance issues</li>
  <li>High targeting priority based on the risk model</li>
  <li>Previous detention or significant deficiency history</li>
</ul>

<p>The best way to avoid triggering a detailed inspection is to present cleanly on the initial check — certificates in order, clearly maintained vessel, a captain who answers questions directly and confidently. A confident, well-prepared response to an initial check does not guarantee no inspection, but a flustered response almost always produces one.</p>

<h2>Deficiencies, rectification, and detention</h2>

<p>PSC deficiencies are categorised. Minor deficiencies that do not affect seaworthiness are typically noted and must be rectified by the next port or a specified date. More serious deficiencies — particularly those affecting safety equipment, certificates, or the functioning of the safety management system — require rectification before departure.</p>

<p>Detention occurs when deficiencies are serious enough that the vessel should not sail. Common grounds for detention of superyachts in the NZ/Australian region include:</p>

<ul>
  <li>Expired SMC or ISSC, or no DOC covering the vessel's operational category</li>
  <li>STCW crew certification deficiencies that leave the vessel undermanned for its operating area</li>
  <li>Fire detection or firefighting equipment deficiencies</li>
  <li>Life-saving appliance deficiencies — particularly life raft servicing</li>
  <li>No functioning DPA arrangement</li>
</ul>

<p>A detention means the vessel cannot depart until deficiencies are rectified and re-inspected. In Whangarei or Cairns, that may be manageable. In a remote port, it is a significant operational and financial event.</p>

<h2>Red Ensign Group vessels — specific considerations</h2>

<p>The majority of commercially operated superyachts in this region are registered under Red Ensign Group flags — Isle of Man, Cayman Islands, Channel Islands. PSC officers in New Zealand and Australia are familiar with these registries and know their survey and certification requirements well. A few specific points:</p>

<ul>
  <li>Red Ensign Group flags are generally well-regarded within the Tokyo MOU — vessels under IoM, Cayman, and Channel Islands flags are not automatically high-targeted on flag grounds alone</li>
  <li>However, the RO-issued certificates (DOC, SMC, ISSC) must be current and must reflect the vessel's actual operational category. A superyacht that has changed from private to commercial operation without updating its certification is a significant deficiency</li>
  <li>Flag state endorsements on crew STCW certificates are specifically checked — some Red Ensign Group registries require specific flag endorsements in addition to the STCW certificate</li>
</ul>

<h2>The case for a pre-arrival review</h2>

<p>Port state control officers have time, authority, and a checklist developed specifically to find the gaps that exist in the gap between what a vessel's SMS says and what its records demonstrate. The preparation window — while your vessel is still in the Pacific — is the best opportunity to find those gaps first.</p>

<p>A remote pre-arrival compliance review, completed in the weeks before arrival, covers the same ground a PSC officer covers: certificates, crew certification, SMS records, ISPS arrangements, safety equipment servicing. The difference is that the findings come to you, not to a PSC inspector, and you have time to act on them.</p>

<p>If your vessel is currently in the Pacific and arrival in New Zealand or Australia is planned between September and November, the window to complete this preparation is now.</p>


<p>July and August are decision months in the Pacific. Vessels in French Polynesia, the Cook Islands, Fiji, Tonga, and Vanuatu are planning their southward passages ahead of the cyclone season — which historically becomes active by November. New Zealand and Australia are the destinations, and port state control in both countries is among the most thorough in the Pacific region.</p>

<p>If your vessel is in this position right now, this guide is written for you. It covers what Maritime NZ and AMSA inspectors are looking for, the most common compliance gaps found on superyachts arriving in this region, and — critically — what you can address remotely before you arrive.</p>

<h2>Why pre-arrival preparation matters here specifically</h2>

<p>Port state control in New Zealand and Australia is not the cursory glance some Pacific island ports offer. Both Maritime NZ and AMSA are members of the Tokyo Memorandum of Understanding on Port State Control, and both are known for thorough inspections. AMSA in particular has a reputation for detailed scrutiny.</p>

<p>A detained vessel at Whangarei, Auckland, Sydney, or Cairns — after a long Pacific passage, with crew expecting shore leave and an owner anticipating refit work — is a very expensive outcome. The deficiencies that trigger detention are, in the vast majority of cases, not new problems. They are problems that existed before the vessel arrived and were not identified.</p>

<p>The good news: most of them can be identified and closed before arrival, through a systematic remote review of your documents and records.</p>

<h2>What PSC officers look for on commercially operated superyachts</h2>

<p>Port state control inspections on commercially operated superyachts in New Zealand and Australia typically focus on the following areas:</p>

<h3>Certificates — validity and completeness</h3>
<ul>
  <li><strong>Document of Compliance (DOC)</strong> — company level, issued by your flag state's Recognised Organisation. Must cover the type of operation your vessel is undertaking</li>
  <li><strong>Safety Management Certificate (SMC)</strong> — vessel level. Check the issue date, the expiry date, and whether any intermediate or annual endorsements are due or overdue</li>
  <li><strong>International Ship Security Certificate (ISSC)</strong> — issued following ISPS audit. Commonly found to be expired on vessels that have been cruising in the Pacific for extended periods</li>
  <li><strong>LY3 compliance certificate / flag state survey</strong> — if your vessel operates under LY3 (most commercially operated yachts under 500GT on Red Ensign Group flags), your flag state survey must be current</li>
  <li><strong>MLC certificate or Declaration of Maritime Labour Compliance</strong> — applies to vessels over 500GT on international voyages, but good practice to have MLC-compliant crew welfare provisions regardless</li>
</ul>

<h3>Crew certification</h3>
<ul>
  <li>STCW certificates for all watchkeeping officers — check expiry dates across the crew</li>
  <li>Medical certificates — commonly found to have lapsed during a long passage</li>
  <li>Flag state endorsements — particularly relevant for Isle of Man and Cayman Islands flagged vessels, where some certificates require a specific flag state endorsement in addition to the STCW certificate itself</li>
</ul>

<h3>Safety Management System — is it alive or in a binder?</h3>
<p>This is where PSC officers most commonly find substantive deficiencies on superyachts. An SMS exists — it is almost always well-written — but the records tell a different story. PSC officers specifically look for:</p>
<ul>
  <li>Evidence that safety drills are being conducted at the required frequency — not just recorded</li>
  <li>Non-conformity and near-miss reporting records — an SMS with no reports is almost always an SMS where reporting is not actually happening</li>
  <li>Maintenance records consistent with the planned maintenance schedule</li>
  <li>Evidence that the DPA is actively involved — not just a name and phone number on a bulkhead</li>
</ul>

<h3>ISPS — security arrangements</h3>
<ul>
  <li>Ship Security Plan — current, vessel-specific, approved by the flag state or RO</li>
  <li>CSO contact details — reachable, documented, tested</li>
  <li>Port facility security records for previous port calls</li>
</ul>

<h3>Hours of rest records</h3>
<p>MLC-compliant hours of rest and work records are increasingly scrutinised on superyachts. A vessel with a small crew undertaking demanding deliveries or refit work is likely to have rest hour challenges. Having a realistic, properly maintained record — rather than one that has clearly been constructed to show compliance — is what inspectors are looking for.</p>

<h2>The most common deficiencies found on superyachts arriving in New Zealand and Australia</h2>

<p>Based on experience in this region, the most frequently found deficiencies are:</p>

<ol>
  <li><strong>Expired or incorrectly endorsed crew certificates</strong> — particularly medical certificates and flag state endorsements</li>
  <li><strong>ISSC expired or with endorsement gap</strong> — often occurs during extended Pacific cruising when the annual endorsement window passes without the vessel being near an RO surveyor</li>
  <li><strong>SMS records inconsistent with stated procedures</strong> — drills not recorded, maintenance not evidenced, reporting not happening</li>
  <li><strong>DPA not reachable</strong> — or not known to the crew beyond "there's a number on the bridge"</li>
  <li><strong>Fire detection and firefighting equipment</strong> — servicing certificates expired, particularly for fixed systems</li>
  <li><strong>Life raft and immersion suit servicing</strong> — extended Pacific passages put these through service cycles that are not always tracked</li>
  <li><strong>GMDSS equipment</strong> — battery certification, EPIRB registration and battery expiry, SART testing records</li>
</ol>

<h2>What you can address remotely — right now, before arrival</h2>

<p>The majority of the compliance gaps listed above can be identified — and most can be addressed — remotely, before your vessel arrives. A structured remote pre-arrival review involves:</p>

<ul>
  <li><strong>Document review</strong> — certificates, crew certification matrix, SMS records, ISPS arrangements, maintenance logs — shared electronically and reviewed systematically against the applicable code requirements</li>
  <li><strong>Gap report</strong> — a clear, prioritised list of what needs attention before arrival, what can be addressed en route, and what requires an appointment on arrival</li>
  <li><strong>Non-conformity close-out support</strong> — for gaps that can be closed before arrival (updated procedures, backdated records correction, crew briefings), guidance on how to address them properly</li>
  <li><strong>DPA review</strong> — confirming DPA contact arrangements are documented, current, and known to the crew</li>
</ul>

<p>This is not a statutory audit. It does not produce a certificate. What it produces is a clear picture of your compliance position before a PSC officer produces the same picture — with the difference that you have time to act on it.</p>

<h2>Timing — when to start</h2>

<p>If your vessel is currently in the Pacific and planning arrival in New Zealand or Australia between September and November, the right time to start this process is now — July or August. That allows:</p>

<ul>
  <li>Time to order and receive any crew certification that has lapsed or is due</li>
  <li>Time to arrange servicing for safety equipment at the next port of call in the Pacific</li>
  <li>Time to address SMS record gaps properly, not hastily</li>
  <li>Time to arrange ISSC endorsement or renewal through your RO before arrival</li>
</ul>

<p>A remote pre-arrival review can typically be completed within a week of receiving the relevant documents. The gap report goes back to the captain or chief officer, and follow-up support is available throughout the passage.</p>

<h2>How we can help</h2>

<p>Tasman Maritime Consulting offers remote pre-arrival compliance reviews for superyachts heading to New Zealand and Australia — covering ISM/SMS review, crew certification check, ISPS arrangements, and LY3/flag state certification status. We are based in New Zealand and Australia, and can be reached in the timezone your vessel is actually operating in during a Pacific passage.</p>

<p>If your vessel is currently in the Pacific and you would like to discuss a pre-arrival review, book a free 15-minute call. We can usually give you a clear initial picture of your compliance position within that first conversation.</p>


<p>July and August are decision months in the Pacific. Vessels in French Polynesia, the Cook Islands, Fiji, Tonga, and Vanuatu are planning their southward passages ahead of the cyclone season — which historically becomes active by November. New Zealand and Australia are the destinations, and port state control in both countries is among the most thorough in the Pacific region.</p>

<p>If your vessel is in this position right now, this guide is written for you. It covers what Maritime NZ and AMSA inspectors are looking for, the most common compliance gaps found on superyachts arriving in this region, and — critically — what you can address remotely before you arrive.</p>

<h2>Why pre-arrival preparation matters here specifically</h2>

<p>Port state control in New Zealand and Australia is not the cursory glance some Pacific island ports offer. Both Maritime NZ and AMSA are members of the Tokyo Memorandum of Understanding on Port State Control, and both are known for thorough inspections. AMSA in particular has a reputation for detailed scrutiny.</p>

<p>A detained vessel at Whangarei, Auckland, Sydney, or Cairns — after a long Pacific passage, with crew expecting shore leave and an owner anticipating refit work — is a very expensive outcome. The deficiencies that trigger detention are, in the vast majority of cases, not new problems. They are problems that existed before the vessel arrived and were not identified.</p>

<p>The good news: most of them can be identified and closed before arrival, through a systematic remote review of your documents and records.</p>

<h2>What PSC officers look for on commercially operated superyachts</h2>

<p>Port state control inspections on commercially operated superyachts in New Zealand and Australia typically focus on the following areas:</p>

<h3>Certificates — validity and completeness</h3>
<ul>
  <li><strong>Document of Compliance (DOC)</strong> — company level, issued by your flag state's Recognised Organisation. Must cover the type of operation your vessel is undertaking</li>
  <li><strong>Safety Management Certificate (SMC)</strong> — vessel level. Check the issue date, the expiry date, and whether any intermediate or annual endorsements are due or overdue</li>
  <li><strong>International Ship Security Certificate (ISSC)</strong> — issued following ISPS audit. Commonly found to be expired on vessels that have been cruising in the Pacific for extended periods</li>
  <li><strong>LY3 compliance certificate / flag state survey</strong> — if your vessel operates under LY3 (most commercially operated yachts under 500GT on Red Ensign Group flags), your flag state survey must be current</li>
  <li><strong>MLC certificate or Declaration of Maritime Labour Compliance</strong> — applies to vessels over 500GT on international voyages, but good practice to have MLC-compliant crew welfare provisions regardless</li>
</ul>

<h3>Crew certification</h3>
<ul>
  <li>STCW certificates for all watchkeeping officers — check expiry dates across the crew</li>
  <li>Medical certificates — commonly found to have lapsed during a long passage</li>
  <li>Flag state endorsements — particularly relevant for Isle of Man and Cayman Islands flagged vessels, where some certificates require a specific flag state endorsement in addition to the STCW certificate itself</li>
</ul>

<h3>Safety Management System — is it alive or in a binder?</h3>
<p>This is where PSC officers most commonly find substantive deficiencies on superyachts. An SMS exists — it is almost always well-written — but the records tell a different story. PSC officers specifically look for:</p>
<ul>
  <li>Evidence that safety drills are being conducted at the required frequency — not just recorded</li>
  <li>Non-conformity and near-miss reporting records — an SMS with no reports is almost always an SMS where reporting is not actually happening</li>
  <li>Maintenance records consistent with the planned maintenance schedule</li>
  <li>Evidence that the DPA is actively involved — not just a name and phone number on a bulkhead</li>
</ul>

<h3>ISPS — security arrangements</h3>
<ul>
  <li>Ship Security Plan — current, vessel-specific, approved by the flag state or RO</li>
  <li>CSO contact details — reachable, documented, tested</li>
  <li>Port facility security records for previous port calls</li>
</ul>

<h3>Hours of rest records</h3>
<p>MLC-compliant hours of rest and work records are increasingly scrutinised on superyachts. A vessel with a small crew undertaking demanding deliveries or refit work is likely to have rest hour challenges. Having a realistic, properly maintained record — rather than one that has clearly been constructed to show compliance — is what inspectors are looking for.</p>

<h2>The most common deficiencies found on superyachts arriving in New Zealand and Australia</h2>

<p>Based on experience in this region, the most frequently found deficiencies are:</p>

<ol>
  <li><strong>Expired or incorrectly endorsed crew certificates</strong> — particularly medical certificates and flag state endorsements</li>
  <li><strong>ISSC expired or with endorsement gap</strong> — often occurs during extended Pacific cruising when the annual endorsement window passes without the vessel being near an RO surveyor</li>
  <li><strong>SMS records inconsistent with stated procedures</strong> — drills not recorded, maintenance not evidenced, reporting not happening</li>
  <li><strong>DPA not reachable</strong> — or not known to the crew beyond "there's a number on the bridge"</li>
  <li><strong>Fire detection and firefighting equipment</strong> — servicing certificates expired, particularly for fixed systems</li>
  <li><strong>Life raft and immersion suit servicing</strong> — extended Pacific passages put these through service cycles that are not always tracked</li>
  <li><strong>GMDSS equipment</strong> — battery certification, EPIRB registration and battery expiry, SART testing records</li>
</ol>

<h2>What you can address remotely — right now, before arrival</h2>

<p>The majority of the compliance gaps listed above can be identified — and most can be addressed — remotely, before your vessel arrives. A structured remote pre-arrival review involves:</p>

<ul>
  <li><strong>Document review</strong> — certificates, crew certification matrix, SMS records, ISPS arrangements, maintenance logs — shared electronically and reviewed systematically against the applicable code requirements</li>
  <li><strong>Gap report</strong> — a clear, prioritised list of what needs attention before arrival, what can be addressed en route, and what requires an appointment on arrival</li>
  <li><strong>Non-conformity close-out support</strong> — for gaps that can be closed before arrival (updated procedures, backdated records correction, crew briefings), guidance on how to address them properly</li>
  <li><strong>DPA review</strong> — confirming DPA contact arrangements are documented, current, and known to the crew</li>
</ul>

<p>This is not a statutory audit. It does not produce a certificate. What it produces is a clear picture of your compliance position before a PSC officer produces the same picture — with the difference that you have time to act on it.</p>

<h2>Timing — when to start</h2>

<p>If your vessel is currently in the Pacific and planning arrival in New Zealand or Australia between September and November, the right time to start this process is now — July or August. That allows:</p>

<ul>
  <li>Time to order and receive any crew certification that has lapsed or is due</li>
  <li>Time to arrange servicing for safety equipment at the next port of call in the Pacific</li>
  <li>Time to address SMS record gaps properly, not hastily</li>
  <li>Time to arrange ISSC endorsement or renewal through your RO before arrival</li>
</ul>

<p>A remote pre-arrival review can typically be completed within a week of receiving the relevant documents. The gap report goes back to the captain or chief officer, and follow-up support is available throughout the passage.</p>

<h2>How we can help</h2>

<p>Tasman Maritime Consulting offers remote pre-arrival compliance reviews for superyachts heading to New Zealand and Australia — covering ISM/SMS review, crew certification check, ISPS arrangements, and LY3/flag state certification status. We are based in New Zealand and Australia, and can be reached in the timezone your vessel is actually operating in during a Pacific passage.</p>

<p>If your vessel is currently in the Pacific and you would like to discuss a pre-arrival review, book a free 15-minute call. We can usually give you a clear initial picture of your compliance position within that first conversation.</p>

          <a href="/blog" style="font-size:13.5px;display:block;margin-top:10px;">All articles &rarr;</a>
        </div>

        <div class="blog-sidebar__block">
          <p class="blog-sidebar__heading">Follow on LinkedIn</p>
          <a href="https://www.linkedin.com/company/tasmanmaritime/" target="_blank" rel="noopener" class="btn btn--ghost" style="width:100%;font-size:13.5px;text-align:center;">Follow Tasman Maritime</a>
        </div>
      </aside>

    </div>
  </div>
</div>
  <url>
    <loc>https://tasmanmaritime.com/blog/posts/superyacht-pre-arrival-nz-australia</loc>
    <lastmod>2026-07-13</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.7</priority>
  </url>

<p>If you operate a commercial vessel and have encountered the ISM Code, you have probably also encountered conflicting advice about whether it applies to you, what it actually requires, and what happens if you get it wrong. This article offers a clear, practical explanation — written from the perspective of someone who has managed a Safety Management System at sea and audited them from the shore side.</p>

<h2>What the ISM Code is</h2>

<p>The International Safety Management Code — the ISM Code — is a mandatory IMO standard adopted under SOLAS Chapter IX. Its purpose is straightforward: to establish an international standard for the safe management and operation of ships and for pollution prevention.</p>

<p>In plain terms, the ISM Code requires a shipping company to have a documented <strong>Safety Management System (SMS)</strong> — a set of policies, procedures, and records that define how the vessel is operated safely. The SMS must cover everything from maintenance and emergency procedures to crew training, incident reporting, and the communication lines between ship and shore.</p>

<p>The Code also requires a company-level point of accountability ashore — the <strong>Designated Person Ashore (DPA)</strong> — who has direct access to the highest level of management and can be reached at all times when the vessel is operating.</p>

<h2>Which vessels does it apply to?</h2>

<p>The ISM Code applies to ships engaged in international voyages in the following categories:</p>

<ul>
  <li>Passenger ships, including high-speed passenger craft</li>
  <li>Oil tankers, chemical tankers, gas carriers, bulk carriers and cargo high-speed craft of 500 gross tonnage (GT) and above</li>
  <li>Other cargo ships and mobile offshore drilling units of 500 GT and above</li>
</ul>

<p>For commercially operated yachts and superyachts, the threshold matters: ISM applies to commercially operated passenger vessels on international voyages. A superyacht operating commercially under a Red Ensign Group flag (Isle of Man, Cayman Islands, Channel Islands) will generally fall within this requirement once it exceeds 500GT or carries passengers on international voyages. Smaller commercially operated yachts typically fall under the <strong>MCA Large Yacht Code (LY3)</strong>, which contains its own SMS requirements — but the principles of good safety management apply regardless of which framework governs your vessel.</p>

<h2>What does compliance actually look like?</h2>

<p>A company subject to the ISM Code must hold two certificates:</p>

<ul>
  <li>A <strong>Document of Compliance (DOC)</strong> — issued to the company, covering the types of ships it operates</li>
  <li>A <strong>Safety Management Certificate (SMC)</strong> — issued to each individual vessel</li>
</ul>

<p>Both are issued by a Recognised Organisation (a classification society authorised by the vessel's flag state — Lloyd's Register, DNV, Bureau Veritas, ABS, ClassNK, and others) or directly by the flag state administration. They follow a statutory audit, are renewed periodically, and verified through annual or intermediate audits.</p>

<p>What the certificates represent, though, is not the end of the story — they represent a point-in-time assessment. What happens between those statutory audits is where genuine compliance either exists or doesn't.</p>

<h2>The internal audit — and why independence matters</h2>

<p>ISM Code Clause 12.1 requires companies to carry out internal safety audits to verify that safety and pollution-prevention activities comply with the SMS. The Code specifically requires that auditors be independent of the activities being audited — meaning the engineer cannot audit his own maintenance records, and the captain cannot be the sole auditor of bridge procedures he has authored.</p>

<p>That requirement for independence from the activity is the floor, not the ceiling. The deeper value of internal audit comes from genuine objectivity — an assessor who brings no assumptions about how things are done, no loyalty to existing procedures, and no hesitation in recording what the evidence actually shows rather than what the SMS says should be happening.</p>

<p>This is where good audit methodology matters. A structured internal audit follows a consistent process: planning against defined criteria, gathering objective evidence, assessing findings impartially, and reporting clearly — including findings that are uncomfortable. These are not bureaucratic steps; they are what separates an audit that actually improves safety from one that confirms what everyone already believes.</p>

<blockquote>
The most common pattern in SMS audits: the system is well-written but not well-lived. The procedures exist on paper; the records tell a different story. A rigorous internal audit closes that gap — before a statutory auditor or port state control officer does it for you.
</blockquote>

<p>Critically, internal audit findings are confidential to the company — they exist to drive improvement, not to create a paper trail for regulators. That confidentiality is itself a cornerstone of effective auditing: it allows genuine findings to be reported and addressed without fear of external consequence.</p>

<h2>Evidence-based assessment — what auditors actually look at</h2>

<p>A well-conducted ISM internal audit is evidence-based. It does not rely on what crew members say should be happening — it examines what the records show actually happened. Drill logs, maintenance records, non-conformity reports, hours of rest records, safety committee minutes — these are the objective evidence against which the SMS is assessed.</p>

<p>An SMS with no non-conformity reports is almost always an SMS where the reporting culture hasn't taken hold, not one where nothing has gone wrong. Port state control officers in New Zealand and Australia know this — an empty NCR log is a finding in itself.</p>

<h2>Risk-based thinking throughout the SMS</h2>

<p>The ISM Code requires companies to identify risks and implement safeguards — but the Code itself doesn't prescribe exactly how. Good safety management means applying risk-based thinking proportionately: the hazards relevant to a 45-metre superyacht on a Pacific circuit are not the same as those for a bulk carrier on a fixed route, and the SMS should reflect that. A Safety Management System that has been lifted wholesale from a template and applied without adaptation to the specific vessel, its operations, and its trading areas is one that will struggle under scrutiny — both in an audit and at the quayside.</p>

<h2>What port state control checks in New Zealand and Australia</h2>

<p>Port state control in both New Zealand (Maritime NZ) and Australia (AMSA) actively checks ISM compliance for visiting foreign-flagged vessels. PSC officers can board your vessel, examine your SMS, check your certificates, and detain the vessel if serious deficiencies are found. A missing or expired SMC, an unreachable DPA, or an SMS that clearly does not reflect actual operations are all grounds for detention.</p>

<p>For vessels arriving in this region on a Pacific circuit — often after a long passage from French Polynesia or following a refit period — PSC attention at the first port of call is a real risk if compliance preparations have been deferred during the voyage. The time to close nonconformities is before you arrive, not after a PSC officer has recorded them.</p>

<h2>Summary</h2>

<p>The ISM Code requires commercially operated vessels above certain thresholds to have a documented Safety Management System, a company-level Document of Compliance, a vessel-level Safety Management Certificate, and a Designated Person Ashore available at all times. For vessels planning passages to New Zealand, Australia, or the Pacific, ensuring all of these are current and genuinely implemented — not just on paper — before arrival is the single most valuable compliance step you can take.</p>

<p>If you are unsure whether the ISM Code applies to your vessel or what your current compliance position looks like, a short initial conversation is usually all it takes to get clarity.</p>


<p>If you operate a commercial vessel and have encountered the ISM Code, you have probably also encountered conflicting advice about whether it applies to you, what it actually requires, and what happens if you get it wrong. This article offers a clear, practical explanation — written from the perspective of someone who has managed a Safety Management System at sea and audited them from the shore side.</p>

<h2>What the ISM Code is</h2>

<p>The International Safety Management Code — the ISM Code — is a mandatory IMO standard adopted under SOLAS Chapter IX. Its purpose is straightforward: to establish an international standard for the safe management and operation of ships and for pollution prevention.</p>

<p>In plain terms, the ISM Code requires a shipping company to have a documented <strong>Safety Management System (SMS)</strong> — a set of policies, procedures, and records that define how the vessel is operated safely. The SMS must cover everything from maintenance and emergency procedures to crew training, incident reporting, and the communication lines between ship and shore.</p>

<p>The Code also requires a company-level point of accountability ashore — the <strong>Designated Person Ashore (DPA)</strong> — who has direct access to the highest level of management and can be reached at all times when the vessel is operating.</p>

<h2>Which vessels does it apply to?</h2>

<p>The ISM Code applies to ships engaged in international voyages in the following categories:</p>

<ul>
  <li>Passenger ships, including high-speed passenger craft</li>
  <li>Oil tankers, chemical tankers, gas carriers, bulk carriers and cargo high-speed craft of 500 gross tonnage (GT) and above</li>
  <li>Other cargo ships and mobile offshore drilling units of 500 GT and above</li>
</ul>

<p>For commercially operated yachts and superyachts, the threshold matters: ISM applies to commercially operated passenger vessels on international voyages. A superyacht operating commercially under a Red Ensign Group flag (Isle of Man, Cayman Islands, Channel Islands) will generally fall within this requirement once it exceeds 500GT or carries passengers on international voyages. Smaller commercially operated yachts typically fall under the <strong>MCA Large Yacht Code (LY3)</strong>, which contains its own SMS requirements — but the principles of good safety management apply regardless of which framework governs your vessel.</p>

<h2>What does compliance actually look like?</h2>

<p>A company subject to the ISM Code must hold two certificates:</p>

<ul>
  <li>A <strong>Document of Compliance (DOC)</strong> — issued to the company, covering the types of ships it operates</li>
  <li>A <strong>Safety Management Certificate (SMC)</strong> — issued to each individual vessel</li>
</ul>

<p>Both are issued by a Recognised Organisation (a classification society authorised by the vessel's flag state — Lloyd's Register, DNV, Bureau Veritas, ABS, ClassNK, and others) or directly by the flag state administration. They follow a statutory audit, are renewed periodically, and verified through annual or intermediate audits.</p>

<p>What the certificates represent, though, is not the end of the story — they represent a point-in-time assessment. What happens between those statutory audits is where genuine compliance either exists or doesn't.</p>

<h2>The internal audit — and why independence matters</h2>

<p>ISM Code Clause 12.1 requires companies to carry out internal safety audits to verify that safety and pollution-prevention activities comply with the SMS. The Code specifically requires that auditors be independent of the activities being audited — meaning the engineer cannot audit his own maintenance records, and the captain cannot be the sole auditor of bridge procedures he has authored.</p>

<p>That requirement for independence from the activity is the floor, not the ceiling. The deeper value of internal audit comes from genuine objectivity — an assessor who brings no assumptions about how things are done, no loyalty to existing procedures, and no hesitation in recording what the evidence actually shows rather than what the SMS says should be happening.</p>

<p>This is where good audit methodology matters. A structured internal audit follows a consistent process: planning against defined criteria, gathering objective evidence, assessing findings impartially, and reporting clearly — including findings that are uncomfortable. These are not bureaucratic steps; they are what separates an audit that actually improves safety from one that confirms what everyone already believes.</p>

<blockquote>
The most common pattern in SMS audits: the system is well-written but not well-lived. The procedures exist on paper; the records tell a different story. A rigorous internal audit closes that gap — before a statutory auditor or port state control officer does it for you.
</blockquote>

<p>Critically, internal audit findings are confidential to the company — they exist to drive improvement, not to create a paper trail for regulators. That confidentiality is itself a cornerstone of effective auditing: it allows genuine findings to be reported and addressed without fear of external consequence.</p>

<h2>Evidence-based assessment — what auditors actually look at</h2>

<p>A well-conducted ISM internal audit is evidence-based. It does not rely on what crew members say should be happening — it examines what the records show actually happened. Drill logs, maintenance records, non-conformity reports, hours of rest records, safety committee minutes — these are the objective evidence against which the SMS is assessed.</p>

<p>An SMS with no non-conformity reports is almost always an SMS where the reporting culture hasn't taken hold, not one where nothing has gone wrong. Port state control officers in New Zealand and Australia know this — an empty NCR log is a finding in itself.</p>

<h2>Risk-based thinking throughout the SMS</h2>

<p>The ISM Code requires companies to identify risks and implement safeguards — but the Code itself doesn't prescribe exactly how. Good safety management means applying risk-based thinking proportionately: the hazards relevant to a 45-metre superyacht on a Pacific circuit are not the same as those for a bulk carrier on a fixed route, and the SMS should reflect that. A Safety Management System that has been lifted wholesale from a template and applied without adaptation to the specific vessel, its operations, and its trading areas is one that will struggle under scrutiny — both in an audit and at the quayside.</p>

<h2>What port state control checks in New Zealand and Australia</h2>

<p>Port state control in both New Zealand (Maritime NZ) and Australia (AMSA) actively checks ISM compliance for visiting foreign-flagged vessels. PSC officers can board your vessel, examine your SMS, check your certificates, and detain the vessel if serious deficiencies are found. A missing or expired SMC, an unreachable DPA, or an SMS that clearly does not reflect actual operations are all grounds for detention.</p>

<p>For vessels arriving in this region on a Pacific circuit — often after a long passage from French Polynesia or following a refit period — PSC attention at the first port of call is a real risk if compliance preparations have been deferred during the voyage. The time to close nonconformities is before you arrive, not after a PSC officer has recorded them.</p>

<h2>Summary</h2>

<p>The ISM Code requires commercially operated vessels above certain thresholds to have a documented Safety Management System, a company-level Document of Compliance, a vessel-level Safety Management Certificate, and a Designated Person Ashore available at all times. For vessels planning passages to New Zealand, Australia, or the Pacific, ensuring all of these are current and genuinely implemented — not just on paper — before arrival is the single most valuable compliance step you can take.</p>

<p>If you are unsure whether the ISM Code applies to your vessel or what your current compliance position looks like, a short initial conversation is usually all it takes to get clarity.</p>

  <url>
    <loc>https://tasmanmaritime.com/blog/posts/ism-code-explained</loc>
    <lastmod>2026-07-22</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.7</priority>
  </url>

<p>One of the most common areas of confusion in superyacht compliance is the relationship between the IMO ISM Code and the MCA Large Yacht Code (LY3). Both involve safety management requirements. Both apply to commercially operated yachts. But they do not apply to the same vessels in the same way, and conflating them leads to real compliance gaps.</p>

<p>This article explains the distinction clearly — from the perspective of someone who has operated commercially under both frameworks.</p>

<h2>The MCA Large Yacht Code (LY3)</h2>

<p>The MCA Large Yacht Code — currently in its third edition (LY3) — is a UK Maritime and Coastguard Agency standard that applies to <strong>commercially operated yachts of 24 metres in length and above</strong> that are flagged under Red Ensign Group registries (Isle of Man, Cayman Islands, Bermuda, Channel Islands, British Virgin Islands, and others).</p>

<p>LY3 is a comprehensive framework covering construction, stability, life-saving appliances, fire protection, crew certification, watchkeeping, and — critically for this discussion — operational requirements including a <strong>Safety Management System</strong>. The LY3 SMS requirements are derived from the ISM Code but adapted for the superyacht context.</p>

<p>For commercially operated yachts of 24m and above but <strong>under 500 gross tonnage</strong> operating under Red Ensign Group flags, LY3 is the primary compliance framework. The ISM Code, as an IMO instrument, does not formally apply to vessels below 500GT — LY3 is the applicable standard.</p>

<h2>The ISM Code</h2>

<p>The IMO ISM Code applies to ships engaged in international voyages, and for commercially operated passenger vessels and cargo ships, the threshold is <strong>500 gross tonnage</strong>. For a superyacht, this means:</p>

<ul>
  <li>A commercially operated yacht of 24m to approximately 500GT operating under a Red Ensign Group flag: <strong>LY3 applies</strong></li>
  <li>A commercially operated yacht over 500GT on international voyages: <strong>both LY3 and ISM Code requirements apply</strong></li>
  <li>A commercially operated passenger vessel on international voyages regardless of GT: <strong>SOLAS and ISM apply</strong></li>
</ul>

<p>In practice, this means that a well-run 45-metre superyacht under 500GT on a commercial charter operating under an IoM flag needs to comply with LY3 — including its SMS requirements — but does not formally require ISM certification (a DOC and SMC) in the way a 600GT vessel does.</p>

<h2>Where it gets complicated — flag state variations</h2>

<p>Flag states within the Red Ensign Group each maintain their own specific requirements, and the precise application of LY3 versus ISM can vary. The Isle of Man Ship Registry, Cayman Islands Shipping Registry, and Channel Islands registries all apply LY3 but may have specific additional requirements or interpretations. Your flag state and your Recognised Organisation (the classification society your flag state delegates survey authority to) are the definitive source for your specific vessel's obligations.</p>

<p>What is consistent across all of them is this: <strong>commercially operating without a functioning, documented SMS — whether under LY3 or ISM — is not an option</strong>. Both frameworks require it, and port state control in New Zealand, Australia, and across the Pacific actively checks that it exists and is genuinely implemented.</p>

<h2>ISPS — the other code that applies to both</h2>

<p>The ISPS Code (International Ship and Port Facility Security Code) applies to passenger vessels on international voyages regardless of the LY3/ISM distinction. If your superyacht is operating commercially and making international port calls — including the Pacific island states, PNG, or Indonesian ports — ISPS compliance is required. This means:</p>

<ul>
  <li>An approved Ship Security Plan (SSP)</li>
  <li>A Ship Security Officer (SSO) on board</li>
  <li>A <strong>Company Security Officer (CSO)</strong> ashore, reachable at all times</li>
  <li>Port-specific security measures documented and implemented before arrival</li>
</ul>

<h2>What this means practically for vessels approaching this region</h2>

<p>For a commercially operated superyacht on a Pacific circuit heading for New Zealand or Australia, the compliance picture typically looks like this:</p>

<ul>
  <li><strong>LY3 compliance</strong> — SMS, crew certificates, survey status current</li>
  <li><strong>ISM compliance (if over 500GT)</strong> — DOC and SMC current, DPA in place and reachable</li>
  <li><strong>ISPS compliance</strong> — SSP current, CSO in place and reachable, port-specific security measures ready</li>
</ul>

<p>Port state control officers in Auckland, Sydney, and Cairns are familiar with all three frameworks and will check them. A vessel arriving after a long Pacific passage with lapsed certificates, an unreachable DPA, or an SMS that clearly has not been maintained is a detention risk at exactly the point where the crew and owner least want the disruption.</p>

<h2>Summary</h2>

<p>For commercially operated superyachts under Red Ensign Group flags: LY3 is your primary framework if you are under 500GT; ISM applies additionally if you are over 500GT on international voyages. Both require a functioning SMS. ISPS applies on international voyages regardless of size. Know which framework applies to your vessel, ensure your certificates are current, and ensure your DPA and CSO are reachable in the timezone your vessel is actually operating in.</p>

<p>If you are heading to the South Pacific, New Zealand, or Australia and are uncertain about your compliance position, a pre-departure review is worth considerably more than the time it takes.</p>


<p>New Zealand and Australia are not the same as Tahiti or Fiji when it comes to port state control. Both are members of the Tokyo Memorandum of Understanding on Port State Control, both have professional and well-resourced PSC teams, and both are increasingly focused on commercially operated superyachts — a category that has historically received lighter scrutiny than commercial shipping but is no longer able to count on that.</p>

<p>If your vessel is arriving from the Pacific, this guide explains how PSC works in each country, what triggers a detailed inspection, and what the outcomes look like when things are not in order.</p>

<h2>How port state control works — the basics</h2>

<p>Port state control is the inspection of foreign-flagged vessels by the authorities of the country whose port the vessel has entered. The legal basis is a series of international conventions — SOLAS, MARPOL, STCW, MLC, ISPS — that member states have agreed to enforce on vessels in their waters, regardless of the vessel's flag.</p>

<p>In practical terms: when your vessel arrives at a New Zealand or Australian port, the PSC authority has the right to board and inspect. They are checking whether your vessel complies with the international conventions. If they find deficiencies, they can require them to be rectified before departure. If the deficiencies are serious enough, they can detain the vessel — preventing it from leaving until the issues are resolved.</p>

<h2>Maritime NZ — port state control in New Zealand</h2>

<p>In New Zealand, port state control is conducted by <strong>Maritime NZ</strong>. PSC officers are based primarily in Auckland, Tauranga, Wellington, Lyttelton, and Dunedin — though they can operate at any port where vessels arrive.</p>

<p>Maritime NZ targets vessels for inspection using a risk-based targeting system within the Tokyo MOU framework. Factors that increase your vessel's targeting priority include:</p>

<ul>
  <li>First visit to New Zealand waters</li>
  <li>Significant time since last PSC inspection</li>
  <li>Previous deficiency history in the Tokyo MOU region</li>
  <li>Flag state performance — vessels under flags with poor Tokyo MOU performance records receive more attention</li>
  <li>Vessel type and age</li>
</ul>

<p>A superyacht arriving in New Zealand for the first time, from a Pacific crossing, under a Red Ensign Group flag, with no recent PSC history in the region, is a moderate-to-high targeting priority. That does not mean an inspection is certain — but it means the probability is real enough to prepare for.</p>

<p><strong>Typical entry points in New Zealand:</strong> Whangarei (Marsden Cove, Norsand Boatyard) and Auckland (Viaduct Harbour, Westhaven) are the most common first ports of call for superyachts arriving from the Pacific. PSC inspections at these ports are routine.</p>

<h2>AMSA — port state control in Australia</h2>

<p>In Australia, port state control is conducted by the <strong>Australian Maritime Safety Authority (AMSA)</strong>. AMSA has a well-established reputation for thorough inspections and follows both the Tokyo MOU and, for some vessel categories, Paris MOU procedures.</p>

<p>AMSA PSC officers are active at all major Australian ports: Brisbane, Gold Coast, Sydney, Melbourne, Cairns, Darwin, Fremantle, and others. AMSA uses a similar risk-based targeting system to Maritime NZ, with comparable factors affecting inspection priority.</p>

<p>One distinction worth knowing: AMSA publishes its deficiency and detention records, and its PSC teams are known for detailed scrutiny of safety management systems — not just checking that the SMS exists, but testing whether it is genuinely implemented. This is an area where superyachts frequently fall short.</p>

<p><strong>Typical entry points in Australia:</strong> Cairns and Darwin are common first ports for vessels arriving from the Pacific or Southeast Asia. Brisbane, Sydney, and Melbourne are major refit destinations where PSC inspections occur regularly.</p>

<h2>What triggers a detailed inspection</h2>

<p>Not every arrival results in a detailed inspection. A PSC officer may conduct an initial check of certificates and overall condition and, if satisfied, issue a clearance without a full inspection. What triggers a move from initial check to detailed inspection:</p>

<ul>
  <li>Certificates not immediately available or visibly irregular</li>
  <li>Obvious deficiencies in condition observed during initial boarding</li>
  <li>Information from port agents, the crew, or other sources suggesting compliance issues</li>
  <li>High targeting priority based on the risk model</li>
  <li>Previous detention or significant deficiency history</li>
</ul>

<p>The best way to avoid triggering a detailed inspection is to present cleanly on the initial check — certificates in order, clearly maintained vessel, a captain who answers questions directly and confidently. A confident, well-prepared response to an initial check does not guarantee no inspection, but a flustered response almost always produces one.</p>

<h2>Deficiencies, rectification, and detention</h2>

<p>PSC deficiencies are categorised. Minor deficiencies that do not affect seaworthiness are typically noted and must be rectified by the next port or a specified date. More serious deficiencies — particularly those affecting safety equipment, certificates, or the functioning of the safety management system — require rectification before departure.</p>

<p>Detention occurs when deficiencies are serious enough that the vessel should not sail. Common grounds for detention of superyachts in the NZ/Australian region include:</p>

<ul>
  <li>Expired SMC or ISSC, or no DOC covering the vessel's operational category</li>
  <li>STCW crew certification deficiencies that leave the vessel undermanned for its operating area</li>
  <li>Fire detection or firefighting equipment deficiencies</li>
  <li>Life-saving appliance deficiencies — particularly life raft servicing</li>
  <li>No functioning DPA arrangement</li>
</ul>

<p>A detention means the vessel cannot depart until deficiencies are rectified and re-inspected. In Whangarei or Cairns, that may be manageable. In a remote port, it is a significant operational and financial event.</p>

<h2>Red Ensign Group vessels — specific considerations</h2>

<p>The majority of commercially operated superyachts in this region are registered under Red Ensign Group flags — Isle of Man, Cayman Islands, Channel Islands. PSC officers in New Zealand and Australia are familiar with these registries and know their survey and certification requirements well. A few specific points:</p>

<ul>
  <li>Red Ensign Group flags are generally well-regarded within the Tokyo MOU — vessels under IoM, Cayman, and Channel Islands flags are not automatically high-targeted on flag grounds alone</li>
  <li>However, the RO-issued certificates (DOC, SMC, ISSC) must be current and must reflect the vessel's actual operational category. A superyacht that has changed from private to commercial operation without updating its certification is a significant deficiency</li>
  <li>Flag state endorsements on crew STCW certificates are specifically checked — some Red Ensign Group registries require specific flag endorsements in addition to the STCW certificate</li>
</ul>

<h2>The case for a pre-arrival review</h2>

<p>Port state control officers have time, authority, and a checklist developed specifically to find the gaps that exist in the gap between what a vessel's SMS says and what its records demonstrate. The preparation window — while your vessel is still in the Pacific — is the best opportunity to find those gaps first.</p>

<p>A remote pre-arrival compliance review, completed in the weeks before arrival, covers the same ground a PSC officer covers: certificates, crew certification, SMS records, ISPS arrangements, safety equipment servicing. The difference is that the findings come to you, not to a PSC inspector, and you have time to act on them.</p>

<p>If your vessel is currently in the Pacific and arrival in New Zealand or Australia is planned between September and November, the window to complete this preparation is now.</p>


<p>New Zealand and Australia are not the same as Tahiti or Fiji when it comes to port state control. Both are members of the Tokyo Memorandum of Understanding on Port State Control, both have professional and well-resourced PSC teams, and both are increasingly focused on commercially operated superyachts — a category that has historically received lighter scrutiny than commercial shipping but is no longer able to count on that.</p>

<p>If your vessel is arriving from the Pacific, this guide explains how PSC works in each country, what triggers a detailed inspection, and what the outcomes look like when things are not in order.</p>

<h2>How port state control works — the basics</h2>

<p>Port state control is the inspection of foreign-flagged vessels by the authorities of the country whose port the vessel has entered. The legal basis is a series of international conventions — SOLAS, MARPOL, STCW, MLC, ISPS — that member states have agreed to enforce on vessels in their waters, regardless of the vessel's flag.</p>

<p>In practical terms: when your vessel arrives at a New Zealand or Australian port, the PSC authority has the right to board and inspect. They are checking whether your vessel complies with the international conventions. If they find deficiencies, they can require them to be rectified before departure. If the deficiencies are serious enough, they can detain the vessel — preventing it from leaving until the issues are resolved.</p>

<h2>Maritime NZ — port state control in New Zealand</h2>

<p>In New Zealand, port state control is conducted by <strong>Maritime NZ</strong>. PSC officers are based primarily in Auckland, Tauranga, Wellington, Lyttelton, and Dunedin — though they can operate at any port where vessels arrive.</p>

<p>Maritime NZ targets vessels for inspection using a risk-based targeting system within the Tokyo MOU framework. Factors that increase your vessel's targeting priority include:</p>

<ul>
  <li>First visit to New Zealand waters</li>
  <li>Significant time since last PSC inspection</li>
  <li>Previous deficiency history in the Tokyo MOU region</li>
  <li>Flag state performance — vessels under flags with poor Tokyo MOU performance records receive more attention</li>
  <li>Vessel type and age</li>
</ul>

<p>A superyacht arriving in New Zealand for the first time, from a Pacific crossing, under a Red Ensign Group flag, with no recent PSC history in the region, is a moderate-to-high targeting priority. That does not mean an inspection is certain — but it means the probability is real enough to prepare for.</p>

<p><strong>Typical entry points in New Zealand:</strong> Whangarei (Marsden Cove, Norsand Boatyard) and Auckland (Viaduct Harbour, Westhaven) are the most common first ports of call for superyachts arriving from the Pacific. PSC inspections at these ports are routine.</p>

<h2>AMSA — port state control in Australia</h2>

<p>In Australia, port state control is conducted by the <strong>Australian Maritime Safety Authority (AMSA)</strong>. AMSA has a well-established reputation for thorough inspections and follows both the Tokyo MOU and, for some vessel categories, Paris MOU procedures.</p>

<p>AMSA PSC officers are active at all major Australian ports: Brisbane, Gold Coast, Sydney, Melbourne, Cairns, Darwin, Fremantle, and others. AMSA uses a similar risk-based targeting system to Maritime NZ, with comparable factors affecting inspection priority.</p>

<p>One distinction worth knowing: AMSA publishes its deficiency and detention records, and its PSC teams are known for detailed scrutiny of safety management systems — not just checking that the SMS exists, but testing whether it is genuinely implemented. This is an area where superyachts frequently fall short.</p>

<p><strong>Typical entry points in Australia:</strong> Cairns and Darwin are common first ports for vessels arriving from the Pacific or Southeast Asia. Brisbane, Sydney, and Melbourne are major refit destinations where PSC inspections occur regularly.</p>

<h2>What triggers a detailed inspection</h2>

<p>Not every arrival results in a detailed inspection. A PSC officer may conduct an initial check of certificates and overall condition and, if satisfied, issue a clearance without a full inspection. What triggers a move from initial check to detailed inspection:</p>

<ul>
  <li>Certificates not immediately available or visibly irregular</li>
  <li>Obvious deficiencies in condition observed during initial boarding</li>
  <li>Information from port agents, the crew, or other sources suggesting compliance issues</li>
  <li>High targeting priority based on the risk model</li>
  <li>Previous detention or significant deficiency history</li>
</ul>

<p>The best way to avoid triggering a detailed inspection is to present cleanly on the initial check — certificates in order, clearly maintained vessel, a captain who answers questions directly and confidently. A confident, well-prepared response to an initial check does not guarantee no inspection, but a flustered response almost always produces one.</p>

<h2>Deficiencies, rectification, and detention</h2>

<p>PSC deficiencies are categorised. Minor deficiencies that do not affect seaworthiness are typically noted and must be rectified by the next port or a specified date. More serious deficiencies — particularly those affecting safety equipment, certificates, or the functioning of the safety management system — require rectification before departure.</p>

<p>Detention occurs when deficiencies are serious enough that the vessel should not sail. Common grounds for detention of superyachts in the NZ/Australian region include:</p>

<ul>
  <li>Expired SMC or ISSC, or no DOC covering the vessel's operational category</li>
  <li>STCW crew certification deficiencies that leave the vessel undermanned for its operating area</li>
  <li>Fire detection or firefighting equipment deficiencies</li>
  <li>Life-saving appliance deficiencies — particularly life raft servicing</li>
  <li>No functioning DPA arrangement</li>
</ul>

<p>A detention means the vessel cannot depart until deficiencies are rectified and re-inspected. In Whangarei or Cairns, that may be manageable. In a remote port, it is a significant operational and financial event.</p>

<h2>Red Ensign Group vessels — specific considerations</h2>

<p>The majority of commercially operated superyachts in this region are registered under Red Ensign Group flags — Isle of Man, Cayman Islands, Channel Islands. PSC officers in New Zealand and Australia are familiar with these registries and know their survey and certification requirements well. A few specific points:</p>

<ul>
  <li>Red Ensign Group flags are generally well-regarded within the Tokyo MOU — vessels under IoM, Cayman, and Channel Islands flags are not automatically high-targeted on flag grounds alone</li>
  <li>However, the RO-issued certificates (DOC, SMC, ISSC) must be current and must reflect the vessel's actual operational category. A superyacht that has changed from private to commercial operation without updating its certification is a significant deficiency</li>
  <li>Flag state endorsements on crew STCW certificates are specifically checked — some Red Ensign Group registries require specific flag endorsements in addition to the STCW certificate</li>
</ul>

<h2>The case for a pre-arrival review</h2>

<p>Port state control officers have time, authority, and a checklist developed specifically to find the gaps that exist in the gap between what a vessel's SMS says and what its records demonstrate. The preparation window — while your vessel is still in the Pacific — is the best opportunity to find those gaps first.</p>

<p>A remote pre-arrival compliance review, completed in the weeks before arrival, covers the same ground a PSC officer covers: certificates, crew certification, SMS records, ISPS arrangements, safety equipment servicing. The difference is that the findings come to you, not to a PSC inspector, and you have time to act on them.</p>

<p>If your vessel is currently in the Pacific and arrival in New Zealand or Australia is planned between September and November, the window to complete this preparation is now.</p>

  <url>
    <loc>https://tasmanmaritime.com/blog/posts/port-state-control-nz-australia-superyachts</loc>
    <lastmod>2026-07-13</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.7</priority>
  </url>

<p>July and August are decision months in the Pacific. Vessels in French Polynesia, the Cook Islands, Fiji, Tonga, and Vanuatu are planning their southward passages ahead of the cyclone season — which historically becomes active by November. New Zealand and Australia are the destinations, and port state control in both countries is among the most thorough in the Pacific region.</p>

<p>If your vessel is in this position right now, this guide is written for you. It covers what Maritime NZ and AMSA inspectors are looking for, the most common compliance gaps found on superyachts arriving in this region, and — critically — what you can address remotely before you arrive.</p>

<h2>Why pre-arrival preparation matters here specifically</h2>

<p>Port state control in New Zealand and Australia is not the cursory glance some Pacific island ports offer. Both Maritime NZ and AMSA are members of the Tokyo Memorandum of Understanding on Port State Control, and both are known for thorough inspections. AMSA in particular has a reputation for detailed scrutiny.</p>

<p>A detained vessel at Whangarei, Auckland, Sydney, or Cairns — after a long Pacific passage, with crew expecting shore leave and an owner anticipating refit work — is a very expensive outcome. The deficiencies that trigger detention are, in the vast majority of cases, not new problems. They are problems that existed before the vessel arrived and were not identified.</p>

<p>The good news: most of them can be identified and closed before arrival, through a systematic remote review of your documents and records.</p>

<h2>What PSC officers look for on commercially operated superyachts</h2>

<p>Port state control inspections on commercially operated superyachts in New Zealand and Australia typically focus on the following areas:</p>

<h3>Certificates — validity and completeness</h3>
<ul>
  <li><strong>Document of Compliance (DOC)</strong> — company level, issued by your flag state's Recognised Organisation. Must cover the type of operation your vessel is undertaking</li>
  <li><strong>Safety Management Certificate (SMC)</strong> — vessel level. Check the issue date, the expiry date, and whether any intermediate or annual endorsements are due or overdue</li>
  <li><strong>International Ship Security Certificate (ISSC)</strong> — issued following ISPS audit. Commonly found to be expired on vessels that have been cruising in the Pacific for extended periods</li>
  <li><strong>LY3 compliance certificate / flag state survey</strong> — if your vessel operates under LY3 (most commercially operated yachts under 500GT on Red Ensign Group flags), your flag state survey must be current</li>
  <li><strong>MLC certificate or Declaration of Maritime Labour Compliance</strong> — applies to vessels over 500GT on international voyages, but good practice to have MLC-compliant crew welfare provisions regardless</li>
</ul>

<h3>Crew certification</h3>
<ul>
  <li>STCW certificates for all watchkeeping officers — check expiry dates across the crew</li>
  <li>Medical certificates — commonly found to have lapsed during a long passage</li>
  <li>Flag state endorsements — particularly relevant for Isle of Man and Cayman Islands flagged vessels, where some certificates require a specific flag state endorsement in addition to the STCW certificate itself</li>
</ul>

<h3>Safety Management System — is it alive or in a binder?</h3>
<p>This is where PSC officers most commonly find substantive deficiencies on superyachts. An SMS exists — it is almost always well-written — but the records tell a different story. PSC officers specifically look for:</p>
<ul>
  <li>Evidence that safety drills are being conducted at the required frequency — not just recorded</li>
  <li>Non-conformity and near-miss reporting records — an SMS with no reports is almost always an SMS where reporting is not actually happening</li>
  <li>Maintenance records consistent with the planned maintenance schedule</li>
  <li>Evidence that the DPA is actively involved — not just a name and phone number on a bulkhead</li>
</ul>

<h3>ISPS — security arrangements</h3>
<ul>
  <li>Ship Security Plan — current, vessel-specific, approved by the flag state or RO</li>
  <li>CSO contact details — reachable, documented, tested</li>
  <li>Port facility security records for previous port calls</li>
</ul>

<h3>Hours of rest records</h3>
<p>MLC-compliant hours of rest and work records are increasingly scrutinised on superyachts. A vessel with a small crew undertaking demanding deliveries or refit work is likely to have rest hour challenges. Having a realistic, properly maintained record — rather than one that has clearly been constructed to show compliance — is what inspectors are looking for.</p>

<h2>The most common deficiencies found on superyachts arriving in New Zealand and Australia</h2>

<p>Based on experience in this region, the most frequently found deficiencies are:</p>

<ol>
  <li><strong>Expired or incorrectly endorsed crew certificates</strong> — particularly medical certificates and flag state endorsements</li>
  <li><strong>ISSC expired or with endorsement gap</strong> — often occurs during extended Pacific cruising when the annual endorsement window passes without the vessel being near an RO surveyor</li>
  <li><strong>SMS records inconsistent with stated procedures</strong> — drills not recorded, maintenance not evidenced, reporting not happening</li>
  <li><strong>DPA not reachable</strong> — or not known to the crew beyond "there's a number on the bridge"</li>
  <li><strong>Fire detection and firefighting equipment</strong> — servicing certificates expired, particularly for fixed systems</li>
  <li><strong>Life raft and immersion suit servicing</strong> — extended Pacific passages put these through service cycles that are not always tracked</li>
  <li><strong>GMDSS equipment</strong> — battery certification, EPIRB registration and battery expiry, SART testing records</li>
</ol>

<h2>What you can address remotely — right now, before arrival</h2>

<p>The majority of the compliance gaps listed above can be identified — and most can be addressed — remotely, before your vessel arrives. A structured remote pre-arrival review involves:</p>

<ul>
  <li><strong>Document review</strong> — certificates, crew certification matrix, SMS records, ISPS arrangements, maintenance logs — shared electronically and reviewed systematically against the applicable code requirements</li>
  <li><strong>Gap report</strong> — a clear, prioritised list of what needs attention before arrival, what can be addressed en route, and what requires an appointment on arrival</li>
  <li><strong>Non-conformity close-out support</strong> — for gaps that can be closed before arrival (updated procedures, backdated records correction, crew briefings), guidance on how to address them properly</li>
  <li><strong>DPA review</strong> — confirming DPA contact arrangements are documented, current, and known to the crew</li>
</ul>

<p>This is not a statutory audit. It does not produce a certificate. What it produces is a clear picture of your compliance position before a PSC officer produces the same picture — with the difference that you have time to act on it.</p>

<h2>Timing — when to start</h2>

<p>If your vessel is currently in the Pacific and planning arrival in New Zealand or Australia between September and November, the right time to start this process is now — July or August. That allows:</p>

<ul>
  <li>Time to order and receive any crew certification that has lapsed or is due</li>
  <li>Time to arrange servicing for safety equipment at the next port of call in the Pacific</li>
  <li>Time to address SMS record gaps properly, not hastily</li>
  <li>Time to arrange ISSC endorsement or renewal through your RO before arrival</li>
</ul>

<p>A remote pre-arrival review can typically be completed within a week of receiving the relevant documents. The gap report goes back to the captain or chief officer, and follow-up support is available throughout the passage.</p>

<h2>How we can help</h2>

<p>Tasman Maritime Consulting offers remote pre-arrival compliance reviews for superyachts heading to New Zealand and Australia — covering ISM/SMS review, crew certification check, ISPS arrangements, and LY3/flag state certification status. We are based in New Zealand and Australia, and can be reached in the timezone your vessel is actually operating in during a Pacific passage.</p>

<p>If your vessel is currently in the Pacific and you would like to discuss a pre-arrival review, book a free 15-minute call. We can usually give you a clear initial picture of your compliance position within that first conversation.</p>


<p>July and August are decision months in the Pacific. Vessels in French Polynesia, the Cook Islands, Fiji, Tonga, and Vanuatu are planning their southward passages ahead of the cyclone season — which historically becomes active by November. New Zealand and Australia are the destinations, and port state control in both countries is among the most thorough in the Pacific region.</p>

<p>If your vessel is in this position right now, this guide is written for you. It covers what Maritime NZ and AMSA inspectors are looking for, the most common compliance gaps found on superyachts arriving in this region, and — critically — what you can address remotely before you arrive.</p>

<h2>Why pre-arrival preparation matters here specifically</h2>

<p>Port state control in New Zealand and Australia is not the cursory glance some Pacific island ports offer. Both Maritime NZ and AMSA are members of the Tokyo Memorandum of Understanding on Port State Control, and both are known for thorough inspections. AMSA in particular has a reputation for detailed scrutiny.</p>

<p>A detained vessel at Whangarei, Auckland, Sydney, or Cairns — after a long Pacific passage, with crew expecting shore leave and an owner anticipating refit work — is a very expensive outcome. The deficiencies that trigger detention are, in the vast majority of cases, not new problems. They are problems that existed before the vessel arrived and were not identified.</p>

<p>The good news: most of them can be identified and closed before arrival, through a systematic remote review of your documents and records.</p>

<h2>What PSC officers look for on commercially operated superyachts</h2>

<p>Port state control inspections on commercially operated superyachts in New Zealand and Australia typically focus on the following areas:</p>

<h3>Certificates — validity and completeness</h3>
<ul>
  <li><strong>Document of Compliance (DOC)</strong> — company level, issued by your flag state's Recognised Organisation. Must cover the type of operation your vessel is undertaking</li>
  <li><strong>Safety Management Certificate (SMC)</strong> — vessel level. Check the issue date, the expiry date, and whether any intermediate or annual endorsements are due or overdue</li>
  <li><strong>International Ship Security Certificate (ISSC)</strong> — issued following ISPS audit. Commonly found to be expired on vessels that have been cruising in the Pacific for extended periods</li>
  <li><strong>LY3 compliance certificate / flag state survey</strong> — if your vessel operates under LY3 (most commercially operated yachts under 500GT on Red Ensign Group flags), your flag state survey must be current</li>
  <li><strong>MLC certificate or Declaration of Maritime Labour Compliance</strong> — applies to vessels over 500GT on international voyages, but good practice to have MLC-compliant crew welfare provisions regardless</li>
</ul>

<h3>Crew certification</h3>
<ul>
  <li>STCW certificates for all watchkeeping officers — check expiry dates across the crew</li>
  <li>Medical certificates — commonly found to have lapsed during a long passage</li>
  <li>Flag state endorsements — particularly relevant for Isle of Man and Cayman Islands flagged vessels, where some certificates require a specific flag state endorsement in addition to the STCW certificate itself</li>
</ul>

<h3>Safety Management System — is it alive or in a binder?</h3>
<p>This is where PSC officers most commonly find substantive deficiencies on superyachts. An SMS exists — it is almost always well-written — but the records tell a different story. PSC officers specifically look for:</p>
<ul>
  <li>Evidence that safety drills are being conducted at the required frequency — not just recorded</li>
  <li>Non-conformity and near-miss reporting records — an SMS with no reports is almost always an SMS where reporting is not actually happening</li>
  <li>Maintenance records consistent with the planned maintenance schedule</li>
  <li>Evidence that the DPA is actively involved — not just a name and phone number on a bulkhead</li>
</ul>

<h3>ISPS — security arrangements</h3>
<ul>
  <li>Ship Security Plan — current, vessel-specific, approved by the flag state or RO</li>
  <li>CSO contact details — reachable, documented, tested</li>
  <li>Port facility security records for previous port calls</li>
</ul>

<h3>Hours of rest records</h3>
<p>MLC-compliant hours of rest and work records are increasingly scrutinised on superyachts. A vessel with a small crew undertaking demanding deliveries or refit work is likely to have rest hour challenges. Having a realistic, properly maintained record — rather than one that has clearly been constructed to show compliance — is what inspectors are looking for.</p>

<h2>The most common deficiencies found on superyachts arriving in New Zealand and Australia</h2>

<p>Based on experience in this region, the most frequently found deficiencies are:</p>

<ol>
  <li><strong>Expired or incorrectly endorsed crew certificates</strong> — particularly medical certificates and flag state endorsements</li>
  <li><strong>ISSC expired or with endorsement gap</strong> — often occurs during extended Pacific cruising when the annual endorsement window passes without the vessel being near an RO surveyor</li>
  <li><strong>SMS records inconsistent with stated procedures</strong> — drills not recorded, maintenance not evidenced, reporting not happening</li>
  <li><strong>DPA not reachable</strong> — or not known to the crew beyond "there's a number on the bridge"</li>
  <li><strong>Fire detection and firefighting equipment</strong> — servicing certificates expired, particularly for fixed systems</li>
  <li><strong>Life raft and immersion suit servicing</strong> — extended Pacific passages put these through service cycles that are not always tracked</li>
  <li><strong>GMDSS equipment</strong> — battery certification, EPIRB registration and battery expiry, SART testing records</li>
</ol>

<h2>What you can address remotely — right now, before arrival</h2>

<p>The majority of the compliance gaps listed above can be identified — and most can be addressed — remotely, before your vessel arrives. A structured remote pre-arrival review involves:</p>

<ul>
  <li><strong>Document review</strong> — certificates, crew certification matrix, SMS records, ISPS arrangements, maintenance logs — shared electronically and reviewed systematically against the applicable code requirements</li>
  <li><strong>Gap report</strong> — a clear, prioritised list of what needs attention before arrival, what can be addressed en route, and what requires an appointment on arrival</li>
  <li><strong>Non-conformity close-out support</strong> — for gaps that can be closed before arrival (updated procedures, backdated records correction, crew briefings), guidance on how to address them properly</li>
  <li><strong>DPA review</strong> — confirming DPA contact arrangements are documented, current, and known to the crew</li>
</ul>

<p>This is not a statutory audit. It does not produce a certificate. What it produces is a clear picture of your compliance position before a PSC officer produces the same picture — with the difference that you have time to act on it.</p>

<h2>Timing — when to start</h2>

<p>If your vessel is currently in the Pacific and planning arrival in New Zealand or Australia between September and November, the right time to start this process is now — July or August. That allows:</p>

<ul>
  <li>Time to order and receive any crew certification that has lapsed or is due</li>
  <li>Time to arrange servicing for safety equipment at the next port of call in the Pacific</li>
  <li>Time to address SMS record gaps properly, not hastily</li>
  <li>Time to arrange ISSC endorsement or renewal through your RO before arrival</li>
</ul>

<p>A remote pre-arrival review can typically be completed within a week of receiving the relevant documents. The gap report goes back to the captain or chief officer, and follow-up support is available throughout the passage.</p>

<h2>How we can help</h2>

<p>Tasman Maritime Consulting offers remote pre-arrival compliance reviews for superyachts heading to New Zealand and Australia — covering ISM/SMS review, crew certification check, ISPS arrangements, and LY3/flag state certification status. We are based in New Zealand and Australia, and can be reached in the timezone your vessel is actually operating in during a Pacific passage.</p>

<p>If your vessel is currently in the Pacific and you would like to discuss a pre-arrival review, book a free 15-minute call. We can usually give you a clear initial picture of your compliance position within that first conversation.</p>

  <url>
    <loc>https://tasmanmaritime.com/blog/posts/superyacht-pre-arrival-nz-australia</loc>
    <lastmod>2026-07-13</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.7</priority>
  </url>
</urlset>
