Skip to content

Tie

Pitzen Knot

Compact high-retention tippet terminal with precise tag path.

Intermediate · Monofilament / Fluorocarbon

Connection card

Pitzen Knot

For line → hook.

What it joins Line → hook. In monofilament, fluorocarbon.
Turns 4 to 7. Count them before you seat it; afterwards you are guessing.
Shape Terminal wrap stack at eye or along shank
Tag end Tag exits clean and short
Seated Fully seated to eye or shank
Start again if Guessed wrap count, uneven stack. The usual unexplained Pitzen break

This card does not say how strong the knot is. A retention figure comes from a bench, in one material, at one diameter, tied by somebody who ties it all day — and the line in your hand is none of those. What it does tell you is whether the thing you have just tied is the thing the record describes.

What this plate is telling you

Compact high-retention tippet terminal with precise tag path.

Save this as a picture and it works with a dead signal and a nearly dead battery, which is when a joint is most often tied badly. The rest of this page — the steps, the seating sequence, the failure modes and the bench — is for the evening before.

Before you start

  • ·Also called the Eugene bend or the 16-20 knot. NetKnots notes it is easier to tie in lighter line or tippet than in heavier line.
  • ·Leave a long tag. Four wraps and the tuck through the finger loop use more tippet than they look.
  • ·For slippery braided line, NetKnots points to the San Diego Jam, a variant that passes the tag through a bottom opening before the top loop.
  • ·Wet the knot before sliding it to the eye, and move it with your fingertips rather than by pulling the standing line.
Line + hardware: Tippet, Fly

Step 1 of 4. Push the tippet through the hook eye and bring the tag back under the standing line, so the tag and standing line run side by side.

How to tie it — step 1 / 4

No drawing of this exact knot yet. The written steps are the reference.

swipe to step

01

Push the tippet through the hook eye and bring the tag back under the standing line, so the tag and standing line run side by side.

You should now see

Two parallel strands leaving the eye with the tag lying underneath the standing line and a long tag free to wrap with.

If it goes wrong

Starting with a short tag. Four wraps plus the tuck through the finger loop use more tippet than they look, and the tag runs out before the tuck.

Fix: Pull more tippet through the eye before you start wrapping. It is easier than finishing the knot with a stub.

Why: NetKnots brings the tag back under the standing line. Following that layout keeps your knot matching the wrap and tuck in the next two steps.

What fails if this is wrong
  • Guessed wrap count, uneven stackThe usual unexplained Pitzen break. Pitzen retention is wrap count and even coil, not folklore.

Watch the tie

Pitzen Knot Tying Instructions - RIO ProductsInTheRiffle · Opens on YouTube

External video from a creator we follow — not produced by us. Nothing on this page loads from YouTube until you follow the link.

Seating sequence — where failures are born

The step list compresses the finish. Run these phases in order, one at a time.

  1. 01 Moisten

    Wet the structure before any load reaches it.

    Zero. Nothing tightens yet.

  2. 02 Load

    Take up slack slowly until the wraps begin to gather.

    Light and even — both ends moving together.

  3. 03 Dress

    Watch the wraps stack in order; stop and back off if any cross.

    Hold, do not pull. Correction happens here or not at all.

  4. 04 Set

    One continuous pull to full seat — no sawing, no jerks.

    Firm, single direction, standing line against the terminal end.

  5. 05 Trim

    Cut the tag square, leaving a short stub proud of the knot.

    None. Never trim under load.

Finished structure — what correct looks like

No drawing of this exact knot yet. The written steps are the reference.

  • ·Terminal wrap stack at eye or along shank
  • ·Fully seated to eye or shank
  • ·Tag exits clean and short
  • ·Even wraps, no crossings

Verify before you load it

Every line is pass or fail. One fail means retie — do not load a knot you argued with.

  • 01Terminal wrap stack at eye or along shank
  • 02Fully seated to eye or shank
  • 03Tag exits clean and short
  • 04Even wraps, no crossings
  • 05None
  • 06pitzen
Something failed → open Diagnose

Field notes — dark, cold, gloves

  • ·Retie by feel first, light second — the seat is a tactile event, not a visual one.
  • ·Gloves off for the dress phase. Fabric hides a crossing wrap.
  • ·Wrong twice in a row means the material or the hardware is fighting you. Change one, not your technique.
HTH · Reference layout

Pitzen Knot — finished-state checks, on the shared reference layout

Pitzen Knot — finished-state checks, on the shared reference layout
Hook the Horizon reference plate
Failure modes

When this family fails, it fails as these. The recovered end still outranks the name.

Jam-hitch terminal family

A compact hitch or jam at the eye — fewer wraps, a different lock than a clinch barrel.

  • !Lock never jammed to the eye — it is a loose hitch in disguise
  • !Used on a small eye that cannot take the bulk of the jam
  • !Confused with a clinch: the tag path is not a barrel tuck
Fails when
  • !Tag passed beside the finger loop instead of through it, so the knot falls apart
  • !Crossed wraps that do not bed evenly, so the knot seats lumpy
  • !Pulled to the eye by the standing line, which heats the line and can leave the knot short of the eye
Geometry
  • Guessed wrap count, uneven stack

    The usual unexplained Pitzen break

    Pitzen retention is wrap count and even coil, not folklore · step 01

  • Seated early on a wrong path

    Locks a defective structure you cannot inspect

    Do not seat until the tag path is the Pitzen path · step 02

  • Tag buried in the stack

    Unverifiable — treat as failed

    A buried Pitzen tag is not a finish · step 03

If you saw this
  • Fails under load

    Check

    • ?Compact even stack at eye

    Then

    • Retie slowly
    • Practice offline
  • Finished check failed — Lost wrap order during the draw

    Check

    • ?Ordered wraps with the distinctive Pitzen draw path
    • ?Coil seats tightly to the eye
    • ?Tag exits controlled

    Then

    • Retie. A misdrawn Pitzen loses the strength that justifies the knot.
  • Guessed wrap count, uneven stack

    Check

    • ?The usual unexplained Pitzen break
    • ?Inspect step 01

    Then

    • Retie. Do not dress a defective structure and call it seated.
  • Seated early on a wrong path

    Check

    • ?Locks a defective structure you cannot inspect
    • ?Inspect step 02

    Then

    • Retie. Do not dress a defective structure and call it seated.
  • Tag buried in the stack

    Check

    • ?Unverifiable — treat as failed
    • ?Inspect step 03

    Then

    • Retie. Do not dress a defective structure and call it seated.
Same family

Same failure class, different geometry. Open the plates — Diagnose still starts from the symptom.

This failed — start Diagnose
The bench · rep 1

Get it right with everything in your favour0/5 clean

Good light, dry hands, a table. Until the sequence is automatic here there is nothing for the harder rungs to test — you would only be learning that difficult conditions are difficult, which you already knew.

How · Tie it, check it against the list, log it. Five clean and the ladder opens.

Conditions for this rep
What went wrong, if anything

Nothing marked. Log it clean, or mark what happened first.

Not ideal for

  • ×Cold hands in high wind without practice
  • ×Braid

Strength, and where the number comes from

Not established

No published break test; NetKnots documents it without a strength claim.

Percentages come from published tests on their own line, their own knot-tyer and their own pull rate. Yours is a different system. Treat a figure as a reason to test, not as a result you already have.

Sources for this record

Record reviewed 2026-08-13

Vetted references

Already tied it?

Check the finished knot against what correct looks like before you load it.