Why Cave Rope Length Isn't Just Pitch Depth

Say a pitch is 28 metres deep. It's a completely natural first instinct to think you need a 28-metre rope, or maybe round up slightly to be safe. Worked through properly, that same 28-metre pitch can reasonably call for a rope closer to 40 or 45 metres — not because the arithmetic is exotic, but because "rope needed" and "pitch depth" are answering two different questions. This article is about that arithmetic and where the extra length actually goes; it isn't a rigging tutorial, and nothing here is a substitute for a trained rigger's judgment about a specific pitch. What follows is worked with the site's own Rope Length Calculator, run directly rather than approximated, so the numbers are real outputs of the same tool you can use yourself.

Depth is the start of the sum, not the whole of it

A rigged pitch needs rope to do more than simply span the vertical drop. Rope is consumed tying off and rigging the top anchor, before the rope even starts its descent. More rope is needed past the bottom of the pitch as a tail beyond the stopper knot, so the working end isn't sitting exactly at head height with no margin. And on a pitch that isn't a single clean drop — one with a rebelay or a deviation, a fresh anchor point partway down used to keep the rope off a hazard — rope is consumed at that intermediate point too, in the knots and wraps needed to re-anchor and continue the hang below it. None of these allowances are exotic; they're just easy to forget when the instinct is to measure the drop and stop there.

On top of all of that, a sensible safety margin gets applied to the total, because real anchors sit a little further back from the pitch head than a tape measure along the drop would suggest, ledges and rub points shift where the rope actually needs to run, and a measurement taken once, sometimes years earlier, is not a promise about the exact conditions on your specific day.

Running the numbers on a real 28-metre pitch

Feed a 28-metre pitch depth into the calculator with no rebelays at all, using its default allowances (2.5m to rig the top anchor, 1.5m of tail past the bottom knot, and a 10% safety margin), and the base length before the margin comes to 32m; adding the margin brings the exact total to 35.2m, which the tool rounds up to the nearest 5m increment — the length rope is actually bought, cut, and marked in — for a recommended 40m.

Now add two rebelays to that same 28-metre pitch, each consuming the tool's default 3m allowance for re-anchoring. The base length rises to 38m (28m of depth, plus the same 2.5m top-rig and 1.5m tail allowances, plus 6m for the two rebelays), the 10% margin adds 3.8m for an exact total of 41.8m, and rounding up to the nearest 5m gives a recommended 45m. Two rebelays, on the same 28-metre drop, move the recommended rope from 40m to 45m — a genuinely material difference that "pitch depth" alone never would have surfaced, and the kind of gap that matters when you're deciding which rope in the club's rope store to actually take.

Every one of those figures — 32, 35.2, 40, 38, 41.8, 45 — is a direct output of ropeLength(), the same function behind the calculator on this site, not a hand-typed approximation. Change the inputs on the live tool and you'll get the identical arithmetic back.

What the number actually means, and what it doesn't

"Recommended rope length: 45m" is an answer to a specific, narrow question: roughly how much rope should you plan to bring for a pitch of this depth, with this many rebelays, before accounting for whatever rigging losses the specific anchor and rock actually demand on the day. It is not a rigging spec, and it is not a statement that 45m of rope, arriving at the pitch head, is safe to descend on without a trained rigger making real-time judgment calls about the actual anchor, the actual rub points, and the actual rope in hand. Real rigging consumes rope in ways a depth figure alone can't fully capture in advance — the precise position of a viable anchor, an unexpected rub point discovered only once the rope is hanging, a knot tied slightly differently than the model assumed. A planning estimate gets you to the cave with a rope that's very likely long enough; it doesn't rig the pitch, and it was never meant to.

Why the safety margin is a percentage, not a flat number

It's worth noticing that the calculator's safety margin scales with the base length rather than adding a fixed number of metres regardless of pitch size, and that's a deliberate, sensible choice. A flat, say, 3-metre margin would be generous on a short 10m pitch and thin on a genuinely deep 80m one, because the sources of real-world slack the margin is meant to absorb — an anchor placed a little further back than expected, a rope that sits slightly differently under load than a tape measurement along the wall predicted — scale roughly with the pitch's overall size, not with a fixed constant. A percentage-based margin keeps the buffer proportionate: a bigger pitch gets a bigger absolute margin, a smaller one gets a smaller one, and the 10% default reflects a reasonable balance between not being wastefully conservative on easy pitches and not being dangerously thin on deep ones.

Where the depth figure itself comes from

It's worth asking where "28 metres" comes from in the first place, because the depth you plan around is only as good as its source. A published pitch depth in a guidebook or a club's trip notes usually traces back to a cave survey — the same tape, compass, and clinometer process covered in this site's article on reading a cave survey, where a slope-distance tape reading and an inclination reading reduce, leg by leg, into a vertical depth figure through simple trigonometry. A well-surveyed pitch, closed against the rest of the system's survey, gives a genuinely reliable depth. A pitch depth passed along informally, estimated by eye, or copied from an old and possibly outdated source deserves more scepticism, and more margin, precisely because the number feeding into the rope calculation is only as trustworthy as the measurement behind it.

This is also a good moment to be explicit about scale: the difference between a well-surveyed 28m and a roughly-guessed "about 28m, maybe a bit more" can easily be several metres either way, and several metres is exactly the range separating "the rope comfortably reaches with tail to spare" from "the rope runs uncomfortably short at the bottom." A planning tool is only as good as the number you feed it.

Why teams carry more than one rope, not just one long enough one

A single rope sized to a single pitch is only part of how experienced teams actually pack for a multi-pitch trip. Redundancy matters at the level of the whole trip, not just within one calculation: a rope that's damaged, wet and swollen beyond its comfortable working diameter, or simply the wrong length for a pitch that turns out different from what the trip notes described is a realistic scenario on any trip into a system with more than one drop. Teams commonly carry a spare rope, or size their rope bag for the trip's longest plausible pitch rather than its average one, for exactly the same underlying reason a caver carries a backup headlamp: single points of failure get planned around at every layer of the trip, not just within one formula.

Why riggers still round up, even past the calculator's margin

Experienced rigging teams routinely carry more rope than even a padded planning estimate suggests, for reasons a single calculation can't fully anticipate. A system's water level can be higher than expected, changing where a safe rig point actually sits. A known anchor might be out of commission — worn, or removed — forcing a rig from a different point with a different effective drop. A team might choose an extra rebelay on the day specifically to avoid a rub point that wasn't obvious from a written trip report. None of these are failures of the arithmetic; they're exactly the kind of on-the-day judgment call a trained rigger makes, and exactly why a planning tool's output is a floor to plan around, not a ceiling to trust blindly.

What the calculator can't see

A depth-and-rebelay-count model necessarily leaves out things that only show up in person: a rope's actual diameter and how much it stretches under load, which affects how it handles at a rebelay; how many rebelays a pitch actually needs, which is a judgment call made on the rock, not a number decided in advance from a guidebook description; and the exact condition of a specific rope on a specific day, wet or dry, new or well-used. None of that is a flaw in the arithmetic — it's simply outside what a depth-and-count model was ever built to know, which is exactly why every figure this calculator produces is described as rope to carry, not a rigging spec to follow. If you're building out a fuller trip plan around a pitch like this — lighting, layering, and a gear list alongside the rope itself — the site's Trip Planning Reference lays several of those planning figures out side by side by trip length.

The takeaway

Pitch depth is the biggest single number in the sum, but it's rarely the only one that matters, and treating it as the whole answer is exactly the kind of gap that catches out someone rigging from a guess rather than a worked-through plan. Run your own pitch's numbers on the Rope Length Calculator before a trip, bring more than the bare minimum it suggests, and leave the actual rigging — anchor selection, rub-point avoidance, and every technique this article deliberately hasn't described — to training and a qualified leader.