SailNet Community - View Single Post - Cotter Pin
Thread: Cotter Pin
View Single Post
post #10 of Old 09-03-2008
Maine Sail
Senior Member
Maine Sail's Avatar
Join Date: Jan 2003
Location: Maine Coast
Posts: 6,386
Thanks: 22
Thanked 301 Times in 233 Posts
Rep Power: 18
One important thing..

One important point no one has brought up is pin to hole clearance. We all know a clevis pin must be the right size for the hole it is fit into to avoid failure and maximize the contact surface area of the clevis pin to the hole in say the chain plate.

I don't like rings and neither does my rigger. Why? Pins are very hard to find in the right wire diameter for the clevis pin end holes they are intended to fit into. These holes need the proper size coter pin and that's easy as coter pins come in many diameters. A cotter pin or ring sized too small for the clevis pin hole IS a potential failure point!

I never reuse a cotter pin and I would never re-use a ring. Talk about being "penny wise pound foolish". My entire lifetime supply and assortment of stainless cotter pins cost me about $35.00 over seven years ago and I still have a LOT left.

The most important thing to consider when installing cotter pins and or rings is the fit in the hole. The pin should be as large as possible yet still fit into the hole.

Years ago I had a goose neck failure on my boom because someone at the factory used an undersized cotter pin that slopped around in the hole until it failed. I replaced it with another cotter pin, of the right size, and it's still going strong over ten years later. In fact I just passed my old boat while sailing yesterday..

I have yet to see a properly sized, bent and taped cotter pin fail though I'm sure it could happen. I have seen one ring failure due to it being undersized..

-Maine Sail / CS-36T

To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts.

Images In Posts Property of Compass Marine Inc.

Maine Sail is offline  
Quote Share with Facebook
For the best viewing experience please update your browser to Google Chrome