Worked examples — Fault tree analysis (FTA) — top-down, AND - OR gates
Before anything else, one reminder of what the symbols MEAN, so we never use them un-earned.
The number keeps appearing — it is the survival probability of event (the chance it does NOT happen). Keep that phrase in your head; it is the hero of the OR gate.
The scenario matrix
Every FTA calculation you will ever meet is one of these cells. The examples below are labelled with the cell they hit, and together they cover the whole grid.
| Cell | Case class | What makes it tricky |
|---|---|---|
| A | Single OR gate, small | approximation vs exact |
| B | Single AND gate, small | how fast the product shrinks |
| C | Degenerate input | a perfect part in the tree |
| D | Degenerate input | a guaranteed failure in the tree |
| E | Mixed tree (AND under OR) | order of operations, dominant term |
| F | Limiting behaviour: many identical OR inputs | |
| G | Common cause failure (dependent) | independence assumption breaks |
| H | Real-world word problem | translate English into gates |
| I | Exam twist: "which improvement helps?" | sensitivity, dominant path |
| J | Large probabilities ( near 1) | sum-approximation blows up |
Cell A — Single OR gate, small probabilities
Forecast: Any one of three small failures kills solar. So the answer should be bigger than any single input but still small — guess "roughly the sum, about ."
-
Write each survival probability. Why this step? The OR formula is built from "did it survive?", so convert every failure into its opposite first.
-
Multiply the survivals — the chance ALL three stay healthy. Why? Independent parts all surviving is a joint event, and joint = product.
-
Subtract from 1. Why? "At least one failed" is the complement of "none failed."
Verify: Compare with the lazy sum . The exact answer is just below the sum — that tiny gap is the double-counting the sum ignores. Because the are small, sum ≈ exact. Sanity: answer sits between and . ✓
Recall Why is the exact OR answer always ≤ the sum of inputs?
The sum double-counts the "two fail at once" overlaps ::: the exact OR subtracts them out, so exact ≤ sum, with equality only in the limit of tiny probabilities.
Cell B — Single AND gate, small probabilities
Forecast: Both must break — much rarer than one. Guess "way smaller than ."
- Multiply the two failure probabilities. Why? AND = all inputs fail together = joint probability = product (for independent banks).
Verify: is smaller than either input (). That is redundancy doing its job — the AND gate crushed the risk. Units: still a bare probability, dimensionless. ✓

Look at the figure: the middle bar (OR gate of three inputs) is taller than the yellow reference line marking one single input (risk piles up); the right bar (AND gate of two inputs) is far shorter than that line (risk collapses). Same class of small inputs, opposite behaviour — that contrast is the whole point of the page.
Cell C — Degenerate input: a perfect part ()
Forecast: A zero-probability input contributes nothing to an OR. Guess "answer drops to the OR of just the other two."
- Survival of the perfect part is . Why this step? A part that never fails always survives.
- Multiply survivals: Why? times anything leaves it unchanged.
- Subtract: .
Verify: Compare to Cell A (). Removing the deployment risk dropped the total by — essentially the deployment probability. A perfect input in an OR gate is invisible — exactly what we expect. ✓
Cell D — Degenerate input: a guaranteed failure ()
Forecast: A guaranteed input on an OR gate guarantees the OR fires. Guess "."
- AND branch: (Why? both transponders must die.)
- Survival of HGA: . Why this step? A part that always fails never survives.
- OR formula: .
Verify: means certain failure — correct, because HGA alone (an OR input) is a single point of failure that is already broken. A input saturates an OR gate. (In an AND gate it would be invisible: — again exactly opposite to Cell C.) ✓
Cell E — Mixed tree (AND nested under OR)
Forecast: Two redundant transponders make the AND branch tiny; the lone HGA is exposed. Guess "HGA dominates, answer ≈ ."
- Solve the deepest gate first (AND). Why? You cannot evaluate a gate until its inputs are numbers; work inside-out.
- Feed that into the OR gate alongside HGA. Why? The AND result is now just one input to the OR.
- Compute survivals and multiply: .
- Subtract: .
Verify: The HGA contributes ; the whole answer is . So the redundant transponders add only — the HGA drives of the risk (). Matches the forecast. This is the payoff of FTA: it points a finger at the single point of failure. ✓

Read the figure top-down: the pink Loss of Comm box sits above a yellow OR junction with two branches. The left blue branch is the AND of the two transponders (); the right pink branch is the lone HGA (). The yellow arrow points at the HGA branch — that dominant OR input is where nearly all the risk lives, and it is the box a designer must attack first.
Cell F — Limiting behaviour: many identical OR inputs
Before this example we need one more tool, and we build it from zero.
Forecast: Even tiny risks, piled into an OR gate over and over, must creep upward. Guess "107 of them gives a few percent; infinitely many → certain failure."
- General formula: all identical, so . Why? The OR formula multiplies the survival factors ; when every factor is the same number , multiplying it times is raising it to the power .
- : . (One mechanism = its own risk.)
- : .
- : , so .
Verify: Check with the logarithm trick just defined. Why logs? Multiplying by itself 107 times by hand is brutal, but the power-slides-out rule turns it into one multiplication: . Since (the log of a number just below 1 is a small negative), the exponent is , and the antilog , giving . ✓ Lesson: an OR gate over many parts is a slow poison — this is why JWST demanded per-mechanism reliability of ; with each, , a coin-flip mission. Compare in Reliability Block Diagrams — an OR gate of failures is a series chain of survivals.

The curve in the figure is climbing with the number of OR inputs . The yellow dot marks (risk , barely off the floor); the pink dot marks (risk jumped to ); and the dotted line at the top shows the ceiling that the curve creeps toward as . Watch how a "negligible" per-part risk becomes a real threat once you stack enough of them under one OR.
Cell G — Common cause failure (dependence breaks the formula)
Forecast: The naive AND said . But a shared cause creates a "both fail together" shortcut. Guess "much bigger than — the regulator dominates."
- Why the naive product is wrong. The formula assumes independence. A common cause violates that: one event flips both at once. Multiplying pretends that never happens.
- Split each transponder's total risk into shared + independent. Each transponder's total is made of the shared regulator () PLUS its own independent modes. So the independent-only part is . Why subtract? The is already counted in the shared term; if we also left it in we would double-count it.
- Both fail from their own independent causes: .
- OR the shared cause with the independent double-failure. Why OR? Either route makes both transponders dead: the regulator dying, OR both independently dying.
- Compute: , so .
Verify: True answer vs naive — the shared regulator makes the "redundant" pair about 80× more likely to both fail (). The independent double-failure () is utterly negligible next to the shared ; the regulator IS the risk. The redundancy is an illusion until you power the two transponders separately. See Boolean Algebra and Logic Design for why we must add the regulator as its own basic event rather than hide it. ✓
Cell H — Real-world word problem (translate English → gates)
Forecast: Three redundant wheels → tiny AND. Lone star tracker → the exposed OR input. Guess "≈ , tracker-dominated."
- Translate the English. "At least one wheel needed" = "lost only if all fail" = AND of three wheels. "Star tracker has no backup" = OR input at the top. Why this step? Gates come from redundancy words: all/both → AND, any/either → OR.
- Wheel AND gate: . Why cube? Three independent wheels all failing is the product .
- Top OR gate: . Why? The wheel-AND result is now one OR input alongside the star tracker.
- Compute survivals and multiply: , so .
Verify: Answer vs star-tracker alone — the three wheels add only . If a designer wanted to spend money, adding a second star tracker (making it an AND branch, ) would slash the top risk far more than a fourth wheel would. Matches Spacecraft Redundancy Architectures intuition. ✓
Cell I — Exam twist: "which single improvement helps most?"
Forecast: The HGA is the dominant term, so fixing it should win by a mile. Guess "(a)."
- Option (a): HGA becomes AND of two. New HGA branch . Why? Two identical antennas both must fail.
- Option (b): transponders improved. AND branch .
- Compare. (a) drops the risk from to (a improvement). (b) barely moves it — .
Verify: Option (a) wins overwhelmingly, confirming the forecast. Exam lesson: always attack the dominant OR input first — improving a term that is already negligible (the transponders) wastes budget. Find dominant paths with Minimum Cut Sets before spending a single dollar. ✓
Cell J — Large probabilities ( near 1)
Forecast: With numbers this big, the "sum ≈ OR" trick from Cell A must break — the sum is already above 1, which is impossible for a probability. Guess "the true OR is high but stays below 1; the AND is a modest fraction."
- Survival probabilities. Why? The OR formula still runs on "did it survive?", no matter how big the failure risks are.
- Multiply the survivals — chance all three survive. Why? All-survive is still a joint event = product.
- OR result: .
- AND result: multiply the failure probabilities directly. Why? AND = all fail together = product of the themselves.
Verify: The lazy sum gives — a nonsense "probability" above 1, so the small-number shortcut has completely failed here; only the exact formula is trustworthy. Sanity: sits in . ✓ Notice the OR () is far bigger than the AND () — the same gap-between-gates from Cell B, but now dramatic because the inputs are huge. Lesson: the "OR ≈ sum" rule is only safe when every is small; near you MUST use the survival-product form.
Connections to Spacecraft Design
Beyond these cells, FTA feeds directly into Monte Carlo Reliability Simulation (when probabilities themselves are uncertain), Failure Modes and Effects Analysis (FMEA) (the bottom-up complement), and the Single Point Failure Review (which hunts exactly the OR inputs that dominated Cells E, I, and J).
Active recall
Recall In an OR gate, what does a
input do, and what about ? is invisible (survival , changes nothing). saturates the gate to (certain failure) ::: opposite of an AND gate, where forces the gate's failure to (guaranteed success for that branch) and is invisible.
Recall Two "redundant" units share one power supply. Why is
wrong? That formula assumes independence; the shared supply is a common cause that fails both at once ::: model it as a separate basic event OR-ed with the independent double-failure — and remember to subtract the shared risk from each unit's total before squaring the independent part.
Recall Given a mixed tree, which gate do you evaluate first?
The deepest gate (inputs must be numbers before a gate can be computed) ::: work inside-out, bottom-up.
Recall When is the "OR ≈ sum of inputs" shortcut safe?
Only when every is small ::: near the sum can exceed 1 (impossible), so you must use the exact survival-product form .