Fault Tree Analysis, or FTA, is a deductive method used to analyze how combinations of failures or conditions can produce a specific undesired event.
The analysis starts with the top event.
Then the team works backward to identify the events that could cause it.
Logical relationships are used to show whether causes must occur together or whether any one of several causes is sufficient.
Start with a precise top event
The top event should describe a specific failure.
Weak:
Machine problem.
Stronger:
Packaging line stops because the main conveyor cannot move product.
The clearer the top event, the more useful the tree.
OR gates
An OR relationship means any one of the listed events can produce the higher-level event.
For example:
Conveyor stops if:
- drive motor fails; OR
- safety circuit opens; OR
- gearbox jams.
Each branch can be investigated further.
AND gates
An AND relationship means multiple conditions must occur together.
For example:
A redundant pumping system loses flow only if:
- Pump A unavailable; AND
- Pump B unavailable.
This is important because system risk can depend on combinations rather than single failures.
FTA vs Fishbone
A Fishbone Diagram is useful for organizing possible causes around categories.
FTA is more explicit about logical relationships between events.
Use Fishbone when broad cause generation is useful.
Use FTA when system logic, combinations, and failure pathways matter.
FTA and Root Cause Analysis
Root Cause Analysis is the broader discipline of investigating why a problem occurred.
FTA can support RCA by showing possible pathways to the event.
The tree should not be treated as proof.
Events still need evidence.
FTA and FMEA
FMEA usually works forward from potential failure modes and asks about their effects.
FTA works backward from a defined undesired event and asks what could cause it.
The methods are complementary.
FMEA is often useful for prevention during design or process planning.
FTA is useful when a particular top-level failure needs deeper logical analysis.
Add probability carefully
Fault trees can be quantified when reliable event probabilities are available.
This can help estimate system-level risk.
But poor input data creates false precision.
A qualitative FTA can still be valuable because the logic itself exposes combinations, dependencies, and weak controls.
Common mistakes
Using a vague top event, mixing causes and symptoms, building the tree from opinion without evidence, treating all branches as equally likely, and assuming the diagram itself proves causation are common mistakes.
Practical sequence
- Define the top event.
- establish system boundaries.
- identify immediate causes.
- connect them with AND or OR logic.
- decompose each branch.
- identify basic events.
- review dependencies and common causes.
- verify the important branches with evidence.
- identify prevention or detection controls.
- update the analysis when the system changes.
The practical lesson
Fault Tree Analysis is useful when a failure can result from several interacting pathways.
The tree helps teams reason about those pathways before deciding where prevention effort should go.