Today’s post is part of a special series here on Planet Pailly called Sciency Words. Each week, we take a closer look at an interesting science or science-related term to help us all expand our scientific vocabularies together. Today’s term is:
The chief engineer marched herself up to the captain’s ready room, saluted, and stood at attention. The captain leaned back in his chair, reading the chief engineer’s report.
“So the starboard engine pod just exploded?” the captain said. “For unknown reasons?”
“Yes, sir,” the engineer replied. “I cannot explain it. My team has no idea what happened. The circumstances of the explosion are so unusual that we don’t even know where to start.”
“Well, couldn’t you start with a fault tree analysis?”
I first encountered the term “fault tree” in an article about the recent Space X rocket explosion (click here, it’s an interesting read). I then read more about fault tree analyses in NASA’s Fault Tree Handbook for Aerospace Applications (click here, but I’ll warn you it’s pretty dull reading).
Basically, a fault tree analysis is a method of evaluating all the things that could go wrong to produce an undesirable result (like your engine pod mysteriously blowing up). Fault trees are sort of like flow charts, and they look something like this:
As I understand it, you start from the bottom of the chart are work your way up. Which subsystems failed? How did those subsystem failures affect the main systems, potentially leading to the “top event” on your chart?
One of the key advantages to using a system like this is that it can show how two or more seemingly unimportant problems can combine to cause bigger problems farther up the tree.
According to NASA’s Fault Tree Handbook, fault tree analyses have become fairly standard for space flights ever since the space shuttle Challenger disaster in 1986. A good, well thought out fault tree can not only help figure out what caused an accident, but it can also help determine what might go wrong before an accident even occurs.
“Oh, right,” the chief engineer said, chuckling at her own foolishness. “A fault tree analysis! That’s been standard procedure since, what… the the 20th Century?”
The captain nodded.
“Sorry, Captain. Sometimes I forget I’m a real engineer and not a character in a science fiction story.”
“Happens to the best of us,” the captain said. “Carry on.”
P.S.: I have been having a really rough writing week this past week. I wonder if writer’s block can be diagrammed with a fault tree.