Home » Calculators » Electro-Static Charge Safe Flow Calculator
Electro-Static Charge Safe Flow Calculator
By using this calculator, you confirm that you have read and agree to the Terms of Use and Disclaimer
Static Charge Safe Flow Calculator
Results update automatically as you type. The tool calculates multiple standards-aligned model limits and highlights the most conservative (lowest applicable) maximum velocity.
Unit system
Results
Most conservative maximum average velocity (minimum of applicable models)
—
—
Max volumetric flow rate (based on ID)
—
—
Governing model(s)
—
—
Conductivity class (IEC-style)
—
—
Relaxation time constant τ
—
—
Microfilter downstream residence time
—
—
Submergence guidance (informational)
—
—
Model outputs: each model below produces a maximum velocity. The highlighted row(s) are the most conservative and govern the final recommendation.
Notes & warnings
For engineering use, verify applicability and inputs. This tool does not replace professional judgment.
Assumptions & Applicability
Intended for liquid transfer/filling where electrostatic ignition of a flammable atmosphere is a credible concern.
Assumes appropriate bonding/grounding of conductive equipment and use of conductive fill pipes/hoses where required. Nonconductive hoses/liners can change charge behavior and may require a dedicated assessment.
Limits are based on commonly applied guidance models, including slow-start limits, vehicle loading v·d limits with a velocity cap, microfilter residence-time guidance, and a conservative approach when dispersed phases are present.
This tool does not model streaming current in detail, spark energy, turbulence factors, two-phase flow dynamics, additive chemistry, or temperature dependence. Use measured product properties and site procedures.
References
API Recommended Practice 2003, Protection Against Ignitions Arising Out of Static, Lightning, and Stray Currents
NFPA 77, Recommended Practice on Static Electricity
IEC/TS 60079-32-1, Explosive atmospheres – Part 32-1: Electrostatic hazards, guidance: