A real loch mess: Navy larks sunk by a truculent torpedo

Row, row, row your boat, gently down the... BOOM

Who, Me? The weekend is receding, and Monday lumbers into view. Delay the inevitable with a tale of nautical nonsense from The Register's regular Who, Me? column.

This week's confession comes from "Colin", and takes us back a good few years to when the Royal Navy was in the throes of validating the torpedo designs of a favoured contractor.

Back then, "I was a real engineer," said Colin, his chest puffed out, "and not a code-slinger. I worked on underwater weapons for a certain company, which had a contract with the Royal Navy."

Colin was involved in the guidance system of the torpedo and so, when the Navy decided it was time for a user acceptance test, he and the rest of the design team accompanied the prototype to a remote loch, deep in the heart of Scotland.

We can imagine the scene. Skies of flinty grey, an icy wind and an awful lot of boot polish.

As Colin recalled: "On the shore was a small stand, with a collection of chairs and tables, where were seated about half a dozen uniformed Navy types, each equipped with the mandatory pair of binoculars and clipboard."

All eyes were trained on the loch as the carefully crafted prototype was delicately manoeuvred toward the water atop the appropriate platform. "A converted tea trolley," admitted Colin.

Once in, a countdown was solemnly intoned. The torpedo was activated and, being a self-propelled device, began to move.

"All binoculars followed the white furrow on the surface of the water," recalled Colin, "while our chief engineer enthusiastically showed the Navy guys how the remote control worked."

The view from inside a data centre rack

'We're changing shift, and no one can log on!' It was at this moment our hero knew server-lugging chap had screwed up


It all seemed to go swimmingly at first until Colin noticed the chief engineer was getting even more enthusiastic with the controller; waving it around wildly and then smacking the side of it with his hand.

Oh dear.

While the engineer struggled, the uniforms had got to their feet and were following the white furrow made by the torpedo with a renewed, fixed interest.

Colin pulled out his own binoculars to see what had attracted the attention of the brass.


The white furrow, recalled Colin, was "unswervingly heading towards a small boat, from which one of the locals was fishing".

There is a certain inevitability that, with the whole of the loch to choose from, the torpedo would head for the chap enjoying a bit of alone time, with only rod and bait for company.

"To give him his due," said Colin, "he had probably seen enough movies where a white trail in the water, coming towards your vessel, usually ended badly. So he leapt from the boat, a few seconds before the impact."

And end badly it did. There was no warhead on the torpedo, but it still remained a substantial chunk of metal and machinery. The impact made short work of the fragile fishing boat.

The unfortunate fisherman was swiftly rescued by a Royal Navy inflatable, "while our chief engineer mumbled things about lawsuits and damages while pointing to us engineers".

However, although down a fishing boat, the victim waved off the Navy's enquiries over his health and the, er, legal implications of the incident. "To everyone's surprise," remembered Colin, "he said his only condition was to be taken home in an official Royal Navy car."

Scarcely able to believe their luck, the team immediately agreed. And the reason?

"If I tell my wife I was torpedoed while fishing, she'll never believe me."

We can imagine the conversation: "So, tell me again: what happened to the boat?..."

Let he or she who has never told a tall tale to a significant other in order to cover up an act of foolishness, or an extended visit to the pub, cast the first stone.

And the uncooperative underwater weapon?

"Someone," said Colin, "had left out an 'O' ring during the final assembly, and the electronics got introduced to the health benefits of the loch water."

Ever had a sinking feeling when your project veered out of control and threatened the innocent? Or had to come up with an excuse when reality was simply too implausible? Confess all with an email to Who, Me? ®

Similar topics

Broader topics

Other stories you might like

  • September 16, 1992, was not a good day to be overly enthusiastic about your job
    If I get in early and work hard, everyone will notice, right?

    Who, Me? "The early bird trashes the business" is a saying that we've just made up, but could easily apply to the Register reader behind a currency calamity in today's episode of Who, Me?

    Our hero, Regomized as "Mike", was working as a "data entry operative" for a tourism company in 1992. The company ran bus tours to the then brand-new EuroDisney, parent company of Disneyland Paris (now the most visited theme park in Europe), which had opened earlier that year.

    Mike was an eager beaver, his youthful naivete having convinced him that if he worked extra hard, came in extra early, and kept the in-tray clear, then his efforts would be both noticed and rewarded with promotion and a bump in pay.

    Continue reading
  • An international incident or just some finger trouble at the console?
    All routers are equal, but some are more equal than others

    Who, Me? Welcome to an edition of Who, Me? where some configuration confusion left an entire nation cast adrift.

    Today's story is set in the early 2000s and comes from a reader Regomized as "Mikael" who was gainfully employed at a European ISP. The company had customers in multiple countries and Mikael's team was responsible for the international backbone.

    "Us senior network engineers were widely regarded as consummate professionals," he told us, before adding, "at least amongst ourselves."

    Continue reading
  • A discounting disaster averted at the expense of one's own employment
    I know what this process needs: Microsoft Access!

    Who, Me? A tale of discounts and process improvement via the magic of Excel, Access and a fair bit of electronic duct tape we imagine. Welcome to Who, Me?

    "James" is the Regomized reader of record today, and continues the theme of running the risk of doing a job just that little bit too well with an ancedote from the end of the last century involving his first job out of university, at a certain telecommunications giant.

    The job involved a process of calculating the discount received by big customers (the ones with multiple branches). "For the life of me I can't remember what the main DB was called," he told us, "but it was the old style green writing on a black screen that took forever to download the necessary data."

    Continue reading
  • In IT, no good deed ever goes unpunished
    When being helpful can mean being shown the door

    Who, Me? Going above and beyond in IT can sometimes lead to also going directly out of the door, as one Register reader found when discovering that sometimes efficiencies can be less than rewarding.

    A reader Regomised as "Will" told of us his days working at a now-defunct company that produced large telephone switches. In those days whenever a major software revision occurred, customers were expected to send in their configurations and Will's group would merge them into the latest and greatest. A new load would then be returned to the customers.

    It was not a fun process, not least because of constant hardware and software failures during the merge process. "When I first started, there was a constant grumble about how unreliable the machine used for the merging was," Will told us.

    Continue reading

Biting the hand that feeds IT © 1998–2022