Naval, Defense and Search-and-Rescue

Two of the most demanding jobs at sea share a hull form and almost nothing else. A frigate is built to take a missile hit and keep fighting; a rescue cutter is built to put a swimmer in the water beside a capsized fishing boat at three in the morning. One belongs to the armed forces of a state and carries weapons; the other belongs to a coastguard and carries stretchers. Yet the same UNCLOS article that defines the warship also binds it, and every merchant ship that passes, to drop everything and rescue a person in danger of being lost. This is the hub for naval, defense, and search-and-rescue: the corner of the maritime world where the ships are built and crewed by states rather than by owners chasing freight, and where the governing question is not what cargo to carry but who must rescue whom, and what a fighting ship is allowed to do. It sits under the security, defense, technology and specialized operations portal because the rules here are SAR conventions and the law of armed force at sea, not the commercial conventions that govern a charter or a cargo claim. The hub routes down to two cluster hubs, search and rescue and naval and defense vessels, and to the calculators that work the alerting and carriage rules, such as the GMDSS sea-area coverage check and the SOLAS V/33 distress-alert calculator.

The two worlds are distinct, and the split is worth holding from the start. Search and rescue is a safety system: a duty owed to any person in distress, run by civil authorities through coordination centers and built on the 1979 SAR Convention. Naval and defense is a question of status and capability: what makes a ship a warship under the law, what immunity that status carries, and how a fighting ship is designed and classed so it survives a hit a merchant ship would not. The threads cross because a warship is often the best rescue unit in an area, & because the same duty to assist binds the destroyer and the container ship alike. The rest of this hub walks the two in turn and shows where they meet.

Two distinct worlds under one hub

The cleanest way to keep the two apart is by the question each answers and the body that answers it. Search and rescue asks who must rescue a person in distress and how the rescue is coordinated, and the answer comes from the IMO through the SAR Convention, the SOLAS duty to assist, and the IAMSAR Manual. Naval and defense asks what a warship is, what it may do, and how it is built, and the answer comes from UNCLOS for the status, from national navies and class societies for the design. One world is run for the benefit of any person who ends up in the water; the other is run for the projection & defense of state power. They share the sea and the duty to rescue, and almost nothing else.

The table understates how often a single incident touches both columns. A migrant boat in distress in the central Mediterranean triggers the civil SAR machinery, an MRCC tasking, an on-scene coordinator, the SOLAS duty on every passing merchant ship, and just as often a navy frigate diverted to act as the most capable rescue unit on scene. The two worlds are run by different bodies and built to different rules, yet they meet on the water the moment a person is in danger of being lost, which is why this hub treats them as one subject rather than two.

The two worlds also rest on different parts of the law of the sea, and the chronology shows why they feel so different to apply. The dates below are the adoption or entry-into-force dates of the governing instruments, not the date any single ship or rescue center complied.

• 1948: the IMO is established by convention (then the Inter-Governmental Maritime Consultative Organization), the body that would later write the SAR Convention and co-publish the IAMSAR Manual.
• 1974 to 1980: the present SOLAS Convention is adopted in 1974 and enters into force on 25 May 1980, carrying the Chapter V duty to assist and the radio-communications chapter that becomes the GMDSS framework.
• 1979 to 1985: the SAR Convention is adopted at Hamburg on 27 April 1979 and enters into force on 22 June 1985, building the shore-side rescue machinery the ship-level duty had lacked.
• 1982 to 1994: UNCLOS is adopted in 1982 and enters into force on 16 November 1994, fixing the Article 29 definition of a warship and the Article 98 duty to render assistance in treaty law.
• 1992 to 1999: the GMDSS is phased in under SOLAS Chapter IV, becoming fully mandatory for affected ships from 1 February 1999, replacing the old Morse-code distress watch with automatic satellite and digital alerting.

The order matters because the later instruments lean on the earlier ones. The SAR Convention assumed the SOLAS duty already existed and added the coordination layer; the GMDSS gave that coordination an automatic alert to act on; and UNCLOS put both the warship definition and the rescue duty into the framework treaty that the IMO instruments operate within. A single rescue can engage a 1974 SOLAS regulation, a 1979 convention, and a 1982 law-of-the-sea article at once.

Search and rescue: the duty and the machinery

The first world rests on a split that confuses people who meet it for the first time: the duty to rescue and the machinery to coordinate the rescue come from different instruments. The duty on the individual ship is old, written into seafaring tradition and into treaty law long before any international SAR plan existed. SOLAS Regulation V/33 puts it plainly: the master of a ship at sea which is in a position to provide assistance, on receiving a signal from any source that persons are in distress at sea, is bound to proceed with all speed to their assistance, if possible informing them or the search and rescue service that the ship is doing so. UNCLOS Article 98 sets the same duty in the framework treaty, requiring the master to render assistance so far as they can without serious danger to the ship, the crew, or the passengers. The detail of the convention sits in the search and rescue cluster hub; this hub gives the shape.

What the 1979 SAR Convention added was the missing half: the shore-side organization that turns one ship’s distress alert into a coordinated operation. Before it, a ship in distress could send a signal and hope a passing vessel heard, but no system tasked the right units, divided the responsibility between coastal states, or coordinated maritime and aeronautical assets. The Convention built that system, and after its adoption the IMO Maritime Safety Committee divided the world’s oceans into 13 search and rescue areas, within which states delimit the search and rescue regions they answer for. The IMO SAR 1979 calculator frames the convention’s coverage logic.

SAR regions and rescue coordination centers

The spine of the SAR system is geographic: the ocean is divided into search and rescue regions (SRRs), and each SRR has a state that is responsible for it, running a Rescue Coordination Center that covers it. An SRR is not a claim of sovereignty over the water; it is an allocation of rescue responsibility, so that any point at sea falls within some state’s coordination area and no distress alert lands in a gap. The boundaries are agreed between neighboring states and registered with the IMO, and they often follow but do not have to match the limits of a flight information region or a territorial sea.

The Rescue Coordination Center (RCC) is the unit that runs a case. On the maritime side it is usually called a Maritime Rescue Coordination Center (MRCC), and it is staffed around the clock to receive alerts, designate a SAR mission coordinator, task the available ships and aircraft, and stay in charge until the case is closed or handed over. A large country runs several MRCCs with subordinate Maritime Rescue Sub-Centers (MRSCs) under them; a small coastal state may run one. The center is the fixed point a distress alert flows to, and the unit a merchant master talks to when reporting that they are diverting to assist, which is why the GMDSS sea-area coverage check and the alerting equipment behind it matter to the rescue as much as to the ship.

The IAMSAR Manual, in three volumes

The working document of the SAR world is the International Aeronautical and Maritime Search and Rescue Manual (the IAMSAR Manual), published jointly by the IMO and the International Civil Aviation Organization (ICAO) so that aviation and maritime SAR follow one approach. It runs to three volumes, each aimed at a different reader, and a new edition is published every three years; the 2025 edition carried amendments approved by the IMO Maritime Safety Committee at its 109th session in December 2024.

Volume I, Organization and Management, is for the people who build and run national and regional SAR systems: the concept of the global SAR system, how to set up the RCCs and the regions, and how neighboring states cooperate to give effective and economical SAR services. Volume II, Mission Coordination, is for the staff who plan and coordinate a specific SAR operation: the search planning, the datum and search-pattern methods, the tasking of facilities. Volume III, Mobile Facilities, is the one carried aboard ships, rescue craft, and aircraft, written to help the crew perform a search, act as on-scene coordinator, or handle their own emergency. A merchant ship is required to carry Volume III precisely because any ship can be the first capable unit on scene and find itself running the search until a dedicated SAR unit arrives.

GMDSS as the alerting layer

The SAR machinery only works if the distress alert reaches it, and that is the job of the Global Maritime Distress and Safety System (GMDSS). Required by SOLAS Chapter IV, the GMDSS is the set of radio and satellite equipment and procedures that lets a ship raise the alarm automatically and lets shore authorities and nearby ships receive it, replacing the old requirement for a radio officer to keep a continuous Morse watch. It became mandatory for affected ships from 1 February 1999, and it carries the alert that sets the whole rescue in motion. The detail sits in the GMDSS overview and the SOLAS Chapter IV radio communications articles.

The system divides the sea into four areas by the kind of alerting that reaches them, and the required equipment scales with the area a ship trades in. Sea area A1 is within VHF range of a coast station with digital selective calling; A2 is within MF range; A3 is within the footprint of a recognized mobile-satellite service; and A4 is the polar regions beyond that footprint, where the equipment has to reach a satellite system covering the high latitudes. The GMDSS sea-area coverage check works that determination, the EPIRB coverage check frames the float-free satellite-EPIRB carriage, and the radio and EPIRB battery autonomy calculator checks the reserve-source capacity SOLAS IV requires.

The 406 MHz EPIRB is the clearest tie between alerting and rescue. It is a satellite-EPIRB that floats free as a ship sinks, switches on by water contact, and transmits the ship’s identity and position to a Rescue Coordination Center through the Cospas-Sarsat system, so an RCC can start tasking units before any human has reported the ship missing. The search-and-rescue radar transponder (SART) does the close-in half: once units are on scene, the SART radar transponder paints a line of blips on a searching ship’s radar that points straight at the survival craft, which is why the AIS-SART search-and-rescue transmitter sits in the same equipment family.

Mass-rescue operations and the on-scene coordinator

Most rescues involve a handful of people; a mass-rescue operation (MRO) is the case that overwhelms the normally available resources, a sinking ferry or cruise ship with hundreds or thousands aboard, or a large migrant vessel. The IAMSAR Manual treats the MRO as a distinct planning problem because the limiting factor stops being finding the survivors and becomes recovering and caring for very large numbers faster than the sea kills them. A coordination center planning for an MRO has to pre-arrange the ships, aircraft, ports of safety, and medical reception that no single rescue unit can supply, because improvising it during the event costs lives.

The on-scene coordinator (OSC) is the unit that holds the rescue together on the water. The RCC plans and tasks from ashore, but it designates an OSC at the scene, often the first capable ship or aircraft to arrive, to coordinate the search and rescue actions of all the facilities working the area: assigning search sectors, deconflicting tracks, relaying to the RCC, and avoiding the collisions and duplicated effort that kill a rescue’s momentum. A merchant master who answers a distress alert can become the OSC by default, running the operation from a cargo ship’s bridge until a coastguard cutter, a SAR aircraft, or a warship takes over, which is the practical reason every SOLAS ship carries IAMSAR Volume III and trains the bridge team in its use.

The coordination roles stack in a clear order, and a single case moves up and down the ladder as it develops. The table separates the shore-side coordinator from the unit running the search on the water and from the master of any passing ship who carries the duty to assist.

The split matters because the same physical ship can occupy more than one row at once. A merchant master first on scene is at that moment the assisting ship under SOLAS V/33 and the OSC under IAMSAR Volume III, taking direction from an SMC sitting in an MRCC hundreds of miles away. Keeping the roles distinct is what lets a coordination center hand the OSC function from a cargo ship to a coastguard cutter to a warship as more capable units arrive, without losing the thread of the search.

Naval and defense vessels: status, design, and class

The second world starts not with a duty but with a definition, because almost everything a warship is allowed to do at sea flows from its legal status. UNCLOS Article 29 sets the test, and it is exact: a warship is a ship belonging to the armed forces of a State, bearing the external marks distinguishing such ships of its nationality, under the command of an officer duly commissioned by the government of the State and whose name appears in the appropriate service list or its equivalent, and manned by a crew which is under regular armed forces discipline. Four limbs, all required, and the ship fails the test if it misses any one. The table breaks the single Article 29 sentence into the four conditions a ship has to meet at once to be a warship in law.

The detail sits in the naval and defense vessels cluster hub; this hub gives the shape and the consequences.

The status carries weight a merchant ship never has. A warship on the high seas enjoys complete immunity from the jurisdiction of any state other than its flag state, so no other state may board, arrest, or exercise enforcement over it. The flip side is enforcement power: under UNCLOS, the right of visit, the boarding of a vessel reasonably suspected of piracy or other listed conduct, and the seizure of a pirate ship may be carried out only by warships, military aircraft, or other clearly marked ships on government service and authorized to that effect. The same sovereign immunity attaches to a naval auxiliary on government non-commercial service. This is why the warship sits at the center of maritime enforcement, from the counter-piracy task forces in the war risk and high-risk areas of the Gulf of Aden to the interdiction of sanctioned cargoes, and the naval auxiliary CII-exemption calculator frames the regulatory carve-out that follows from the status.

The contrast with a merchant ship is sharpest when the two are put side by side. A merchant ship is subject to the jurisdiction of any coastal state whose waters it enters and to port-state control wherever it calls; a warship answers only to its flag state and cannot be boarded or detained by another state. A merchant ship is a target for enforcement; a warship is the enforcer. The table sets out the legal split that flows from the Article 29 status, and it is the reason the same hull cannot be both at once.

The one row where the two ships are identical is the last. UNCLOS Article 98 binds the warship and the merchant ship to the same duty to render assistance, which is the single legal thread that runs straight across the split status, and the reason the naval world cannot be separated from the SAR world this hub also covers.

The enforcement powers in the third row are narrower than they look, and the limits matter at sea. The right of visit under UNCLOS Article 110 lets a warship board a foreign ship on the high seas only on reasonable grounds to suspect piracy, the slave trade, unauthorized broadcasting, statelessness, or that the ship is really of the warship’s own nationality though flying a foreign flag. The repression of piracy under Article 105 lets a warship seize a pirate ship and arrest those aboard, with the courts of the seizing state deciding the penalties. Both powers are reserved to warships, military aircraft, or other clearly marked government ships authorized to that effect, which is the precise legal hook that lets a navy frigate stop and board a suspected pirate skiff that a merchant ship, however large, has no authority to touch.

Naval ship classes

Navies group their surface combatants and support ships into classes by role and size, and the rough hierarchy holds across most fleets even where the exact tonnages differ. A destroyer is a large surface combatant built for air defense and strike, typically the heaviest escort in a fleet. A frigate is a general-purpose escort, smaller than a destroyer, weighted toward anti-submarine and anti-surface work. A corvette is smaller again, a light combatant for coastal and littoral work. An offshore patrol vessel (OPV) is a lightly armed ship for constabulary tasks, fishery protection, and exclusive-economic-zone patrol rather than high-end combat. Above the escorts sit the amphibious ships, landing platform docks and landing helicopter docks that put troops and vehicles ashore, and the auxiliaries that keep the fleet at sea.

The classes are not watertight, and the same name covers very different ships between navies; one country’s frigate displaces what another calls a destroyer. What the hierarchy fixes is the trade between size, armament, and endurance: a destroyer carries the area-air-defense radar and missiles a corvette cannot, at several times the displacement and cost, while an OPV trades the weapons for the endurance and economy a patrol mission needs. The design choices behind each class connect to the naval architecture coefficients that govern any hull, warship or merchant, because a frigate still obeys the same displacement, prismatic-coefficient, and powering relationships as a cargo ship even as its mission rewrites the priorities.

Survivability, signatures, and naval class rules

A warship is designed around a word that rarely appears in a merchant specification: survivability. A merchant ship is built to carry the most cargo for the least steel and to survive the sea; a warship is built to survive a deliberate attack and keep floating, moving, and fighting after a hit that would disable a commercial hull. That single difference reshapes the whole design. Magazines are protected and arranged to vent an explosion away from the ship; compartments are subdivided and the damage-control systems built to isolate flooding and fire fast; the hull and machinery are mounted to take the shock of an underwater explosion that a merchant ship’s rigid mounts would transmit straight into the structure.

Signature reduction is the second naval-only driver. A warship is designed to be hard to detect: the radar cross-section cut by sloped surfaces and shaping, the infrared signature reduced by cooling the exhaust, the acoustic & magnetic signatures managed to defeat mines and submarines. None of this serves a cargo ship, and none of it appears in SOLAS, which is why navies and class societies wrote separate naval ship rules. SOLAS itself does not reach a warship: Regulation I/3 exempts ships of war and troopships from the Convention, leaving each navy to set the standard its own fleet meets. The NATO Naval Ship Code (ANEP-77), the alliance’s goal-based naval safety standard, fills part of that gap by giving navies a SOLAS-equivalent framework written for the warship rather than the merchant ship. DNV publishes its Naval (NV) rules, captured in the DNV naval-ships class calculator; Lloyd’s Register publishes Rules for the Classification of Naval Ships; and the American Bureau of Shipping publishes its Naval Vessel Rules. They add the shock, vulnerability, recoverability, and weapons-integration requirements a merchant rule set never needed, while keeping the structural and stability backbone a class society brings to any ship.

The naval auxiliary and the civil-military interface

Between the gray warship and the merchant ship sits the naval auxiliary, and it is where the two worlds of this hub overlap most. A fleet replenishment tanker, a stores ship, or a hospital ship keeps a navy at sea but is often built closer to merchant standards, sometimes to commercial class with naval additions, and crewed by a civilian or mixed service rather than by uniformed sailors. The Royal Fleet Auxiliary (RFA) is the clearest example: a civilian-manned fleet that fuels, stores, and supports the Royal Navy and operates under naval command on government service, carrying the sovereign immunity of a government non-commercial ship without being a warship under Article 29.

The auxiliary marks the civil-military interface that runs through the whole naval world. A navy does not operate in a sealed system; it buys ships built in commercial yards, classes many of them with the same societies that class merchant fleets, charters merchant tonnage for sealift, and relies on the civil SAR organization for rescue coordination. The interface also runs the other way, since a warship’s Article 98 duty to assist puts it into the civil SAR system as a rescue unit, and a naval task force in a high-risk area protects the merchant trade the maritime security and risk world is built around. The auxiliary is the hull that physically straddles the line, built like a merchant ship, crewed like a hybrid, and tasked like part of the fleet.

Where the two worlds meet

The two halves of this hub are run by different bodies and built to different rules, and three intersections matter. The duty to rescue is the first: UNCLOS Article 98 binds the warship and the merchant ship alike, so a destroyer is no more free to pass a person in distress than a container ship is, and the duty continues even in armed conflict. The on-scene coordinator role is the second: a warship is often the most capable rescue unit in an area, with the speed, the boats, the medical facility, and the command structure to run a mass-rescue operation, so naval vessels are written into regional SAR plans as assets the coordination centers can task. Enforcement is the third: the warship is the only ship that may exercise the right of visit and act against piracy under UNCLOS, which puts naval vessels at the center of the counter-piracy and high-risk-area response.

This is why the subject is treated as one. A navy frigate in the Gulf of Aden in 2026 is at once a warship under Article 29, a rescue unit under Article 98, and an enforcement platform under the right-of-visit provisions, and it can be all three within a single watch: escorting merchant traffic, diverting to recover survivors from a foundering skiff, and boarding a suspected pirate vessel. The civil SAR world supplies the coordination, the naval world supplies the capability, and the law of the sea supplies the authority that lets one ship do all three.

A fourth thread runs under both worlds: the framework treaty that holds the definitions and the duty together. UNCLOS is not a SAR convention and not a naval rulebook, but it fixes both the Article 29 warship test and the Article 98 rescue duty in one instrument, and it sets the high-seas freedoms and the enforcement powers within which navies and coastguards operate. The detail sits in the UNCLOS overview for shipping; the point for this hub is that the same treaty that tells you what a warship is also tells you that the warship must rescue, which is why the legal layer ties the two cluster hubs together rather than separating them.

How the two cluster hubs fit together

The first cluster hub, search and rescue, carries the SAR world in full: the 1979 SAR Convention and the global SAR plan, the search and rescue regions and the Rescue Coordination Centers, the IAMSAR Manual in its three volumes, the SOLAS V/33 and UNCLOS Article 98 duty to assist, the GMDSS alerting layer, mass-rescue operations, and the on-scene coordinator. It is where the GMDSS overview, the SOLAS Chapter IV radio communications, the SOLAS Chapter III life-saving appliances, and the AIS-SART articles sit, and it links the GMDSS, EPIRB, SART, and SAR calculators.

The second, naval and defense vessels, carries the naval world: the UNCLOS Article 29 definition of a warship and the sovereign immunity that follows, the ship classes from corvette to destroyer to amphibious, the survivability and signature-reduction design drivers, the naval class rules of DNV, Lloyd’s Register, and ABS, the naval auxiliary and the RFA, and the civil-military interface. It is where the naval architecture coefficients and naval nuclear propulsion overview articles connect, and it links the naval-ships class and naval-auxiliary calculators.

The subject also sits beside the security side of the same portal, because a naval task force and a war-risk premium answer the same threat from two directions. A seizure in the Strait of Hormuz, a piracy attack off Somalia, or a drone strike in the Red Sea engages the warship as enforcer and rescuer at the same time the maritime security and risk world prices the risk and hardens the merchant ship, which ties this hub to the war risk and high-risk areas cluster and to the SUA Convention 1988, the treaty that makes acts of violence against shipping a crime states must prosecute once a navy makes the capture.

Limitations

This hub maps the SAR and naval worlds and the instruments that govern them; it is not the SAR Convention text, the IAMSAR Manual, UNCLOS, or any naval class rule set. The SAR Convention builds the coordination machinery and divides the ocean into 13 areas, but the operative documents for any one rescue are the national SAR plan, the RCC’s standing orders, and the IAMSAR Manual volumes in force, not the generic description here. The ship-level duty to assist is set by SOLAS V/33 and UNCLOS Article 98 read together, and the master’s judgment that assistance can be rendered without serious danger to the ship, the crew, or the passengers is a judgment this hub cannot make for any real case.

The naval side is described at the level of status and design principle, not at the level of any one navy’s classification or any one society’s rule edition. The UNCLOS Article 29 test for a warship is fixed treaty text, but how a given state applies it, and which ships it places on its service list, is a matter of national practice. The ship-class names used here, destroyer, frigate, corvette, OPV, amphibious, and auxiliary, are working categories whose tonnages and armament differ between fleets; the same name covers different ships. The naval class rules of DNV, Lloyd’s Register, and ABS are revised on their own cycles, so the controlling document for a given hull is the rule edition cited in its building contract, not the general description of naval classification given here.

The dates stated, the SAR Convention in force 22 June 1985, SOLAS 1974 in force 25 May 1980, UNCLOS in force 16 November 1994, and the GMDSS mandatory from 1 February 1999, are the entry-into-force or application dates of the instruments, not the date any individual ship, rescue center, or navy achieved compliance. None of the linked calculators replaces the carriage and equipment determination of a flag administration, the operational planning of a Rescue Coordination Center, or the design and class approval of a naval ship by the responsible society and navy.

See also

• Search and rescue: the SAR Convention 1979, the SRRs and RCCs, the IAMSAR Manual, the duty to assist, GMDSS, mass rescue, and the on-scene coordinator.
• Naval and defense vessels: the UNCLOS Article 29 warship test, sovereign immunity, the ship classes, survivability and signatures, naval class rules, and the naval auxiliary.
• GMDSS overview: the global maritime distress and safety system and the four sea areas.
• SOLAS Chapter IV radio communications and the GMDSS: the radio-carriage chapter behind the alerting layer.
• SOLAS Chapter III life-saving appliances and arrangements: the survival craft and rescue boats a ship carries.
• SOLAS Chapter V safety of navigation: the chapter carrying the V/33 duty to assist.
• AIS-SART search-and-rescue transmitter: the close-in homing device for survival craft.
• UNCLOS overview for shipping: the framework treaty holding the Article 29 and Article 98 provisions.
• Naval architecture coefficients: the hull-form relationships a warship shares with any ship.
• Naval nuclear propulsion overview: the reactor plants behind the largest warships.
• Maritime security and risk: the security side of the same portal, where the warship is the enforcer.
• War risk and high-risk areas: the chokepoints where naval task forces and war-risk cover meet.
• SUA Convention 1988: the treaty criminalizing unlawful acts against shipping.
• GMDSS sea-area coverage check: the A1 to A4 determination that drives radio carriage.
• EPIRB coverage check: the 406 MHz float-free EPIRB carriage check.
• Radio and EPIRB battery autonomy calculator: the reserve-source capacity check under SOLAS IV.
• SART radar transponder: the close-in radar homing for survival craft.
• IMO SAR 1979 calculator: the SAR Convention coverage logic.
• SOLAS V/33 distress-alert calculator: the duty to proceed and the distress-message handling.
• DNV naval-ships class calculator: the DNV Naval (NV) class notation.
• Naval auxiliary CII-exemption calculator: the regulatory carve-out for naval auxiliaries.