First major screw-up in twenty-five years

  • Thread starter Thread starter Ivan Seeking
  • Start date Start date
  • Tags Tags
    Major Years
Click For Summary

Discussion Overview

The discussion revolves around a participant's experience of making a significant mistake while operating a piece of equipment, leading to damage. The scope includes personal anecdotes related to equipment operation, safety protocols, and the implications of errors in technical environments.

Discussion Character

  • Exploratory
  • Debate/contested
  • Technical explanation

Main Points Raised

  • One participant recounts a mistake that resulted in damaging a customer's equipment, highlighting the lack of indicators for the equipment's operational status.
  • Another participant shares a similar experience involving a CNC machine that was damaged due to an untested program, emphasizing the importance of status lights and safety measures.
  • Some participants express surprise at the rarity of such mistakes, noting that one major error in twenty-five years is impressive.
  • There are suggestions that clients should implement better safety features, such as status lights, to prevent future incidents.
  • Several participants reference other significant technical failures, drawing parallels to the original incident and discussing the broader implications of such errors in engineering contexts.

Areas of Agreement / Disagreement

Participants generally agree that mistakes can happen in technical fields, and many share personal anecdotes of similar experiences. However, there is no consensus on the best preventive measures or the specific responsibilities of clients versus operators.

Contextual Notes

Some discussions involve assumptions about safety protocols and operational standards that may not be universally applicable. The conversation also touches on the emotional impact of making mistakes in high-stakes environments.

Who May Find This Useful

Individuals interested in engineering, equipment operation, safety protocols, and those who have experienced similar professional challenges may find this discussion relevant.

Ivan Seeking
Staff Emeritus
Science Advisor
Gold Member
Messages
8,252
Reaction score
2,664
For the first time in twenty-five years I made a mistake that damaged a customer's piece of equipment. I was doing a last minute I/O check as there had been some discrepancies, and I inadvertently started a piece of equipment that provides no indication that it's running. My first clue was the loud crunching noise heard as some gears self destructed...

The last time I made a mistake like this I shorted out an entire hospital! At least this time the damage was not quite so alarming. But damn, did I feel stupid. I am always soooooo careful. I can't believe that something got away from me like that. Of course to be fair to myself, I was set up a bit. I had no way to know that the equipement was running as there is no sound or light or indicator of any kind. Even worse: They had the torque turned down for testing but cranked it back up just before I got there. If they had waited until the testing was complete, as they should have, this never would have happened.

But damn, did I feel stupid! At least they were very nice about it and they didn't seem to be terribly upset. They can probably fab some new parts in a few hours.
 
Last edited:
Engineering news on Phys.org
Man that sucks, well at least it will be back together and working today. How old was that piece of equipment almost everything I worked with has some status lights somewhere on the control board, or by the testing ports.

In a custom fab shop I use to work in someone loaded an incomplete and untested CNC program onto our 7 axis milling machine, the resulting damage put the machine out of commission for two months for the manufacturer to rebuild the head and one of the arms.
 
Last edited by a moderator:
See there was me thinking all the Mentors on PF weren't human, and that they perhaps either fabricate real lives because they live in jars. Or that they are ascended beings. So much for that theory. :smile: I'd say 1 major mistake in 25 years is bloody impressive.
 
re Argentum Vulpes: This is a new custom machine that is already weeks late in shipping. They do real special apps stuff [submarines and such], so it is not unusual for these systems to be uniquely dangerous as compared to an off-the-shelf system.
 
Schrödinger's Dog said:
...Or that they are ascended beings.

Even ascended beings need day jobs. :biggrin:
 
Ivan Seeking said:
Even ascended beings need day jobs. :biggrin:

:smile: I suppose so. :-p
 
Sorry to hear about the smash-up, but it seems that your clients bear much of the burden for that. Perhaps in the future they will install some status lights with colored LEDs to indicate when that machine is powered, and when key solenoids/relays are open or closed. That little bit of caution would have prevented this problem.
 
Argentum Vulpes said:
In a custom fab shop I use to work in someone loaded an incomplete and untested CNC program onto our 7 axis milling machine, the resulting damage put the machine out of commission for two months for the manufacturer to rebuild the head and one of the arms.
I've seen something similar in a specialty shop, where the folks should have known better. A CNC program was required to lower a drill bit then drill a boss on a rather expensive prototype part. I would have thought that they would have a test plate to make sure the software was verified.

As I watched, the drill came down - and Clunk! - the head of the drill bit wet too far and damaged the part beyond repair. The operator looked at it, looked at me, looked at the instructions - then quietly walked away. I'll be they were off just a few mils, but that was enough to destroy a part.

Ivan, like SD mentioned, "1 major mistake in 25 years is bloody impressive".
 
  • #10
So what the hell were you working on?
 
  • #11
mgb_phys said:

OH jeez that's painful to look at...! But from the brief description there were many root causes of this accident. Hard to imagine a good safety / loss prevention program wouldn't have picked up on all the deficiencies.
 
  • #12
binzing said:
So what the hell were you working on?

I would guess that if he told us, he would have to kill us all :eek: .
 
  • #14
How would you like to have been this guy?
http://www.phunnycar.com/data/missile-mishap.jpg
http://www.phunnycar.com/pictures/1042_Missile_Mishap.html
 
Last edited by a moderator:
  • #15
mgb_phys said:

I remember that event. We wondered -

How could they not notice 24 bolts were missing, and why did the system allow someone to remove 24 bolts without securing the satellite?

This was after the satellite which crashed into Mars because two sets of units were used by two parties, who didn't compare calcs.
 
  • #16
This was a pretty big screw up. Ariane 5 Flight 501. Basically a programming screw up forced the rocket into a tighter turn than it was designed for, .5 degree turn vs 5 degree turn snapping it in half and trigering the self destruct.
http://video.google.ca/videoplay?docid=-7960908757881187694&q=Ariane+5+rocket+explosion&total=4&start=0&num=10&so=0&type=search&plindex=1
 
Last edited by a moderator:
  • #17
I sure as hell wouldn't like to be either of those guys!
 
  • #18

Similar threads

Replies
64
Views
7K
  • · Replies 35 ·
2
Replies
35
Views
9K
  • · Replies 10 ·
Replies
10
Views
2K
Replies
9
Views
4K
  • · Replies 3 ·
Replies
3
Views
2K
  • · Replies 4 ·
Replies
4
Views
2K
  • · Replies 27 ·
Replies
27
Views
2K
  • · Replies 6 ·
Replies
6
Views
2K
  • · Replies 7 ·
Replies
7
Views
3K
  • · Replies 22 ·
Replies
22
Views
2K