When a block is not a block
Quote:
Originally Posted by Iceaxe
Yeah... I've been thinking that many of the current practices used by canyoneers should be reviewed. I've been following the Heaps accident discussion on some of the climbing forums and those guys are just rolling their eyes at some of the things we do.
Also.... I thinking it might be good standard practice to use a safety as pictured in Tom's tech tips, and after the safety is removed to have someone down below tie into the retrieval line..... I know many of us use 6mm for our pull chords but there is a good chance 6mm would hold a short fall....
anyhoo.... food for thought.
Well, kinda, sorta. But really, the point is, if the ring is too large and there is even the remote possibility of the biner block pulling through, then you don't have a BLOCK, you have a land-mine-block or a pseudo-block, but you don't have a block.
Tom
Re: When a block is not a block
Quote:
Originally Posted by ratagonia
Quote:
Originally Posted by Iceaxe
Yeah... I've been thinking that many of the current practices used by canyoneers should be reviewed. I've been following the Heaps accident discussion on some of the climbing forums and those guys are just rolling their eyes at some of the things we do.
Also.... I thinking it might be good standard practice to use a safety as pictured in Tom's tech tips, and after the safety is removed to have someone down below tie into the retrieval line..... I know many of us use 6mm for our pull chords but there is a good chance 6mm would hold a short fall....
anyhoo.... food for thought.
Well, kinda, sorta. But really, the point is, if the ring is too large and there is even the remote possibility of the biner block pulling through, then you don't have a BLOCK, you have a land-mine-block or a pseudo-block, but you don't have a block.
Tom
What would you think of putting up some pictures of what not to do? I noticed that every one of your biner blocks have either a safety or a substantial length of cord on the non-weighted side. Under the "Do Not" section you could have:
-A picture of a biner block with only a few feet on the retrieval end - no backup.
-A biner block put on another biner as the anchor (which seems to be the cause of the fatality).
-A quicklink that is too large and will allow a block to slide through.
If you're wondering about my first suggestion, I saw some guys last summer in Spry that were doing something that looked both smart and dumb all at the same time. They ran about five feet of their rope through the rap ring, put a biner block on it, and then rappelled on the long end. Yes, it held, but use of a biner block without a backup or a substancial lenth or rope behind it didn't seem completely secure to me. On the other hand, it worked well because it got they first guy down the rope with a reasonable assurance that he would reach bottom with rope to spare, but with no solid way to keep the rope from sliding on the clove hitch it seemed risky. What are your thoughts?
Re: When a block is not a block
Quote:
What would you think of putting up some pictures of what not to do? I noticed that every one of your biner blocks have either a safety or a substantial length of cord on the non-weighted side. Under the "Do Not" section you could have:
-A picture of a biner block with only a few feet on the retrieval end - no backup.
-A biner block put on another biner as the anchor (which seems to be the cause of the fatality).
-A quicklink that is too large and will allow a block to slide through.
If you're wondering about my first suggestion, I saw some guys last summer in Spry that were doing something that looked both smart and dumb all at the same time. They ran about five feet of their rope through the rap ring, put a biner block on it, and then rappelled on the long end. Yes, it held, but use of a biner block without a backup or a substancial lenth or rope behind it didn't seem completely secure to me. On the other hand, it worked well because it got they first guy down the rope with a reasonable assurance that he would reach bottom with rope to spare, but with no solid way to keep the rope from sliding on the clove hitch it seemed risky. What are your thoughts?
Rope doesn't slide on a properly tied clove hitch or it would not be a suitable knot for a block. I would trust a clove with 5 feet of tail, but I wouldn't use it (if that makes sense?) because I would never have ocassion to do that, based on how I use biner blocks. (The clove hitch biner block is definitely one of those "freak out the uninitiated" knots, like the EDK, that leaves the uninitiated saying "Shouldn't we tie some more knots on that thing?".)
I rarely use a clove hitch block without a backup, except for on the last person down (me, if I set up the anchor) and even then having someone tied into the pull side is a good idea that I've sometimes used. Before the last one or two down, its easy enough to tie a figure eight on a bight and clip that into a bomber anchor, or back it up to another anchor near by (I don't hesitate to use a couple live bodies for a backup where there is a braceable position; but some people take issue with that); or even better, use a contingency anchor. For the last man or two down, the pull chord is lowerd and tested. I like to have two people to visually confirm the final setup, then one goes with a backup and tests and then the final one goes without having to rerig much or anything. If you're the last man down, I think its a great idea to have someone set a belay on the pull strand.
So, yeah, redundancy is important, but not having it shouldn't be classified in the same category as your second and third suggestion.
Related story #1: Once, in my earliest days of biner blocks, I clipped in the rope as a backup and forgot to unclip the rope as I rappelled down. Needless to say, I was immediately ascending back up to fix my rigging once we tried to pull and I realized what I'd done. Luckily it was a short, pretty easily ascendable rappel. Since then I've become meticulous double and triple checker, especially when i'm the last man down.
Related story #2: When Eric and I did Heaps, Eric went down on our tied off 300 (we carried it through, drybagged), and then I tied our two 150's together on the pull side and carefully lowered them to him. He then pulled the knot out past the nasty rope catching lip and tied that pull side to himself or a large boulder. Someone else took care of a fireman belay. Note that we were using rope on the pull side, NOT thin pull cord. We liked this because he rappelled off a tied-in (at the top) anchor and I rappelled off a tied-in (at the bottom) anchor , with the added benefit of having all our knots/biners out past the lip. The rope was threaded through the chain, nothing fancy. Don't take this to mean thats the right way to do the final Heaps rappel. You should already know exactly how to do that for yourself and evaluate for yourself whether you like or don't like this technique... it has its pros and cons that I won't elaborate.
PS.
I like to think of the acronym CHAD when double checking things at every rappel. When I'm a group leader with less-experienced folk I do it for others or try and have them do it. Carabiner (twisted shut), Harness (doubled back), Anchor (checked, depends on the anchor what I'm looking for, but always make sure that you are rappelling on the right strand and the block is set up properly) Device (Make sure the rope is threaded correctly through my rappel device and it's attached to my harness). Unfortunately the name Chad has no special significance for me so I find myself remembering the four things I check and then remembering what the Acronym was :)