Woolly Worm – a horrible looking grub that is awesome
Woolly Worm
Tying Instructions
1. Attach the thread to the hook shank behind the eye and lay a thread base to the bend of the hook.
2. Attach the tail. Usually this is a piece of red yarn which extends about half the gape past the bend. Secure the yarn to the top of the shank for the full length of the shank. On the original, Martinez used Grizzly fibers. Secure the butt ends to the top of the shank and return the thread to the bend of the hook..
3. Attach a piece of chennille at the bend of the hook by the inner core thread.
4. Attach a saddle hackle by the butt just in front of the chennile with the dull side of the hackle facing forward. The hackle should be one size less than the hook since it will be palmered over the body.
5. Wrap the chenille forward to just behind the eye. Make sure to give a full wrap of chenille behind the hackle before proceeeding forward. Tie down.
6. Wrap the hackle forward, palmer style, taking care not to catch the hackle fibers. Note how the fibers go forward. Secure with thread wraps and cut off the tag. Whip Finish.
The Woolly Worm utilizes a palmered hackle along the entire hook shank which has been documented as early as the 1500’s during Napolean’s time. According to A.J. McClane (The Practical Fly Fisherman, 1975), Izaak Walton described the fly in “The Compleat Angler’ (1653) as a simulation of a caterpillar known as the Woolly Bear. One variation, the Palmer Fly, was shown on the cover of R. Brookes book, “The Art of Angling” (1770).
Don Martinez
Sometime in the 1920’s, this pattern was introduced into the United States from England and was used as a Smallmouth Bass Fly in the Ozarks of Missouri and Arkansas. Don Martinez, a West Yellowstone Fly Shop owner from California, received this pattern from a friend in Arkansas sometime in the late 1930’s and created variations that he called “Woolly Worms”. Don Martinez is generally regarded as the individual who developed the modern day Woolly Worm for trout fishing. In the 1940, he wrote to Preston Jennings notes on the pattern:
“This horrible looking grub, Woolly Worm, is a made over bass and crappie fly. Properly fished it is murderous all season long. I made and sold as many of these things as all other flies combined last summer. I hate the looks of them and consider them more a lure than a fly, but they have had a boom for the two seasons last past with no sign of a let up. They should be used only in still or very slow water, fished deep, with a twitching of the line by the left hand. The movement of the hackle is what gets, em, suggesting perhaps the waving breathing apparatus of the may-fly nymphs and others.”
Inspired the Woolly Bugger
The original woolly worm designed by Martinez had a black chenille body with a Grizzly hackle wound along the body and a Grizzly hackle tip for a tail. Martinez attached the hackle at the bend of the hook by the butt and wound it forward with the dull or concave side facing the hook eye. By pointing the fibers forward, the hackle would undulate during the retrieve. Rather then using red hackles for the tail, many woolly worms today use a red wool yarn tag. During the 1950’s this fly was used throughout the west as an imitation of giant stones, dragon flys, crane flies, etc. His Woolly Worm patterns eventually became the inspiration of the Woolly Bugger.
Contemporary Patterns
The body material has been changed on more contemporary patterns of woolly worms. The pattern is popular on Pyramid Lake outside of Reno, Nevada for the large Lahontan Cutthroats. Often, these flies are tied on a size 2 or 4 – 3X or 4X long streamer hook. Estaz or Crystal Chenille is used rather than Chenille. This provides increased action and attraction to the fly. The Hackle has been changed as well. Many of the contemporary patterns utilize a webby hackle such as a Hen Cape Hackle or Rooster Saddle to allow the fibers to flow back towards the rear similar to a bugger pattern. Within these newer patterns, the tail has been omitted completely or substituted with the basal marabou from the saddle hackle.
Used to monitor number of Google Analytics server requests when using Google Tag Manager
1 minute
_gid
ID used to identify users for 24 hours after last activity
24 hours
_gac_
Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together.
90 days
_gali
Used by Google Analytics to determine which links on a page are being clicked
30 seconds
_ga
ID used to identify users
2 years
__utmx
Used to determine whether a user is included in an A / B or Multivariate test.
18 months
__utmv
Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server.
2 years after last activity
__utmz
Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server
6 months after last activity
__utmc
Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session.
End of session (browser)
__utmb
Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server.
30 minutes after last activity
__utmt
Used to monitor number of Google Analytics server requests
10 minutes
__utma
ID used to identify users and sessions
2 years after last activity
SourceBuster is used by WooCommerce for order attribution based on user source.
Name
Description
Duration
sbjs_migrations
Technical data to help with migrations between different versions of the tracking feature
session
sbjs_current_add
Timestamp, referring URL, and entry page for your visitor’s current visit to your store
session
sbjs_first_add
Timestamp, referring URL, and entry page for your visitor’s first visit to your store (only applicable if the visitor returns before the session expires)
session
sbjs_current
Traffic origin information for the visitor’s current visit to your store
session
sbjs_first
Traffic origin information for the visitor’s first visit to your store (only applicable if the visitor returns before the session expires)
session
sbjs_udata
Information about the visitor’s user agent, such as IP, the browser, and the device type
session
sbjs_session
The number of page views in this session and the current page path
30 minutes
You can find more information in our Cookie Policy and .