UIE-Wells-NF-201159 Upstream International Europe September 2011

Dropped riser chute bucket during riser running operations

Riser
Target audience for this newsflash Chute
 Drilling Site Supervisor
 Drops Focal points

What happened
Operation at time of incident was running BOP on marine riser. The first joint of
marine riser was being picked up from the riser storage area to the rig floor via Riser
the riser chute. After picking up the joint a distance of approximately 8 – 9m, a Bucket
noise was heard from the area of the riser chute and lifting of riser stopped. On
investigating, it was found that the riser chute bucket normally parked at the
bottom of the riser chute had been lifted up with the riser joint, before coming
free and dropping back down the riser chute to its parked position at the bottom
of the chute. The bucket dropped a distance of 8 to 9m and weighs 1760kgs.
No personnel were in the vicinity of the bucket as it dropped as all personnel are
required to be out of riser storage area during lifting / lowering of riser.

Why it happened
The investigation of this incident is not yet complete.

Suggested toolbox/safety meeting questions

 How do you know that the design of your critical equipment is fit for purpose ?
 How do you know that your critical equipment is well maintained in safe conditions after being used ? Could it be
possible to have any inspection routine to detect any anomalies ?
 Before starting any operation, Do you consider different scenarios to assess and control the involved risk ?
ensure that safety critical equipment is maintained on your site ?
 Once the technical solutions are identified, what systems we should use to log and follow up the implementation of
the corrective actions?
 Do you consider the magement change procedure to implement changes in the equipment?
 Could it be possible to monitor the bucket during operation and/or proper checking of the temporary guides
prior to start running riser ?

Further information
Fountain: # 709977 ; EDM Operational Code: BPR
For more incident details or more information regarding this incident, contact: Chris Holmes