A plunger lift controller can open a well and hope, but to actually run the cycle intelligently it needs to know one thing above all: did the plunger make it to surface, and how fast? Plunger arrival detection is the sensing that answers that question. This guide explains the sensor at the top of the well that registers the plunger's arrival, how its timing yields an arrival velocity, why a plunger that fails to arrive triggers a protective response, and how the arrival status feeds directly into the controller's decision about the next cycle.
Plunger Arrival Detection in one line: Plunger arrival detection is the sensing, usually by a magnetic or acoustic sensor at the lubricator on top of the wellhead, that registers the moment a plunger reaches the surface at the end of its run. It confirms a successful lift, and the time it took gives an arrival velocity. A missing arrival within the expected window is treated as a fault that typically triggers the controller to shut the well in for safety.
The plunger arrives at the very top of the tubing string, into a fitting called the lubricator that sits above the wellhead and provides a place for the plunger to land and be caught. The arrival sensor is mounted on or near this lubricator, positioned to detect the plunger as it reaches the top of its travel. The most common type is a magnetic sensor: the steel plunger passing into the lubricator changes the local magnetic field, and the sensor registers that passage as a discrete arrival event, sending a signal to the controller. Because it senses the plunger's ferrous mass rather than requiring contact, a magnetic sensor is robust and simple, which suits an unattended wellhead.
Acoustic detection is the other common approach. Instead of sensing magnetism, an acoustic sensor picks up the sound of the plunger striking the top of the lubricator or the spring and catcher it lands against - a distinct impact the sensor recognizes as arrival. Whether magnetic or acoustic, the sensor's job is the same: convert the physical event of the plunger reaching surface into an electrical signal the controller can act on. The lubricator also houses a catcher mechanism that can hold the plunger at surface when needed, for instance to keep it out of the well during certain operations, and a spring to cushion the plunger's landing.
Reliability of this sensing is important because everything the controller concludes about the cycle rests on it. A sensor that misses genuine arrivals will make the controller think the well is failing when it is not, and a sensor that reports false arrivals will let the controller believe cycles are succeeding when they are not. The sensor is therefore a small but consequential piece of the installation, and its correct mounting and function at the lubricator are what make arrival-based control possible.
Arrival is not just a yes-or-no fact; when it happens carries information. The controller knows the moment it opened the valve and began the flow phase, and it knows the moment the arrival sensor fired, so the elapsed time between them, against the known tubing length, gives an arrival velocity - how fast the plunger traveled up the well. That velocity is a valuable indicator. A plunger arriving very fast suggests the well had more than enough energy, which can be hard on equipment as the plunger slams into the lubricator, while a plunger arriving slowly suggests the well was near the edge of having enough energy to complete the lift. Operators generally aim to keep arrival velocity within a target window, neither too fast nor too slow.
Non-arrival is the case the detection scheme must handle carefully. If the arrival sensor does not fire within an expected time window after the valve opens, the controller concludes the plunger did not reach surface - it may have stalled in the tubing because the well lacked the pressure to lift it. This is not a benign outcome: continuing to flow a well whose plunger is stuck partway up can worsen the situation, and the safe response is to close the well and let it build pressure again. Most controllers therefore treat non-arrival as a fault condition that triggers an immediate shut-in for protection, rather than simply proceeding as if nothing were wrong.
Repeated non-arrivals are a signal in their own right. An occasional missed arrival can be a one-off, but a well that keeps failing to arrive is telling the operator that its cycle is mistuned or that its conditions have changed - it may need longer shut-in to build more energy, or it may be entering a regime where plunger lift is struggling. Because the controller logs arrivals and non-arrivals, that pattern becomes visible and actionable rather than an invisible loss of production.
Arrival status closes the loop of the plunger cycle by feeding directly into the controller's next decision. A successful, well-timed arrival tells the controller the cycle worked and it can proceed - typically into afterflow to produce gas, then on to the next shut-in. A non-arrival tells the controller to protect the well by shutting in and rebuilding. And the arrival velocity tells the controller whether the last cycle was tuned about right or drifting toward too fast or too slow, which is the input an adaptive control scheme uses to adjust the next cycle's timing. In this way the single arrival event is what makes the cycle responsive to how the well is actually behaving rather than blindly following a fixed schedule.
For an operator, the value of arrival data multiplies when it reaches SCADA. A cloud SCADA reading the controller sees not only pressures and production but the stream of arrival events, arrival velocities, and non-arrival faults, which together reveal how well each plunger well is running. A well whose arrivals are slowing over days, or whose non-arrival count is climbing, is flagging a developing problem before it becomes a dead well, and that pattern is far easier to catch across a fleet on a dashboard than by visiting sites.
Merobix reads plunger controllers over field protocols such as Modbus and DNP3, so arrival status, velocity, and non-arrival counts become monitored values alongside casing pressure and production. An operator watching many gas wells can see at a glance which wells are arriving cleanly, which are drifting out of their velocity window, and which have started missing arrivals and shutting themselves in - and can respond by retuning a cycle remotely or scheduling a visit. The arrival sensor at one lubricator, multiplied across a field and surfaced on a screen, becomes a fieldwide health indicator for plunger lift.
Most arrival sensors are magnetic: the steel plunger passing into the lubricator at the top of the well changes the local magnetic field, and the sensor registers that as a discrete arrival event. Others are acoustic, picking up the sound of the plunger striking the top of the lubricator or its catcher. Either way, the sensor converts the plunger reaching surface into an electrical signal the controller can act on.
Arrival velocity is how fast the plunger traveled up the tubing, calculated from the time between the valve opening and the arrival signal against the tubing length. Too fast means the plunger slams into the lubricator with excess energy, which is hard on equipment; too slow means the well is near the edge of being able to complete the lift. Operators aim to keep arrival velocity inside a target window.
If the arrival sensor does not fire within the expected window, the controller concludes the plunger stalled in the tubing because the well lacked the energy to lift it. Continuing to flow the well in that state can make things worse, so the controller typically treats non-arrival as a fault and shuts the well in to build pressure again. Repeated non-arrivals signal that the cycle is mistuned or conditions have changed.
This page references the protocol specifications published by the organizations below. Editions, product capabilities, and documentation change over time - confirm current requirements and specifications directly with the source.
Last reviewed: July 27, 2026. Merobix is not affiliated with, endorsed by, or sponsored by these organizations; their names are used only to identify the standards and products discussed.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.