Derrick and Mast Inspection: The Steel Over Your Head

Every load on a drilling rig passes through the derrick or mast. The drill string hangs from the crown, the setback rack stands in the legs, and the wind pushes against the whole frame. When that steel fails, nothing above the failure survives. The failure is rarely sudden. It starts as a cracked weld, a loose bolt, or a patch of rust at the base, and it grows while the rig keeps working. That is why inspection of the structure is not paperwork. It is the check that decides whether the next load comes down safely.

What the derrick carries and where it fails

A derrick or mast carries the crown block and the traveling block, the drill string, and the pipe racked in the setback. Every one of those loads runs down the legs and into the substructure. The legs work in compression, and compression members do not bend before they fail. A dent, a bent flange, or a corroded section quietly reduces what the member can hold, and the load does not wait for a warning.

Most failures start at the joints. Bolted connections loosen under vibration, and the bolts at leg splices carry the whole load of the section above. Welds crack at their toes and ends, where stress concentrates. At the base, mud, water, and drilling fluids sit against the steel, and corrosion eats inward, often hidden behind paint or scale. The same conditions attack the access ladders crews climb every shift, and fixed ladders on rig structures must meet the requirements of 29 CFR 1926.1053. Wire rope damage follows a different pattern, and it is covered in our wire rope inspection guide.

The API RP 4G inspection framework

API RP 4G is the framework most rigs work to. It lays out an inspection program for drilling and well servicing structures: what gets checked, how often, who is qualified to do the checking, and what has to be recorded. The program runs on two rhythms. Regular inspections follow a schedule and catch wear while it is still small. Detailed inspections are less frequent, use instruments, and cover the structure as a whole.

Special inspections sit between the two. They happen after something changes the structure: a storm, a rough move, a dropped load, a repair, or an event the operator cannot explain. The record is the point of every one of these checks. An inspection that is not written down is not evidence that it happened, and the next inspection starts from the previous record. API RP 54, the recommended practice for occupational safety in drilling and servicing operations, treats the working condition of the structure as part of a safe workplace, so the safety case and the inspection file are the same document trail.

What a third-party inspection actually checks

A third-party inspector starts before anyone climbs. The first task is reading the structure's history: its rated capacity, its past reports, its repairs. That tells the inspector where to look and which tools to bring. On the structure, the work is mostly visual. The inspector looks for dents, buckled members, missing or loose bolts, cracked welds, and corrosion, and marks anything suspicious for a closer look.

The closer look uses non-destructive testing. Ultrasonic testing measures wall thickness in legs and connections and finds corrosion hiding inside the steel. Magnetic particle testing exposes surface cracks in welds that paint hides. Dye penetrant does the same on members where magnetism does not work well. Critical members get the most attention: the legs, the splices, the crown, and the points where the structure bolts to the substructure. If a repair or a rough move is in the file, a load test may be the final check that the structure still holds its rated load. For how a full third-party program runs and how to choose an inspector, see our third-party rig inspection guide.

Keeping the certificate honest

A certificate is only as good as the file behind it. A load test certificate with no supporting report tells the next operator nothing about what was found, what was fixed, and what is still outstanding. The report should name the inspector, the date, the equipment checked, the defects found, and the repairs done. When a member is repaired, the repair record belongs next to the inspection record, because the next inspector needs to know what changed and when.

That file follows the rig. It moves with the mast from location to location, it changes hands with the equipment, and it is the first thing a buyer, an operator, or an insurer asks for. The practical way to keep it honest is to keep it attached to the rig record in field software, so the reports travel with the equipment instead of living in a binder that gets lost in a truck. OpsFlo holds inspection reports, certificates, and repair history next to the equipment record, alongside the tickets, timesheets, and approvals that show the work actually happened. For how long each record must be kept, and what happens when the file goes missing, see our rig record retention guide.

← Back to rigs.work