Fault Tree Analysis (FTA)

Fault Tree Analysis (FTA) is a structured, top-down method used to analyze how combinations of component, process, or human failures can lead to a defined undesired event, such as a safety incident, equipment failure, or critical nonconformance. It represents the logical relationships between basic faults and the top event in a graphical tree using standardized symbols and logic gates.

How Fault Tree Analysis works

FTA typically starts with a clearly defined top event (for example, “loss of containment in reactor” or “incorrect part installed on aircraft assembly”). The analysis then proceeds by repeatedly asking what conditions or failures could cause that event, and mapping them in a tree-like structure:

• Top event: The system-level failure or hazardous condition being analyzed.
• Intermediate events: Higher-level causes that can contribute to the top event.
• Basic events: Lowest-level causes that are not further decomposed (e.g., component failure, human error, software fault, incorrect parameter).
• Logic gates: Symbols (commonly AND and OR gates) that show how combinations of events lead to higher-level failures.

In regulated manufacturing and safety-critical industries, FTA is often used to:

• Identify combinations of failures that could lead to hazardous conditions or noncompliant product.
• Support risk assessments, safety cases, and reliability analyses for complex systems.
• Provide a traceable structure for investigations and root cause analysis, especially where evidence must support regulatory or customer review.

Use in industrial and regulated environments

Within industrial operations, FTA commonly appears in:

• Process and equipment design: Evaluating how instrument, control, and mechanical failures can propagate through a production line, production cell, or automated system.
• Safety and risk management: Supporting functional safety, hazard analysis, and risk mitigation activities, especially where formal justification of risk controls is required.
• Quality and reliability engineering: Mapping failure paths that could lead to scrap, rework, escapes, or field failures, often in conjunction with FMEA and other analysis methods.
• Root cause analysis: Providing a structured, evidence-based fault-tree-style investigation when simple tools (such as 5 Whys) are not sufficient for complex or safety-critical issues.

FTA can be performed qualitatively, focusing on structure and logic of failure paths, or quantitatively, where probabilities are assigned to basic events to estimate the likelihood of the top event.

What FTA includes and excludes

FTA typically includes:

• Systematic mapping of potential failure paths for a single defined top event.
• Hardware, software, process, and human failure modes that can be logically combined.
• Explicit assumptions, conditions, and boundary definitions for the analysis.

FTA typically does not include:

• Bottom-up enumeration of all possible failure modes without a specific top event (that is more characteristic of FMEA).
• Project management, scheduling, or resource planning functions.
• Guarantees of system safety or compliance; it is an analysis tool, not a certification.

Common confusion

Fault Tree Analysis vs. FMEA: FTA is top-down, starting from a defined undesired event and working backward to identify contributing faults. Failure Modes and Effects Analysis (FMEA) is bottom-up, starting from component or process failure modes and examining their effects. In practice, both may be used together in manufacturing and regulated environments.

Fault Tree Analysis vs. 5 Whys / Ishikawa diagrams: 5 Whys and fishbone (Ishikawa) diagrams are simpler tools often used for early problem structuring. FTA is more formal and logic-based, and is commonly used when a rigorous, documented analysis of system failures is required.

Connection to root cause and investigations

In aerospace, pharmaceutical, medical device, and other regulated sectors, FTA-style analysis is frequently used as part of root cause analysis and safety investigations. The fault tree structure helps document how evidence supports specific failure paths, how alternative paths were evaluated, and where controls or design changes may interrupt those paths.