Incident Analysis
Important note: Aware Mate was not installed on Alfred. This page uses the official investigation to show where an earlier on-board vigilance alert could have helped interrupt the incident chain. Any intervention sequence is illustrative, not proof of a live deployment.
At 14:00 on 5 July 2022, the roll-on/roll-off passenger ferry Alfred grounded on the east coast of Swona Island in the Pentland Firth while on passage from Gills Bay to St Margaret’s Hope. Forty-one passengers and crew were injured, the vessel’s port bulbous bow was damaged, and almost all vehicles being transported on board were damaged.
MAIB identified three core safety issues: routinely navigating too close to land, fatigue leading to loss of awareness at a critical point in the passage, and weak assurance that procedures were being followed.
Immediately before the accident, Alfred was being guided about 250 metres from shore. Around 90 seconds before grounding, the ferry began to swing towards the coast. The master only became aware of the danger roughly 70 seconds later, then applied hard starboard rudder and full astern, but it was too late to avoid striking the rocks at about 13 knots.
• The master was effectively navigating alone, without a lookout on the bridge.
• Fatigue was likely even though hours-of-work rules had been met; he had joined after only five hours of sleep at home and was operating in a post-lunch circadian low.
• BNWAS was fitted, but it was rarely used and its use was not directed in the safety management system.
• Passage planning and ECDIS use were inadequate; no-go areas and cross-track limits were not properly defined.
• The vessel was taken too close to land, leaving little recovery space once awareness was lost.
• Audits and inspections had not identified flaws in passage planning, bridge manning, or BNWAS use.
MAIB concluded that BNWAS was unlikely to prevent this grounding because the lapse was brief. In a case like Alfred, the role of an additional vigilance layer is not to replace bridge procedures, but to give an earlier indication that alertness may be degrading before a minor heading change becomes a serious track deviation.
• Complements BNWAS as an on-board, human-in-the-loop vigilance layer.
• Estimates sustained drowsiness and distraction risk from non-identifying cues such as eyelid closure, gaze stability, head position, and posture.
• Issues graded local alerts and, where configured, can use a BNWAS-compatible dry-contact path to escalate through existing shipboard alarm chains.
• Does not steer the vessel or take navigational decisions.
• Does not identify people, diagnose medical conditions, or perform emotion recognition.
• Does not send raw video ashore by default; standard operation is on-board processing with configurable retention for derived metrics and event logs.
A familiar route can still become an injury and schedule-disruption event when fatigue, thin bridge support, and narrow passage margins align.
Passenger injury, vehicle damage, repair cost, service disruption, and follow-on claims can all grow from a brief loss of awareness.
Aware Mate is aimed at that upstream gap: an earlier warning layer that stays on board, keeps humans in the loop, and fits a privacy-by-design deployment model.
See how Aware Mate fits your bridge setup and discuss operational fit, privacy boundaries, and next steps.