Compliance

BOP Testing: Pressure Tests and the Paper Trail That Proves Them

A blowout preventer stack is the last line of defense on a well. It sits on top of the wellhead and closes in seconds when pressure comes up the hole. But a BOP that has never been proven under pressure is only a hope, not a barrier. That is why every stack gets pressure tested on a set schedule, and why the test records matter as much as the test itself. Pressure testing proves the stack can hold the pressures it was built for. Function testing proves the parts move. Both are required, and both have to be documented. This article explains why BOP stacks are pressure tested, when the tests happen, and why the paper trail matters.

Why Pressure Test a BOP Stack

A BOP stack is a set of valves and rams that can seal the wellbore in a hurry. During normal drilling the rams sit open and the pipe moves through the stack. When something goes wrong, the crew closes the rams to shut the well in. The whole point of the equipment is to hold pressure, so if it cannot hold pressure it cannot do its job. The encyclopedia page on blowout preventers covers what a stack is made of in more detail.

Function tests show that the rams open and close and that the controls work. That is a necessary check, but it is not enough. A ram can close all the way and still leak under pressure. The seals, the elastomers, and the body of the stack can fail in ways a simple open and close test never reveals. A pressure test loads the equipment the way the well would load it. It is the only honest way to prove the barrier will hold when it matters. That is why pressure tests, not just function tests, are the backbone of BOP maintenance.

Function Tests and Pressure Tests Are Not the Same

A function test asks a simple question: does the equipment move when it should? The crew operates each ram, the annular, and the controls, and checks that everything opens, closes, and holds its position. Function tests are quick and can be run often, even between wells. They catch mechanical problems like stuck rams, worn parts, and control failures.

A pressure test asks a harder question: can the equipment hold pressure without leaking? Pressure tests are run at two levels. A low pressure test checks the seals at low pressure. It finds leaks that high pressure can push closed or hide. A high pressure test then takes the equipment up to its rated working pressure or beyond. The stack has to hold that pressure for the full test period without dropping. Any leak means the test fails, and the equipment has to be repaired and tested again.

Both tests matter. Function tests prove the equipment works. Pressure tests prove it seals. A stack that passes both is as close to proven as a piece of equipment gets.

When the Tests Happen

The rules set the test schedule. Regulators, including the federal agencies that oversee drilling, publish how often BOP stacks must be tested. Operators do not get to pick the interval. The schedule is tied to well activity: tests happen before drilling starts, at regular intervals while drilling continues, and after certain events like a kick or a repair. A kick is a flow of formation fluid into the well, and it is the event a BOP exists to stop. See the article on well control and kicks for how that response works.

The intervals come from the regulations and from industry recommended practice. API Recommended Practice 53 is the main industry standard for BOP systems, and it sets out the testing procedures in detail. Regulators also specify what gets tested, at what pressures, and how the results get recorded. A crew that knows the schedule can plan around it. A crew that lets the schedule slip is exposed the moment something goes wrong.

How a Pressure Test Is Run and Recorded

A pressure test follows a set procedure. The crew picks a test pressure tied to the rating of the equipment or to the pressure the well could put on it. They close the component to be tested, apply pressure with the test pump, and hold it for a set time. During the hold the crew watches the pressure gauge. A steady pressure means the seals are holding. A falling pressure means a leak, and the test fails.

The result goes onto a test chart and into the test records. Many rigs use a chart recorder that draws a line showing pressure over time, which gives a permanent picture of the test. The records include the date, the component tested, the test pressure, the hold time, and the name of the person who ran the test. A company man, a toolpusher, or a qualified technician usually witnesses the test and signs off. The records stay with the well file, and regulators can ask to see them at any time.

Who certifies the test matters. The person running it has to be trained and qualified, and the signature on the record is a claim that the test was run correctly. Crews file test records in ticket software like OpsFlo alongside the other paperwork for the job.

Why the Paper Trail Matters

The test record is the proof. When a regulator walks onto the rig and asks whether the BOP is in service, the answer is a stack of signed charts and records, not a verbal promise. Compliance is judged on paper. An operator that cannot show a current, passing pressure test is out of compliance, no matter how good the equipment actually is.

The paper trail also protects the next operator on the well. Wells change hands, and rigs move to new locations. The next crew does not know what happened on the last shift. The records tell them when the stack was last tested, at what pressure, and what was repaired. A complete file lets the next operator trust the equipment from day one. A missing record is a reason to retest, and a retest costs time and money.

Pressure testing and the records that prove it are the same job. The test keeps the well safe. The record keeps the operator honest. Both have to be done right, every time, on schedule.

Sources and further reading

• eCFR: Title 30, Part 250 Subpart D
• API Recommended Practice 53
• OSHA: Oil and Gas Extraction