Private Forums
Riser running in deepwater: how frequently to test the c&k lines
02 August 2018
Dear all,

As the industry pushes into deeper and deeper water, the BOP/riser running time becomes very significant. We are doing more and more DWOPs for clients drilling in 1500m + water depth.

At this week's DWOP (2000m WD), we discussed optimising BOP/riser running.  The choke & lines are currently tested every 400m.  However, I would like to see if that could be changed to a test once through the spalshzaone, and then before picking up the slip-joint.

What are the rest of you doing and what is your experience? If you are doing as I propose, what are you doing to mitigate the risk (such as new c&K seals every time running the stack.
Key question: Has ansyone ever had to pull back after a failed test? If so, had the seals all been new?

Many thanks


2 answer(s)
Managing Director (
Relentless Pursuit Of Perfection Ltd.
Total Posts: 416
Join Date: 10/01/05
Input from another two Senior Toolpushers working for the same Drilling Co, but different clients:

1. Well that is a tricky one. If the client cannot be negotiated with,  it should be every 10 joints. Most will agree that for efficiency once after connecting the double and splashing the BOP again at the halfway point, again before picking up the slip joint, then after connection of tension ring. Then Land the BOP test the connector once per well after landing stack.

I usually try and get agreement that doing less test as long as the riser is in good shape. We also have to agree that there will be no down time rate applied if there is a leak while we find it.   .

2.  While running riser the connection is tested after BOP is under splash zone 2 joints and then every 10 joints,  and of course at the last connection.

Dave A
Lead Drill Site Manager
Total Posts: 1
Join Date: 14/09/18

For the last few years we have been testing once through splash zone then half way then prior to TJ.

we also don't do low pressure test on rigid conduit , only high test to 5k.

Jump to top of the page