← Civil & Structural Studio
Concept Explainer · Civil & Structural

Structural Redundancy

Why losing one member shouldn't bring down the whole building — and why it sometimes does anyway.

Structural redundancyis a system's ability to redistribute load onto alternate paths when one member, connection, or support is damaged or removed. A redundant structure has more than one independent route for gravity and lateral load to reach the ground at any given location, so losing any single element forces the load it was carrying to find another way through — not to disappear into a collapse. A structure with only one path at a given location has no such option. Lose the one critical link and the load it was carrying simply has nowhere to go. That single fact is the entire mechanism behind progressive collapse.

Same lost column, two different outcomes

Elevation view
NON-REDUNDANT — ONE LOAD PATHREDUNDANT — MULTIPLE LOAD PATHSfloor above (two independent simple spans)columncolumninterior columnlost (impact / blast / error)no adjacent path — spans dropload from this bay has nowhere else to gosoilfloor above (continuous over columns)columncolumnsame interior columnlost, same eventload redistributes sidewaysthrough the continuous beamfloor above stays intact — adjacent columns pick up the extra sharesoil
Independent load paths to ground, at that bay
1
Two simply-supported spans, each fully dependent on the one interior column. No continuity means no detour.
Independent load paths to ground, at that bay
2+
A continuous beam ties the bay to its neighbors, so the adjacent columns can absorb the redistributed share.
The Setup

A local failure only stays local if there's somewhere else for the load to go

Every structure is built to survive its normal design loads with margin. What redundancy addresses is a different question entirely: what happens after an abnormalevent — a vehicle impact, an explosion, a fire, a design or construction error — removes a member the design never planned on losing? In a non-redundant structure, that member was the only route the load above it had to reach the ground. When it's gone, that load doesn't reduce itself to fit whatever is left; it has to go somewhere, immediately, and if nothing was built to receive it, the result is failure of whatever is nearby — which is exactly how a local, contained incident turns into a structural collapse.

How a local failure becomes a disproportionate collapse — or doesn't

Chain reaction
WITHOUT REDUNDANCY / TIES — cascade1. Local failureone column lost2. Adjacent memberssuddenly overloaded3. Those members fail too4. Disproportionate collapsedamage far larger than the initial lossWITH REDUNDANCY / TIE FORCES — arrested1. Same local failureone column lost2. Floor hangs / redistributesvia alternate paths & tie forcesCollapse arresteddamage stays local to one bayno cascade beyond the initial loss
Steps from local loss to full collapse
Uncontrolled
Each failed member dumps its load onto neighbors that weren't designed to receive it — the cascade only stops when it runs out of structure.
Steps from local loss to full collapse
1, by design
Redundant paths and tie forces catch the redistributed load at the very next member, so the damage never propagates past the original bay.
Why this works

Redundancy doesn't prevent the initial loss. It contains what happens next.

No practical design can guarantee that a column or connection will never be damaged — vehicles hit buildings, gas lines explode, fires burn hotter than assumed, and construction errors happen. Robustness-focused design accepts that an initial local failure can occur and asks a narrower, more answerable question: if it does, does the rest of the structure have somewhere to send the load it was carrying? Three design responses answer that in practice. Key element design gives specific critical members — ones with no alternate path — extra capacity to resist abnormal loads directly. Alternate load paths (structural redundancy) mean no single member is truly irreplaceable, because the framing itself can reroute load around a gap. Tie forces and catenary action let a floor system hang in tension from the structure beside it if a column below is lost, rather than simply falling. Together these are usually grouped under structural integrity or robustness provisions — a layer of design that sits on top of, and is separate from, simply sizing each member for its own expected load.

Common misconception
"As long as every member has an adequate safety factor for its own load, the building is safe from a major collapse."

False, and it's a dangerous gap precisely because the first half of the sentence is true. A member's safety factor protects against that member failing under its own normal design load — it says absolutely nothing about what happens to the rest of the structure if that member is lost anyway, for a reason it was never designed against: an impact, an explosion, a fire, a design or construction error. A building made entirely of individually well-designed, adequately-safety-factored members can still be highly vulnerable to progressive collapse if it has no redundant load paths and no tie-force continuity between members — because the moment any one of those well-designed members is removed by an abnormal event, the load it carried has to land somewhere, and "somewhere adequate" is not guaranteed just because every member passed its own individual check. This is exactly why structural integrity and robustness requirements exist as a design consideration separate from ordinary member-by-member strength design — they ask what happens after a member is gone, which no individual safety factor can answer on its own.

Related Concept Explainers
Load Path & Tributary Area — What's Actually Different
Read it →
Key Element Design — Engineering for Abnormal Loads
Coming soon

Structural Redundancy & Progressive Collapse — Concept Explainer

Explains structural redundancy — a system's ability to redistribute load onto alternate paths when a member, connection, or support is lost — and why its absence is the underlying mechanism of progressive collapse, where a single local failure cascades into damage disproportionate to its cause.

Why This Is Commonly Misunderstood

It's intuitive to assume a building is safe from major collapse as long as every member carries an adequate safety factor for its expected load. That reasoning only covers ordinary conditions. It says nothing about what happens if a member is removed anyway by an abnormal event — vehicle impact, gas explosion, fire, or a design or construction error the original safety factor was never meant to cover. Whether the rest of the structure can survive that loss is a separate question, answered by redundancy and structural-integrity design, not by member-level safety factors.

The Mechanics

A redundant structure has more than one independent path for gravity and lateral load to reach the ground at a given location — beams continuous over multiple supports, moment connections, or tie reinforcement let load redistribute sideways to adjacent columns if one support is lost. A non-redundant, single-load-path structure has only one route at that location; when the critical member fails, the load it carried has no alternate path, and the overload lands on whatever is nearest. Those adjacent members, suddenly carrying load they weren't designed for, can fail in turn — an initial local failure triggering the next, cascading into a collapse far larger than the original damage. This is progressive (or disproportionate) collapse.

Where This Matters

Three design strategies are the practical answer: key element design gives specific irreplaceable members extra capacity to resist abnormal loads directly; alternate load path design (redundancy) builds in more than one route so no single member is truly critical; and tie force / catenary action design lets floor systems hang in tension from adjacent structure if a supporting column below is lost. Collectively these fall under structural integrity or robustness provisions — the design layer, distinct from ordinary member sizing, that governs what happens to a building after it has already lost a piece of itself. This reasoning underlies alternate-path analysis methods used in blast- and impact-resistant design guidance and post-9/11 building code provisions for disproportionate collapse.

Frequently asked questions

What is structural redundancy?

Structural redundancy is a structural system's ability to redistribute load onto alternate paths if one member, connection, or support is damaged or removed. A redundant structure has multiple independent routes for gravity and lateral load to reach the ground at any given location, so the loss of any single element forces load to redistribute through the remaining structure instead of triggering a collapse.

What is progressive collapse and what causes it?

Progressive collapse is a chain reaction in which an initial, local structural failure (one member or connection) overloads adjacent members that weren't designed to carry the redistributed load, causing them to fail as well, which overloads further members in turn — producing a collapse disproportionately larger than the original local damage. It happens specifically when a structure lacks alternate load paths at the point of the initial failure.

Does having a high safety factor on every member prevent progressive collapse?

No. A member's safety factor protects that member against failing under its own normal design load. It does not address what happens to the rest of the structure if that member is lost anyway due to an abnormal event such as impact, explosion, fire, or a design or construction error. Preventing progressive collapse requires redundancy and tie-force continuity between members — a separate design consideration from individual member strength.

What is key element design?

Key element design is the practice of giving a specific structural element extra capacity to resist abnormal or accidental loading directly — used when that element genuinely has no practical alternate load path, so its own robustness has to substitute for redundancy at that location.

What are tie forces and catenary action?

Tie forces are horizontal and vertical tension connections detailed between structural members specifically so that, if a supporting column is lost, the floor system above can hang in tension from the adjacent structure (catenary action) instead of simply falling. This gives a structure an alternate way to carry the load even when the original compression/bending load path is gone.

How is this different from load path and tributary area?

Load path and tributary area (covered in the companion Concept Explainer) describe how load normally reaches the ground and how much of it each member is assigned under everyday conditions. Structural redundancy specifically addresses what happens after that normal load path is interrupted by the loss of a member — whether an alternate route exists, or whether the load has nowhere else to go.

🎓

Try our Civil & Structural Studio

More calculators, simulators, and guides for this discipline.

Related tools & guides

Load Path & Tributary Area — Concept ExplainerLoad-Path VisualizerBeam Reactions CalculatorFoundation Bearing Calculator