BNWAS: Bridge Navigational Watch Alarm System

BNWAS carriage under SOLAS V/19.2.2.3: ships covered, phase-in dates to 2018, the 3 to 12 minute dormant period, MSC.128(75) alarm stages and IEC 62616 testing.

Contents16 sections

The Bridge Navigational Watch Alarm System (BNWAS) is a timer-driven alarm that checks the officer of the watch (OOW) is still awake and on the bridge, and calls the master or a back-up officer when the OOW stops responding. It is carried under SOLAS regulation V/19 paragraph 2.2.3 on cargo ships of 150 GT and upwards and on passenger ships irrespective of size, and it must run whenever the ship is underway at sea. The carriage rule was inserted by resolution MSC.282(86) of 5 June 2009 and has been in force since 1 January 2011.

The equipment itself is specified in MSC.128(75), adopted on 20 May 2002: a dormant period of 3 to 12 minutes, a flashing bridge indication, then three audible stages that reach the master’s cabin 30 seconds after the dormant period ends. Units are tested to IEC 62616:2010. The UK Marine Accident Investigation Branch counted 81 collision, grounding and contact investigations after the 2009 mandate, 20 of which involved a sole watchkeeper at night or in restricted visibility and/or a disabled BNWAS (safety flyer, 30 November 2023).

Definition and purpose

A BNWAS monitors OOW awareness and automatically alerts the master or another qualified OOW if the watchkeeper becomes incapable of performing the watch. That is the scope statement in paragraph 1 of the annex to MSC.128(75). The preamble names the failures it is meant to catch: incapacity of the watchkeeping officer through accident or sickness, and a security breach such as piracy or hijacking.

The device has no sensor for alertness itself. It runs a countdown, and the OOW proves presence by pressing a reset or by moving within view of a motion detector. Any reset restarts the full countdown. If the countdown expires, the system escalates from the bridge to the cabins in fixed steps.

That design defines what the system can and cannot see. It detects an OOW who is asleep, collapsed, absent or restrained. It does not detect an OOW who is awake, resetting on schedule and navigating badly, which is the gap the MV Wakashio grounding of 25 July 2020 sits in (see the casualty section below).

On the bridge the BNWAS is one item among the integrated bridge systems carried under V/19. Its engine-room counterpart is the engineer’s dead-man alarm used for unattended machinery spaces, described under engine-room automation and monitoring; the two share the timed-reset principle and nothing else in their regulatory basis.

Development of the requirement, 2002 to 2015

The BNWAS existed as an IMO equipment standard for seven years before any ship was obliged to carry one. The sequence, from the documents cited in this article:

DateInstrument or eventEffect
20 May 2002MSC.128(75), prepared by NAV 47Performance standard; Governments asked to apply it to systems installed on or after 1 July 2003
2004MAIB Bridge Watchkeeping Safety StudyFound two-watchkeeper manning inadequate on many short-sea ships
5 June 2009MSC.282(86) adopted at MSC 86Inserts V/19.2.2.3: carriage on cargo ships of 150 GT and upwards and all passenger ships
2 December 2009A.1021(26)Classes the second and third stage remote alarms as emergency alarms
1 January 2011MSC.282(86) in forceNew ships from 1 July 2011; existing ships 2012 to 2014
14 January 2013US Coast Guard notice, 78 FR 2683States carriage on US-flag ships is voluntary under US law
21 June 2013MSC.350(92) adoptedInserts V/19.1.2.4 for ships constructed before 1 July 2002
23 May 2014MSC.1/Circ.1474 approved at MSC 93Automatic mode not to be used, pending revision of MSC.128(75)
1 January 2015MSC.350(92) in forcePre-2002 ships fitted by surveys in 2016 to 2018
3 December 2025A.1204(34)Code on Alerts and Indicators, 2025, revokes A.1021(26); defines the BNWAS alarm in paragraph 3.3.8 by reference to MSC.128(75)

The 2002 standard came first and the carriage rule second, which is the source of the Automatic-mode conflict covered below. The MAIB later dated the mandate from June 2009, the month MSC.282(86) was adopted, though no ship had to carry the system until the 2011 entry-into-force dates bit.

Carriage requirement under SOLAS V/19.2.2.3

SOLAS regulation V/19.2.2.3 requires a BNWAS on cargo ships of 150 GT and upwards and on passenger ships irrespective of size, and states that the system “shall be in operation whenever the ship is underway at sea”. The paragraph sits in the V/19.2.2 tier of the carriage table, alongside the spare magnetic compass and the daylight signalling lamp, and was inserted into the SOLAS Convention by MSC.282(86).

MSC.282(86) was adopted by the Maritime Safety Committee on 5 June 2009, deemed accepted on 1 July 2010 and entered into force on 1 January 2011. The same resolution introduced the ECDIS carriage requirement in V/19.2.10, which is why the two phase-in tables are often read together.

Ships covered

The thresholds are gross tonnage and ship type, not length or trade:

  • Passenger ships: every size, from the smallest SOLAS passenger ship upwards.
  • Cargo ships: 150 GT and upwards. Tankers, bulk carriers, container ships, general cargo ships and gas carriers are all cargo ships for this purpose.
  • Self-propelled mobile offshore units are brought in by flags that apply chapter V to them; the Marshall Islands states this in a footnote to Marine Notice 2-011-40.

SOLAS chapter V applies to all ships on all voyages under V/1.1, except government ships on non-commercial service and ships navigating only the Great Lakes. V/1.4 then lets the Administration decide how far regulations V/15 to V/28 apply to ships below 150 GT, ships below 500 GT not on international voyages, and fishing vessels. A BNWAS on a fishing vessel or a small domestic ship is therefore a flag state decision, not a SOLAS one.

Phase-in for ships constructed before 1 July 2011

V/19.2.2.3 set compliance dates by ship type and size. Ships constructed on or after 1 July 2011 had to carry the system from delivery; existing ships complied by their first survey after a fixed date:

Ship categoryConstructedCompliance
Cargo ships 150 GT and upwards, passenger shipsOn or after 1 July 2011From delivery
Passenger shipsBefore 1 July 2011First survey after 1 July 2012
Cargo ships 3,000 GT and upwardsBefore 1 July 2011First survey after 1 July 2012
Cargo ships 500 GT to less than 3,000 GTBefore 1 July 2011First survey after 1 July 2013
Cargo ships 150 GT to less than 500 GTBefore 1 July 2011First survey after 1 July 2014

The survey is the one recorded against the ship’s safety equipment or passenger ship safety certificate, so the real compliance date differed ship by ship within each band. MSC.282(86) also added the BNWAS to the Records of Equipment, Form E for cargo ships and Form P for passenger ships, which is where a surveyor or port state control officer looks for it. Under MSC.1/Circ.1290, cited by the US Coast Guard in 78 FR 2683, a ship whose keel was laid before a compliance date but which was delivered after it meets the requirement at its initial survey. SOLAS chapter I governs those surveys and certificates.

Ships constructed before 1 July 2002: V/19.1.2.4

A second tier exists because the 2009 text did not reach ships built before the 2000 revision of chapter V. Resolution MSC.350(92), adopted on 21 June 2013, deemed accepted on 1 July 2014 and in force from 1 January 2015, inserted V/19.1.2.4 to cover ships constructed before 1 July 2002:

Ship category, constructed before 1 July 2002Compliance
Passenger shipsFirst survey after 1 January 2016
Cargo ships 3,000 GT and upwardsFirst survey after 1 January 2016
Cargo ships 500 GT to less than 3,000 GTFirst survey after 1 January 2017
Cargo ships 150 GT to less than 500 GTFirst survey after 1 January 2018

The full BNWAS phase-in therefore ran to 2018, not 2014. V/19.1.3 lets the Administration exempt a ship that will be taken permanently out of service within two years of its compliance date. Fitting dates are now history for every ship in service; the tables matter in 2026 mainly when reading an older survey record or a casualty report from the transition years.

Equipment installed before 1 July 2011

V/19.2.2.4 lets the Administration exempt a BNWAS installed before 1 July 2011 from full compliance with the IMO performance standard. The flags publish their own acceptance criteria. The Isle of Man’s MSN 061 (1 August 2018) accepts, for example, an automatic function wired so that the BNWAS runs whenever the ship is underway, and requires the malfunction indication and emergency call to be powered from main and emergency supplies. The Marshall Islands, in Marine Notice 2-011-40 Rev. 3/15, accepts pre-2011 units on the recommendation of the classification society if they were manufactured for marine service and sound in the wheelhouse and bridge wings.

High-speed craft

A craft certified and surveyed under the High-Speed Craft Code is outside V/19.2.2.3. Regulation X/3.1 of SOLAS chapter X deems a craft built, surveyed and certified under the Code to comply with regulations V/18, V/19 and V/20, so its navigation equipment is set by the Code instead. The Isle of Man’s MSN 061 puts it directly: craft certified under the HSC Code are the only exception to the V/19.2.2.3 requirement on commercial ships over 150 GT, a group it states includes yachts. A flag may still require a BNWAS on a high-speed craft under national rules.

The performance standard: MSC.128(75)

Resolution MSC.128(75), adopted on 20 May 2002 on the work of the NAV Sub-Committee’s 47th session, is the IMO performance standard for a BNWAS. Operative paragraph 2 recommends that Governments ensure systems installed on or after 1 July 2003 conform to it. SOLAS V/18 makes equipment carried under V/19 conform to performance standards not inferior to those adopted by the IMO, which is how a recommendatory resolution becomes binding on a ship that must carry the device.

MSC.128(75) has not been replaced. A revision was flagged as pending in 2014, and Regulation (EU) 2025/1533, which sets the current EU marine equipment list, still cites MSC.128(75) together with MSC.1/Circ.1474 as the performance requirements for item MED/4.57. Resolution MSC.355(92), cited in some secondary sources as a BNWAS revision, is a set of amendments to the International Convention for Safe Containers, 1972, adopted on 21 June 2013, and does not deal with the BNWAS.

Scope and the conflict with V/19.2.2.3

The 2002 standard was written before the 2009 carriage rule, and the two disagree on when the system runs. Annex paragraph 1 says the BNWAS should be operational whenever the ship’s heading or track control system is engaged, unless inhibited by the master. V/19.2.2.3, written seven years later, says it shall be in operation whenever the ship is underway at sea. The treaty text governs.

The practical consequence is the Automatic mode problem described next. Annex paragraph 3 also fixes a definition that matters for reset siting: “Bridge” means the wheelhouse and bridge wings.

Operating modes and MSC.1/Circ.1474

Paragraph 4.1.1.1 of MSC.128(75) gives three modes:

  • Automatic: brought into operation whenever the ship’s heading or track control system is activated, and inhibited when it is not.
  • Manual ON: in operation constantly.
  • Manual OFF: does not operate under any circumstances.

Automatic mode ties the BNWAS to the autopilot. When the OOW switches to hand steering, the alarm stops, though the ship is still underway at sea. The NAV Sub-Committee concluded at its 55th session that Automatic mode was therefore not usable on a ship complying with SOLAS. MSC.1/Circ.1474, issued on 23 May 2014 following MSC 93, states that “as an interim measure and pending a revision of the Performance standards” in MSC.128(75), “the automatic operational mode, if it is available, should not be used”. The circular quotes the note to clause 3.1.1 of IEC 62616:2010, which says the same.

Equipment still offers the Automatic position so it can conform to the 2002 standard. The selection is a shipboard procedure. The Marshall Islands requires the safety management system to address when each mode is used and states that Automatic mode shall not be utilized; the Isle of Man adopts Circ.1474 in MSN 061.

Dormant period

The dormant period, written Td in the standard, is the interval between the last reset and the first indication. Paragraph 4.1.2.1 sets it as adjustable between 3 and 12 minutes. Paragraph 4.3 requires both the mode selector and the Td setting to be security protected so that access is restricted to the master only.

The standard gives no rule for choosing a value inside that range. A 12-minute Td leaves an incapacitated OOW undetected for 12 minutes 30 seconds before anyone else is called; a 3-minute Td cuts that to 3 minutes 30 seconds at the price of four times as many resets per hour. A ship in a traffic separation scheme at night and a ship in open ocean in daylight have different answers, and the safety management system is the place to write them down.

Reset load across a watch

The dormant period fixes the minimum number of resets an OOW makes, and that number explains much of the tampering the MAIB found. On a four-hour watch with a 12-minute Td, an OOW who never moves within range of a sensor presses the reset at least 20 times. At 6 minutes the figure is 40; at 3 minutes it is 80, one press every three minutes for four hours.

A system that integrates motion sensors or reset inputs from other bridge equipment under paragraph 4.1.3.3 reduces the deliberate presses, because normal work at the radar or ECDIS restarts the timer. The same paragraph is what makes siting decisive. Lysblink Seaways carried a separate radar watch alarm that sounded every 6 minutes and the OOW was able to reset without leaving the chair. The MAIB’s 2023 flyer lists crews regarding the alarm as a nuisance and older units needing manual resets among the recurring factors in BNWAS-related casualties.

Alarm sequence

Paragraph 4.1.2 sets the sequence. The figure in the annex gives the times as Td, Td + 0.25 minutes, Td + 0.5 minutes and Td + 2.0 minutes:

StageTriggerWhere it sounds or showsElapsed from the last reset
Visual indicationEnd of the dormant periodOn the bridge, flashingTd
First-stage audible alarm15 s after the visual indicationOn the bridgeTd + 15 s
Second-stage remote audible alarm15 s after the first stageBack-up officer’s and/or master’s locationTd + 30 s
Third-stage remote audible alarm90 s after the second stageLocations of further crew able to take corrective actionTd + 2 min

Two variations are permitted. On ships other than passenger ships, paragraph 4.1.2.6 lets the second and third stages sound in all locations at the same time, in which case the third stage may be omitted. On larger vessels, paragraph 4.1.2.7 allows the delay between second and third stage to be set at installation up to 3 minutes, to give the back-up officer time to reach the bridge.

Timings must be accurate to 5% or 5 seconds, whichever is less, under all environmental conditions (paragraph 4.2). A 12-minute Td thus has a tolerance of 5 seconds, not 36.

Reset devices and where they go

Reset is the half of the standard that casualty reports most often show being defeated, and the rules are specific:

  1. Reset or cancellation is not possible from any device, equipment or system “not physically located in areas of the bridge providing proper look out” (4.1.3.1).
  2. A single operator action cancels the visual indication and all audible alarms and starts a new dormant period; a reset during the dormant period restarts it in full (4.1.3.2).
  3. The input may come from an integral reset device or from external equipment “capable of registering physical activity and mental alertness of the OOW” (4.1.3.3).
  4. A continuous activation of any reset device should not prolong the dormant period or suppress the sequence (4.1.3.4), so a taped-down button does not work.

Paragraph 5.1.4 lists where reset devices should be reachable from: the conning position, the workstation for navigating and manoeuvring, the workstation for monitoring, and the bridge wings. A chartroom is not on that list, and a chartroom with no view ahead is excluded by 4.1.3.1. Reset devices are to be of uniform design, illuminated for identification at night, and arranged to minimize operation by anyone other than the OOW (6.2.2).

Motion detectors are the main flag-level variation. The Isle of Man accepts passive infrared detectors as a reset under 4.1.3.3. The Marshall Islands limits sensed areas to forward of the bridge curtains, excludes bridge chairs unless the chair is integral to the primary conning position (a cockpit-style console), bars curtains whose movement could trigger a reset, and requires motion-sensor systems to be checked at least once a day.

Emergency call

Paragraph 4.1.4 allows, but does not require, an Emergency Call push button on the bridge that immediately activates the second-stage and then the third-stage remote alarms. It gives the OOW a way to call the master without leaving the conning position or waiting for the timer. The component is powered from a battery-maintained supply under paragraph 6.3, as is the malfunction indication.

Indications, power and tamper resistance

The visual indication “should take the form of a flashing indication”, in a colour that does not impair night vision and dimmable “although not to extinction” (5.2.2). The first-stage bridge tone is “intended to alert, but not to startle” (5.2.3). The remote alarm must be identifiable by its sound, indicate urgency and be loud enough “to wake sleeping persons” (5.2.4). The standard specifies no colour and no decibel level.

The rest of the build requirements are short:

  • General requirements: A.694(17) on shipborne radio and navigational equipment, A.813(19) on electromagnetic compatibility, IEC 60945 and MSC/Circ.982 on bridge ergonomics (6.1).
  • Tamper resistance: the system is to be “tamper-proof so that no member of the crew may interfere” with it (6.2.1).
  • Power: ship’s main supply, with the malfunction indication and Emergency Call on a battery-maintained supply (6.3).
  • Failure indication: a malfunction or power-supply failure is to be indicated, repeated on the central alarm panel where one is fitted (4.4.1).
  • Interfaces: inputs for additional reset devices or bridge equipment by contacts, equivalent circuits or serial data to IEC 61162, and outputs for additional indications and remote alarms (7.1 and 7.2).

Alert classification and bridge alert management

The Code on Alerts and Indicators, adopted as resolution A.1021(26) on 2 December 2009, classifies the BNWAS outputs. Paragraph 3.2.8 lists the second and third stage remote audible alarms as emergency alarms, the highest of the Code’s alert priorities, although the Code’s own location tables list the same stages at alarm priority. Table 10.1.1 for the navigation bridge treats the end of the dormant period as an indicator, the first-stage audible alarm as an alarm, and a BNWAS malfunction or power failure as a warning. The Code on Alerts and Indicators also says, in paragraph 8.2, that the BNWAS should conform to MSC.128(75). Those paragraph and table numbers are from the 2009 text. The IMO Assembly replaced it with the Code on Alerts and Indicators, 2025, resolution A.1204(34), adopted on 3 December 2025, whose operative paragraph 4 revokes A.1021(26); the 2025 Code defines the BNWAS alarm in paragraph 3.3.8 by reference to MSC.128(75).

Bridge Alert Management under MSC.302(87) of 17 May 2010 names the BNWAS only in its documentation clause. It sets no BNWAS timing or priority. The EU equipment list nonetheless cites MSC.302(87) and the BAM interface standards IEC 62923-1 and IEC 62923-2 against MED/4.57, so a BNWAS approved for the EU market is expected to interface with a BAM-compliant bridge, including an integrated navigation system where one is fitted.

The voyage data recorder is the evidential link. MSC.333(90) of 22 May 2012 requires the status of all mandatory bridge alarms to be recorded as individually identified alarms (paragraph 5.5.10). The MAIB’s 2023 flyer found that VDRs on the ships it had investigated did not log BNWAS status, which left investigators unable to say when a system had been switched off. The Marshall Islands now requires the link where the BNWAS was installed on or after 1 July 2011 and the VDR on or after 1 July 2014.

Type approval and test standards

IEC 62616:2010 is the BNWAS test standard. Edition 1.0 was published by IEC Technical Committee 80 on 11 February 2010, a corrigendum followed in July 2012, and no second edition has been issued. It sets minimum performance, technical characteristics, test methods and required results for a BNWAS as required by SOLAS chapter V, and is read with IEC 60945:2002, edition 4.0 of 14 August 2002 (corrigendum 1, 2008), for environmental, EMC and general tests.

Approval of the equipment is a flag function under SOLAS V/18.1, exercised by the Administration or a body acting for it. Three common routes:

  • European Union: item MED/4.57 under the Marine Equipment Directive 2014/90/EU. The current list is Commission Implementing Regulation (EU) 2025/1533 of 23 July 2025, in force 23 September 2025. It cites IEC 62616:2010 including its 2012 corrigendum, IEC 60945:2002, the IEC 61162 interface series, IEC 62288 for display presentation and IEC 62923-1 and -2 for BAM; conformity modules B+D, B+E, B+F or G apply.
  • Class and flag type approval: certificates issued by classification societies acting as recognized organizations for flags that delegate equipment approval.
  • United States: under 78 FR 2683 the Coast Guard or a recognized classification society assesses a BNWAS against MSC.128(75); operators seeking acceptance of a unit installed before 1 July 2011 submit a gap analysis against MSC.128(75) to the Commercial Vessel Compliance Division (CG-CVC-1).

A unit tested to IEC 62616 has passed a specific bench sequence. Whether it is installed so that every reset sits in a lookout position, and whether the cabin alarms reach the right cabins, is a survey question for the flag or its RO, not a type-approval one.

Flag-state overlays

The IMO text is the baseline. Several flags add detail that a master on those registers must follow. Three published positions:

FlagInstrumentWhat it adds
Isle of ManMSN 061, 1 August 2018Passive infrared detectors accepted as reset; adopts MSC.1/Circ.1474; acceptance criteria for pre-2011 units; HSC Code craft the only exception; applies to yachts over 150 GT
Marshall IslandsMarine Notice 2-011-40 Rev. 3/15Motion sensors forward of curtains only, chairs excluded unless integral to the conning position; daily check of motion sensors; SMS to set mode use, Automatic mode not used; BNWAS to VDR link for post-2011 BNWAS with post-2014 VDR; at sea means underway outside pilotage waters
United States78 FR 2683, 14 January 2013, Docket USCG-2012-0772No domestic regulations adopted, so carriage on US-flag vessels is voluntary under US law; warns that a ship on international voyages without BNWAS past its date may be detained abroad

The US position is the one most often misread. The Federal Register notice states that the Coast Guard “has not yet adopted domestic regulations to implement the SOLAS BNWAS requirements” and that carriage “is voluntary”, then warns that a vessel on international voyages without one “may be subject to detention by foreign port state officials”. A US-flag ship trading internationally is therefore exposed abroad even where US law does not compel the fitting.

BNWAS and the lookout

A BNWAS does not satisfy the lookout obligation, and nothing in MSC.128(75) suggests it does. COLREG Rule 5 requires every vessel at all times to maintain a proper lookout by sight and hearing as well as by all available means appropriate to the circumstances. Under the COLREGs that is a duty about seeing the situation; the BNWAS only proves that someone pressed a button.

STCW Code section A-VIII/2 allows the OOW to be the sole lookout in daylight only, after the situation has been carefully assessed for the weather, visibility, traffic density, proximity of dangers and attention needed for traffic separation schemes, and with assistance immediately available. The UK Maritime and Coastguard Agency’s MGN 315 describes the OOW acting as sole lookout in darkness or restricted visibility as dangerous and irresponsible. The MAIB flyer of November 2023 refers to “the international requirements to post a dedicated lookout during the hours of darkness and to operate a BNWAS” as two separate obligations.

The IMO stated the same separation when the carriage rule was drafted. The US Coast Guard’s 2013 notice quotes the NAV Sub-Committee’s report NAV 54/25 of 14 August 2008: carriage of a BNWAS “should not lead to a reduction in manning levels on the bridge”, and the Coast Guard does not expect to grant exemptions from the BNWAS on the strength of multiple bridge watch personnel alone.

The two safeguards fail together in the casualty record. In every one of the three MAIB groundings described below, the bridge had no lookout and the BNWAS was off.

Fatigue and rest hours

The BNWAS is a backstop for seafarer fatigue, not a control on it. STCW section A-VIII/1 requires watchkeepers to have at least 10 hours of rest in any 24-hour period and 77 hours in any 7-day period. Standard A2.3 of MLC 2006 lets the flag set either those minimum hours of rest or maximum hours of work of 14 hours in 24 and 72 hours in 7 days. The manning that makes those hours achievable is fixed in the minimum safe manning document under SOLAS V/14.

The MAIB’s 2004 Bridge Watchkeeping Safety Study found that two watchkeepers were “not enough to operate sea-going vessels safely”, especially on a 6-hours-on, 6-hours-off pattern disrupted by port calls. In the Danio report of 2 April 2014 the Chief Inspector recorded nine further groundings of ships with two watchkeepers since that study, and stated that the barriers mandated against cumulative fatigue in the short-sea sector were not working.

Port state control

The BNWAS is inspected as part of the Safety of Navigation group in port state control. Its deficiency code is 10138, “Bridge Navigational Watch Alarm System (BNWAS)”, in the Paris MoU code list held in the THETIS database; the Australian Maritime Safety Authority, which inspects under the Tokyo MoU, lists the same code.

A port state control officer checking a BNWAS is looking at installation and operation against V/19.2.2.3 and MSC.128(75): whether the system is on at sea, whether resets sit in lookout positions, whether the second-stage alarm reaches the master’s or back-up officer’s location, and whether the mode and Td controls are restricted to the master. A defective or switched-off BNWAS on a ship that must carry one is a SOLAS non-compliance. Whether it leads to detention is the officer’s professional judgement under the regime’s procedures.

Casualty record

Three MAIB groundings show the pattern the BNWAS was introduced to stop, each with the system switched off:

ShipMAIB reportDate and placeBNWAS finding
Danio, general cargo8/2014, published 2 April 20140330, 16 March 2013, Longstone, Farne IslandsChief officer asleep on watch for more than 3 hours; no lookout posted; bridge watch alarm turned off
Lysblink Seaways, general cargo25/2015, published 19 November 201518 February 2015, near Kilchoan, ArdnamurchanSole watchkeeper inattentive from alcohol; BNWAS not switched on; ECS off-track alarm silenced
BBC Marmara, general cargo8/2023, published 30 November 20230332, 25 July 2021, Eilean Trodday, Little MinchWatchkeeper asleep after drinking; lookout, BNWAS and coastguard safeguards removed

Lysblink Seaways ran aground at full speed, stayed on the foreshore for almost two days, lost about 25 tonnes of marine gas oil from breached tanks and was declared a constructive total loss. The Marine Accident Investigation Branch concluded that, had the BNWAS been switched on, the OOW would probably have realized at an earlier stage that a waypoint had been missed. The ship also had a radar watch alarm sounding every 6 minutes, which the OOW was able to reset without leaving the chair: a device built like a BNWAS but sited so that it tested nothing.

The BBC Marmara report and its companion flyer widened the point from one ship to the fleet. Of 81 MAIB investigations of collisions, groundings and contacts after the 2009 mandate, 20 involved sole watchkeepers at night or in restricted visibility and/or a disabled BNWAS. The common factors the flyer lists include crews treating the alarm as a nuisance, older units that needed manual resetting, keys or codes kept on the bridge, and VDRs that did not record BNWAS status.

The limit of the device: MV Wakashio

The Wakashio grounding off south-east Mauritius on 25 July 2020 turned on decisions, not on an absent watchkeeper. The Japan Transport Safety Board’s report MA2023-10 found that the master had ordered the offing cut from about 22 to about 5 nautical miles to obtain a smartphone signal, on an electronic chart displayed overscale. From 18:00 the deck cadet was told not to come to the bridge and the chief officer kept the watch alone, contrary to the company’s procedures. None of the cited reports addresses the ship’s BNWAS.

On this site’s reading, the case marks the device’s boundary. A timer that confirms an OOW is pressing buttons has nothing to say about where the ship is being taken, and the Wakashio bridge had a sole watchkeeper at night, the same configuration the MAIB cases show. That is why the BNWAS is one layer of bridge safety alongside Bridge Resource Management, passage planning under SOLAS V/34, and the master’s standing orders, and not a substitute for any of them.

Shipboard procedures

The IMO texts leave several decisions to the company and the master, and casualty reports show where those decisions go wrong. A workable procedure in the ISM Code safety management system covers at least these points:

  • Mode: Manual ON at sea; Automatic not used, per MSC.1/Circ.1474. State when Manual OFF is permitted, for example alongside or at anchor with an anchor watch set, and who may select it.
  • Dormant period: the Td for each navigational condition, chosen by the master under MSC.128(75) 4.3.
  • Access control: where the master’s key or password is kept, given the MAIB finding that keys or codes left on the bridge let crews disable systems.
  • Cabin routing: which cabins receive the second and third stages, updated when officers change cabins or the master is ashore.
  • Testing: a routine test of each stage, including the cabin alarms, and a daily check of motion sensors where fitted (a Marshall Islands requirement).
  • Pilotage: whether the system stays on with a pilot on the bridge; under V/19.2.2.3 it does whenever the ship is underway at sea, subject to the flag’s reading of that phrase.
  • Defects: recording a BNWAS defect, informing the flag and the next port where required, and posting an additional watchkeeper until it is repaired.

Watch arrangements around the alarm belong in the STCW watchkeeping instructions given to deck officers, and in the master’s night orders. A procedure that says the BNWAS is “always on” but leaves no lookout at night repeats the configuration found on Danio and BBC Marmara.

Autonomous and remotely operated ships

The BNWAS assumes a human OOW on the bridge. For maritime autonomous surface ships operated from a remote control centre, the same function (detecting that the person responsible for the watch has stopped responding) has to be provided at the remote station, and SOLAS V/19.2.2.3 says nothing about how. The smart shipping article covers the wider state of autonomy regulation.

Limitations

This article states the IMO baseline and three published flag positions. A ship’s obligations come from its flag’s implementation of SOLAS, which may add requirements not shown here, and from the class or RO acting for that flag. MSC.128(75), MSC.1/Circ.1474, A.1021(26) and the cited MAIB reports were read in the versions linked in the sources; IEC 62616:2010 is a paid standard and its internal test clauses, including any sound-level or photometric limits it sets, are not reproduced here. The circular is cited from a copy of the IMO document hosted by ClassNK.

The phrase “underway at sea” in V/19.2.2.3 is not defined in SOLAS, and flags read it differently, particularly in pilotage waters and at anchor. The dormant-period discussion is the site’s own arithmetic on the MSC.128(75) timings, not an IMO recommendation. The HSC Code’s own navigation equipment chapter is not reproduced here; check the consolidated Code for whether a given craft must carry an equivalent alarm. The MAIB figures of 81 and 20 investigations are the MAIB’s own count for UK waters and UK ships to November 2023 and are not a global casualty rate.

Frequently Asked Questions (FAQs)

Which ships must carry a BNWAS?

Cargo ships of 150 GT and upwards and passenger ships irrespective of size, under SOLAS regulation V/19.2.2.3 as inserted by MSC.282(86).

New ships constructed on or after 1 July 2011 had it from delivery; existing ships were brought in by survey dates running from 2012 to 2014, and ships constructed before 1 July 2002 by a second set of dates from 2016 to 2018 under V/19.1.2.4 (MSC.350(92)).

When must the BNWAS be switched on?

Regulation V/19.2.2.3 says the system shall be in operation whenever the ship is underway at sea.

SOLAS does not define at sea for this purpose. The Marshall Islands, in Marine Notice 2-011-40, defines it for its own ships as underway outside pilotage waters; other flags set their own reading, so the ship’s safety management system should state when the system is in Manual ON.

Should the BNWAS be left in Automatic mode?

No. MSC.1/Circ.1474 of 23 May 2014 says that, pending a revision of MSC.128(75), the automatic operational mode, if available, should not be used.

Automatic mode only runs the system while the heading or track control system is engaged, which leaves the bridge unmonitored during hand steering, a state V/19.2.2.3 does not permit at sea.

What is the BNWAS alarm sequence and timing?

Under MSC.128(75) paragraph 4.1.2, after a dormant period of 3 to 12 minutes a flashing visual indication appears on the bridge; 15 seconds later the first-stage audible alarm sounds on the bridge; 15 seconds after that the second-stage alarm sounds at the back-up officer’s and/or the master’s location; and 90 seconds after the second stage the third-stage alarm sounds at the locations of further crew members able to take corrective action.

How long after the dormant period ends is the master alerted?

Thirty seconds.

The visual indication starts at the end of the dormant period, the bridge audible alarm follows 15 seconds later and the second-stage remote alarm 15 seconds after that, so with a 12-minute dormant period the master or back-up officer is called at 12 minutes 30 seconds after the last reset (MSC.128(75) 4.1.2).

Who may set the dormant period and the operating mode?

The master only. MSC.128(75) paragraph 4.3 requires the mode selector and the dormant-period setting to be security protected so that access is restricted to the master.

The MAIB found, in its November 2023 safety flyer, that keys or codes kept on the bridge let crews switch systems off.

Where may BNWAS reset devices be fitted?

Only in positions on the bridge that give a proper lookout.

MSC.128(75) paragraph 4.1.3.1 bars a reset from any device not physically located in such areas, and paragraph 5.1.4 says reset devices should be easily accessible from the conning position, the navigating and manoeuvring workstation, the monitoring workstation and the bridge wings. A chartroom without a view ahead is not on that list.

Can the master silence the BNWAS from the cabin?

No. Reset or cancellation of the alarm sequence is not possible from any device outside the bridge areas that give a proper lookout (MSC.128(75) 4.1.3.1).

Silencing the remote alarm from a cabin would defeat the purpose of the second stage, which is to bring a second qualified person to the bridge.

Are motion sensors allowed as a BNWAS reset?

Yes, as a type of input.

MSC.128(75) paragraph 4.1.3.3 allows reset inputs from other equipment capable of registering physical activity and mental alertness of the OOW. The Isle of Man accepts passive infrared detectors under MSN 061 (2018). The Marshall Islands, in Marine Notice 2-011-40, excludes bridge chairs from the sensed area unless the chair is integral to the primary conning position, and requires motion-sensor systems to be checked at least daily.

Can holding a reset button down stop the BNWAS alarm?

No. MSC.128(75) paragraph 4.1.3.4 says a continuous activation of any reset device should not prolong the dormant period or suppress the sequence.

A jammed or taped button therefore still lets the sequence run.

What is the BNWAS Emergency Call function?

An optional push button on the bridge that immediately activates the second-stage remote alarm and then the third stage, so the OOW can summon help without waiting for the timer (MSC.128(75) 4.1.4).

The standard uses may, so not every unit has one; where fitted, its power supply is battery maintained under paragraph 6.3.

Does a BNWAS replace a lookout?

No. The lookout duty sits in COLREG Rule 5 and STCW Code section A-VIII/2; the BNWAS is a separate SOLAS V/19 carriage item that only detects whether the OOW is still resetting it.

The MAIB’s November 2023 flyer treats the dedicated lookout during darkness and the operation of a BNWAS as two distinct international requirements, and its casualty reports find both removed together.

Do high-speed craft need a BNWAS?

Not under SOLAS V/19 where the craft is certified and surveyed under the HSC Code.

SOLAS regulation X/3.1 deems such craft to comply with regulations V/18, V/19 and V/20, and the Isle of Man’s MSN 061 describes HSC Code craft as the only exception to V/19.2.2.3. A flag can still require a BNWAS on a high-speed craft by its own rules.

Do fishing vessels or small domestic ships have to carry a BNWAS?

SOLAS V/1.4 lets the Administration decide how far regulations V/15 to V/28, which include the V/19 carriage rules, apply to ships below 150 GT, ships below 500 GT not on international voyages, and fishing vessels.

Carriage on those ships is a flag decision, so the answer is in the flag’s national rules.

Does the United States require BNWAS on US-flag ships?

The US Coast Guard notice at 78 FR 2683 of 14 January 2013 states that the Coast Guard had not adopted domestic regulations to implement the SOLAS BNWAS requirement, so carriage on US-flag vessels is voluntary under US law.

The same notice warns that a ship on international voyages without a BNWAS past its compliance date may be detained by foreign port state officials.

Which test standard applies to a BNWAS?

IEC 62616:2010, edition 1.0 published 11 February 2010 with a corrigendum of July 2012, read with the general environmental and EMC test standard IEC 60945:2002 (edition 4.0).

In the EU the equipment is item MED/4.57 under Commission Implementing Regulation (EU) 2025/1533 and carries the wheel mark once approved under module B with D, E or F, or under module G.

How loud must the BNWAS cabin alarm be?

MSC.128(75) sets no decibel figure. Paragraph 5.2.4 requires the remote alarm to be easily identifiable, to indicate urgency and to have a volume sufficient to wake sleeping persons, and paragraph 5.2.3 says the first-stage bridge tone should alert but not startle.

Tone and volume are set at commissioning.

Is the BNWAS alarm classed as an emergency alarm?

The second and third stage remote audible alarms are.

The Code on Alerts and Indicators, A.1021(26) of 2 December 2009, lists them as emergency alarms in paragraph 3.2.8; in its table 10.1.1 the end of the dormant period is an indicator, the first-stage bridge alarm is an alarm and a BNWAS malfunction or power failure is a warning. The 2009 Code was revoked by the Code on Alerts and Indicators, 2025, resolution A.1204(34) of 3 December 2025, which defines the BNWAS alarm in paragraph 3.3.8 by reference to MSC.128(75).

Is the visual BNWAS indication steady or flashing?

Flashing. MSC.128(75) paragraph 5.2.2 requires a flashing indication in a colour that does not impair night vision, dimmable but not to extinction.

The standard does not prescribe the colour.

What is the PSC deficiency code for BNWAS?

10138, Bridge Navigational Watch Alarm System (BNWAS), in the Safety of Navigation group of the Paris MoU deficiency code list; the Australian Maritime Safety Authority uses the same code.

Whether a defect leads to detention is the port state control officer’s professional judgement under the regime’s procedures.

Is MSC.355(92) the revised BNWAS standard?

No. Resolution MSC.355(92) of 21 June 2013 amends the International Convention for Safe Containers (CSC), 1972, and does not mention the BNWAS.

The BNWAS performance standard is still MSC.128(75) of 20 May 2002; the only IMO follow-up is MSC.1/Circ.1474 of 23 May 2014 on the auto function.

Can an older BNWAS installed before 2011 stay in service?

Yes, at the flag’s discretion. SOLAS V/19.2.2.4 lets the Administration exempt a BNWAS installed before 1 July 2011 from full compliance with the IMO performance standard.

The Isle of Man and Marshall Islands both publish acceptance criteria for such units.

Does the VDR record the BNWAS?

VDRs built to MSC.333(90) record the status of all mandatory bridge alarms as individually identified alarms (paragraph 5.5.10), which covers BNWAS alarms routed to the recorder.

The MAIB’s 2023 flyer found that VDRs on the ships it investigated did not log BNWAS status, and the Marshall Islands requires a BNWAS link where the BNWAS was installed on or after 1 July 2011 and the VDR on or after 1 July 2014.

What dormant period should a ship use?

MSC.128(75) only sets the range, 3 to 12 minutes, and puts the setting in the master’s hands.

The choice belongs in the safety management system; a shorter period at night or in confined waters reduces the time an incapacitated OOW goes undetected, at the cost of more resets.

Can a sole OOW on a ship with a BNWAS act as lookout at night?

The STCW Code allows the OOW to be the sole lookout only in daylight and only after the conditions in section A-VIII/2 are assessed, with assistance immediately available.

The UK MCA, in MGN 315, calls the OOW acting as sole lookout in darkness or restricted visibility dangerous and irresponsible. A BNWAS does not change either position.

Sources

  1. IMO Resolution MSC.282(86), adoption of amendments to SOLAS 1974 chapter V (regulation V/19.2.2.3 BNWAS carriage), 5 June 2009 imo.org
  2. IMO Resolution MSC.350(92), adoption of amendments to SOLAS 1974 (regulation V/19.1.2.4 BNWAS for ships constructed before 1 July 2002), 21 June 2013 imo.org
  3. IMO Resolution MSC.128(75), Performance Standards for a Bridge Navigational Watch Alarm System (BNWAS), 20 May 2002 imo.org
  4. IMO MSC.1/Circ.1474, Guidance on the Bridge Navigational Watch Alarm System (BNWAS) auto function, 23 May 2014 classnk.or.jp
  5. IMO Resolution A.1021(26), Code on Alerts and Indicators, 2009, 2 December 2009 imo.org
  6. IEC 62616:2010, Maritime navigation and radiocommunication equipment and systems. Bridge navigational watch alarm system (BNWAS) webstore.iec.ch
  7. IEC 60945:2002, Maritime navigation and radiocommunication equipment and systems. General requirements, methods of testing and required test results webstore.iec.ch
  8. Commission Implementing Regulation (EU) 2025/1533 on design, construction and performance requirements and testing standards for marine equipment (item MED/4.57 BNWAS) eur-lex.europa.eu
  9. US Coast Guard, Carriage Standards for Bridge Navigational Watch Alarm Systems (BNWAS) Aboard U.S. Flagged Vessels, 78 FR 2683, 14 January 2013, Docket USCG-2012-0772 govinfo.gov
  10. Isle of Man Ship Registry, MSN 061 Bridge Navigational Watch Alarm Systems (BNWAS), 1 August 2018 iomshipregistry.com
  11. Australian Maritime Safety Authority, port state control deficiency codes (10138 Bridge Navigation Watch Alarm System) amsa.gov.au
  12. MAIB Accident Investigation Report 8/2014, grounding of general cargo vessel Danio off Longstone, Farne Islands, 16 March 2013 gov.uk
  13. MAIB Accident Investigation Report 25/2015, grounding of general cargo vessel Lysblink Seaways near Kilchoan, 18 February 2015 gov.uk
  14. MAIB Accident Investigation Report 8/2023, grounding of general cargo vessel BBC Marmara on Eilean Trodday, 25 July 2021 gov.uk
  15. MAIB safety flyer, Circumvention of navigational safeguards, 30 November 2023 gov.uk