Individually Identifiable Detection: What SOLAS Now Requires

From 1 January 2026, new vehicle carriers must fit fire detection that identifies the individual detector in alarm — not just the zone it sits in. SOLAS Chapter II-2 Regulation 20, as amended by IMO Resolution MSC.550(108), moves vehicle-deck detection from zone-level to individually identifiable smoke and heat detectors. Existing vehicle carriers follow no later than the first survey on or after 1 January 2028. [VERIFY: exact 'individually identifiable' wording and the 2028 existing-ship survey trigger against the MSC.550(108) primary text.]

What 'individually identifiable' actually requires

The requirement is that the system resolve which specific detector is in alarm, rather than reporting only the section or loop. A zone-addressed system tells the bridge that something is happening somewhere on a deck that may hold several hundred vehicles. An individually identifiable system points to a single detector position. On a car deck where finding the source fast is the entire problem, that distinction is the difference between a search and a location.

Why the zone model kept failing

Zone detection tells crew a deck, not a vehicle — and on a fully-laden car carrier that gap is decisive. In the Fremantle Highway fire of July 2023, investigators found the crew did not even know where the battery-electric vehicles were stowed, on a ship loading 3,783 vehicles including 498 BEVs. Felicity Ace, lost in 2022 with an estimated cargo value above $400 million, made the same point: by the time a zone alarm is acted on, an enclosed-deck fire has often moved past the point of containment.

What it means for detection design

Individual identifiability pushes detection toward finer spatial granularity — at the limit, resolution approaching one detector per vehicle position. A system already built around per-vehicle sensing meets the intent natively, because every cell is its own addressable point reporting its own state. The harder retrofits are zone-loop systems that have to be re-engineered to report at detector level before the 2028 survey. The regulation does not mandate a technology; it mandates a reporting resolution, and the cheapest way to satisfy it is to have started from individual points.

What it means for owners and class

For owners of existing vehicle carriers, the 2028 first-survey trigger is the planning date — a detector-level reporting capability has to be demonstrable to the attending surveyor, not promised. The same amendment package (MSC.555(108) on the FSS Code, plus the PFOS firefighting-foam prohibition under SOLAS II-2) means the detection upgrade rarely lands alone. The owners least exposed are those whose detection is already individually addressable; the requirement formalises what early detection was always trying to do — point at the vehicle, not the deck.

Sources

• 1. SOLAS II-2/20 amendments, IMO Resolution MSC.550(108), adopted MSC 108 (May 2024); new vehicle carriers from 1 Jan 2026, existing by first survey on/after 1 Jan 2028 — classification-society regulatory guidance (ABS, DNV, Lloyd's Register). [VERIFY: exact detector-identifiability wording and survey trigger]
• 2. FSS Code amendments, IMO Resolution MSC.555(108); PFOS firefighting-foam prohibition under SOLAS II-2 — IMO, classification-society guidance
• 3. MSC 110 (18–27 June 2025) agreed to consider further revision of SOLAS II-2/20 and FSS Code Chapter 7 on fixed fire-extinguishing systems — imo.org, dnv.com
• 4. Casualty context — Fremantle Highway (3,783 vehicles / 498 BEVs, crew unaware of EV stowage, 2023) and Felicity Ace (~$400M cargo, 2022) — Dutch Safety Board/EMSA, commercial.allianz.com, gcaptain.com