Common FERA Mistakes are rarely about complicated mathematics—they are most often rooted in assumptions, blind spots, and process lapses that creep into Fire and Explosion Risk Assessment work. In high-hazard industries across the UAE, from upstream and downstream oil and gas to petrochemicals, construction, logistics, power generation, and manufacturing, FERA is a decision tool that only works when its inputs, modeling logic, and interpretation are disciplined. This article unpacks where FERAs typically go wrong, why those errors matter, and how organizations can build assessments that stand up to engineering scrutiny, regulators’ expectations, and operational reality.
To keep the focus practical, we will reference familiar standards and practices—IEC 61511 for safety instrumented systems (SIS), API RP 750 and API 521 for process safety and relief/flare considerations, NFPA codes relevant to fire protection (including NFPA 30, 59A, 68, and 69), and methodologies like HAZOP, HAZID, LOPA, Bowtie, and QRA. We will also situate the discussion in the UAE regulatory context—Abu Dhabi OSHAD, Dubai Municipality, UAE Civil Defence approvals, MOHRE requirements, and ADNOC HSE Codes of Practice—so that the implications of getting FERA wrong are clear to duty holders and stakeholders alike.
Who Does This Affect?

Because a fire or explosion can affect every dimension of an operation—from people and assets to compliance and continuity—this topic touches a wide range of roles and facility types. FERAs are not the exclusive domain of process safety specialists; the outcomes shape decisions across the lifecycle of assets and projects.
- HSE and process safety leaders responsible for risk governance, ALARP demonstration, and regulatory interfaces (e.g., submissions to UAE Civil Defence).
- Plant managers, operations superintendents, and control room leadership making calls on isolation philosophy, ESD segmentation, firewater demand, and emergency response.
- Engineering and projects teams (including EPC/EPCM partners) defining siting and layout, utility sizing, passive fire protection (PFP) thicknesses, fireproofing scope, and explosion venting or relief provisions.
- Maintenance and turnarounds teams planning hot work, temporary isolation strategies, and simultaneous operations (SIMOPS) where transient risk can dominate.
- Asset integrity and reliability engineers aligning FERA assumptions with equipment condition, fireproofing upkeep, and impairment management for F&G detection, deluge/sprinkler systems, hydrants, and foam systems.
- Security and logistics teams at tank farms, bulk liquid terminals, and high-rack warehouses storing flammable liquids, aerosols, and pressurized gases—where inventory control and packaging changes alter fire dynamics.
- Stakeholders in offshore platforms, onshore gas plants, refineries, petrochemical complexes, power and desalination plants, and construction mega-projects with temporary fuel storage and pressurized systems.
In short, anyone who must sign off on facility design decisions, operating envelopes, emergency planning, or compliance declarations is impacted by the quality of the FERA that informs those decisions.
Why This Topic Matters

Once a facility is designed and built, many risk levers become expensive or disruptive to change. FERA informs decisions at concept and detailed design—setbacks, module layout, blast ratings for control rooms, passive fire protection, firewater ring main capacities, foam concentrate requirements, and the logic of detection, ESD, and blowdown. If the analysis underestimates credible fires or explosion overpressures, mitigations can be undersized. If it overestimates, the project may carry avoidable capex and opex. Both are business risks.
Beyond design economics, the stakes are regulatory and societal. ADNOC operators, for example, must show that risks are ALARP under their HSE Case frameworks. UAE Civil Defence approvals depend on demonstrated compliance with applicable NFPA, IFC, and local codes, and the fire strategy must be technically defensible. OSHAD requirements emphasize systematic risk assessment and control measures for Abu Dhabi entities. Insurers and lenders scrutinize FERA conclusions when they assess portfolio risk.
Even in steady-state operations, the FERA is a living input to management of change (MOC), SIMOPS planning, and emergency response drills. As inventories, operating modes, and occupancy patterns shift—night shift staffing, temporary laydown yards, or process debottlenecking—the underlying fire and explosion risk profile changes. A FERA riddled with untested assumptions can anchor an organization to a false sense of security.
Key Points to Understand

Before diagnosing pitfalls, it helps to clarify what a good Fire and Explosion Risk Assessment is intended to do and how it fits with companion studies like QRA and EERA. At its core, FERA:
- Identifies credible loss-of-containment (LOC) events of flammable materials across states (gas, liquid, two-phase) and pressure/temperature ranges.
- Estimates initiating frequencies and conditional probabilities (ignition probability, escalation to jet/pool fire or vapor cloud explosion) using data, HAZOP/LOPA insights, and facility-specific protections.
- Models consequences—thermal radiation, flame impingement, smoke production, overpressure—from credible scenarios, with attention to congestion, confinement, and meteorology.
- Assesses escalation to adjacent equipment, impairment of critical safety systems, and impact on occupants and egress routes.
- Benchmarks results against tolerability metrics (individual risk, societal risk, risk matrix) and performance standards for protective systems.
FERA interfaces closely with other processes: HAZOP drives scenario credibility, LOPA/IEC 61511 ensure SIS integrity for ignition prevention and isolation, API 521 guides blowdown and flare capacity, and NFPA standards define detection and suppression performance. Offshore, ISO 13702 and EERA guidance link directly to fire and explosion loads for escape, evacuation, and rescue analysis. With that context, the critical question is where do typical FERAs stumble?
| Typical Mistake | How It Happens | What Gets Missed | Operational Result |
|---|---|---|---|
| Using generic failure/ignition data without localization | Copy-paste from old studies; no calibration to ADNOC, vendor, or site-specific histories | Frequency skew; wrong conditional ignition probabilities | Over/under-sized PFP, detection spacing, or firewater capacity |
| Ignoring congestion and partial confinement | Applying open-air models to congested modules or pipe racks | Deflagration amplification and higher overpressures | Under-rated blast walls and occupied building hardening |
| Outdated inventory and operating envelopes | FERA not refreshed after debottlenecking or feedstock change | Larger release rates or new two-phase conditions | Unexpected jet/pool fire sizes and escalation paths |
| Over-optimistic impairment assumptions | Assuming all F&G, deluge, and ESD work as designed—always | Realistic failure-on-demand and delays in isolation | Insufficient layers of protection in abnormal states |
| Weak scenario screening | Eliminating “unlikely” LOCs without justification | Small-bore, maintenance-induced, or transient releases | Blind spots during startup/shutdown or SIMOPS |
| Misaligned risk criteria | Mixing societal F–N and individual risk thresholds improperly | Clear acceptability basis (ALARP) and decision thresholds | Unclear rationale for mitigation or acceptance |
| No integration with emergency response | FERA ends at contours; no test against evacuation/egress | Visibility, smoke movement, heat flux on routes | Unsound mustering plans and response times |
Each row reflects a class of error that propagates through the analysis. For instance, if congestion is ignored, a “non-explosive” vapor cloud in an open model might actually produce damaging overpressure in a pipe rack, changing the required blast resistance for a control room. Similarly, assuming immediate isolation often underestimates jet fire duration, which in turn drives PFP thickness and firewater duration calculations.
How This Works in Practice

Translating principles into day-to-day decisions is where many organizations stumble. The chain typically starts with HAZOP and HAZID sessions, where teams enumerate credible LOCs. The FERA then screens and models a subset of those scenarios. But busy teams under delivery pressure may re-use scenario sets from similar units without testing for differences: a new propylene inventory in a mixed feed reformer; a higher vapor pressure solvent in a paint line; a longer pipe run increasing drop-out distances in a jet fire; or new congestion from added cable trays.
Consider a few real-world contexts from facilities common across the UAE:
- Refineries and gas plants: Hot, dry ambient conditions alter dispersion and evaporation. A two-phase release from a high-pressure condensate line can project droplets well beyond presumed rainout distances, affecting off-plot hazards. API 521 blowdown assumptions, if not recalibrated, may underrate the flare’s ability to prevent a delayed ignition event.
- Tank farms and terminals: NFPA 30 foam application rates and durations must align with tank sizes, rim seal fire probabilities, and nearby exposure tanks. A FERA that overlooks full-surface fire scenarios after roof failure can misstate ring main demand or foam concentrate stocks.
- Offshore platforms: Partial confinement within modules and congested equipment skids can magnify vapor cloud explosion pressures. EERA must align with FERA loads to ensure evacuation systems and TR (temporary refuge) integrity are adequate.
- High-rack warehouses and logistics hubs: Aerosol cans, pressurized cylinders, and mixed commodity storage can change fire growth and smoke characteristics. Misclassification of commodities leads to unrealistic sprinkler/deluge performance assumptions.
- Power generation and utilities: Gas turbine enclosures, lube oil systems, and H2-cooled generators carry specific jet/pool fire risks. Applying generic hydrocarbon jet fire data may miss unique enclosure ventilation effects.
These examples show why a FERA should be synchronized with the site’s most recent P&IDs, isometrics, 3D models, and operating procedures. It should also acknowledge human and organizational performance: detection delays in noisy workfaces, alarm response during shift change, or limitations during sandstorms. Without these factors, even the most elegant model ceases to be decision-grade.
Benefits and Practical Use Cases

When teams specifically address the pitfalls above, the benefits are immediate and measurable—not only in compliance but in operational clarity. Organizations see the difference in several ways:
- Right-sized protection: PFP, detection spacing, and deluge are optimized to credible loads, avoiding both underprotection and gold-plating.
- Stronger ALARP cases: The link between risk drivers, mitigations, and residual risk becomes transparent for ADNOC HSE submissions or Civil Defence approvals.
- Sharper emergency planning: Egress routes, muster points, and response tactics are tested against radiation and smoke contours that reflect realistic impairment and delay.
- Better MOC decisions: Small plant changes—valve replacements, modified nozzle sizes, layout adjustments—are screened quickly against FERA assumptions so that creeping risk does not accumulate unnoticed.
- Assurance in SIL and LOPA targets: SIS and instrumented functions (per IEC 61511) inherit credible demand rates from a calibrated FERA, reducing debates about target SILs.
- Insurance and financing credibility: A technically robust assessment supports negotiations with insurers and financiers who often review the fire strategy in detail.
Practical use cases span project and operations contexts. During concept select, a FERA can discriminate between alternative layouts or module densities on an offshore topsides. In brownfield upgrades, it can target limited budgets at the few controls that cut the most escalation risk—like adding a remotely actuated isolation valve or upgrading foam proportioners where tank-to-tank radiant heat flux exceeds thresholds. In logistics settings, it can guide commodity zoning and pallet height rules to avoid contiguous fire spread beyond sprinkler design criteria.
Best Practices and Points of Caution

Building on the benefits, the way to avoid common pitfalls is to engineer rigor into each step of the assessment and to keep governance tight so that the FERA remains current. The following practices have proven effective across diverse facilities:
- Anchor scenarios in current, verified data: Refresh inventories, equipment tags, and operating envelopes from the latest P&IDs, datasheets, and historian trends. Cross-check LOPA data for initiating event frequencies and independent protection layers (IPLs).
- Respect congestion and confinement: Use models suitable for congested modules, racks, or partially enclosed spaces; avoid applying open-field correlations where deflagration risks exist. Reference API RP 752/753 for occupied building siting relative to blast loads.
- Model impairment credibly: Introduce realistic failure-on-demand rates and response times for key protections—F&G detection, ESD valves, deluge start, manual firefighting arrival. Consider shift patterns and alarm floods.
- Cover transient and small-bore risks: Include maintenance-induced releases, startup/shutdown cases, SIMOPS, and high-frequency small-bore failures that can produce persistent jet fires.
- Integrate with emergency response: Translate outputs into clear performance standards for egress, muster, intervention times, and water/foam logistics. Validate routes against predicted heat flux and smoke visibility.
- Align with codes and corporate criteria: Square the assessment with NFPA, API, IEC 61511, ADNOC HSE, UAE Civil Defence guidance, and corporate risk tolerability criteria (individual risk, F–N curves, ALARP demonstration).
- Document the assumptions register: Maintain a living log of assumptions, data sources, model limitations, and deviations. Revisit the register at every MOC and major turnaround.
- Peer review and iterate: Use internal or third-party reviewers to challenge scenario screening, data selections, and interpretation. Reconcile contradictions between FERA, QRA, and EERA outputs.
Governance around controlled documents is just as important as modeling. Version control, distribution to duty holders, and change tracking prevent drift between what the study assumes and how the plant actually runs. For readers exploring structured documentation management approaches and curated technical resources, a useful starting point is CABINET NPM, which illustrates how organized repositories streamline access to current procedures, standards, and evidence.
Finally, do not treat FERA as a static deliverable. It should be triggered for refresh by events like significant production changes, incident learnings, facility expansions, major maintenance campaigns, or regulatory updates. A short annual review against the assumptions register often prevents multi-year gaps that lead to surprises.
Frequently Asked Questions About Fire and Explosion Risk Assessment (FERA)

How is FERA different from QRA or EERA?

FERA focuses specifically on the initiation and escalation of fire and explosion scenarios, quantifying thermal radiation and overpressure effects for design and protection decisions. QRA is broader—addressing all major accident hazards, calculating individual and societal risk, and often encompassing toxic releases. EERA (commonly offshore) evaluates whether people can escape, evacuate, and be rescued under defined loads; it relies on FERA outputs (e.g., overpressure, heat flux) to test life-safety performance.
Which standards should a credible FERA reference?
Depending on facility type, common references include API RP 521 (relief/blowdown and flare), API RP 14C/750 for process safety concepts, IEC 61511 for SIS lifecycle, NFPA 30/59A/11/15/68/69 (flammable liquids, LNG, foam, water spray, deflagration venting and prevention), ISO 13702 for offshore, and corporate or regulator-specific criteria (ADNOC HSE Codes of Practice, UAE Civil Defence guidance, OSHAD requirements). The FERA should explicitly cite and align with the applicable editions.
What data quality is “good enough” for initiating event frequencies?
Use the best available, defendable sources: company incident databases, vendor reliability data, industry datasets, and calibrated expert judgment when gaps remain. The key is transparency—record sources, ranges, and rationale in an assumptions register, and sensitivity-test decisions that hinge on uncertain parameters (e.g., ignition probabilities or isolation delays).
How should occupied buildings be treated in explosion assessments?
Occupied building risk needs dedicated analysis: siting relative to credible overpressures, structural resistance, and HVAC shutdown/smoke ingress considerations. API RP 752/753 provide guidance. Do not rely solely on distance; assess blast resistance and fragility of windows and walls, and verify egress routes remain viable under defined loads.
Is it acceptable to exclude small-bore leaks from screening?
Not by default. Small-bore leaks are frequent and can produce persistent jet fires with high local heat flux that threatens cable trays, instrument tubing, and adjacent equipment. Screening out such cases requires explicit justification and, where excluded, compensating controls or monitoring should be documented.
How often should an operating site refresh its FERA?
At minimum, review annually against the assumptions register and revalidate in depth when there are material changes—feedstock, throughput, new equipment, altered layouts, or significant incident learning. For projects, refresh at key stage gates (concept, FEED, detailed design) and before start-up if any design changes have occurred.
What is the best way to link FERA outputs to emergency response?
Convert radiation and smoke contours into performance standards for time-to-muster, firefighting access, and resource deployment (water/foam). Test routes and tactics through drills and tabletop exercises; adjust procedures where modeled conditions suggest impaired visibility, untenable heat, or blocked access.
Do detection and deluge models need to include impairments?
Yes. Realistic unavailability (failure on demand, maintenance outages) and response delays should be included. Overly optimistic assumptions can underestimate fire duration and escalation. Align impairment modeling with maintenance records, reliability data, and organizational factors such as shift coverage and alarm handling practices.
Avoiding the Traps: Bringing It Together
Stepping back from the detail, the thread that runs through common FERA mistakes is untested assumptions. Data drawn from a different facility, generic models used in congested spaces, inventories that no longer match operations, or risk criteria applied inconsistently—all can produce conclusions that misguide design and operating decisions. The remedy is an engineered approach: current data, credible modeling of congestion and impairment, explicit links to emergency response, and governance that keeps the study alive through MOC and turnarounds.
For operators in oil and gas, petrochemical, construction, logistics, power, and manufacturing environments, this rigor is not academic. It determines whether a fireproofed support survives long enough to prevent collapse, whether a control room remains tenable after a deflagration, whether a foam inventory carries you through a full-surface tank fire, and whether muster routes remain viable through smoke and heat. When people talk about Common FERA Mistakes, they are often pointing at process discipline gaps—each fixable with sound data practices, careful scenario screening, alignment with IEC/NFPA/API guidance, and periodic peer review.
To go further on this topic, NPM’s broader Fire And Explosion Risk Assessment Services UAE page covers this in more depth.
Our References
NPM’s references illustrate how disciplined Fire and Explosion Risk Assessment underpins resilient industrial operations. Across refineries, gas processing plants, offshore platforms, petrochemical complexes, tank terminals, high-rack logistics centers, and power generation assets, our teams have helped clients interrogate assumptions, calibrate models, and translate findings into practical performance standards. In one project, updating a decade-old assessment exposed inventory changes that increased jet fire reach, prompting targeted upgrades to isolation valves and passive fire protection rather than wholesale retrofits. In another, a congested module on an offshore installation had been assessed with open-air correlations; re-modeling with realistic congestion factors changed blast load predictions, informing strengthened barriers and revised emergency response protocols.
Our track record also includes alignment of FERA outputs with QRA, LOPA, and IEC 61511 SIL target setting, ensuring consistency between frequency assumptions and instrumented protection layers. We have supported clients in reconciling NFPA-driven firewater and foam strategies with site-specific risks, helping them validate ring main capacities and foam concentrate storage against credible full-surface and rim seal fire scenarios. Throughout these engagements, the common thread is robust evidence: we establish assumptions registers, build sensitivity cases, and document rationales in a way that stands up to regulatory and insurer review. Whether the facility is a new-build or a mature brownfield site, our approach emphasizes lifecycle governance so that the assessment remains decision-grade as operations evolve.
For more information about our references, visit Our References.
Speak with NPM
If you are reflecting on how your current Fire and Explosion Risk Assessment handles congestion, impairment, or changing inventories, a short discussion can help clarify priorities. NPM’s team welcomes technical questions and is happy to share perspective on practical next steps for your facility’s context. We aim to contribute useful, grounded insight—whether you are at concept design, pre-startup, or steady-state operations.
For any further questions or to speak with our team, Contact Us.