What is a 500m safety zone? A mariner's plain-English guide

If you've worked offshore for any length of time, "the 500" is part of the vocabulary. But the legal basis, the operational meaning and the day-to-day reality of the 500-metre safety zone are often blurred together — and that blurring is itself a safety issue.

This is a plain-English reference for crews, charterers, and anyone procuring or operating offshore vessels. No legalese, no marketing.

What the 500m safety zone actually is

A 500-metre safety zone (also called an exclusion zone) is a regulator-defined three-dimensional cylinder of water surrounding an offshore installation. The zone extends 500 metres horizontally from any point on the installation's outermost extremity, and from the seabed to the surface (and, in practice, the airspace immediately above).

In UK waters the zone is established under the Petroleum Act 1987 and the Offshore Installations (Safety Zones) Order, with equivalent provisions in most other jurisdictions operating offshore oil, gas and wind infrastructure. Internationally, the underlying convention is UNCLOS Article 60(5), which permits coastal states to establish safety zones of up to 500 metres around offshore installations.

The zone applies automatically to most fixed and floating installations engaged in exploration, exploitation or associated activities. It does not generally apply to vessels in transit, mobile drilling units under tow with no operational activity, or wind turbines that fall under separate national rules — but those exceptions vary by jurisdiction and should always be checked.

Who is allowed to enter the zone

The default position in law is simple: no vessel may enter the 500m safety zone of an offshore installation without authorisation. The exceptions are tightly drawn:

• Vessels providing services to, or directly supporting, the installation (supply vessels, ERRVs, walk-to-work, dive support, crew transfer).
• Vessels engaged in saving or attempting to save life.
• Vessels operating under stress of weather, where compliance would put the vessel in greater danger.
• Vessels with prior written permission from the duty holder, typically coordinated through the OIM.

In every other case, entry is an offence. In the UK it is prosecutable; in practice it is almost always also reported as a dangerous occurrence under RIDDOR.

What "authorised" really means

This is where the language gets dangerous. "Authorised" does not mean "safe." It means *permitted, subject to the procedures the duty holder has set for that entry*.

In practice an authorised entry typically requires:

1. A current contractual or operational relationship between the vessel and the installation.
2. Pre-entry communication on a designated VHF channel.
3. Confirmation of the operation being supported (cargo, personnel transfer, standby, dive, etc.).
4. Acknowledgement that the vessel's Master remains in command and responsible for collision avoidance.
5. Completion of any pre-entry checklist required by the duty holder's safety case.

Every one of those steps is a coordination handoff, and every one of those handoffs is where authorised-vessel incidents typically originate (see our companion article on the 98.6% figure).

What the duty holder actually owes

The duty holder — usually the operator of the installation — owes a defined set of duties under the relevant safety case regime. In a 500m context the most relevant are:

• Maintaining a current safety case approved by the regulator.
• Ensuring the installation is broadcasting its position and identity on AIS continuously.
• Maintaining a competent OIM and a duty deck officer with visibility over the zone.
• Operating, or contracting, an ERRV (Emergency Response and Rescue Vessel) where required by the safety case.
• Pre-briefing attending vessels on the operational picture, weather, simultaneous operations and any restrictions.

Crucially, the duty holder owes a coordination duty, not a control duty. The Master of the attending vessel does not surrender command on entering the zone. This shared responsibility model is why synchronised situational awareness matters: both parties remain in command, but they need to be working from the same picture.

Three misconceptions worth retiring

"I'm authorised, so I'm cleared to manoeuvre." No. Authorisation grants you the right to be inside the zone for a defined purpose. Every manoeuvre still requires its own communication, its own checklist, and — increasingly — its own logged digital acknowledgement.

"VHF acknowledgement equals action complete." No. Verbal acknowledgement on a congested channel, under fatigue, with a non-native English speaker, is one of the highest-failure-rate handoffs in the offshore working environment. Modern safety practice treats acknowledgement and action as two separate events requiring two separate confirmations.

"The 500m zone protects the vessel from the installation." Not really. The zone exists primarily to protect the installation, the people on it, and the marine environment from vessel impact. Vessel protection is a downstream benefit of the same coordination discipline.

How to know your operation is running the zone well

A few simple, vendor-neutral diagnostics:

• Can your OIM, your attending vessel's Master, and your shoreside marine coordinator describe the current operational picture in the same way, in real time, without picking up a radio?
• Is your last 500m entry logged as a single auditable digital timeline, or is it scattered across three logs that have to be reconciled later?
• When a "stand off" or "make safe" is called, does every party see the call on a screen as well as hear it on the radio?

If the answer to any of those is "not really", you are operating the zone the way the industry has operated it for forty years — which is the way that produced the 98.6% number.

There is a better way to run it, and it does not require waiting for the next regulatory change.