The Convention for the Suppression of Unlawful Acts Against the Safety of Maritime Navigation (SUA), adopted in Rome on 10 March 1988 and in force since 1 March 1992, is the primary international treaty that criminalises violent acts targeting ships at sea and requires the 166 contracting states to either prosecute or extradite offenders. It was a direct response to the October 1985 hijacking of the cruise liner Achille Lauro, which exposed a gap in international law that left maritime terrorists without a clear legal framework to be brought to justice.
Background: the Achille Lauro hijacking and the jurisdictional gap
On 7 October 1985, four members of the Palestine Liberation Front seized the Italian cruise liner Achille Lauro in the eastern Mediterranean. The ship was sailing from Alexandria toward Ashdod, Israel, carrying around 400 passengers and crew. The hijackers demanded Israel release 50 Palestinian prisoners. On 8 October, at approximately 3:00 pm, they shot Leon Klinghoffer, an elderly American wheelchair-user, and threw his body into the sea.
The incident produced an immediate legal puzzle. No existing treaty squarely covered what had happened. UNCLOS Article 101, which defines piracy, requires that the violent act be committed for private ends on the high seas by one vessel against another. The Achille Lauro hijacking involved a single ship, was politically motivated, and occurred partly in Egyptian territorial waters. None of the three UNCLOS conditions was met. The Tokyo Convention 1963 and Hague Convention 1970 addressed aircraft hijacking, but no equivalent covered ships. The offenders were therefore left to be dealt with under domestic Italian law, which produced prosecutions of varying effectiveness but no coherent international framework.
The United States dispatched F-14 Tomcat fighters to intercept the EgyptAir aircraft carrying the hijackers from Egypt and forced it to land at a NATO base in Sicily. That action prevented the attackers from reaching a safe haven, but it also illustrated the ad hoc, state-by-state character of any response. Without a treaty obligation, other states had no duty to cooperate.
The IMO convened a legal working group in 1986. Italy, Austria, and Egypt submitted a joint draft convention in 1987. After two years of negotiation the Rome Conference adopted two instruments on 10 March 1988: the Convention for the Suppression of Unlawful Acts Against the Safety of Maritime Navigation and its companion Protocol for the Suppression of Unlawful Acts Against the Safety of Fixed Platforms Located on the Continental Shelf.
The 1988 instrument family
The SUA family spans four instruments, two adopted in 1988 and two in 2005.
| Instrument | Adopted | Entry into force | Scope |
|---|---|---|---|
| SUA Convention 1988 | 10 March 1988 | 1 March 1992 | Ships in international navigation |
| Fixed Platforms Protocol 1988 | 10 March 1988 | 1 March 1992 | Fixed platforms on the continental shelf |
| Protocol of 2005 to the SUA Convention | 14 October 2005 | 28 July 2010 | Terrorism, WMD transport, boarding regime |
| Protocol of 2005 to the Fixed Platforms Protocol | 14 October 2005 | 28 July 2010 | Terrorism offences on fixed platforms |
The 1988 Convention entered into force on 1 March 1992 after the required 15 ratifications were deposited with the IMO Secretary-General, who serves as depositary for all four instruments. As of June 2015 (the most recent figure with a verified source), 166 states were parties, representing 94.5% of world merchant fleet gross tonnage. The 2005 Protocol had 47 contracting parties as reflected in the UN Treaty Collection, a smaller group that includes Algeria, Denmark, France, Germany, Greece, Norway, Panama, Spain, Sweden, Switzerland, the United Kingdom, and the United States.
Article 3: the original offence list
The 1988 Convention’s core provision is Article 3, which requires each contracting state to make the following acts criminal offences under its domestic law:
Seizing or exercising control of a ship by force, threat, or intimidation. This is the paradigm case drawn directly from the Achille Lauro facts.
Performing an act of violence against a person on board a ship if that act is likely to endanger the safe navigation of the ship. The drafters deliberately used “likely to endanger” rather than requiring actual danger, so the offence is complete when the risk materialises, not only when a collision or sinking results.
Destroying a ship or causing damage to a ship or to its cargo that is likely to endanger the safe navigation of that ship.
Placing, or causing to be placed, on a ship a device or substance which is likely to destroy the ship, cause it damage that endangers navigation, or damage port facilities.
Destroying or seriously damaging maritime navigational facilities or interfering with their operation, where the act is likely to endanger safe navigation. This brings interference with AIS transponders, lighthouses, and VHF communications within scope.
Communicating false information that endangers safe navigation of a ship. Deliberate misuse of distress signals or false position reports fall here.
Injuring or killing any person in connection with the commission of any of the foregoing offences or of an attempt to commit them.
Attempting to commit any of the above.
Being an accomplice of a person who commits or attempts to commit any of the above.
Compelling a person by threats to commit any of the above.
The list covers all four stages of an attack: preparation, execution, injury, and compulsion of others. It makes no reference to the motivation of the offender. A hijacking is an Article 3 offence regardless of whether the perpetrators are political, religious, or commercially motivated. This is a deliberate departure from the UNCLOS “private ends” requirement and was accepted after significant debate about the tension between a broad offence list and the risk of criminalising acts of political resistance.
Which ships the Convention covers
Article 4 confines the Convention’s reach to ships in navigation or scheduled for navigation “into, through, or from waters beyond the outer limit of the territorial sea of a single State.” A vessel operating exclusively within one state’s internal waters is outside the Convention. A coastal ferry that crosses no international boundary is not covered. This is not an oversight but a deliberate jurisdictional limit that preserves coastal-state autonomy over domestic waterway security. The result is a gap: an act of violence on a purely domestic vessel in a port would be tried under domestic law, not the SUA framework.
Fixed platforms on the continental shelf are covered by the 1988 Protocol rather than the main Convention. Article 1 of that Protocol applies an equivalent offence list to “fixed platforms,” defined as structures permanently attached to the seabed for the purpose of exploration or exploitation of resources. Floating production, storage, and offloading vessels (FPSOs) and mobile offshore drilling units (MODUs) operating as ships rather than fixed structures fall under the main Convention, not the Protocol.
Jurisdiction: Article 6
A convention that creates offences but leaves every state free to decide whether it has jurisdiction produces a patchwork. Article 6 addresses this by requiring each state party to establish jurisdiction when:
The offence is committed against or on board a ship flying its flag. This is flag-state jurisdiction, the most traditional maritime jurisdictional basis.
The offence is committed in the territorial sea of that state. This is territorial jurisdiction.
The offence is committed by a national of that state. This is active-personality jurisdiction.
A national of that state is seized, threatened, injured, or killed during the commission of the offence. This is passive-personality jurisdiction, allowing a victim’s home state to assert a claim.
The offence is committed in an attempt to compel that state to do or abstain from doing any act. This allows states that are the target of coercion to assert jurisdiction even if the attack happens elsewhere.
Article 6(2) additionally permits, but does not require, states to establish jurisdiction in other cases. The convention thus creates a mandatory floor and allows voluntary expansion. This matters when an offender surfaces in a state with no mandatory jurisdictional link; that state may still prosecute but isn’t obliged to.
The prosecute-or-extradite obligation: Article 10
Article 10 carries the convention’s central enforcement mechanism: aut dedere aut judicare, Latin for “either extradite or submit for prosecution.” A state in whose territory an alleged offender is found must, without exception and whether or not the offence was committed in its territory, submit the case to its competent authorities for prosecution, or extradite the person to any requesting state that has established jurisdiction.
The obligation is unconditional on the submission-to-prosecution side. A state cannot simply decline to act. If extradition is not carried out, the case goes to prosecutorial authorities. What the convention does not require is a conviction: prosecution means a good-faith submission to the relevant authorities, not a guaranteed outcome.
Articles 11 and 11bis reinforce this by treating the SUA offences as extraditable offences under any existing bilateral extradition treaty and requiring states to include them in future treaties. The 2005 Protocol added Articles 11bis and 11ter, which explicitly prohibit treating a SUA offence as a political offence for extradition purposes. Before 2005, a state could theoretically invoke the political offence exception to refuse extradition of a maritime hijacker. That route is now closed for states party to the 2005 Protocol, at least as between themselves.
The 1988 Fixed Platforms Protocol
The companion instrument to the main Convention addresses a structural weakness in maritime law: offshore oil and gas platforms on the continental shelf are not ships and are therefore outside any ship-focused convention. The 1988 Protocol extends an equivalent set of offences to fixed platforms, requiring states to criminalise:
Seizing or exercising control of a fixed platform by force.
Acts of violence against persons on a platform that are likely to endanger its safety.
Destroying or damaging a fixed platform.
Placing destructive devices on a platform.
Injuring or killing persons in connection with the foregoing acts, plus attempt and accomplice liability.
The Protocol has the same jurisdictional architecture as the main Convention and incorporates by reference the aut dedere aut judicare obligation. The 2005 Protocol to the Fixed Platforms instrument added terrorism-purpose offences equivalent to those in Article 3bis of the main 2005 Protocol, so an attack on a platform motivated by a desire to coerce a government falls within the same framework as a ship-based attack.
The 2005 Protocols: terrorism, WMD transport, and the boarding regime
The 2005 Protocols were adopted in London on 14 October 2005 after a Diplomatic Conference on the Revision of the SUA Treaties convened from 10 to 14 October 2005. They entered into force on 28 July 2010, after the required 12 ratifications were deposited. The negotiating context was the post-September-2001 counterterrorism environment and, more specifically, the push by the United States and its Proliferation Security Initiative partners for a multilateral legal basis for maritime interdiction of weapons of mass destruction.
Article 3bis: terrorism-purpose offences
Article 3bis divides new offences into two groups based on whether the act has a terrorism purpose.
The first group (Article 3bis(1)(a)) covers acts where “the purpose of the act, by its nature or context, is to intimidate a population, or to compel a Government or an international organization to do or to abstain from doing any act.” Within that frame, it criminalises:
Using explosives, radioactive material, or biological, chemical, or nuclear (BCN) weapons against or on a ship in a way likely to cause death or serious injury.
Discharging oil, LNG, or other hazardous substances from a ship in quantities likely to cause death, serious injury, or major damage.
Using a ship itself as a weapon, in the manner of a maritime suicide attack.
Threatening to commit any of the above.
The second group (Article 3bis(1)(b)) covers proliferation acts, not requiring a terrorism purpose but still a new category of SUA offence:
Transporting explosives or radioactive material knowing it is intended to cause death or serious injury.
Transporting any BCN weapon.
Transporting source or special fissionable material knowing it is intended for use in a nuclear explosive or non-safeguarded nuclear activity.
Transporting equipment or materials that will contribute in a material way to the design, manufacture, or delivery of a BCN weapon.
The distinction matters because the first group requires proof of a terrorism purpose (an element that can be difficult to establish), while the second requires only that the carrier knew the intended use, making it more accessible as a prosecutorial theory.
Article 3ter: transporting fugitives
Article 3ter separately criminalises transporting persons on board a ship with intent to help them evade criminal prosecution when the carrier knows those persons committed a SUA offence, including the new WMD transport offences. This provision closes a pathway used in historical incidents where offenders moved by sea between jurisdictions specifically to avoid air-travel document checks.
Article 3quater: extended accomplice liability
Article 3quater adds four further accessory offences applicable to all SUA Convention offences, including 3bis and 3ter: injuring or killing persons in connection with a covered offence, attempting a covered offence, being an accomplice, and organising or directing others to commit a covered offence. The organizing-and-directing provision is aimed at command structures: a terrorism organiser who plans a ship-based attack but is not physically present can still be prosecuted.
Article 8bis: the ship-boarding regime
Article 8bis is the most operationally contested provision in the 2005 Protocol. It establishes a structured process for one state party to board a vessel flying the flag of another state party that it reasonably suspects is involved in a SUA offence.
The basic rule is that flag state authorisation is required before boarding. A requesting state that has reasonable grounds for suspicion contacts the flag state and requests consent. The regime then allows for three different authorisation tracks:
Standard request. The requesting state contacts the flag state by the fastest available means. The flag state has four hours to respond. If it authorises boarding, the requesting state may proceed. If it refuses, boarding is prohibited.
Pre-notified four-hour default consent. A flag state may notify the IMO Secretary-General in advance that any other state party may board a vessel flying its flag if the flag state does not respond to a boarding request within four hours. States that file this notification effectively waive the four-hour requirement in their favour.
Pre-notified general consent. A flag state may go further and notify the IMO Secretary-General that it authorises boarding by any state party at any time, without a case-by-case request.
The United States, which pushed hard for the boarding regime during negotiations, nonetheless declared that it would not file either form of advance notification with the IMO Secretary-General, meaning its flag vessels remain subject to the case-by-case standard request process. This is a significant practical asymmetry: the United States can request to board other nations’ pre-consenting vessels without delay, while other nations must wait for case-by-case US authorisation before boarding US-flag ships.
Article 8bis(10) sets out safeguards that apply to all boardings: the boarding state must not endanger life at sea; must preserve the human dignity of persons on board in accordance with human rights law; must protect the safety and security of the ship and its cargo; must take environmentally sound measures; and must avoid unduly detaining or delaying the ship. If the suspicion is not confirmed, the state that requested boarding must provide adequate compensation to the flag state for any loss or damage resulting from the boarding.
The boarding regime’s relationship to the Proliferation Security Initiative (PSI), launched by the United States in 2003, was explicit in the US Senate ratification debate. The Department of Defense stated that Article 8bis “will facilitate timely coordination of boarding requests from flag states, some of which are not participating in the PSI” and will “strengthen the international legal basis for interdictions at sea carried out under the PSI.” The 2005 Protocol thus acts as a multilateral underpinning for what had been a US-led set of bilateral and informal arrangements for WMD interdiction at sea.
Political offence exception: Articles 11bis and 11ter
Before the 2005 Protocol, states could potentially invoke a political offence exception to refuse extradition of a maritime attacker on the grounds that the underlying act was politically motivated. Articles 11bis and 11ter of the 2005 Protocol remove this option for states party to that instrument. SUA offences are excluded from any political offence exception under extradition treaties between 2005-Protocol parties. The only carve-out is Article 11ter, which prohibits using the extradition obligation as a pretext for persecuting a person on account of race, religion, nationality, or political opinion.
Relationship to the ISPS Code and SOLAS Chapter XI-2
The SUA Convention operates at the criminal law level: it defines offences and creates an extradition-and-prosecution framework. The ISPS Code and SOLAS Chapter XI-2, which entered into force on 1 July 2004, operate at the security management level: they require ships and port facilities to assess threats, implement security plans, appoint security officers, and maintain security logs.
The two frameworks are complementary rather than overlapping. ISPS addresses prevention and preparedness. SUA addresses prosecution after an act has been committed or attempted. In practice, the security plan that an ISPS-compliant ship maintains is designed to prevent the very acts that the SUA Convention criminalises. A ship that has been seized by force has almost certainly failed ISPS requirements; the SUA framework then determines what happens to the perpetrators.
The IMO coordinates both frameworks under its Maritime Security programme, described on the IMO website as encompassing “the ISPS Code and SOLAS chapter XI-2, counter-piracy initiatives, and the SUA Convention.” Flag states and port states draw on the SUA offence list when enacting domestic shipping security legislation, and domestic courts applying port state control enforcement encounter SUA-derived offence categories when evaluating security deficiencies.
Relationship to UNCLOS piracy provisions
UNCLOS Article 101 defines piracy as illegal acts of violence, detention, or depredation committed for private ends on the high seas by the crew or passengers of a private ship against another ship. The definition excludes acts in territorial waters, acts against one’s own ship, and acts with political motivation.
The SUA Convention fills several of these gaps. It covers:
Acts in ports and territorial seas. An attack on a ship in a harbour, or a seizure by its own crew (the Achille Lauro hijackers boarded as passengers), falls within SUA but not UNCLOS.
Politically motivated acts. The SUA Convention makes no reference to the purpose of the offence; the 1988 text is motive-neutral.
Single-ship incidents. UNCLOS piracy requires two ships. SUA Article 3(1)(a) covers seizing control of a ship by any person on board.
However, SUA does not replicate the universal jurisdiction that UNCLOS gives states over piracy. UNCLOS Article 105 allows any state to seize a pirate ship on the high seas and try the offenders. SUA creates a web of overlapping mandatory jurisdictions but does not grant a right of universal enforcement. A state cannot, under SUA, board a foreign-flag vessel on the high seas merely because it suspects a SUA offence, without the flag state’s consent (Article 8bis applies this consent requirement directly). The tension between the broad offence list and the narrower enforcement authority is a recurring criticism.
The Somali piracy crisis of 2008 to 2012 brought this tension into focus. Piracy attacks in the Gulf of Aden and off the Somali coast reached a peak of 237 incidents in 2011 (IMO figure). States conducting counter-piracy operations under UN Security Council Resolutions 1816 (2008), 1851 (2008), and 1897 (2009) relied primarily on the UNCLOS piracy regime and the specific authorisations in those resolutions to enter Somali territorial waters and arrest suspects. SUA provided the domestic legal basis for prosecution in some states: the United States charged Somali suspects under 18 U.S.C. §2280, the domestic statute implementing the SUA Convention, in prosecutions including United States v. Lei Shi (2008) and United States v. Dire (2012).
Enforcement and notable prosecutions
The SUA Convention’s enforcement record is sparse but meaningful.
United States v. Lei Shi (2008). The defendant, master of a Taiwanese-flag cargo vessel, killed two crew members and held others hostage. US authorities charged him under 18 U.S.C. §2280, the SUA-implementing statute. The Ninth Circuit Court of Appeals confirmed that the statute gave US courts jurisdiction over offences against ships even when the ship was not of US flag and the victims were not US nationals, provided the ship subsequently entered US waters. The case confirmed that SUA-basis domestic legislation could extend US jurisdiction to a vessel not otherwise connected to the United States.
Somali piracy prosecutions (2008 to 2012). Several US federal prosecutions of Somali pirates relied on 18 U.S.C. §2280 as one of the charging statutes, alongside the historic piracy statute (18 U.S.C. §1651). In United States v. Dire et al. (2012), the Fourth Circuit Court of Appeals sustained SUA-based charges against defendants who had attacked the USS Nicholas, a Navy warship. The SUA Convention’s inclusion of military vessels as potential victims (unlike UNCLOS piracy, which requires a private ship) was relevant to those convictions.
European national prosecutions. Several EU member states, including France, the Netherlands, and Belgium, prosecuted Somali pirates arrested by their naval forces during counter-piracy patrols. These prosecutions used SUA-implementing domestic legislation as the jurisdictional basis.
The prosecution record reveals a structural difficulty: SUA creates the obligation to prosecute but does not resolve the resource and practical burden of holding, trying, and imprisoning offenders. Many states intercepting pirates at sea found it operationally simpler to release them rather than transfer them for trial. The Djibouti Code of Conduct (2009), a regional instrument covering states around the Gulf of Aden and western Indian Ocean, addressed this partly by creating mechanisms for information sharing and regional prosecution.
The Achille Lauro perpetrators themselves were tried under Italian domestic law, not an SUA-equivalent instrument that did not yet exist at the time of the attack. Abu Abbas, the Palestine Liberation Front leader who planned the operation, was convicted in absentia in Italy and given a life sentence in 1986. He was later arrested in Baghdad in 2003 by US forces and died in US custody in 2004. The four hijackers who were on board the ship received sentences ranging from 15 to 30 years from the Italian courts. The episode illustrated precisely the kind of prolonged, jurisdictionally complex aftermath that the SUA Convention was designed to prevent for future incidents.
The distinction between SUA prosecution and UNCLOS-based piracy prosecution matters for practising lawyers. UNCLOS piracy carries universal jurisdiction: any state may arrest a pirate ship on the high seas. SUA requires one of the Article 6 mandatory jurisdictional links or the flag state’s consent under Article 8bis. In the Gulf of Aden, most intercepting naval states asserted UNCLOS jurisdiction for the arrest and relied on bilateral transfer agreements with Kenya, the Seychelles, or Mauritius for the actual trial. SUA-implementing statutes were then used in home-state prosecutions when naval vessels brought suspects back. The two regimes operated in parallel rather than in sequence.
The 2005 boarding regime in practice
Article 8bis had not, as of the most recent public IMO reporting, generated a large volume of formally documented boarding authorisation requests. The PSI bilateral ship-boarding agreements that the United States negotiated with Panama, the Bahamas, Croatia, and several other flag states between 2004 and 2010 follow broadly similar consent-and-response architecture to Article 8bis and were the operational template from which the multilateral text was derived. The difference is coverage: a US-Bahamas bilateral agreement applies only to Bahamian-flag ships, while Article 8bis applies to all SUA 2005 parties’ flag ships with a single legal text.
States that have pre-notified the IMO Secretary-General of advance boarding consent include a limited group; the IMO has not publicly released a full list in a format confirmed by primary source research for this article. The operational tempo of interdiction requests under Article 8bis in practice runs below what the PSI mechanism processes bilaterally.
Relationship to the flag-state and port-state control frameworks
The SUA Convention assumes the foundational maritime law principle of flag-state jurisdiction: a ship on the high seas is subject to the law of the state whose flag it flies. Article 8bis reinforces this by making flag state consent the entry point for boarding authorisation. This connects directly to the responsibilities of flag states and flags of convenience: a flag state that fails to respond to a boarding request within four hours has de facto given no consent and the boarding cannot proceed under SUA, regardless of how strongly the requesting state suspects an offence is occurring.
Port state control (PSC) is the mechanism by which states inspect foreign-flag vessels in their ports. PSC inspections under the Paris MOU, Tokyo MOU, and other regional regimes are not directly governed by SUA, but PSC officers who find evidence of an offence on a vessel in port can act on domestic criminal law implementing SUA obligations. A ship in port is within the Convention’s scope (Article 4 covers ships “scheduled for navigation” into international waters), and a port state that detains offenders is bound by the Article 10 aut dedere aut judicare obligation.
The SOLAS Convention interacts with SUA at the level of ship security equipment. SOLAS Chapter XI-2 requires ships of 300 GT and above on international voyages to carry AIS transponders and ship security alert systems. Tampering with AIS, a SUA Article 3(1)(e) offence (interference with navigational aids), triggers SOLAS equipment obligations on the technical side simultaneously.
Limitations
The SUA Convention does not create a dedicated international enforcement body. There is no SUA tribunal, no standing maritime security force, and no automatic mechanism that identifies or brings suspects to any particular jurisdiction. The aut dedere aut judicare obligation is only as effective as the domestic legal systems of contracting states, and enforcement varies substantially between jurisdictions.
The Convention’s geographic scope excludes purely domestic voyages, which is a real gap in regions where maritime crime migrates to internal routes precisely to avoid the international framework. In Southeast Asia, for example, attacks on vessels operating between Indonesian islands do not trigger SUA obligations.
The motive-neutral character of the offence list, which was the deliberate intent of the drafters, creates political friction when states characterise maritime violence as legitimate resistance or insurgency. The 1988 text lacks a political offence carve-out, which was controversial at adoption; the 2005 Protocol’s Articles 11bis and 11ter remove the extradition escape but apply only between 2005-Protocol parties, and as of 2016 those parties numbered 40, a subset of the 166 parties to the 1988 Convention.
The Article 8bis boarding regime is a compromise that satisfies neither enforcement practitioners, who regard four hours as too long to wait before acting on a time-sensitive intelligence lead, nor civil libertarians and flag states concerned about unilateral enforcement of powerful states. The US decision not to grant advance consent while retaining the ability to request consent from others who have granted it creates an asymmetry that smaller maritime states have noted in IMO debates.
The Convention applies to physical acts against vessels and persons. Cyber attacks that interfere with ship navigation systems, AIS spoofing, and GPS jamming may fall within Article 3(1)(e) (interference with navigation aids) or Article 3(1)(f) (communicating false information endangering navigation), but the drafters in 1988 did not contemplate digital vectors. A 2022 paper in the International Law Studies journal (US Naval War College) argued that malware affecting a vessel’s navigation systems could be read as a SUA offence, but no authoritative domestic or international ruling has confirmed that interpretation as of the most recent available sources.
The 2005 Protocol’s WMD transport provisions (Article 3bis(1)(b)) require proof that the carrier knew the intended use of the material. Proving mens rea in a bulk cargo vessel carrying dual-use materials that could serve either civilian or weapons purposes is a substantial prosecutorial challenge. No publicly documented prosecution under these provisions had been confirmed at the time of writing.
The domestic implementation gap is a further structural limitation. The Convention obliges states parties to “take such measures as may be necessary to establish jurisdiction” and to enact domestic offences, but it sets no model text and no implementation deadline. The quality and coverage of domestic implementing legislation varies widely. Some states, like the United States with 18 U.S.C. §2280, enacted specific statutory provisions that have been tested in court and interpreted by appellate judges. Others incorporated SUA obligations by a general ratification decree without dedicated implementing legislation, leaving prosecutors to use analogue domestic offences that may not mirror the Article 3 list. The IMO’s technical cooperation programme has assisted states with implementation, but the result is an uneven patchwork.
The Convention also does not address what states must do with a ship after a SUA incident. After an offender is arrested and extradition or prosecution begins, the ship itself may sit in port for months as evidence. Crew members who are witnesses, not suspects, can find themselves unable to leave the jurisdiction. SOLAS imposes no parallel provision requiring their repatriation or the expeditious release of the vessel once it is no longer needed as a crime scene. These operational consequences are managed under domestic law and bilateral diplomatic channels, not the SUA framework itself.
The 2005 Protocol’s 47-state ratification base (UN Treaty Collection figure) contrasts with 166 parties to the 1988 Convention. Several major flag states and commercially important maritime states remain outside the 2005 instrument, meaning the WMD transport offences and the Article 8bis boarding regime apply only to a fraction of world shipping. A requesting state attempting to board a vessel flying the flag of a non-party to the 2005 Protocol must fall back on UNCLOS, Security Council resolutions, or bilateral agreements, not Article 8bis.
The SUA Convention in context: the IMO legal architecture
The SUA Convention sits within a broader IMO legal architecture alongside the SOLAS Convention, MARPOL, the STCW Convention, and specialised instruments. The ISPS Code is its closest operational partner. The SOLAS Chapter XI-2 article on this site covers the regulatory detail of ship security plans, security levels, and the ISPS certification process that the SUA framework backstops with criminal liability.
For mariners and shipping companies, the SUA Convention is a background legal instrument. It does not impose operational requirements directly: no ISPS-equivalent certification, no ship security plan template, no reporting format. Its practical effects are: if a ship is seized, the crew murdered, or a bomb placed on board, there is an international legal obligation on contracting states to prosecute or extradite the perpetrators; and if a vessel is suspected of WMD transport under the 2005 Protocol, there is a defined consent mechanism for a boarding state to request flag state authorisation.
The convention’s importance is therefore prosecutorial, deterrent, and normative rather than operational. It establishes that maritime violence is a category of serious international crime, not merely a domestic matter to be handled by whoever happens to have custody of the offender. For the 166 states that are parties, and for the maritime industry operating globally, that norm has practical value even when individual prosecutions are rare.