{"id":51638,"date":"2026-04-17T21:51:14","date_gmt":"2026-04-17T20:51:14","guid":{"rendered":"https:\/\/maritimehub.co.uk\/?p=51638"},"modified":"2026-04-17T21:51:14","modified_gmt":"2026-04-17T20:51:14","slug":"lookouts-and-bnwas","status":"publish","type":"post","link":"https:\/\/maritimehub.co.uk\/lookouts-and-bnwas\/","title":{"rendered":"Lookouts and BNWAS"},"content":{"rendered":"
\n

BRIDGE \u2192 Watchkeeping Fundamentals<\/strong><\/p>\n

Position on the Bridge<\/strong><\/p>\n

System Group:<\/strong> Navigation \/ Watch Safety<\/p>\n

Primary Role:<\/strong> Maintaining a continuous, competent human watch and detecting watchkeeper incapacitation<\/p>\n

Interfaces:<\/strong> OOW, lookout, master, VDR, GMDSS, alarm management systems, company SMS<\/p>\n

Operational Criticality:<\/strong> Absolute \u2014 without a proper lookout, every other navigational system is background noise<\/p>\n

Failure Consequence:<\/strong> Reduced situational awareness leads to late or absent collision avoidance action; fatigued or absent watchkeeper produces grounding or contact without any precursor alarm<\/p>\n<\/div>\n

A lookout watches. A BNWAS checks that someone is still standing.<\/em>
They are not substitutes for each other, and neither is a substitute for judgment.<\/em><\/p>\n

Introduction<\/h2>\n

The requirement for a proper lookout predates radar, ARPA, AIS, and every piece of electronics now fitted to a ship’s bridge. It predates SOLAS. It is embedded in COLREGS Rule 5 and reinforced by STCW Regulation VIII\/2 because the sea has repeatedly demonstrated what happens when it is neglected. None of that history appears to have shortened the accident list.<\/p>\n

BNWAS arrived as a mandated fitment under SOLAS Chapter V Regulation 19, phased in from 2011. It was intended to detect incapacitation \u2014 the watchkeeper who collapses, suffers a medical event, or simply falls asleep and stops moving. The intent was narrow and specific. In practice, the industry absorbed it as a paperwork item, crews learned its rhythms, and the alarm became something to silence rather than something to heed.<\/p>\n

The interaction between lookout requirements, single-person watchkeeping, fatigue, and BNWAS abuse sits at the centre of a pattern of casualties that recurs with depressing consistency. The ships are different. The geography changes. The underlying condition is identical: a bridge with one person, that person exhausted, and a system that confirms only that a button was pressed.<\/p>\n

Contents<\/h2>\n
    \n
  • 1. The Lookout Requirement: What STCW Actually Demands<\/li>\n
  • 2. Single-Person Watchkeeping: The Conditions and Who Decides<\/li>\n
  • 3. BNWAS: Function, Modes, and Reset Intervals<\/li>\n
  • 4. What BNWAS Does Not Detect<\/li>\n
  • 5. Abuse: The Tape, the Proxy, and the Disabled Stage<\/li>\n
  • 6. Fatigue as the Governing Variable<\/li>\n
  • 7. The Accident Signature<\/li>\n
  • 8. The Only Configuration That Actually Works<\/li>\n
  • 9. Closing Reality<\/li>\n<\/ul>\n

    1. The Lookout Requirement: What STCW Actually Demands<\/h2>\n

    STCW Regulation VIII\/2 is explicit. A proper lookout shall be maintained at all times. The phrase by all available means<\/em> in COLREGS Rule 5 is frequently reduced in practice to radar and AIS, but the regulation pairs it with sight and hearing for a reason. Radar does not resolve ambiguity in the visual domain. AIS shows only vessels that are transmitting correctly. Hearing detects fog signals, breaking water, and distress calls from small craft with no electronic fit.<\/p>\n

    The lookout function encompasses collision avoidance, proximity to navigational hazards, and weather development. It is not simply watching for other ships. It is maintaining an accurate mental model of the environment around the vessel at all times.<\/p>\n

    A dedicated lookout is a person whose sole duty is that function. Not a rating who is also taking helm orders, making coffee, or monitoring machinery. A dedicated lookout whose attention is divided is not fulfilling the function regardless of what the deck log records.<\/p>\n

    2. Single-Person Watchkeeping: The Conditions and Who Decides<\/h2>\n

    STCW Section A-VIII\/2 permits the OOW to be the sole lookout during daylight hours under specific and cumulative conditions: daylight, good visibility, the situation assessed as low risk, lookout duties not impairing watchkeeping, and an immediate call system to a backup watchkeeper who can reach the bridge without delay. These conditions must all be met simultaneously. They are not a menu from which the most convenient are selected.<\/p>\n

    The master decides. That decision is to be recorded and supported by the ship’s passage plan and prevailing conditions. In practice, sole watchkeeping has become the default on many vessels regardless of conditions, passage phase, or traffic density. The conditions specified in the regulation are treated as a formality rather than a genuine threshold.<\/p>\n

    Congested waters remove the permission entirely. Restricted visibility removes it. Night removes it. A vessel in the Dover Strait at 0300 in reduced visibility has no regulatory basis for a single-person bridge watch, yet this configuration appears repeatedly in the record.<\/p>\n

    The master’s authority to make this decision is also the master’s responsibility when it goes wrong. Flag state and port state control will examine whether the decision was justified. In a grounding or collision, it rarely was.<\/p>\n

    3. BNWAS: Function, Modes, and Reset Intervals<\/h2>\n

    BNWAS operates on a simple principle. If the watchkeeper does not interact with the system within a defined period, it assumes incapacitation and escalates through an alarm sequence. The system does not assess whether the watchkeeper is alert. It assesses only whether the watchkeeper has pressed a button or triggered a sensor.<\/p>\n

    The operating modes are typically Automatic, Manual A, Manual B, and Inactive. Automatic mode allows the system to assess that bridge activity \u2014 helm movement, radar interaction, course alterations \u2014 constitutes watchkeeper presence and resets the timer accordingly. Manual modes require deliberate physical interaction. Inactive mode disables BNWAS entirely, which is permitted in port but should log the change.<\/p>\n

    Reset intervals under MSC.1\/Circ.1474 and the performance standards in IMO Resolution MSC.282(86) provide for a dormancy period of three to twelve minutes before the first stage alarm sounds on the bridge. If that is not acknowledged, a second stage follows, typically within fifteen seconds, escalating to an audible alarm at a backup location \u2014 the master’s cabin, or a duty officer station. A third stage may then alert a further location.<\/p>\n

    The escalation design is sound. The vulnerability is that each stage can be defeated individually.<\/p>\n

    4. What BNWAS Does Not Detect<\/h2>\n

    BNWAS does not detect drowsiness. It does not detect a watchkeeper who is standing at the console staring at nothing. It does not detect a watchkeeper who is present but cognitively absent \u2014 the microsleep state that fatigue research identifies as the dominant precursor to bridge incapacitation casualties.<\/p>\n

    A person in a microsleep lasting three to five seconds can be standing upright. They will not fall. They will not trigger a panic alarm. They may reset the BNWAS on schedule because the habit is conditioned. The system records normal watchkeeping. The ship drifts.<\/p>\n

    BNWAS also does not monitor lookout quality. A watchkeeper who is technically alert but focused entirely on the radar plot while a fishing fleet works across the bow without AIS is not maintaining a proper lookout. BNWAS has nothing to say about this.<\/p>\n

    Alarm acknowledgment is not situational awareness. It never was.<\/em><\/p>\n

    5. Abuse: The Tape, the Proxy, and the Disabled Stage<\/h2>\n

    BNWAS abuse is not rare. It appears in accident investigation reports from the Marine Accident Investigation Branch, the National Transportation Safety Board, the Danish Maritime Accident Investigation Board, and equivalent bodies across multiple flag states. The methods are consistent.<\/p>\n

    The most primitive is the taped or weighted reset button \u2014 a piece of electrical tape holding the button depressed, or a heavy object placed on a touch-sensitive panel. The system records continuous acknowledgment. The watchkeeper sleeps. This shows up on VDR data as a perfectly regular reset pattern with no associated bridge activity.<\/p>\n

    Proxy resetting involves a second person \u2014 a rating, a cadet, occasionally another officer \u2014 entering the bridge at intervals to reset the alarm while the watchkeeper rests elsewhere. This is not solo watchkeeping in any meaningful sense. It is an unqualified person in sole charge of the bridge while the officer sleeps in the chartroom.<\/p>\n

    Disabling individual alarm stages is more sophisticated. The third-stage alarm, which would wake the master, is defeated at the panel or by isolating the relevant circuit. The first and second stages continue to function, which allows the system to appear operational during any inspection, while the escalation that would actually summon help is silenced.<\/p>\n

    Investigators identify these patterns through VDR data: reset events with no associated control input, reset intervals so precise they suggest mechanical operation, or the complete absence of any third-stage alarm record in circumstances where fatigue was demonstrably present.<\/p>\n

    The VDR does not lie. The BNWAS log does not lie. The gap between what those records show and what actually happened on the bridge is where the abuse lives.<\/p>\n

    A ship that requires BNWAS abuse to maintain its schedule has a manning problem, not a watchkeeping problem.<\/em><\/p>\n

    6. Fatigue as the Governing Variable<\/h2>\n

    Fatigue is not a personal failing. It is a physiological state produced by insufficient sleep, circadian disruption, workload, and port turnaround patterns that ITF, maritime labour organisations, and flag states have documented at length without producing a maritime industry that reliably prevents it.<\/p>\n

    The hours of work and rest provisions under MLC 2006 and STCW 2010 set a minimum rest of ten hours in any twenty-four-hour period and seventy-seven hours in any seven-day period. These figures were derived from negotiation as well as physiology. They are a floor, not a guarantee of fitness for watch. A watchkeeper who has taken the minimum allowable rest across a week of port calls, cargo operations, and overtime drills is not rested. They are legally compliant.<\/p>\n

    Fatigue degrades decision-making before it degrades consciousness. Reaction time lengthens. Target fixation increases. The watchkeeper focuses on one element of the traffic situation at the expense of a broader scan. Complacency about familiar waters develops faster. These are the precursor states to a grounding or a collision, and they are invisible to BNWAS.<\/p>\n

    Single-person watchkeeping concentrates this risk. Two people on a bridge share the cognitive load. One person can alert the other to a developing situation they have not noticed. Fatigue affects both, but one fatigued watchkeeper monitored by a second person with a lower cognitive burden is safer than one fatigued watchkeeper monitored by a system that checks only whether a button was pressed.<\/p>\n

    7. The Accident Signature<\/h2>\n

    Grounding casualties involving fatigued watchkeepers and BNWAS abuse share a recognisable signature. The vessel is on a well-known route. The traffic is light or the visibility is good. The passage is short enough that the OOW calculated they could manage it alone. The BNWAS shows a normal reset pattern until it does not. The VDR shows the helm going to autopilot and staying there. The engine telegraph does not move. No collision avoidance action is taken. The vessel grounds or makes contact at close to full sea speed.<\/p>\n

    Post-incident, the BNWAS log is among the first items examined. Investigators look for the regularity of resets, the correlation between resets and other bridge activity, and the presence or absence of third-stage alarms. The taped button leaves an unmistakeable trace: reset events at machine-precise intervals with no corresponding radar interaction, no AIS acknowledgment, no helm input.<\/p>\n

    The master is then examined on their knowledge of the watchkeeper’s condition, the decision to permit sole watchkeeping on that particular passage, and the company’s rest hour records. In most cases, the records show compliance. The reality, as reconstructed from the VDR and crew testimony, shows something else.<\/p>\n

    The casualty was not a surprise to the ship. It was the eventual consequence of an accepted practice.<\/p>\n

    8. The Only Configuration That Actually Works<\/h2>\n

    A rested OOW, with a dedicated lookout, in conditions appropriate to the passage phase, maintaining a proper watch by all available means including sight and hearing. This is what STCW describes. It is also what the casualty record repeatedly demonstrates was absent.<\/p>\n

    The lookout is not a formality. On a vessel approaching a TSS in reduced visibility, the difference between a lookout on the bridge wing and a watchkeeper managing everything from the console is the difference between hearing a fog signal in time and not hearing it at all. AIS does not replace this. Radar does not replace this. The regulations did not require sight and hearing by accident.<\/p>\n

    BNWAS supports this configuration by providing a backstop against incapacitation. It is correctly understood as a last-resort safety net for a rare event, not a substitute for the watch itself. A vessel that relies on BNWAS to manage its bridge watch has inverted the safety hierarchy.<\/p>\n

    Manning levels that make a proper watch structurally impossible are a management decision, not a watchkeeping problem. When the schedule demands that the OOW work twenty hours out of twenty-four across a port turnaround, the lookout requirement cannot be met regardless of what the deck log records. The responsibility for that condition does not rest solely with the OOW who eventually falls asleep.<\/p>\n

    STCW does not say maintain a lookout when convenient. It says at all times.<\/em><\/p>\n

    The master’s authority to call additional watchkeepers, to slow the vessel, to anchor rather than proceed through a passage in conditions where the watch cannot be properly maintained, exists precisely because these situations arise. Exercising that authority is not a failure of commercial management. Failing to exercise it and subsequently grounding the ship is.<\/p>\n

    Skill fade in visual watchkeeping is real. Officers who have spent years on highly automated vessels with light traffic loads lose the rapid, disciplined sector-scanning habit that a busy coastal passage demands. The scan becomes lazy. Targets are detected later. The ARPA is trusted beyond its capability. This is not an individual deficiency; it is what happens when the system normalises reduced watchkeeping standards over time.<\/p>\n

    9. Closing Reality<\/h2>\n

    Every vessel that has grounded with a sleeping or incapacitated watchkeeper had a BNWAS fitted and a lookout requirement in its SMS. The documents were in order. The certificates were valid. The system was running.<\/p>\n

    None of it substituted for a person who was awake, alert, and looking out of the window.<\/p>\n

    BNWAS abuse is endemic because the conditions that produce it \u2014 chronic fatigue, inadequate manning, commercial schedule pressure \u2014 are endemic. Fixing the symptom without addressing the condition produces better-documented accidents, not fewer of them.<\/p>\n

    The lookout requirement is not a legacy provision awaiting deletion by the next round of SOLAS amendments. It is the foundational act of seamanship from which everything else on the bridge follows. A ship without a proper lookout is not being navigated. It is being aimed.<\/p>\n","protected":false},"excerpt":{"rendered":"

    STCW demands a proper lookout by sight and hearing. BNWAS proves nothing except that someone pressed a button. These are not the same thing.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"fifu_image_url":"","fifu_image_alt":"","c2c-post-author-ip":"2a02:c7c:2ef8:2400:931:afb1:9971:4a62","footnotes":""},"categories":[10,1],"tags":[9205,9207,9076,2060,271,9206,9201,9123],"class_list":["post-51638","post","type-post","status-publish","format-standard","hentry","category-bridge","category-latest","tag-bnwas","tag-bridge-safety","tag-collision-avoidance","tag-fatigue","tag-grounding","tag-lookout","tag-stcw","tag-watchkeeping"],"acf":[],"_links":{"self":[{"href":"https:\/\/maritimehub.co.uk\/?rest_route=\/wp\/v2\/posts\/51638","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/maritimehub.co.uk\/?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/maritimehub.co.uk\/?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/maritimehub.co.uk\/?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/maritimehub.co.uk\/?rest_route=%2Fwp%2Fv2%2Fcomments&post=51638"}],"version-history":[{"count":1,"href":"https:\/\/maritimehub.co.uk\/?rest_route=\/wp\/v2\/posts\/51638\/revisions"}],"predecessor-version":[{"id":51639,"href":"https:\/\/maritimehub.co.uk\/?rest_route=\/wp\/v2\/posts\/51638\/revisions\/51639"}],"wp:attachment":[{"href":"https:\/\/maritimehub.co.uk\/?rest_route=%2Fwp%2Fv2%2Fmedia&parent=51638"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/maritimehub.co.uk\/?rest_route=%2Fwp%2Fv2%2Fcategories&post=51638"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/maritimehub.co.uk\/?rest_route=%2Fwp%2Fv2%2Ftags&post=51638"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}