Fire, Landslide & Multi-Hazard

Every hazard so far has threatened a building while leaving the ground roughly in place. A landslide is different and frightening because the ground itself moves - and a building is only ever as stable as what it stands on. A landslide is the downslope movement of soil, rock or debris under gravity, and it can be a slow creep over years or a sudden, catastrophic collapse in seconds. It threatens buildings in two broad ways: a building below a slope can be buried, struck or swept away by material coming down; a building on or cut into a slope can be carried away, or have the ground pulled out from under its foundations, when the slope fails beneath it.

What triggers slopes to fail is worth knowing, because several triggers are things design and construction influence. Water is the great destabiliser: heavy or prolonged rain saturates a slope, adds weight and reduces the friction holding soil together, which is why landslides cluster in the monsoon and why drainage is central to hillside safety. Earthquakes shake slopes loose, which is one of the ways hazards combine. Undercutting - cutting into the toe of a slope for a road or a building platform, or removing vegetation whose roots bound the soil - removes the support that held it, a very common man-made trigger. Overloading the top of a slope, or poor drainage that channels water into it, does the same. Steep slopes, certain weak or layered soils, and previously disturbed ground are inherently more prone.

For the designer, landslides make siting and groundwork decisive. Building below an unstable slope or cutting carelessly into a hillside can doom an otherwise sound structure, while sensible siting, careful cut-and-fill, retaining structures, slope drainage and keeping vegetation can greatly reduce the risk - all developed in Module 2. The governing judgement - whether a slope is stable, how it will behave, what retaining and drainage it needs - is a matter of slope-stability analysis by a geotechnical engineer using site-specific soil data, never an assumption from the surface. The principle every designer must carry is simple and sobering: on a slope, the hazard is not only to the building but to the ground beneath it, and the ground must be understood before the building is placed.

Fire is a hazard in its own right, and in everyday terms the most common one a building will ever face. Unlike the natural forces in this module it is usually internal and human-related in origin - electrical faults, cooking, heating, stored fuels - but it behaves like the others in one key respect: the loss it causes depends enormously on how the building is designed, detailed and equipped. Fire safety is its own deep discipline, covered by dedicated codes and in Studio Matrx's Fire and Life-Safety course, and it turns on principles such as limiting how fire starts and spreads, compartmenting the building so fire is contained, protecting the structure so it does not collapse while people escape, providing safe escape routes, and enabling detection and suppression. The overriding aim is life safety: get everyone out, and keep the structure standing long enough to allow it.

What belongs squarely in a disaster course is the way fire couples with other hazards - above all fire following earthquake. Some of history's worst urban fire disasters were not started by a fire source at all but by an earthquake: the shaking ruptures gas lines and fuel stores, topples stoves, heaters and lamps, and severs electrical wiring, igniting many fires across a city at once. At the same moment, the earthquake has often broken the water mains that firefighters need, blocked roads with debris so engines cannot pass, and overwhelmed emergency services - so fires that would normally be controlled instead spread unchecked. The 1906 San Francisco earthquake is the classic case, where fire destroyed far more of the city than the shaking itself; the danger remains real in dense, gas-supplied cities today.

The lesson is that the hazards are not independent. A building may survive the shaking only to be lost to the fire that the shaking started, so seismic resilience and fire resilience have to be considered together - securing gas and fuel supplies with seismic shut-off where appropriate, protecting the structure against both shaking and fire, and recognising that post-earthquake firefighting may be crippled. The specifics - fire ratings, compartment sizes, escape provisions, detection and suppression, seismic gas shut-off - come from the fire and building codes, NBC 2016 Part 4, and fire-safety specialists. The principle for this module is that fire is both a standalone hazard and a frequent, dangerous consequence of earthquakes, and resilient design anticipates both.

The hard truth this module has been building toward is that real sites almost never face a single, isolated hazard. A coastal city in eastern India may face cyclones, storm surge, flooding and earthquakes. A Himalayan hill town may face earthquakes, landslides, flash floods and fire. A building must be resilient against the combination it actually faces, and the combination is often more than the sum of its parts. Three ideas capture how hazards interact. They can simply coincide - a site exposed to several independent threats, each of which must be designed for. They can compound - two hazards arriving together and adding their effects, as when a cyclone brings extreme wind and storm surge and flooding at once, so the building must resist wind uplift while standing in fast, deep, debris-laden water. And they can cascade - one hazard triggering another in a chain: an earthquake triggers a landslide and a fire; heavy rain triggers both flooding and slope failure; a dam failure triggers a flash flood.

Cascading and compounding failures are especially dangerous because defences designed for one hazard may be useless or even counterproductive against the next in the chain, and because the systems you would rely on for response - water, power, roads, communications - are often knocked out by the first event just as the second strikes. The collapse of one element can also propagate through a building or a settlement: a single failed retaining wall, roof or lifeline can set off a sequence far larger than the initial cause. This is why resilience is increasingly understood as a property of whole systems and settlements, not just individual buildings - a theme Module 8 develops.

For the designer, the discipline is to identify all the credible hazards for a site, not just the most obvious one, and to understand how they might combine and cascade, before committing to a design. That means engaging the right specialists early - structural, geotechnical, fire, coastal - and checking that a measure taken against one hazard does not worsen another. The multi-hazard assessment for a specific site, and the design that answers it, is specialist, code-governed work; the principle for every designer is to refuse the comforting fiction that hazards come one at a time, and to design for the messy, combined reality instead.

Designing for several hazards together is not simply doing each single-hazard design in turn and stacking them up, because measures can conflict as well as reinforce. The art - and it is one the architect is well placed to lead at concept stage - is to find the moves that help against several hazards at once, and to resolve the places where hazards pull in opposite directions, consciously rather than by accident.

Many good moves are synergies that serve multiple hazards. A continuous, well-connected load path resists both earthquake shaking and wind uplift. A simple, regular, compact building form behaves better in earthquakes *and* in wind. Elevating a building above the flood level also lifts it clear of some debris and scour. Good siting - off the floodplain, off the unstable slope, away from the eroding coast - reduces several hazards together. Robust, well-anchored construction and sound drainage help almost everywhere. These are the decisions to reach for first, because they multiply their value across the hazard profile.

But there are real conflicts that must be navigated with judgement and specialist advice. Making a building very heavy and massive might feel protective against wind, but it increases the earthquake inertia force - lightness and mass point in opposite directions for wind versus seismic, and the balance depends on which hazard governs. Elevating a building on slender columns to escape floodwater can create a soft, weak storey that is dangerous in an earthquake unless it is properly braced - a flood defence becoming a seismic flaw. Sealing a building tightly against wind-driven rain can conflict with the ventilation and escape needs of fire safety. Large openings for daylight and cross-ventilation are wonderful until they are the weak points a cyclone exploits. None of these conflicts means one hazard must simply lose; they mean the design must be resolved deliberately, by the whole team, with the specialists quantifying the trade-offs against the governing codes. The designer's job is to see the conflicts early, treat resilience as a single integrated problem rather than a stack of separate ones, and hand the engineers a concept that has already reconciled the hazards as far as design judgement can - which is exactly the integrated, principle-first resilience this whole course sets out to build.