Please login or register.

Login with username, password and session length
Advanced search  


Reading the forum on your cell phone? There's an easier way. We've enabled a Tapatalk app that makes browsing the forum a whole lot easier. Check it out in the iPhone or Android store if you don't own it already.

Pages: [1]   Go Down

Author Topic: Cathedral helmet confusion  (Read 171 times)


  • NEClimbs Newbie
  • *
  • Offline Offline
  • Posts: 1
Cathedral helmet confusion
« on: June 13, 2004, 06:30:50 AM »

Gave three climbers a ride down the road last night. You: dark Honda with VT plates, just finished Thin Air/Toe Crack. Us: Green Toyota pickup from NH. You accidentally made off with my helmet, white BD Half Dome with tick marks on the back, Bell sticker on the front. Please contact me now for an address to mail it to.


  • NEClimbs Newbie
  • *
  • Offline Offline
  • Posts: 2
  • Please see my listing of helmets for sale on eBay!
    • My favorite website
Re: Cathedral helmet confusion
« Reply #1 on: June 13, 2004, 09:26:05 PM »

Hi losthelmet-

I actually STOLE your helmet. Sorry, but I'm way to cheap to buy one so i had to get one somehow. Hope you don't mind.

And what's with the tick marks? Is that the number of times you have successfully top roped Child's Play? Jeez, get a life and start climbing some real stuff, like me, I'm rad.

Maybe I'll see you around.



  • NEClimbs God
  • *****
  • Offline Offline
  • Posts: 3837
  • Nick Goldsmith
Re: Cathedral helmet confusion
« Reply #2 on: June 15, 2004, 06:33:16 AM »



  • NEClimbs Full Member
  • ***
  • Offline Offline
  • Posts: 156
Re: Cathedral helmet confusion
« Reply #3 on: June 15, 2004, 07:44:06 AM »

I was one of the three in that party. thanks for the lift. In the darkness, there was definite confusion, where one of us accidentally grabbed your helmet. This mishap was not discovered until the next day and she felt very bad about it.

PM me your shipping info and it will be shipped ASAP.

sorry about that
Pages: [1]   Go Up

Page created in 0.15 seconds with 22 queries.