By the time MCF rate confirms a gas well is liquid-loaded, the well has typically been at 30–50% of potential for 5–14 days. The early signals are already in the SCADA tags — pressure, temperature, plunger arrival, choke position. They just don't fire as alarms because each one alone looks unremarkable. Read together against the well's own history, they form a load-up signature 1–2 weeks before flow rate confirms it.
Liquid loading is what happens when a gas well's flowing velocity at depth drops below the minimum required to lift the heaviest droplet of formation water or condensate to surface. Below that threshold, droplets stop moving up, accumulate in the tubing, and the resulting hydrostatic head chokes off inflow from the formation.
Three formulas dominate the field:
Where σ is interfacial tension (lbf/ft, typically 0.005 for condensate or 0.06 for water), ρL is liquid density (lb/ft³), ρg is gas density at depth (lb/ft³). The output is critical velocity in ft/s; multiply by tubing cross-section to get critical rate in mcfd.
Calculator: Try the free Turner / Coleman / Lea critical-velocity calculator — enter your tubing ID, FTP, temperature, gas SG, and liquid type; all three correlations in one screen.
This guide stays in plain English, but the formulas matter because the early warning signs below are what the SCADA tags do before velocity drops below vc. By the time MCF confirms loading, you're already past it.
The textbook sign and the most reliable. As liquid begins accumulating at the bottom of the tubing, the static head it creates raises the differential across whatever flow element is being measured (orifice, V-cone, ultrasonic, Coriolis). If the well's MCF rate has not changed yet, but DP has crept up 15% or more over 3–5 days, the well is filling.
DP trending up >15% over 3–5 days while MCF flat or falling <5%. DP-to-MCF ratio diverging from the well's own 90-day baseline. Confirm with FTP — if FTP is flat or falling while DP rises, hydrostatic head is the source.
Confounders: orifice plate fouling (which also raises DP without flow change), gathering-line backpressure rising upstream, instrument drift after a recent calibration. Eliminate these before you commit to a soap or plunger dispatch — see the decision tree at the bottom of this guide.
On a flowing well, casing pressure (CP) and flowing tubing pressure (FTP) maintain a roughly stable relationship driven by the gas column and the producing interval's deliverability. As liquid loads up the tubing, the increased hydrostatic head compresses the gas column, and CP begins to rise relative to FTP. The well is essentially building head pressure against itself.
(CP − FTP) widening >20% over 7–10 days. CP rising while FTP falls. Slope of CP-FTP delta inflecting upward. Pattern repeats across multiple wells on the same gathering segment if it's gathering-driven instead — diagnose by group, not by well alone.
Why this fires before MCF moves: the formation can sustain a higher backpressure for several days by drawing down reservoir pressure faster, which masks the rate impact in the short term. The pressure shift shows up first.
Before a well goes fully loaded, it usually goes intermittent. A liquid column that's accumulated enough to partially block flow gets blown out periodically by gas pressure, then re-accumulates. The flow trace, viewed at high resolution (1-minute or 5-minute scans), shows the signature: short-period oscillations with peak/valley amplitude an order of magnitude higher than the well's normal noise floor.
Standard deviation of MCF rate inflecting upward (>2x baseline) on rolling 24-hour window. Peak-to-valley amplitude on short-period (5–30 min) oscillations exceeding well's normal flow variability. Daily total may still look normal — the noise rises before the mean falls.
Why most dashboards miss it: they roll up to hourly or daily averages and the slug signature is a sub-hour phenomenon. You need the high-resolution trace, or a derived "flow stability" tag, to see it. Add this calc once and it'll fire on every well that starts slugging from now on.
If the well is on automated choke control to maintain a target rate or pressure, the controller compensates for early loading by progressively opening the choke. To the dashboard, MCF looks stable. To the choke position log, the well is using up its margin to hold the rate. Once choke position hits the upper rail, MCF will fall — and the alarm will finally fire, days after the underlying problem started.
Choke position increasing >5% over 7 days without operator command. Choke at >85% open and still trending. Rate setpoint unchanged. If the well is on manual choke, equivalent signal is operator notes / dispatcher comments documenting "opened up to hold rate."
The trap: rate-targeted controllers turn early loading into a rate-holding silent state. You can run a well from 100% deliverability down to choke-rail-out without seeing a rate alarm. This is the signal that catches it weeks earlier.
On a plunger-lift well, arrival velocity is the cleanest single indicator that the plunger is fighting added column weight. Before the plunger fails to surface entirely, it surfaces slow. Operators tracking arrival times week-over-week catch this; operators reviewing the well today against today catch it only after a no-arrival cycle has already happened.
Arrival velocity trending below the well's own 30-day baseline by >15%. Cycle frequency lengthening (more time between arrivals). Afterflow duration shortening. No-arrival cycles starting to appear, even at <5% rate.
Common misdiagnosis: assuming the plunger itself is worn or stuck and dispatching a workover. Roughly half the time, the plunger is fine — it's the fluid load that has changed. A soap or foam program at $2–$5/day is the right intervention; the workover is a $10k+ misallocation.
Counterintuitive but reliable. As liquid accumulates at the bottom of the tubing, gas-only flow above the liquid column moves faster through a smaller effective cross-section, generates less Joule-Thomson cooling, and the wellhead reads warmer than it should for the weather. A well that is normally 50°F at the wellhead in January reading 65°F is telling you something has changed.
Wellhead temperature elevated >5°F above same-week seasonal baseline (year-over-year compare) without ambient temperature explanation. Tubing-shoe to wellhead temperature delta narrowing. Pattern correlates with sign 1 (DP rising).
Confounder check: a recent change in choke position, gathering-line pressure, or ambient temperature can mimic this. Take the seasonal baseline from the same calendar week last year, not from the last 30 days, to factor weather out.
If the well is on a soap or foamer program, consumption rate against rate response is one of the earliest economic signals. A foamer program working at design rate produces a measurable post-treatment MCF bump for 24–72 hours. When a load-up trend is starting, the bump shrinks (less gas in less time), the half-life of the response shortens, and the pumper finds themselves dropping more sticks per week to hold the same rate. The program's economics quietly invert from positive to negative.
Sticks-per-week count rising >20% with flat or falling 30-day MCF. Average post-treatment MCF lift dropping below historical baseline. Half-life of MCF bump compressing (positive response disappearing inside 24 hours). Pumper notes mentioning "doubling up" without engineering signoff.
Why this matters more than people give it credit for: a working soap program that's quietly stopped working is the most expensive kind of "treated." Cost is going up, production is being lost, and nobody has flagged it because the chemical truck is still arriving on schedule. Read in concert with the FSR notes and the production trend, the divergence is unmistakable.
One sign firing in isolation can be noise. Two or more firing on the same well within a 7-day window is a load-up signature. When that happens, here's the order to work in. Don't dispatch a chemical truck or a plunger crew before you've ruled out the cheaper confounders.
None of the seven signs above is hard to read. Every experienced production engineer can spot any one of them on a single well in 60 seconds with the right plot in front of them.
The gap is not knowledge. The gap is systematic daily coverage across the whole portfolio. A 150-well operator with a 4-person engineering team gets less than 90 seconds per well per day if everyone in the room reviews every well every morning. Nobody has 90 minutes a day to scroll dashboards looking for the well where Sign 4 (choke creep) is silently combining with Sign 6 (wellhead temperature creep). So the well sits, the signals compound, MCF eventually drops, the alarm fires, and the team finds themselves diagnosing a problem that started 12 days earlier.
This is the gap an automated daily diagnostic layer fills. It doesn't replace the engineer's judgment or the pumper's eyes — it eliminates the morning scroll. Every well, every morning, against its own historical baseline and against the gathering segment it shares, with the seven signs (and another forty patterns like them) checked automatically. Anything firing makes it onto a ranked queue with the data and reasoning attached. The engineer arrives at 7 AM and starts the day on the three wells that need them, not on the dashboard scroll.
Charter-partner operators (20–200 active gas wells) get every active well diagnosed against the seven-sign pattern (and dozens more) every morning, before 6:30 AM CT. Setup waived, 50% off three months, penalty-free wind-down at week 12.
Apply to Charter Beta → Or build a quote