Opens in a new tab

Earthquake, Snow, Rain, and Flood Loads: Which Codes Control What?

Last updated: October 26, 2026

Facility type, structure classification, and jurisdiction decide which code governs earthquake, snow, rain, and flood loads on an oil and gas project, before any single named standard does. iFluids Engineering maintains dedicated articles on ASCE 7 and IBC fundamentals, earthquake loads, rain loads, load combinations, and soil, flood, and hydrostatic loads; this piece does not repeat those mechanics. It answers the question those leave open: once a structure’s type and jurisdiction are known, which code actually governs, and how does an engineer select the right combination across a development that spans onshore and offshore scope.

Earthquake, snow, rain and flood at industrial facilities

A Worked Example: One Development, Several Governing Codes

A single integrated development, an offshore wellhead platform feeding an onshore receiving terminal, illustrates why one structural submission can legitimately contain more than one design basis. The issue is not that the development has several governing codes; it is applying one set of assumptions to every structure in it.

StructureAuthority to ConfirmStructural ClassificationHazards Typically GoverningDocuments to Verify
Offshore wellhead platformOffshore regulator and project design basisFixed offshore platformWave, wind, and seismic where applicableAPI RP 2A-WSD edition; API RP 2EQ scope if seismic governs; DNV-RP-C205 if specified for metocean input
Onshore receiving terminal control buildingLocal building authority under the adopted IBC cycleBuilding, ASCE 7 Chapter 12 seismic provisionsSeismic, wind, and site-dependent snow or rainThe adopted IBC edition and the specific ASCE 7 edition it references
Elevated pipe rack and vessel supportsSame local authority, separate classification checkNonbuilding structure, ASCE 7 Chapter 15 seismic provisionsSeismic, often governing due to a different fundamental period and detailing requirement than the control buildingWhether Chapter 15 or Chapter 12 applies, and any project specification overriding the default classification
Elevated storage tankSame local authority, plus any tank-specific standard the project referencesNonbuilding structure, project-specific tank standard where applicableSeismic sloshing, wind, and flood-related inundation at gradeThe applicable tank design standard and whether ASCE 24 applies at this site

Which Code Applies, by Facility Type and Structure Class

ASCE 7 governs earthquake, snow, rain, and flood loads for onshore structures once a jurisdiction adopts it through the IBC. An offshore platform’s design basis instead follows the applicable offshore regulatory framework, typically API RP 2A-WSD where specified, with API RP 2EQ addressing seismic design and DNV-RP-C205 the environmental methodology.

Structure classification decides the applicable seismic provisions even within one facility, which is why the worked example above splits the control building from the pipe rack and tank. ASCE 7 Chapter 12 sets seismic requirements for buildings, while Chapter 15 sets separate requirements for nonbuilding structures such as pipe racks, vessel supports, and tanks, and these chapters address seismic classification specifically, not the snow, rain, or flood provisions, which sit in their own chapters regardless of building or nonbuilding status. A fixed offshore platform’s structural design follows API RP 2A-WSD rather than ASCE 7, and where the site is seismically active, API RP 2EQ governs that scope for structures designed under API RP 2A-WSD 22nd edition and later, a standard introduced separately from the platform-specific seismic approach used in earlier editions. A platform relocated or requalified for a new site needs its seismic case rechecked against the edition required for that relocation or reassessment, which is not necessarily the most recently published edition.

ASCE, API and DNV code selection for industrial structures
Establish the authority, edition, structure classification, and hazards before selecting design provisions
0
A DECADE OF SAFETY, AN Ai POWERED FUTURE

Recognized for excellence.

0

PROJECTS DELIVERED ACROSS THE GLOBE

Core Provisions and the Code Selection Matrix

ASCE 7 addresses flood loads in Chapter 5, snow in Chapter 7, and rain in Chapter 8 as individual chapters, while seismic classification spans Chapters 11 through 23 by structure type. ASCE 7-22 revised ground snow loads to strength-based, risk-category values, a revision to the snow basis, not a removal of ASD.

Diagrams of earthquake, snow, roof rain and flood forces
Ground acceleration, snow accumulation, roof water, and inundation create different structural demands

That edition-specific detail matters more than any single coefficient repeated across projects. Our load combinations and earthquake loads articles walk through the current combination sets in detail; the point for a selection guide is simpler: confirm the governing edition’s Chapter 2 directly rather than carrying a combination factor forward from a prior project. The same applies to rain loads, covered in depth in our rain loads article: a roof drainage analysis distinguishes static head, the hydraulic head needed to discharge the design flow through the applicable drainage outlet, and the ponding head that builds as roof deflection lets more water collect, with secondary drainage sized for a blocked primary system. Flood loads, covered in our soil, flood, and hydrostatic loads article, address inundation-related actions on the structure and foundation, including hydrostatic and hydrodynamic pressure, buoyancy, debris impact, and wave effects, not only water depth at grade.

Code Selection Guide by Structure and Situation

Structure or SituationGoverning Basis to EstablishSupporting CodesQualification
US building under an adopted IBCLocal adoption and amendmentsASCE 7 (edition the IBC cycle references); ASCE 24 where flood design is requiredThe published ASCE 7 edition and the edition a jurisdiction has adopted can differ by several years
Onshore pipe rack, vessel support, or equipment structureStructural classification and load pathRelevant ASCE 7 building or nonbuilding seismic provisions (Ch. 12 or Ch. 15); snow and rain provisions (Ch. 7, Ch. 8) apply regardless of that classificationOne facility can require more than one seismic classification across its structures
Fixed offshore platformOffshore regulatory and project design basisAPI RP 2A-WSD where specified by the governing requirements; API RP 2EQ for seismic scope under 22nd edition and laterSpecify the exact edition; do not extend fixed-platform guidance to floating facilities
Marine environmental assessmentSite metocean criteria feeding a structural codeDNV-RP-C205 where specified by the projectEnvironmental-load guidance on its own is not a substitute for a structural design code
Indian onshore facilityApplicable national and facility-specific requirementsRelevant IS 1893 part and edition; facility-specific OISD requirements where applicableConfirm the current part, edition, and adoption basis directly, since status has been revised more than once in recent years
GCC or Southeast Asian facilityNamed national or municipal authorityReferenced international standard plus local amendmentsTreat each country, and each authority within it, individually rather than as one regional default

Whether ASCE 24 governs a specific onshore project is a separate question from whether flood exposure exists on site. ASCE 24 applies through the regulation, adopted reference, or contractual design basis a project is bound to, not automatically because a site sits near mapped flood hazard.

A Six-Step Workflow for Selecting the Governing Code

Selecting the governing code for a multi-structure development follows a repeatable sequence rather than a single chapter lookup. The steps below move from confirming the authority and permit basis through classifying each structure to documenting how the different design bases interface within one coordinated submission.

  1. Identify the governing authority and permit requirements for each structure in the development.
  2. Record the adopted standards, editions, amendments, and any required supplements.
  3. Classify each structure and its supported equipment, since classification can change which chapter or document applies even within one facility.
  4. Establish the applicable site hazards and the hazard data accepted by the governing authority.
  5. Select the relevant load provisions and combinations from the governing edition, not from memory or a prior project.
  6. Document how the different structures’ design bases interface, and resolve any conflicting requirements before the structural submission goes out.

Regional Code Selection: GCC, India, and Southeast Asia

This section is a selection framework for identifying the governing authority and code by region, not a substitute for confirming country-specific snow, rain, or flood values directly with the named authority, since GCC, India, and Southeast Asia each require that confirmation separately rather than sharing one regional default.

GCC authorities generally reference international codes through local regulation, but each names its own authority, code, edition, and amendment, making a single regional default unreliable. India requires relevant OISD standards to apply alongside the applicable structural code where the facility and regulation call for it, rather than one standard replacing the other. Southeast Asia shares no single approach: Singapore’s Building and Construction Authority, for instance, works from a Eurocode-based framework rather than an ASCE 7-derived one. A refinery structural package in India typically needs to cite both a facility-specific OISD standard, where applicable, and the current part and edition of IS 1893, the Indian seismic design code. The status of IS 1893 has been revised more than once through recent gazette notifications, so engineers should confirm the applicable part, edition, and adoption status directly with the Bureau of Indian Standards rather than assuming the most recently published draft is in force. IS 1893 and ASCE 7 share the same underlying structural dynamics principles but differ in hazard models, coefficients, and design procedures: IS 1893 derives base shear from a seismic zone factor, an importance factor, a response reduction factor, and the structure’s fundamental period, while ASCE 7 works from mapped spectral acceleration values and site class. We are a global authority in process safety and risk engineering, and a combination of codes that does not match a facility’s actual type and jurisdiction, not a calculation error, is typically what a structural reviewer flags first on a mismatched submission.

Common Issues to Check During Design-Basis Review

Four issues are worth checking before a load submission goes out: whether the correct code applies to each facility type, whether the cited edition matches what the jurisdiction adopted, whether the roof ponding check has been done, and whether any snow-seismic factor came from the governing edition rather than a prior project.

The first check is whether ASCE 7 scope has been applied to an offshore structure, or API RP 2A-WSD scope to an onshore building, since the governing load combination format differs between the two. The second is whether a project cites an outdated ASCE 7 edition’s seismic maps or snow values where the jurisdiction has since adopted a newer edition, particularly given how far ASCE 7-22 moved from allowable-stress to strength-based snow values. The third is the roof ponding instability check under ASCE 7 Chapter 8: it deserves attention on its own terms, independent of a site’s seismic or snow exposure, since ponding is a load case in its own right rather than a secondary effect of another hazard. The fourth is confirming the combination factor applied where snow and seismic loads coexist against the governing edition’s Chapter 2, rather than a value carried forward from memory. None of these is guaranteed to surface at review; an incorrect hazard input or an omitted load case can go undetected and affect how the structure actually performs, which is why these checks belong at the design-basis stage.

Conclusion

Earthquake, snow, rain, and flood loads on an oil and gas project depend on facility type, structure classification, and jurisdiction before they depend on a single named standard. ASCE 7 governs onshore buildings and nonbuilding structures through the IBC adoption chain, API RP 2A-WSD and API RP 2EQ take over where specified for fixed offshore platforms, and OISD and IS 1893 add a further, edition-sensitive layer for Indian facilities. Confirming facility classification and the specific adopted edition before confirming which code governs a given load is the practical takeaway, since an incorrect hazard input or an omitted load case can affect how a structure actually performs, not only the project schedule.

iFluids Engineering’s engineering design and consulting team helps confirm the governing code set and edition before detailed design begins, across onshore, offshore, GCC, and Indian jurisdictions. For process safety considerations that intersect with structural compliance, see our process safety management services.

Frequently Asked Questions

ASCE 7 is a standard, not a building code. The IBC adopts it by reference, and each IBC edition cycle references one specific ASCE 7 edition rather than automatically updating to the newest one published. A jurisdiction’s adopted IBC edition determines which ASCE 7 edition governs a project, which can lag the most recent edition by several years.

Flood loads sit in Chapter 5, snow loads in Chapter 7, and rain loads in Chapter 8, each as a single chapter. Seismic classification spans Chapters 11 through 23, with Chapter 12 covering buildings and Chapter 15 covering nonbuilding structures, among other chapters addressing nonstructural components and site-specific ground motion separately.

ASCE 7-22 introduced strength-based ground snow load maps tied to risk category, replacing the allowable-stress values earlier editions used, and revised the associated combination factors in Chapter 2. This is a revision to the snow-load basis, not a removal of allowable stress design, since both ASD and strength combinations remain available.

Rain loads in Chapter 8 address roof ponding, calculated from static head, the hydraulic head needed to discharge the design flow, and the ponding head from roof deflection, with secondary drainage sized for a blocked primary system. Flood loads in Chapter 5 address inundation-related actions at grade, a distinct hazard with its own hydrostatic and hydrodynamic requirements.

ASCE 24 is required when the applicable regulation, adopted building code, or project design basis specifically calls for it, not automatically because a site has flood exposure. Coastal or riverine sites in a mapped flood hazard area often fall under this requirement, but engineers should confirm the governing regulation before assuming it applies.

API RP 2A-WSD governs the overall structural design of fixed offshore platforms where specified by the governing requirements, while API RP 2EQ is a separate standard governing seismic design, applicable to structures designed under API RP 2A-WSD 22nd edition and later. Both the structural design and seismic basis should be checked against the correct edition.

Facility type and jurisdiction both need confirmation before a load code is selected, since a GCC authority, an Indian national standard, and a Southeast Asian building authority each reference different codes with different local amendments. Confirm the named authority, the adopted code, its edition, and any local amendment directly rather than assuming a single code applies regionally.