Consequence Modeling — Dispersion, Fire & Explosion

By Johnson on July 30, 2026

consequence-modeling-dispersion-fire-explosion

A release of flammable or toxic material doesn't become a real hazard until someone can say how far it will travel, how hot it will burn, or how hard it will hit. Consequence modeling turns a hypothetical loss of containment into a specific radius on a map — a toxic plume boundary, a jet fire's flame length, the overpressure ring from a vapor cloud explosion — so that emergency response plans, evacuation zones, and equipment spacing are based on physics rather than guesswork. Tools like PHAST, FLACS, and EFFECTS each model a different piece of that picture, and picking the wrong one for a given scenario is a surprisingly common mistake in facility siting work. A demo can show how modeled consequence zones connect directly into emergency response planning.

Consequence Modeling
Consequence Modeling for Dispersion, Fire & Explosion
Toxic dispersion, jet fires, pool fires, BLEVEs, and vapor cloud explosions — modeled with the right tool, for emergency planning that holds up under scrutiny.

Why a Hazard Needs a Number, Not Just a Name

Knowing that a vessel contains a flammable or toxic material isn't the same as knowing what happens if it releases. Consequence modeling takes a defined source term — a hole size, a pressure, a phase of release — and works forward through discharge, dispersion or combustion, to a physical endpoint: a toxic concentration boundary, a radiant heat footprint, or an overpressure contour. That endpoint is what actually drives decisions during facility siting, quantitative risk assessment, and emergency response planning, because a plant can only size an evacuation zone or a control-room blast wall correctly if it knows the real distance the hazard reaches, not an assumed one.

Getting this wrong in either direction carries a cost. Undersizing a hazard zone leaves people and equipment inside a boundary that looks safe on paper but isn't. Oversizing it wastes money on separation distances, protective structures, or evacuation radii that were never actually necessary, and it can erode trust in the modeling process itself the next time a number gets questioned.

Five Scenarios, Five Different Physics

Toxic Dispersion
A released chemical forms a plume whose reach depends on release rate, wind speed, and atmospheric stability. The endpoint that matters is the distance to a defined toxic concentration threshold, not the release itself.
Jet Fire
A pressurized release that ignites immediately burns as a directional flame. Flame length and radiant heat intensity, not the total inventory released, determine how far equipment needs to sit from the source.
Pool Fire
A liquid spill that ignites burns from a spreading pool. Pool diameter, burn rate, and containment geometry drive the radiant heat footprint far more than the chemical identity alone.
BLEVE & Fireball
A vessel failing under fire exposure can release its contents almost instantly as a rising fireball. The event is short, often seconds, but the thermal radiation intensity during that window can be extreme.
Vapor Cloud Explosion
A flammable cloud that ignites after drifting into a congested or confined area can accelerate into an explosion. Overpressure, not flame reach, is the endpoint that governs structural and personnel risk.

Choosing the Right Modeling Tool

ToolBest Suited ForWhy It's Used
PHAST / Safeti Dispersion, pool and jet fires, BLEVE, toxic effects Covers the full release-to-endpoint chain in one integrated package
FLACS Gas dispersion and explosion in congested or confined 3D geometry CFD-based modeling captures how equipment density changes overpressure
EFFECTS Source term, dispersion, fire and explosion calculations Built on the TNO Colored Books methodology used widely in facility-wide QRA

Common Modeling Mistakes That Undersize Real Risk

Wrong Endpoint
Modeling to a general concentration threshold instead of the specific toxic or flammable endpoint relevant to the receptor produces a hazard zone that looks precise but answers the wrong question.
Stale Congestion Data
Running an explosion model against an old equipment layout after new piping or vessels have been added understates overpressure in exactly the areas that changed.
Single Weather Case
Modeling only one stability class and wind speed, rather than the range a site actually experiences, can miss the worst-case dispersion distance entirely.
Ignoring Rainout
Treating a pressurized liquid release as a pure vapor release when some of it will fall out as a liquid pool skips an entire secondary hazard the model should be capturing.

Inputs That Actually Drive Accuracy

Release
Hole size, operating pressure, and phase of release set the source term every downstream calculation depends on.
Weather
Atmospheric stability class and wind speed change how far and how concentrated a dispersing plume remains.
Layout
Congestion and confinement around the release point are what turn a flash fire into a damaging vapor cloud explosion.
Ignition
Whether ignition is immediate or delayed changes the entire scenario, from a contained jet fire to a drifting flammable cloud.
Receptors
Where people, control rooms, and escape routes actually sit relative to the modeled zone decides what the number means in practice.
Terrain
Ground-level obstacles, elevation changes, and nearby structures can channel or slow a dispersing plume in ways a flat, open-field assumption will miss.
Get It Right the First Time
Don't Let a Bad Input Undersize Your Safety Zone
See how iFactory keeps process inputs feeding your consequence models accurate as conditions on site change.

Where Consequence Modeling Feeds Into Regulatory Compliance

Consequence modeling isn't just an internal engineering exercise — it's frequently the technical backbone behind a facility's regulatory submissions. OSHA's Process Safety Management standard and the EPA's Risk Management Program both expect a documented hazard analysis that can justify the separation distances, mitigation systems, and emergency planning zones a facility has chosen, and consequence modeling outputs are usually what that justification is built on. In jurisdictions covered by Seveso-style major accident hazard regulations, the same modeling underpins the safety report submitted to regulators.

The practical implication is that a consequence model isn't a one-time deliverable filed away after a siting study. Regulators and auditors periodically expect to see that the modeled scenarios still reflect current inventory, layout, and process conditions, which is why tying model review to the same management-of-change triggers used elsewhere in a process safety program keeps a facility's compliance position current rather than reactive.

From Model Output to Emergency Response Plan

A consequence model is only useful once its output becomes a decision. A dispersion boundary needs to translate into a shelter-in-place or evacuation radius that responders can actually use. A jet or pool fire's radiant heat footprint needs to inform equipment spacing and fireproofing specs before construction, not after. A vapor cloud explosion's overpressure contour needs to drive control-room and occupied-building siting, since that's where a poorly sited structure turns a process incident into a fatality event. The modeling work is the input; the response plan, the layout drawing, and the siting study are where it actually protects anyone.

This is also where consequence modeling connects back to the leading and lagging indicators tracked elsewhere in a process safety program. A facility that models its worst-case scenarios accurately but never updates those models as equipment, inventory, or layout changes is working from a hazard picture that's already stale, which is its own kind of leading indicator worth watching.

Frequently Asked Questions

Do I need both PHAST and FLACS, or is one enough?
It depends on the scenario. PHAST covers the broad range of dispersion, fire, and BLEVE scenarios efficiently and is often sufficient for open, uncongested layouts. FLACS earns its place specifically when equipment congestion or confinement is dense enough to meaningfully accelerate an explosion, since its CFD approach captures 3D geometry effects that simpler models can't. Support can help review which tool fits your specific layout and scenario set.
How often should consequence models be updated?
Any time inventory, equipment layout, process conditions, or nearby occupied structures change materially, the underlying model assumptions may no longer hold. Many facilities tie a review to their management-of-change process so a layout or inventory change automatically triggers a look at whether the modeled hazard zones are still accurate, rather than waiting for a scheduled multi-year QRA refresh.
What's the difference between a jet fire and a pool fire in practice?
A jet fire comes from a pressurized release igniting in flight, producing a directional flame whose length and heat are driven by release rate and pressure. A pool fire comes from a liquid spill igniting on a surface, with pool diameter and burn rate driving the radiant heat footprint instead. The two require different spacing and mitigation decisions even for the same chemical inventory.
Why does a vapor cloud explosion need congestion to occur?
A flammable cloud that ignites in open, unobstructed air typically burns as a flash fire without generating significant overpressure. It's the presence of pipe racks, equipment, and structural congestion that accelerates the flame front enough to generate a damaging blast wave, which is exactly why FLACS-style CFD modeling of actual plant geometry matters for this scenario specifically. A demo can walk through how modeled congestion zones map to your own equipment layout.
Are consequence modeling results the same as a quantitative risk assessment?
No, consequence modeling produces the physical outcome of a given scenario, such as a heat radiation distance or a toxic concentration boundary, while a quantitative risk assessment combines those consequences with the probability of each scenario occurring to produce an overall risk picture. Consequence modeling is a necessary input to QRA, but it answers a narrower question on its own.
Precision Where It Counts
Keep Every Hazard Zone Grounded in Real Data
See how iFactory keeps consequence modeling assumptions tied to what's actually running on your plant floor.

Share This Story, Choose Your Platform!