Functional safety technical resource

What Is Fault Tree Analysis (FTA)?

Fault Tree Analysis (FTA) is a deductive, top-down method that starts with a defined undesired top event and uses logical relationships to model combinations of equipment failures, human actions, external events, and other conditions that can cause it. An FTA may be qualitative, quantitative, or both, but the diagram is only as defensible as its boundary, logic, dependency treatment, and source data.

Technical resource from Mangan Safety Instrumented Systems (Mangan SIS)

How a Fault Tree Is Built

The analyst first states the top event precisely, including the system boundary, operating mode, mission time, and success or failure criteria. The event is then decomposed through logic gates, commonly AND and OR relationships, into intermediate events and basic events at an appropriate level of detail. Transfer symbols can manage repeated branches, while event descriptions should be testable and unambiguous. The completed structure can identify minimal cut sets: the smallest combinations of basic events sufficient to produce the top event under the modeled logic.

Qualitative and Quantitative Uses

Qualitative review can expose single points of failure, shared dependencies, important combinations, and gaps in safeguards. Quantitative evaluation can estimate a top-event frequency or probability when event data and mathematical assumptions are suitable. That calculation requires deliberate treatment of units, exposure time, repair, testing, conditional events, common-cause failures, human reliability, and dependencies. Simply multiplying nominal component values as though all basic events were independent can materially misstate the result.

FTA Versus FMEA and Event Tree Analysis

FTA works backward from one defined undesired event to combinations of causes. FMEA works forward from individual item or process failure modes to their effects. Event Tree Analysis begins with an initiating event and branches forward through the success or failure of subsequent functions or barriers to possible outcomes. These techniques can complement one another, but they should not be treated as interchangeable; the study question should determine which direction and representation are appropriate.

Common FTA Quality Problems

A broad or ambiguous top event can create an unbounded tree, while a narrow boundary can omit utilities, software behavior, human actions, or external hazards. Other weaknesses include hidden dependencies, mixing probabilities and frequencies without a valid model, double-counting repeated events, and treating uncertain data as exact. Mangan SIS recommends an independent logic review, explicit assumption register, controlled source-data record, sensitivity checks for influential inputs, and revision when the process, architecture, or operating basis changes.

Mangan SIS project context

Apply Fault Tree Analysis (FTA) to documented SIS decisions

FTA can support process hazard analysis, investigation of complex protective-system failures, comparison of design alternatives, and quantitative risk modeling. In SIS work it may help show how sensor, logic-solver, final-element, utility, communication, and common-cause events combine, while the service pages remain the owners for risk studies and functional-safety project delivery.

Sources and scope

Use the source type that fits the decision

Standards

IEC 61025:2006 describes Fault Tree Analysis and provides guidance on its application, assumptions, events, failure modes, rules, and symbols. It is a general dependability-analysis standard rather than a process-industry regulation.

Guidance

IEC 61511-3:2016 illustrates hazard and risk assessment methods used to define safety functional requirements and determine required SIL. It provides a framework and examples but does not prescribe the SIL required for a particular application.

Regulation

OSHA 29 CFR 1910.119(e)(2) lists Fault Tree Analysis as one permissible PHA methodology for covered processes when appropriate. The regulation also requires the PHA to address specified topics, use a qualified team, resolve recommendations, and be revalidated and retained as required.

Mangan recommendation

Mangan SIS recommends defining the top event, boundary, units, mission time, dependencies, and stopping rules before quantification, then subjecting both the logic and influential data to documented review.

Primary references

Common questions

Clarifying Fault Tree Analysis (FTA)

Is Fault Tree Analysis qualitative or quantitative?

It can be either or both. The logical structure can identify event combinations and single vulnerabilities without numerical data. Quantitative results require suitable event data, consistent units, and a model that addresses dependencies, exposure, repair, testing, and other relevant assumptions.

What is the difference between FTA and FMEA?

FTA starts with a top event and works backward through combinations of causes. FMEA starts with individual failure modes and evaluates their effects. One is deductive and top-down; the other is generally inductive and bottom-up.

Does OSHA require Fault Tree Analysis for every covered process?

No. OSHA lists FTA as one of several permissible PHA methodologies. The employer must select one or more methods appropriate to the complexity and hazards of the covered process and meet the rest of the PHA requirements.

Need to understand a complex failure path?

Build a traceable model of the events, dependencies, and assumptions behind the top event.

Contact Mangan SIS

Downloadable term reference

Download: Fault Tree Analysis (FTA) – Functional Safety Glossary PDF

Save or share this term-specific reference, including the answer-first definition, engineering review considerations, and primary-source references.

Download the Fault Tree Analysis (FTA) PDF

Scroll to Top