The Squawk Point

Organisational Mechanics

  • Home
  • Blog
    • People
    • Data
    • Process
    • Wild Cards
    • Index
  • Podcast
  • Book

Should You Punish Mistakes?

2 January, 2014 by James Lawther 22 Comments

If somebody made a mistake that nearly killed you, would you punish the mistake?

In 1989 there was an air show at Brown Field in San Diego.

The test pilot Bob Hoover was taking thrill-seekers for flights in his Shrike Commander, a small, piston-powered, passenger plane.  The passengers were known as “Hoover’s Heavers” — more often than not they were sick during the flight.

On this occasion, the Heavers got more of a thrill than they paid for.

When the plane had climbed to 300 feet it lost all power and gravity started to pull it relentlessly back to earth.  Bob Hoover managed to cut the airspeed and safely crash-landed the plane uphill onto the side of a ravine.  The plane was severely damaged, but he and his two passengers walked away.

What caused the power failure?

This was the question spinning in Bob Hoover’s mind as he sat on the hillside waiting to be rescued.  So he walked back to the plane and smelled the fuel.

Instead of gasoline, it was jet fuel.  A member of the ground crew had mistaken the piston-engined plane for a turboprop and misfuelled it.

A simple mistake, as easy as putting petrol in your diesel engine, but rather more dramatic.

Of course, there were consequences:

The accident lead to a simple process improvement, the development of the Hoover Nozzle, a filling mechanism that prevents the inadvertent filling of a gasoline-powered plane with aviation fuel.

But there was a more remarkable outcome

When he returned to the airfield Bob Hoover walked over to the man who had nearly caused his death and, according to the California Fullerton News-Tribune, said:

“There isn’t a man alive who hasn’t made a mistake. But I’m positive you’ll never make this mistake again. That’s why I want to make sure that you’re the only one to refuel my plane tomorrow. I won’t let anyone else on the field touch it.”

Is it an urban myth?

Perhaps the story is a little too good to be true; the source is Bob Hoover’s own autobiography — in my autobiography, I will also be a saintly hero — but half-truth or not the really interesting questions are…

  • Should you punish mistakes?
  • How do you behave when it all goes wrong?
  • Does that get you the best outcome?

If you enjoyed this post click here for updates delivered to your inbox

Read another opinion

Image by BonzoESC

Filed Under: Blog, Employee Engagement Tagged With: aviation, blame, error proofing, video

About the Author

James Lawther
James Lawther

James Lawther is a middle-aged, middle manager.

To reach this highly elevated position he has worked in numerous industries, from supermarket retailing to tax collecting.  He has had several operational roles, including running the night shift in a frozen pea packing factory and carrying out operational research for a credit card company.

As you can see from his C.V. he has either a wealth of experience or is incapable of holding down a job.  If the latter is true this post isn’t worth a minute of your attention.

Unfortunately, the only way to find out is to read it and decide for yourself.

www.squawkpoint.com/

Comments

  1. Mark H. Davis says

    3 January, 2014 at 4:39 pm

    Hi James. Happy New Year!

    Thanks for sharing this story about Bob Hoover. His gesture was indeed a noble one. I know I would hesitate to place my life in the hands of someone who had nearly ended it — unless I knew that the risk of it happening again had been removed. I’m wondering, how could he know that the fueler would not become distracted somehow? Did he not realize that the same flaw that had allowed the error still existed? Guess it was a risk he was willing to take.

    As noble as his gesture was, it may not be best answer from an organizational standpoint — trusting that an operator has learned a lesson and will do better next time. The goal is to negate the chance of the mistake happening again, regardless of operator. His response was more operator-centered than process-based. Unfortunately, this is an all-too-frequent result of various root-cause analysis efforts — they center on the person, punishment, etc., rather than the process and environment that led to the error. Glad to hear the example above eventually led to a simple structural change to prevent the error from happening again. One less thing for the operator — and, in this case, the fliers/passengers — to remember and worry about.

    Thanks again for sharing.

    Reply
    • James Lawther says

      4 January, 2014 at 9:34 am

      I totally agree Mark. I think the key is for the two approaches to go hand in hand. Don’t blame the person, fix the system.

      James

      Reply
  2. Ilkka Toijala says

    4 January, 2014 at 10:17 am

    Hello James,

    Thank you for the story. For me it brings up a couple of very important points.
    The first is how we react on mistakes. I’m convinced and it is my experience that the vast majority of people want to do their job as good as possible. This means that in most cases we find the root cause of mistakes or bad performance in the way the work is organized, what kind of tools or facilities we have or how the people are trained.The blame culture seems somehow to be the natural reaction and it is not easy to keep the investigation of the issue on the facts without claiming the people. Here the behavior of the management is very important. It takes years of consistent work to create such a culture, but it does not take much to harm it. The reward is that the real reasons are understood and can be worked out. The way we react has a big influence in the working atmosphere. People who feel safe, fare handled and empowered feel good about the work and can and want to achieve excellent results.
    The other issue is that in some cases as in this story systems are designed so that a mistakes are just waiting to happen. When designing work processes, tools and systems we should always seek to minimize the risk of mistakes. In many cases simple low cost solutions may reduce the risk considerably.

    Regards
    Ilkka

    Reply
    • James Lawther says

      4 January, 2014 at 10:56 am

      Ilkka,

      Thanks for your comment, I totally agree with your points, particularly how long it takes to create such a culture and how quickly it can be destroyed.

      James

      Reply
  3. Adrian Swinscoe says

    4 January, 2014 at 3:03 pm

    Hi James,
    Your story reminds of a situation in the second season of The Wire (I’m currently ploughing through the box set), where Lt. Cedric Daniels brings Sgt. Ellis Carver back onto his team after his was disloyal in the first series. Lt. Daniels’ rationale was that Carver, currently on traffic duty, was less likely to make the same mistake twice.

    Like Hoover’s situation, this illustrates the perspectives that Hoover and Daniels take when it comes to people….believing that is does not good to rest on blame and positively believing in the potential of people.

    Fixing the system is one thing but to get the most out of people we also have to believe in them.

    Adrian

    Reply
    • James Lawther says

      13 January, 2014 at 6:37 am

      I suppose for the best outcome you should do both.

      Glad you are enjoying your box set

      James

      Reply
  4. maz iqbal says

    18 January, 2014 at 11:33 am

    Hello James

    I thank you for sharing this story. I find myself touched by the story and in particular Bob Hoover’s behaviour. It occurs to me that I would love to imagine myself acting as calmly-generously as Bob Hoover did. The reality, is that just about every part of my being would be screaming at the “idiot’ who almost got me killed.

    Stepping beyond the gap between my being and Bob Hoover’s being, it occurs to me that Bob Hoover has a deep insight into human nature. It occurs to me that he is operating from the stance that being cooperative is as fundamental to a human being as is being competitive. And there is absolutely that generates trust-gratitude then being forgiven (for a huge mistake) and being trusted with one’s life. Imagine you were the guy who had put the wrong fuel in. That you realised what you had done. And Bob related-interacted with you as he describes in his autobiography. How would you go about refuelling his plane? Would you not take every care in the world? Would you want to let Bob down?

    All the best
    maz

    Reply
    • James Lawther says

      21 January, 2014 at 7:12 am

      I do wonder Maz how long Mr Hover sat on the hill waiting to be picked up.

      It would have taken me more than a little while to calm down

      James

      Reply
  5. Bindiya R says

    13 February, 2014 at 8:38 am

    James,

    I am really not sure whether I can be very cool headed at that time. As human beings we all tend to lose control at times but I feel it is natural. I can be “reactive or responsive” based on the situation and act accordingly.

    Reply
  6. Peter Cox says

    13 February, 2014 at 10:14 am

    All
    I have worked for many managers, the ones that have moved me forward as a worker & person were the ones that never apportioned blame. they were pragmatic, first reactions were deal with mistake, 2nd what did you(we) learn, finally don’t make the same mistake again, closed & move on!

    When the blame game starts or people constantly work in a way that enables them to “CYA” all sensible productivity is lost in route causing, learning & building relationships of trust. You end up with “villains” & “hero’s”, who always need to be seen in the limelight as the go to people for solving everything.

    Culture drives this within companies, do as I do not do as I say, lead by example as from the film Remember the Titan’s “Attitude reflects leadership”.

    Reply
  7. James Lawther says

    14 February, 2014 at 8:44 am

    It is very difficult, I think Peter explains the way we should behave, but Bindiya explains the way most of us do.

    I suppose the trick is to go out and take a — long — walk before you respond.

    Easier said than done.

    Reply
  8. Luke Pollard says

    20 February, 2014 at 3:35 am

    Great story. We have a term on the Blue Bus for this we call an “Excellent Failure”.
    If Hoover didn’t see this simple error as an Excellent Failure a few things may have happened;
    1) They would have sacked the fuel fuel boy as the answer/ solution.
    2) Someone else would have had to invent the Hoover nozzle to eliminate it happening again.
    3) They would have implemented a checklist, & a check the check list, & an audit to make sure the correct process was being followed.
    All 3 actions unfortunately lead to waste & mediocrity.

    Reply
  9. joe says

    20 November, 2014 at 6:22 pm

    Hoover is well known to embellish stories. The crash did in fact happened but the rest is probably tale.

    Reply
    • James Lawther says

      23 November, 2014 at 4:26 pm

      Probably Joe, but we all like a tall story

      Reply
    • David says

      8 October, 2019 at 7:18 pm

      I was there when the event happened and I witnessed the conversation between Mr Hoover and the young man who filled his aircraft with jet fuel. What is written is accurate. There was no a tall story.

      Reply
  10. Fred George says

    15 August, 2016 at 7:05 pm

    James,

    You’ve made an error in writing at your website that Bob Hoover had an accident in his Rockwell International Shrike Commander in 1989 at San Diego Brown Field. It’s understandable, considering that Mr. Hoover, himself, writes that it occurred in 1989 in “Forever Flying”, his autobiography.

    The accident actually occurred on May 27, 1978, according to NTSB records:

    http://www.ntsb.gov/_layouts/ntsb.aviation/brief.aspx?ev_id=42434&key=0&queryId=e2107cea-4764-402b-b0c9-08de9f277398&pgno=1&pgsize=20

    Bob and I discussed the event. He now recalls that it indeed did occur in 1978 and not 1989.

    All the best from San Diego, some 25 miles north of Brown Field.

    Reply
    • David says

      8 October, 2019 at 7:28 pm

      Correct, the crash occurred during an airshow at Browns Field Airport in San Diego. I was 15 years old at the time and worked at the restaurant at the AP Operations facility. There was a small control tower above Ops. I was in was in the tower when i heard the may day on the radio and witnessed the crash. It was like watching a movie as the air craft went down behind a small hill north of the air field. I was even in the restaurant when Mr Hoover spoke to the refuel tech. The conversation went exactly as written. Mr Hoover surprised us all by his poise and respect he showed to everyone involved. I will never forget that day

      Reply
      • James Lawther says

        9 October, 2019 at 9:04 pm

        Thanks very much for the story David

        Reply
  11. Dean says

    19 March, 2019 at 7:50 pm

    Great story! It’s also a featured tale in chapter one of How to Win Friends & Influence People.

    Reply
    • James Lawther says

      21 March, 2019 at 7:15 pm

      I probably stole it from there Dean :) Thank you for reading

      Reply

Trackbacks

  1. If Somebody Made a Mistake that Nearly Killed Y... says:
    5 January, 2014 at 7:54 pm

    […] In 1989 an air show was held at Brown Field in San Diego. The test pilot Bob Hoover was taking thrill seekers for flights in his Shrike Commander, a small, piston powered, passenger plane. The pas…  […]

    Reply
  2. Med Flight Down - Page 3 - Airline Pilot Central Forums says:
    10 September, 2014 at 4:58 am

    […] This is it: If Somebody Made a Mistake that Nearly Killed You […]

    Reply

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Explore

accountability assumptions beliefs best practice blame bureaucracy capability clarity command and control communication complexity continuous improvement cost saving culture customer focus data is not information decisions employee performance measures empowerment error proofing fessing up gemba human nature incentives information technology innovation key performance indicators learning management style measurement motivation performance management poor service process control purpose reinforcing behaviour service design silo management systems thinking targets teamwork test and learn trust video waste

Receive Posts by e-Mail

Get the next post delivered straight to your inbox

Creative Commons

This information from The Squawk Point is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.
Creative Commons Licence
Customer Experience Update

Try This:

  • Fish Bone Diagrams – Helpful or Not?

  • Solutioneering

  • Circles of Influence: Do You Want Your Team Flexing Their’s?

  • Should You Punish Mistakes?

Connect

  • E-mail
  • LinkedIn
  • RSS
  • YouTube
  • Cookies
  • Contact Me

Copyright © 2025 · Enterprise Pro on Genesis Framework · WordPress · Log in