Small tweaks to your hair rig can make a big difference to results.
One of the lessons I’ve had hammered home over the years is that simple changes can do the trick.
Altering the length of hook length, hook bait choice and hair length are often all that is needed to get the spools spinning.
We hear a lot about complicated rig rings with rings and all sorts of supposed anti-eject characteristics – but the basics still count for a lot.
So read on and your hair rig could deliver better results for you…
I’m a big fan of long hairs but switching hook baits on rigs can be problematic.
A change from pellets to half baits, mini boilies or a snowman can leave the hair shorter than ideal resulting in a rig change.
Extended stops were a bit of a breakthrough when they came along.
It’s a simple, ingenious design, coming in three sizes, with different depth hair retaining slots.
The smallest acts as a standard hair stop. The medium and large versions allow you to increase the length of the hair up to another 7 to 11.5 mm without re-tying.
On a typical bottom bait rig I like a good inch or more clearance between hook and bait.
Changing the hook bait to a larger offering or double bait would normally mean a fresh rig.
To tweak the presentation will leave baits crammed up the hair with no clearance between hook and bait.
But so long as there’s enough room to get the baits on to start with, sliding the large extended stop into place lengthens the hair considerably.
Because the extended stops are drawn neatly back into the hook bait, there are only a couple of very small prongs exposed.
The longer stems of the medium and large stops that pull down the hole through the bait make it very difficult for crayfish to remove the stop and pinch your bait.
This is a useful benefit when we’re able to travel abroad, and on the increasing numbers of crayfish venues at home.
All the latest inspiration, tips and guides to help you plan your next Advnture!
Thank you for signing up to Advnture. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.