Silver Cloud II — Asleep at the Helm, Awake by the Rocks

A Trip That Never Really Stopped

Silver Cloud II had come off a repair period on 10 October, and by the time she grounded four days later her skipper had barely had an uninterrupted night's sleep. The vessel sailed the next day with the skipper already carrying flu-like symptoms — headache, sore throat, congestion, muscle aches — but he judged himself fit to go. Over the following three days the crew fished, hauled a torn net, diverted to Stornoway for repairs, landed catch, and then decided to run a night trawl to make up the time they'd lost. MAIB's own table of the skipper's hours shows working days of 16.5 to 18 hours against rest broken into fragments of three, four and six hours — well short of the 10 hours a day the law requires.

At 2130 on 13 October, Silver Cloud II left Stornoway for the fishing grounds. The mate took the first watch; at 2330 the skipper relieved him, set a waypoint, and put the vessel on autopilot. Alone in the wheelhouse, in the window between 0200 and 0600 when human alertness is at its natural low point, he fell asleep. The vessel sailed straight past its waypoint and kept going until it struck the rocks at Rubha Rodha at 0238 — the impact itself was what woke him.

What happened next went well. The skipper found a metre of water rising in the fish hold and gave the order to abandon. All three crew had PFDs on and were off the boat within a minute, using a stowage location built for exactly that. The mate and deckhand got ashore; the skipper tied a rope round his own waist, went into the water, and was pulled onto the rocks by the other two. An RNLI lifeboat had them off the rocks by 0300. Silver Cloud II broke up where she lay and was declared a constructive total loss.

What MAIB Actually Found

• The skipper's rest over the preceding days did not meet the statutory minimum of 10 hours in 24 or 77 hours in 7 — and the four days before that couldn't even be fully reconstructed from the records available.
• A flu-like illness, self-treated with paracetamol, very likely increased his need for sleep while reducing how restorative the rest he did get actually was.
• The grounding happened inside the window of circadian low (roughly 0200–0600), the period when human alertness naturally bottoms out — compounding, not causing, the fatigue already present.
• A watch alarm was fitted and active, but it lived entirely inside the wheelhouse — no visual alarm, no repeater in the crew accommodation — and MAIB found it was very likely masked by music playing at the time.
• Watchkeeping on board was informal, shared between three people with no structured rota, and the vessel routinely ran with a single person alone on watch — not prohibited for a vessel this size, but exactly the arrangement MGN 313 (F) warns against.

The Third Time, Not the First

MAIB didn't investigate this in a vacuum. Two near-identical groundings sit in the same report: Sustain, which ran aground at the entrance to Loch Broom in November 2023 after its skipper fell asleep on watch carrying a significant sleep debt; and Crystal Stream, which grounded on Barmore Island in June 2025, again a lone skipper, again asleep, again a watch alarm that didn't close the gap. That's why MAIB made no new recommendations here — not because nothing was wrong, but because the safety issues are already fully documented and the guidance already exists. The problem isn't a missing rule. It's the same rule not landing, for the third time.

Recommended Actions

Not new requirements — the ones that already applied and would have changed this outcome:

1. MSN 1884 (F) Amendment 1 sets minimum rest at 10 hours in any 24-hour period and 77 hours in any 7-day period, split into no more than two blocks, one of at least 6 hours — plan the trip against this, not around it.
2. MGN 313 (F) recommends a watch alarm specifically because lone watchkeeping is a known risk — but the alarm has to actually be able to reach the watchkeeper, and reach other crew if it doesn't. A wheelhouse-only buzzer with no accommodation repeater has no way to call for backup.
3. Anything competing for a lone watchkeeper's attention in the wheelhouse — a radio, a screen, music — should be treated as reducing the effectiveness of every other safeguard in the room, watch alarm included.
4. Illness on watch isn't a personal toughness question. A crew member symptomatic enough to need self-medicating has already lost some of the alertness margin the job depends on — that's a fitness-for-watch decision, not just a fitness-to-sail one.
5. Regular safety drills paid off here exactly as intended — PFDs stowed for one-minute access, a crew that knew the abandon-ship sequence cold. That's the one part of this story worth deliberately repeating, not just avoiding the rest.

Human Element Analysis

Cross-Industry Parallels

Try the Decision Simulator

You're the skipper, alone in the wheelhouse at 0230, three days into a trip that's run longer than planned. Play through the real decision points and see which ending you land on.

Test Your Knowledge

Think you've got this covered? Put it to the test in Crew Connect's free Knowledge Checker — try a quick safety round and see how you score.

Related Reading

• Sea Eagle — a lone creel skipper lost overboard the same year, a different mechanism, the same single-handed risk
• Crystal Stream — the previous MAIB investigation into a lone, fatigued skipper falling asleep on watch
• Sustain — the first of this pattern, a fatigue-driven grounding at the entrance to Loch Broom