What Is Pigging a Pipeline?

Back to Blog

What Pigs Do

The term "pig" is often said to come from the squealing noise early units made against the pipe wall. Functionally, pigs fall into a few categories. Utility or cleaning pigs scrape wax, scale, and debris off the wall and sweep accumulated liquids ahead of them, which restores flow efficiency and reduces internal corrosion. Batching or sealing pigs separate two different products moving back-to-back in the same line so they do not mix at the interface. Gauging pigs verify a line is round and free of dents before commissioning.

Smart pigs, or inline inspection (ILI) tools, are the sophisticated end. Packed with sensors, they measure the pipe wall as they travel - magnetic flux leakage (MFL) tools find metal loss from corrosion, ultrasonic tools measure wall thickness, and caliper tools map dents and geometry. The data they log is analyzed afterward to locate and prioritize defects for repair, and is a core part of pipeline integrity management.

How a Pig Run Works

A pig is loaded into a pig launcher (a barrel with a valve arrangement) at one end of the line, then isolated and pressured up so the product flow pushes it downstream. It travels at pipeline velocity and is caught at the far end in a pig receiver. Launching and receiving are carefully sequenced operations involving pressurizing, equalizing, and venting the barrel - done wrong they are a safety hazard, so procedures and interlocks matter.

Operators track a pig's progress by watching pressure and flow, and by pig-signalers (passage indicators) mounted along the route that detect the pig going by. SCADA plays a supporting role here: pressure and flow transmitters, launcher and receiver valve and trap-door status, and pig-passage signals can all be brought into the control system so the operator confirms the pig launched, follows its transit, and gets alarmed if it stalls. Those field instruments typically report over Modbus or DNP3, so a cloud SCADA platform can present the whole pig run on one screen.

Planning a Pig Run

Good pig runs are planned before the barrel door ever opens. The first question is piggability: whether the line will pass the tool at all - full-bore valves along the route, bends within what the pig tolerates, barred tees, and a known internal diameter. The second is matching the pig to the job and to the line's condition, because an aggressive pig in a dirty line creates its own emergency. A working pre-run checklist:

1. Confirm piggability and note every diameter change, valve, and fitting along the route.
2. Select the pig for the job - cleaning, sealing, gauging, or inspection - and inspect its condition before loading.
3. Walk the launcher and receiver isolation, pressuring, and venting sequence against the site procedure.
4. Verify pig-signalers, pressure, and flow indications along the route are healthy.
5. Agree the tracking and communication plan, including who does what if the pig is overdue.
6. Confirm the receiver is prepared before launch - a pig with nowhere to land is an incident in waiting.

The barrels themselves are where the hazard concentrates: a pig launcher or receiver is a pressure vessel with a door, and most serious pigging incidents run through opening one wrongly. Trap operations follow the site's written procedure, with qualified personnel, every time, however routine the run has become.

When a Pig Stalls or Goes Missing

A stalling pig writes its signature in the process data: pressure rises upstream of it, falls downstream of it, and flow drops as it packs debris or wedges. The last signaler that confirmed passage and the first one that stayed silent bracket its position. Within that bracket, a symbolic estimate narrows the search: the volume pumped since launch divided by the line's internal cross-sectional area gives the distance the pig should have traveled, which tells a crew where to start before anyone drives the whole route.

Response is an engineering decision, not a console one. Raising the differential pressure across the pig may free it, but pressure limits are absolute - any plan stays inside the line's maximum operating pressure and under the pipeline engineering authority's direction. Debris packing ahead of an over-ambitious tool is a classic cause, which is why progressive programs of the kind described in the cleaning pig run reference start soft and escalate. Some pigs carry tracking transmitters that let a surface crew locate them precisely; where fitted, that turns a search into a drive.

Cleaning Programs and Inspection Intervals

How often a line is pigged is a condition-driven, site-specific question, and the line reports its own fouling. Pressure drop rising at constant flow means the wall is coating or liquids are accumulating, and the volume of liquid and debris arriving at the receiver each run measures how much the current interval is leaving behind. Programs tighten the interval until returns stabilize at a level the operation accepts, and relax it when runs consistently come back clean.

Inspection pigging runs on a different clock: intervals for an inline inspection tool come from the integrity management program and the applicable regulations, not from week-to-week line condition. A smart-pig campaign is also a project in its own right - cleaning runs first so the sensors see the wall rather than the wax, then a gauging run to prove the line passes a rigid body, then the tool itself. The condition data trended between campaigns - pressures, flows, and receiver returns - is what makes both clocks credible.

Frequently Asked Questions