Brute force and whiskey: The solution to all life's problems

Just make sure to drink it AFTER the rocket has successfully launched

Who, Me? Welcome back to Who, Me?, where this week a reader tells us how they used brute force and whiskey to solve a pyrotechnic problem.

Our story comes from a fellow Regomized as "Rick" and concerns a launch campaign using sounding rockets from a European test site.

Sounding rockets can't make it to orbit, but can carry scientific payloads to perform experiments during their sub-orbital lob. Some have an apogee above 500 miles (804km), while others go considerably lower.

The rockets in Rick's story, which is set many, many years in the past, were relatively large, "not to mention expensive," he said.

When perched on its pad, the hardware was connected via a hefty cable that both supplied power to the rocket and telemetry back to the controllers. Connection was via a multi-pin plug stuck into a socket on the vehicle and secured against the pressure of two springs. Seconds before ignition, a pyrotechnic device was fired to release the plug, which would spring away from the rocket.

Simple in theory. Not so simple in practice.

"To the horror of the launch team," said Rick, "it was found that during storage, corrosion had set in on these sockets, and a successful release could not be guaranteed."

What to do? The rocket launching with the cable still attached didn't bear thinking about. But changing the sockets would require rewiring followed by a certification process, all of which would have been expensive and delayed the program.

"After much head-scratching," said Rick, "a solution was found."

At this point, it is worth pointing out once more that the events of this story take place many, many years ago and we can't imagine anything like the disregard for safety described below happening today. Oh wait.

The solution, such as it was, involved heading to a nearby village and finding a retired farmer willing to take some chances in exchange for cigarettes and whiskey.

He was, recalled Rick, "persuaded to stand on the gantry next to the sounding rocket, and when he heard relays click and turbo pumps start winding up, to give the plug in its socket a mighty kick."

This would do the job the pyrotechnic might not and free the cable.

He was then to run down the stairs as fast as he could, across the pad, and "as soon as he saw his shadow in front of him, to throw himself to the ground and remain there until quiet descended."

"Surprisingly," said Rick, "this worked perfectly for all the launches except the last, when it appeared that having forgotten his promise to drink the whiskey after, and not before, the launch, he fell down the gantry and broke his leg.

"The sounding rocket, however, lifted off with complete success."

Ever skipped health and safety in search of success? Or been bribed with the adult beverage to do something that, in retrospect, might not have been too clever? Tell your story 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