SOLAS 2026 Video Monitoring: Who Is Watching?

Nobody is required to, and that is deliberate. The 2026 SOLAS II-2/20 amendment requires an effective video monitoring system over vehicle, special category and ro-ro spaces — and ABS's summary of what MSC.550(108) adopted states it in one line: 'Continuous crew monitoring is not required.' The rule buys cameras and a recording. It does not buy a watchkeeper, and it does not buy detection.

That distinction is worth money at a newbuild specification meeting. An owner fitting cameras to clear a 2026 or 2028 survey can reasonably conclude the deck is now monitored. It is not. The cameras are there to answer a question the detection system has already asked — where is it? — and if they are bought as a substitute for detection rather than a layer beside it, the ship has spent capital and gained no warning time.

Does the rule even apply to your ship?

Only if it carries passengers. This is the single most misread part of the 2026 package, because the II-2/20 amendments as a whole touch both passenger and cargo ships while the video paragraphs do not. ABS Regulatory News 15/2025 tabulates it by ship type and construction date:

• Passenger ships constructed on or after 1 January 2026 — video monitoring required in vehicle, special category and ro-ro spaces, with immediate playback and recordings replayable at a continuously manned control station or safety centre for at least 7 days.
• Passenger ships constructed before 1 January 2026 — the same requirements, except replay capability of at least 24 hours, to be met no later than the first survey on or after 1 January 2028.
• Cargo ships constructed on or after 1 January 2026 — fixed fire detection and alarm requirements apply; there is no video monitoring row at all.
• Cargo ships constructed before 1 January 2026 — the requirements prior to MSC.550(108) remain applicable.
• A pure car and truck carrier is a cargo ship. Under this amendment it is required to fit no cameras on any date.

So the honest answer for a PCTC owner reading the 2026 headlines is that the video requirement is not theirs — yet. The corpus covers where the car-carrier package actually sits (interim guidelines first, SOLAS text no earlier than 2032) in the companion posts on II-2/20 and the compliance calendar.

What 'continuous monitoring' means when nobody has to watch

It describes the coverage, not the attention. IMO's own wording asks for a system 'for continuous monitoring of these spaces, to allow for quick identification of a fire, with cameras to be installed to cover the whole space, high enough to see over cargo and vehicles after loading'. Read the purpose clause rather than the adjective: the cameras run continuously so that when something else raises the alarm, the picture of the right space already exists and can be played back immediately. Continuous is a property of the feed and the recording, not a duty roster.

The drafters were right to write it that way. A crossing spent watching a bank of dark, static deck feeds is a fatigue task with a well-documented failure rate — vigilance decrements set in within roughly half an hour of monitoring a display for rare events, which is why no serious safety regime relies on a human staring at an unchanging picture. A rule that demanded continuous crew observation would have produced a fiction on the certificate and nothing on the deck.

Why a camera is not a fire detector

Because it can only report what is already visible, and by then the useful minutes are gone. A smoke detector responds to particulate reaching the sensor; a camera responds to a change a human or an algorithm can recognise in an image. On an enclosed vehicle deck those are not the same event, and the ordering is unfavourable: an electrical fault under a vehicle produces heat, then vapour, then smoke thick enough to register visually against a dim deck, then flame. A camera enters the story late.

There is a documented case of exactly this. On Commodore Clipper in June 2010, CCTV camera 7 on the port side of the main vehicle deck began to haze at 02:37 and the deck lighting visibly diffused. The first smoke detector did not alarm until 02:42:36. The picture had the fire five minutes before the detection system did — and it made no difference, because a hazy image is not an alarm: the officer of the watch looked at the CCTV, saw no fire, and read the haze as a fault with the picture. By 02:54 the cameras had lost all visibility to smoke. A camera that nobody is required to watch, showing a change nobody is trained to read as fire, delivered exactly nothing.

What the camera is genuinely good for

Two things, and both are valuable if specified for the purpose. The first is localisation: turning a zone alarm into a valve number. The amendment requires that the correspondence between each camera and the fire-extinguishing system sections be clearly displayed near the video monitor, which tells you precisely what the drafters had in mind — a detector says 'section 4', the crew pulls up the camera covering section 4, confirms what is burning and where, and opens the right drencher section without sending anyone onto the deck. That is a genuine reduction in response time and in risk to the crew, and it is the strongest argument for the system.

The second is evidence. Seven days of retained recording on a new ship is long enough to survive a voyage and reach an investigator; 24 hours on an existing one is long enough to survive the incident itself. The value of that is not abstract: the Stuttgart court dismissed the Felicity Ace claim in May 2026 because nobody could prove which vehicle ignited, and the ship's detection had recorded a zone rather than a vehicle. A retained deck recording is one of the few artefacts that can answer an origin question after the hull is gone — provided it is exported off the ship rather than sitting on a recorder that goes down with it.

How to specify it so the money does something

Buy it as a localisation and evidence layer, and keep detection as detection. Three things separate a compliant installation from a useful one. Coverage is planned against the loaded stow plan, not the general arrangement — 'high enough to see over cargo and vehicles after loading' is a constraint set by the tallest cargo the deck is certified to carry, which means a camera count validated against a real loading condition rather than an empty deck. The camera-to-section mapping is displayed where the decision is made, not buried in a manual. And the recording is treated as an evidence chain: retention period, export path, and who can retrieve it after a casualty.

For the owner, the position that survives both a survey and an underwriter's questionnaire is the one that states the layers separately: fixed detection to generate the alarm, video to confirm and locate it, suppression to act on it. For the PCTC owner with no video obligation at all, the useful reading of this amendment is as a preview — what the passenger fleet is fitting in 2026 to 2028 is a fair guide to what the vehicle-carrier package will ask for when it arrives, and to what a charterer or insurer may ask for well before that.

Sources

• 1. IMO — 'Raft of shipping rules in force from 1 January 2026' (press briefing): the amendments require 'an effective video monitoring system in vehicle, special category and ro-ro spaces for continuous monitoring of these spaces, to allow for quick identification of a fire, with cameras to be installed to cover the whole space, high enough to see over cargo and vehicles after loading', alongside separate requirements for a fixed fire detection and fire alarm system. Resolution MSC.550(108), Amendments to Chapters II-2 and V of SOLAS.
• 2. ABS Regulatory News No. 15/2025 (December 2025), 'Fire Safety Requirements for Ro-Ro Passenger and Cargo Ships', read in full: the application table by ship type and construction date. Passenger ships on/after 1 Jan 2026 — video monitoring with immediate playback, recordings replayable at a continuously manned control station or safety centre for at least 7 days, camera-to-fire-extinguishing-system section correspondence clearly displayed near the video monitor, and 'Continuous crew monitoring is not required.' Passenger ships before 1 Jan 2026 — same requirements except replay capability of at least 24 hours, by the first survey on or after 1 Jan 2028. Cargo ships on/after 1 Jan 2026 — fire detection and alarm requirements only, no video monitoring row. Cargo ships before 1 Jan 2026 — pre-amendment requirements remain applicable. References MSC.550(108), MSC.555(108), IACS UI SC 73 and SC160, MSC.1/Circ.1456/Rev.1, MSC.1/Circ.1615.
• 3. Lloyd's Register — Class News 07/2026 (1 April 2026), 'SOLAS amendments: Fire Safety Requirements for ro-ro Passenger Ships', covering MSC.550(108) and MSC.555(108): the II-2/20 amendments apply to cargo ships and ro-ro passenger ships constructed (keel laid) on or after 1 January 2026; existing ro-ro passenger ships comply not later than the first survey on or after 1 January 2028; paragraphs 4.4.1 and 4.4.2 require that 'an effective video monitoring and recording system shall be arranged in vehicle, special category and ro-ro spaces for continuous monitoring of these spaces'.
• 4. MAIB Report No 24/2011 — fire on the main vehicle deck of Commodore Clipper, 16 June 2010: CCTV camera 7 hazing from 02:37 with the deck lighting visibly diffusing; first smoke-detector alarm at 02:42:36; the officer of the watch viewing the CCTV and seeing no indication of fire; all camera visibility lost by 02:54.
• 5. Companion RoRoSAFE analyses — 'What Does SOLAS 2026 Video Monitoring Require?' (the clause-by-clause engineering read and what to specify), 'What Does SOLAS II-2/20 Ask of a Car Carrier?', 'Does the 2026 SOLAS Rule Reach Old Ships?', 'Does Car-Carrier Fire Compliance Arrive in 2027?' and the Commodore Clipper incident anatomy.