Mud Testing on Location: Density, Viscosity, and the Check That Saves the Hole

Every mud report on a rig starts with a set of tests run at the shakers, in the mud room, or at the trip tank. The numbers on that sheet, density, viscosity, gel strength, filtration, decide whether the fluid keeps drilling or gets treated before it costs the well. This guide covers the standard API procedures, who runs them on location, and how the results become a decision.

What field mud testing covers

Field testing measures the properties that keep the well stable and the hole clean. The mud balance gives density in pounds per gallon, the first number checked after every trip and every treatment. Density is the mud's weight, and weight is what holds formation fluids back. The Marsh funnel gives viscosity in seconds per quart, a quick field reading that catches big changes before they become problems.

Beyond those two, the standard check covers gel strength, measured with a viscometer at 10 seconds and at 10 minutes to show how the fluid sets when circulation stops. It also covers filtration, measured with the API filter press to see how much water the mud gives up against the formation. The chemical side, pH and chlorides, tracks contamination from cement, formation water, or salt. Together these numbers answer one question: does the fluid still do its job?

The API procedures and why they are standardized

The procedures come from API Recommended Practice 13B, issued in two parts. RP 13B-1 covers field testing of water-based drilling fluids. RP 13B-2 covers field testing of oil-based drilling fluids. Both spell out the test in detail: which instrument to use, how to prepare the sample, how to read the result, and how to record it.

Standardization matters because different crews test the same mud on different tours, and the results must mean the same thing every time. A density reading from a clean mud balance, a funnel timed to the API method, a filter press run at the API pressure, all of them give an engineer numbers that compare directly against the plan. The related practice, API RP 13C, covers how drilling fluid processing systems are evaluated, the equipment side that decides what stays in the mud and what gets screened out. When the mud is off, the cost shows up fast in chemicals, dilution water, and lost time. Circulation and mud costs are worth reviewing before the next mud order.

Who runs the tests and when

The mud engineer, usually from the fluids service company, owns the full test program. The engineer runs a complete check at the start of each tour, after major treatments, and any time the well does something unusual: a kick, a loss, a trip. The tour crew runs the quick checks in between, density after each trip and at the start of each tour, viscosity whenever pump pressure or torque changes.

Timing is part of the method. A test run late is a test wasted, because the mud has already changed by the time the number reaches the decision maker. Tests after treatments tell you whether the treatment worked. Tests after trips tell you whether the hole is stable. The mud logger reads the same returns for gas and cuttings, and the two sets of numbers together give the crew a full picture of the hole. Mud logging and gas detection work alongside the same testing routine.

From test result to decision

A single reading is data, not a decision. The mud engineer reads trends. Density climbing over three tours means dilution or a lost-circulation check. Filtration creeping up means the filter cake is weakening and the fluid needs treatment. Every result goes onto the mud report with the time, the depth, and the condition of the well at that moment.

From there the numbers become a recommendation: raise the density, lower the water loss, add bentonite or polymer, or keep circulating and watch. The recommendation and the reason behind it go on the report, and the report goes to the operator's office with the rest of the daily record. That paper trail is what turns a field test into an auditable decision, and it is only as strong as the record keeping. Attach the mud report and its test sheets to the daily record in field software, so the office reads the same numbers the rig tested. Book a working session to see how OpsFlo keeps tickets, dispatch, timesheets, and approvals, with the mud sheet filed alongside the tour record. The mud report also feeds the daily morning report that goes out to the office every morning.

← Back to rigs.work