A flare header is a pipe that is usually not carrying much of anything, sitting quiet between the occasional relief or blowdown event, and that idleness is exactly what makes it dangerous. Left truly empty, air can work its way back down the flare stack into the header, and air mixed with the flammable gas that lives there can burn inside the pipe, which is a serious hazard. Purge gas is the continuous trickle of gas fed into the header to prevent that, keeping a minimum upward flow so nothing can travel back down. This guide explains what purge gas is and the minimum purge velocity it has to maintain, how velocity and molecular seals cut the amount of purge needed, and how SCADA watches purge flow against the minimum requirement.
Flare Purge Gas in one line: Flare purge gas is a continuous small flow of gas fed into a flare header to keep a minimum upward velocity through the system, so air cannot travel back down the stack into the header. Preventing that air ingress avoids forming a flammable mixture inside the piping, which could flashback, burn internally, or explode. The required purge rate is set by a minimum purge velocity, and devices such as velocity and molecular seals near the flare tip dramatically reduce how much purge gas is needed to maintain it.
A flare exists to burn off gas that must be relieved, but most of the time there is no relief happening and the header is nearly stagnant. The open top of the flare stack connects that header to the atmosphere, and without something to stop it, air can diffuse or be drawn back down the stack into the header, particularly as the gas inside cools and contracts or as wind and temperature changes work against the stack. Once air gets in and mixes with the residual flammable gas in the header, the inside of the pipe can hold a flammable mixture, which is precisely the condition to avoid in a system whose whole purpose involves ignition at the tip.
The danger of that mixture is real and specific. If a flammable air-gas mixture inside the header finds an ignition source, most obviously the flare's own flame at the tip, it can flashback, letting the flame travel down inside the header and burn internally, which can damage the flare system and in the worst case cause an explosion. Internal burning is not what a flare is designed for, and it threatens the integrity of the header and the stack. Keeping air out of the header is therefore a fundamental safety requirement, not a refinement.
Purge gas is the standing defense against this. By continuously feeding a small flow of gas into the header, the system maintains a gentle but constant upward movement out the stack, so the net flow is always outward and air cannot make headway back down against it. The purge does not need to be large; it only needs to keep the header swept and slightly pressurised so that at the top of the stack gas is always creeping out rather than air creeping in. That continuous sweep is what keeps the interior of the flare system inert of air and safe between relief events.
The requirement is often expressed not as a flow but as a minimum velocity at the flare tip, because what actually keeps air out is the upward speed of gas at the top of the stack, not the raw volume. There is a minimum velocity below which air can begin to diffuse back down against the outward creep, and the purge rate must be enough to maintain at least that velocity. Because velocity depends on the cross-sectional area of the stack, a large-diameter flare needs a great deal of gas to reach the same tip velocity as a small one, so on a big flare the volume of purge gas required to hold the minimum velocity by brute force alone can be substantial and continuous.
This is why flares use seals to cut the purge needed, and the two common types work in different ways. A velocity seal, or fluidic seal, is an internal baffle arrangement near the tip that makes it much harder for air to diffuse downward, effectively trapping a pocket and disrupting the back-flow of air, so the same protection is achieved at a far lower purge rate. A molecular seal, or labyrinth seal, exploits gas density: it holds a pocket of purge gas in a way that forms a barrier air cannot easily displace, so a light purge gas creates a standing seal against heavier air. Both let the flare stay protected on a fraction of the purge that an unsealed stack would demand.
The practical effect of a seal is a much lower minimum purge requirement, which matters because purge gas is consumed continuously, every hour of every day, whether or not the flare is doing any burning. Over a year, the difference between an unsealed flare purging by brute velocity and a sealed one holding the same protection on a trickle is a large amount of gas either wasted and emitted or saved. So the seal is both a safety and an efficiency device: it maintains the air barrier while sharply reducing the standing purge, which is why nearly all modern flares of any size include one. The minimum purge is then set to whatever the sealed system needs to stay safe, which is far below the unsealed figure.
Because the purge is a safety function that runs continuously and silently, the thing that can go wrong is that it quietly falls below the minimum without anyone noticing, and that is exactly what SCADA is there to prevent. The system measures the purge gas flow into the header and compares it against the minimum required to hold the protective velocity, so a purge that has drifted low, been throttled back, or lost its supply is caught rather than assumed to be fine. Trending the purge flow makes the standing safety margin visible instead of taken on faith, and it distinguishes a healthy purge from one that is slowly failing.
The alarms on this measurement are high priority because the consequence of losing purge is air ingress and the risk of internal burning. A low-purge alarm warns that the header may no longer be protected and that air could be working its way in, prompting immediate attention before a flammable mixture can form. Watching the purge flow alongside the flare's pilot and any relief activity gives a fuller picture of the flare's health, since a flare that loses purge is at risk regardless of whether it is actively flaring, and the loss might otherwise go undetected precisely because nothing appears to be happening at the tip.
A cloud SCADA and monitoring platform such as Merobix fits this role well because flares are safety-critical, often remote, and rarely watched closely between events. Merobix trends the purge gas flow against its minimum requirement, logs it continuously, and alarms the moment the purge falls below the safe threshold, so a failed regulator, a closed valve, or a dwindling supply becomes an immediate signal rather than a hazard discovered after the fact. Because the purge is a continuous cost as well as a safety measure, seeing the flow also lets an operator confirm the seal is doing its job and the purge is not running far higher than needed, and across multiple flares the same view provides ongoing assurance that every header is being kept swept and safe from air ingress.
A flare header is nearly stagnant between relief events, and the open stack lets air travel back down into it as the gas cools and contracts. Air mixing with the residual flammable gas can form a flammable mixture inside the piping, which can flashback from the flame at the tip and burn internally or explode. Continuous purge gas keeps a gentle upward flow out the stack so the net movement is always outward and air cannot make its way back down.
A velocity, or fluidic, seal is an internal baffle near the tip that disrupts the downward diffusion of air, while a molecular, or labyrinth, seal uses gas density to hold a standing pocket of purge gas that air cannot easily displace. Both let a flare maintain its air barrier on a small fraction of the purge gas an unsealed stack would need. Because purge gas is consumed continuously, a seal saves a large amount of gas over time while keeping the same safety protection.
SCADA measures the purge gas flow into the header and compares it against the minimum required to hold the protective velocity at the tip, trending it continuously so a purge that drifts low or loses its supply is caught. A low-purge alarm is high priority because losing purge risks air ingress and internal burning, so it prompts immediate attention. Watching purge flow alongside the pilot gives a fuller picture of the flare's safety status even when nothing is actively flaring.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.