Monday, April 29, 2019
Weekly Log: April 22 to 28
Tuesday: 5 Miles
Took monday off as the injury felt like it had taken a step backwards. Felt mostly much better today, definitely some discomfort there. Ran to the student rec field and did laps around there. Tempted to go on the roads, just didn't seem like the right move just yet. Ran on the rec field until I got 5. Actually got into a really quick pace and kept going with it, progressing from 6:30s to sub 6s. I'm definitely out of shape now and sure felt it breathing hard and with a heavy chest throughout. Took a little break halfway to "recover". Besides the hard breathing it felt pretty good. Did a hard stride afterwards across the field, really fun to do something fast.
Wednesday: 1 Mile
Tried to run again, this time on Bremner field which is my favorite of the three. Instantly felt a ton of discomfort/mild pain and when it only got worse, aborted the run after 10 minutes. Big sign that I'm not really getting better through this and time off will almost certainly be a better option.
Really frustrating and annoying, but I'm so sick of running while having to worry about if its good for my leg or not and feeling discomfort/pain. I've tried taking time off and coming back slowly twice now and it hasn't worked either time. Was really excited and enthusiastic during some of last weeks run as it felt like it was getting there, but obviously I overdid something and now as a result, I "can't" run at all again. In terms of races going on, I'm not missing much but I won't be able to run in the Battle Road meet like I was hoping to because there's simply no chance I'll be ready for that fitness wise (and I have no interest in killing myself to run a 9:05 3K and 2:04 800).
My plan is to take as much time as possible to get to 100% healthy and be able to run at least 35 miles my first week back mostly on roads while being able to build up to 50-60 miles within 2-3 weeks and get back to normal training. I'm hoping 8 days will do the trick and I'll start with 5 mile road runs but I don't know. I'm really not interested in jogging 2-3 miles on the turf as I have no guarantee it'll work and it's just no fun. I want to do the Wachusett mountain race, so that would be my next race assuming I'm healthy and at least in better shape. It seems like the perfect crossover between a fast road race and a tough mountain race and I figure the road runner in me (for whatever reason, I seem to be much better at road racing than track or cross country) could lead to success there (and great competition will definitely pull me along). That'll be about 3 months of no racing which is the longest I've ever gone. I'm actually not that bummed out about missing the track season. While it would have been nice to have a comeback season and finally put down some good times, most of the key races I was planning on going to ended up being pretty slow. Even if I was in good shape, slow races are slow races and I probably wouldn't be sub-15 or sub-4 now. It's also somewhat nice to have a break from racing after a really disappointing finish to the indoor season. The one disappointment in not racing is that I was really looking forward to a 10K debut as I think a huge PR would be almost guaranteed. Right now, I'm more disappointed that I'm still not running and I don't know when I will be again. Yearly mileage has probably gone out the window again too, it's so annoying how these setbacks always ruin my bid for a high mileage year.
Weekly Total: 7 Miles
YTD Total: 721 Miles
Highlight: Watched Avengers: Endgame, best movie ever.
Lowlight: Running.
Movies Watched: Observe and Report, Avengers: Endgame, *Bedtime Stories
\
Abs: Everyday but Friday. My quest to get a decent looking stomach is probably actually getting worse because I don't exercise anymore and still eat the same amounts of junk. I do feel like my abs are stronger but need to get into a routine of actually running and eating a little healthier before something starts to change.
Starting to think about summer camping/hiking, excited but still don't really know what I'm doing.
Monday, April 22, 2019
Weekly Log: April 15 to 21
Monday: 30 mins bike, 11 miles
Kept it short as I'm running at least a little now so hard cross training is less necessary. Went a bit easier too. Taking an off day to try to minimize risk of overdoing it too soon/healing better.
Tuesday: 6 Miles
Decided the boredom of the turf was too much and headed out into college woods to explore today. Got onto a decently long trail after crossing the river that was had some fun and challenging singletrack sections. Pretty well marked too. There were a decent amount of off-branching trails I wanted to check out but stayed on the main oyster river trail. Got to a section of easy grass trail but very muddy. Ended up doing an OAB because the trail didn't loop back and I got 6 in total. Leg felt mostly good out there.
Wednesday: 5 Miles
Searched for another trail, foss farm which is a little further out. A couple miles in college woods to get there with more unexpectedly fun challenging singletrack by the river (same trail, opposite direction) before a little bit of road to get there. Foss farm was confusing as nothing was marked and there were a bunch of trail intersections. Tried my best to get onto the main loop but went the wrong direction and once the trail got really narrow I turned around and took the shortest route back to campus. Got my bearings on the way out, will try again at some point.
Thursday: 6 Miles
Had been waiting on new shoes for a while, decided to get my free pair from the school. Finally came in- Nike Pegasus 35, but got the weird flyease variation which doesn't have shoelaces. Seemed really loose at first but was tight in the front of my right foot on the run. Felt super off with the new tight shoes and just overall very heavy/tight today. Some trails again, but a pretty garbage run.
Friday: 3 Miles
Tried to stay on the turf today and go easy but all fields were being used so I was forced on on the trail. Felt some tightness/heaviness but a big improvement on yesterday. Shoes started to get really tight again around 2 miles so I took them off for a minute and when I resumed my leg started to really hurt and I stopped after another mile. Super annoying, not sure if these shoes will end up working out for me.
Saturday: 0 Miles
Everyone was at a track meet so I didn't even bother with cross training.
Sunday: 5 Miles
Stayed on the turf today, alternated loops on the football field and the student rec field. Kinda boring but I think the safest surface until discomfort recedes again. Leg never felt as bad as Friday but still felt worse than the rest of the week. Wore a new pair of Kinvara 10s, fit felt much nicer although still really stiff as its a new shoe.
Weekly Total: 25 Miles
YTD Total: 714 Miles
Going to pass on highlights/lowlights, just hard to do when I'm only running 25 miles. Was happy with my beginning of the week runs, felt mostly good and thought it was improving but end of the week was suddenly really rough. Maybe it might have been better to stay with older shoes, despite them being pretty worn out (for a week or so). I wanted to get to maybe 45 with some on roads next week but that clearly isn't happening now. Definitely a bit frustrating, hopefully just a temporary block and I can be back to 60+ and get into good shape in the next 3-4 weeks.
Movies Watched: Apollo 13, Green Book, A Star is Born
Tuesday, April 16, 2019
Weekly Log: April 8 to 14
Recovery week, final stages of healing before being able to run again.
Monday: 0 Miles
I think I said this last week but was scared/worried about the possibility of a stress fracture that I didn't exercise and got it checked out instead, which was pretty much confirmed not to be. Any pain also went away rather suddenly (after waking up).
Tuesday: 40 mins bike, 15 miles
Wednesday: 45 mins pool run
I feel like biking for cross training is pretty straightforward but pool running is unclear to me on what effort I should be putting in and what form I need. I find that when biking (and especially running) an easy effort is very distinct from a hard effort but in pool running its all the same. I'm never going easy, but I'm never pushing either and I don't feel like I could push myself in either direction. With the form of pool running, I just don't see how I go any faster or slower, its almost locked in. Also, should I be using the belt? I always do because when I don't it's nearly impossible just to stay afloat but it definitely feels like it makes it a little too easy.
Thursday: 45 mins bike, 18 miles. Pushed it pretty hard, top overall speed on any of these rides.
Friday: 2 Miles
Jogged around Bremner field (turf field next to the track) as there was some practice going on on the football field. Ran barefoot, for some reason I thought that would be better. Felt entirely normal to start, but very heavy and awkward. Discomfort increased throughout, never any pain but not as great as I wanted to feel. Did get smoother towards the end.
Saturday: 3 Miles
Bunch of laps around the Student Rec field before the track meet (another turf field a little further down, lacrosse game using football field). Decent amount of discomfort right away which was a little concerning but all went away rather quickly and I actually felt much better than the previous day. Tried making another loop as the field is adjacent to college woods, but just found that very muddy and abandoned that immediately. Wore shoes on this one, I think that helped.
Sunday: 4 Miles
Other fields were in use, so today I ran on the turf inside the track. Didn't actually enjoy it as much, I liked using the entirety of the other fields whereas I now I have this huge track and stadium surrounding me. Additionally, the other fields were almost exactly a quarter mile per lap while this field was quite a bit shorter and the routine felt a little messed up. I wanted to run on the brand new adjacent soccer field but I guess its still under construction because I couldn't find anywhere to enter (although saw kids running and playing soccer on it yesterday). Got bored of the laps and did a college woods loop before returning to the field. On/off discomfort but the best day yet.
Weekly Total: 9 Miles (better than 0, right?)
YTD Total: 689 Miles
Weekly Highlight: I said I wasn't going to do a highlight, but despite a little increase in discomfort I was mostly pleased how the transition back to running went. Not extremely smooth or effortless but unlike some past injuries, I feel like I mostly made the right decisions here and am able to run at this point in time rather than taking more time off. The turf was inevitably but just fun to be running again.
Weekly Lowlight: Nothing specifically bad about this week, obviously always a bummer to be in recovery mode than full training mode but at least that part is getting better.
Abs Status: As fat and flabby as ever, extended to 7x/week (once a day) rather than 3 which was kinda tough at first but is (hopefully) now part of my routine. I don't think the lack of exercise (not running 60+ miles a week) is helping shed the fat either so just hoping to at least look somewhat better in a month or so.
Movies Watched: Lilo and Stitch, Mulan
Season Update (4/16): Thought about this quite a lot the last few weeks and the more I do think about, the less optimistic I am about having a season. Recently it's been more 50/50, but who am I kidding? With the amount of time I've had off and the lack of time I will have to prepare, there isn't really a good justification for trying to race at Pre-Conference (4/27) as I more than likely will be in terrible shape and use up a season of eligibility for one race. A bit of a disappointing conclusion, but I decided today I will not race this season. I'm considering doing a 3K at the Battle Road TC Meet #2 (UMass Lowell) on May 18, but my enthusiasm has also decreased greatly for that as well. Why rush my training just so I can run one race? It'd be nice to finally crack 8:40 but there's no guarantee and if I'm not going to PR, I don't really want to waste a lot of time doing specific (and difficult) training for it and waste a weekend racing.
Anyway, here's a tentative schedule for summer racing. I'm signed up only for Mt. Washington, Blessing, Beach to Beacon and Bottone so anything could change. I'd like to do some hiking as well which could take the spots of some of these races.
Question of the Week: Do I train for/race the 3K at the Battle Road meet?
Tuesday, April 9, 2019
Weekly Log: April 1 to 7
Big questions on the future of this season.
Not going to bother putting 0s in the mileage, every day this week was a 0 due to a planned no-run/full week of rest to attempt to heal the injury.
Monday: 40 mins stationary bike, 14 miles
Tuesday: 45 minute pool run
Wednesday: 45 mins stationary bike, 16.2 miles
Thursday: 50 mins stationary bike, 17.2 miles
Friday: 35 mins stationary bike, 13 miles
Saturday: 45 mins pool run
Sunday: 1hr5min stationary bike, 20.6 miles
Weekly Total: 0 Miles
YTD Total: 680 Miles
Stationary bike mileage: 81 miles
Abs status: As flabby as ever, going to increase quantity per week
Going to wait to do highlights/lowlights until I'm healthy and running again.
Movies Watched: Roma, Triple Frontier, Boy Erased, Shazam!, Glass
Injury Update (4/9): I think neglecting cross training initially was a mistake and it does feel like I'm still getting some work in. That being said, if I'm out long term it's way too tedious and simply not enjoyable to do every day or even at all. I don't know where I'm at right now. Initially the severe pain Sunday dropped down significantly, but remained pretty consistent with little improvement for the rest of the week. Running again Monday was a no go. After discussing with my coach, the possibility of a stress fracture was there, but after meeting with a doctor yesterday, that was pretty much ruled out.
I think it's going to be pretty difficult to compete this season, given how short it is. Even if I managed to get healthy really soon, I'm probably not going to be in great shape if I do race in some of the later meets, and personally I'd rather focus on training than racing if I'm not ready for it. I think some more time off is required, but I'd be surprised if I wasn't ready to at least run lower, easy mileage soon. I really don't know, but I think there's at least potential to race at some open meets come Mid to late May.
Question of the week: How much fitness does cross training maintain (compared to a normal training schedule and compared to doing nothing)?
Saturday, April 6, 2019
Highpointing Year 1: 2018- The Northeast
Back in 2017, when I began to drive on my own, I started to think about getting in some hiking adventures. The views and the terrain of the mountains of the Northeast seemed like something that needed to be experienced, and after completing a few I was instantly hooked and left wanting more. I found out about the 50 high points and while extremely ambitious, it seemed like just the motivation I needed to tackle travel and hiking in a way I never had before. My original plan was to hike 5 of 6 New England highpoints- RI,CT,MA,NH,VT while also getting NY and NJ. The logistics of getting to Mt. Katahdin (ME) seemed far too difficult and would likely have to wait.
About six months after initially setting this goal to get all 50 state high points, I had not only gotten the 7 I had set to conquer, but had the addition of a Mt. Katahdin summit. I additionally completed some great bonus hikes, including Breakneck Ridge, Mt. Tom, several peaks in Acadia National Park and the biggest and most epic adventure I've been on, the Presidential Traverse. There were difficult times along the way, but overall I went on a lot of really fun adventures. 2018, in many ways, was a disappointment, but in hiking it was a massive success.
Here is the full list of notable hikes/mountain runs/high points I completed in 2018:
*Note that Talcott Mountain is not actually a mountain, rather just the highest point in a ridge.
This post will be focused on high points. As you can see above, I completed my last high point in August so you may be wondering why this post is coming so late. I had two items of evidence I wanted to have for highpoints- a gps track (strava activity) and footage (youtube videos). The second part I really procrastinated on doing (video editing) as I had many hours to sort through to make these finished videos. I got the first two up and running fairly quickly but I didn't touch the rest until December and generally completed a video once every 2-3 weeks. After publishing my final video about a month ago, I finally am ready to create a recap of this post. I'll embed my videos in the post, note that most of them are made to showcase the views and terrain of the hike and not be entertaining. The first bunch are either shaky or poor quality, the second half is much better.
Basically for this post, I will be going through each highpoint and giving a write-up with details on what happened and how I felt during the hikes as well as listing things I did or did not like. I'll give each a relative summary for both difficulty and enjoyment and rank them at the end. I'll also put a link to my strava activity with some statistics at the beginning of each.
High Point #1: Jerimoth Hill, Rhode Island (812 feet)
Friday, March 9th, 2018 (12:10 PM)Strava Activity- .4 miles, 14 minutes, 0ft elevation gain
I begun my high point journey over a year ago. Jerimoth hill is essentially a walk in a park with a 10 minute round trip experience from the start point. It's literally an easy and short walk and with no real challenge to it comes no real reward. At this time, I had enjoyed going on a fall hike with track friends Sam and Sebastian and was looking to follow it up as many other plans had fallen apart. That date had ended up being a free date and whatever reason, Sam and I went on a couple short hikes pretty close to home. I wasn't even starting to bag high points at this time, but Jerimoth Hill had been on my bucket list for a while, and having a free day and someone to go with me gave me an excuse to finally get it done. After all, if you're a hiker who lives in the smallest state in the country, shouldn't you have been to the highest point?
We also went to beavertail state park, roger williams zoo and lantern hill that day, but I believe a direct drive from Westerly is about an hour. It's not really close to anything, and will likely be out of the way no matter where you live (unless of course, you lived in the area). Jerimoth Hill is somewhere on route 101 in Foster, RI but is stupidly difficult to find. There is a sign for it, but if I recall correctly, the trail entrance is actually a tenth of a mile away from the sign and across the street. There's also no parking lot whatsoever (although apparently from other's experiences, there is a parking lot and the trail entrance is very clear, so maybe I'm retarded or something) so I had to park on the side of this pretty busy road. There was a decent amount of snow on the ground that day, which made the trail a little more enjoyable as there's really nothing special at all about it. It's a pretty straight and boring quarter mile walk from there on a wide dirt trail that literally doesn't change at all. There's a few signs here and there that make it somewhat unclear where the actual high point is, before coming to a bigger opening and the high point is represented on a rock just around the corner. We cleared off the snow to see the circular metal marking showing the highpoint and signed the trail register, which was perhaps the only neat part of the journey.
Backtracked out of there with one highpoint wrapped up. I had plenty of great footage that day, showing the trail in the snow as well as views of the highpoint itself and the trail register. For whatever reason, my SD became corrupted and I lost all the footage, including additional footage on other walks that day which was a real shame. I ended up coming back on a very rainy day in April and filmed the walk from the road to the high point, but because of the rain, the quality is extremely poor. I don't really have any pictures either, as there's isnt much that looks photo-worthy and I wasn't really committed to completed or documenting the high points at that time. Here's the video below:
High Point #2: Mt. Greylock, Massachusetts (3,491 feet)
Sunday, April 15th, 2018 (9:52 AM)Strava Activity- 10 miles, 4 hrs, 2,328ft elevation gain
Like Jerimoth Hill, Mt. Greylock had been on bucket list for a while and having been the most excited for this one, it was the natural next high point for me. Despite being the next closest high point (tied with CT/NJ), it was still 3 full hours drive away and require a free day. Spring break rolled around, and the first sunday seemed like the perfect time to go. Got Sam on board again. We left at a reasonable hour, 6:45AM which was early enough to allow us to get there with plenty of time to get a hike in, but not a ridiculously early start that would tire us out. 3 hour drive was okay, the part between Westerly and Springfield on highways went by quickly, but the rest was on pretty rural roads which seemed to take a while. We took a quick break at nearby Hoosac Valley High School which offered our first views, and just for fun I ran a quick lap on their track. I even called it random track lap on strava. The mountain looked massive from the high school, which only added to my excitement.
I was looking to bag an extra peak or two and the mostly out-and-back Appalachian trail would get me the additional Saddle Ball Mountain, the second highest peak in the Greylock Range and in Massachusetts. At 7.5 miles, getting to climb primarily on the Appalachian trail and getting the two highest peaks in the state, this seemed like by far the best option. However, after doing more research, I realized that the parking lot for the route required driving on roads that were closed until May, and I had to quickly scramble for new options. I was disappointed, but found another route that still covered Saddle Ball Mountain and the Appalachian trail, the only catch was that it was now 10 miles, which was a little more than I was looking to do.
Parked at the Cheshire Harbor parking lot with the intent to hike Cheshire Harbor trail-Old Adams Road-Appalachian Trail-Summit-Appalachian Trail down-return on Cheshire Harbor trail. We saw there was some snow on the ridgeline driving over, and I was definitely expecting a cold one. What I did not expect, however, was the amount of snow and water that would end up being on the trail.
Begun the hike just before 10. The beginning of Cheshire Harbor trail was very easy, a wide non-technical trail with a decent although not steep incline. It was pleasant to start the hike this way and we made it about a mile before we got to a point where the trail was entirely covered with snow and ice. The trail became dirt again just past the mile and at the intersection of Cheshire Harbor and old adams road. Made the turn onto old adams road. The hike began to decline in enjoyment as old adams road was a long (2-mile) and boring stretch of wide trail. The real problem, however, was the trail was entirely covered in running water and we had to awkwardly walk on sloped snowbanks to avoid getting wet. While there would be breaks where we could walk back on the main trails, a large portion of the trail went on like this, which was not fun at all. To be fair, there were some cool parts as well, including both bridges and small waterfalls.
After a while, it became long and boring as I awaited the turn on what promised to be more exciting terrain of the Appalachian trail. Just before the turn, we approached snow yet again but this was a different, more pleasant experience. While the snow covered the trail entirely, it was crunchy rather than icy or wet and made for very easy walking conditions. The markings for the AT were really confusing but after a while we made the turn- and were instantly presented with a new problem. the snow was frozen over. This would be okay, if not for the footprints that were molded into the trail. This made for awkward stepping into and out of frozen holes, generally having slanted steps and hitting my legs/ankles against the hard snow.
![]() |
| White blazes of the Appalachian Trail. |
I don't remember that section being particularly long (to be honest though, I don't remember a whole lot writing this a year later) and fortunately we soon started an ascent that was less gradual and more steep. The steeper grade was much more difficult to climb and I enjoyed the feeling that I finally felt like I was putting work in, especially compared to the relatively easiness of the rest of the hike so far. For reference, the average grade at this point (1000ft in 3.3 miles) had been 6% and now the grade, at least for the next half mile was around 15%. This was an enjoyable and more challenging section, although the frozen footprint problem still persisted somewhat. I was actually surprised to come up to a section of trail with no snow on it, but as soon as I turned the corner, the snow followed.
After the climb breathed a little life back into a pretty dull hike, I was very excited to soon summit Saddle Ball Mountain and get above treeline. While it would likely be very cold and exposed, I was looking forward to epic views of the surrounding mountains and hopefully more rocky terrain. My watch's elevation inched closer and closer to the 3,238 foot elevation of Saddle Ball mountain and I thought it be any moment before we'd break treeline. Eventually, the trail flattened out considerably and I continued on a flat section. Soon I realized the ridge was entirely covered by trees without exposed sections and that we must have sumitted Saddle Ball Mountain without even realizing it. I had been used to the typical Northeast summit of a exposed section of rock with views for mile, and in contrast the not only completely unremarkable summit in the middle of the woods but also unmarked summit of Saddle Ball was a massive disappointment. However, Greylock still remained and I was excited for that.
The next two miles of the hikes had probably the best hiking terrain as the trail followed the mostly flat ridgeline. Despite being over 3,000 feet in the air, there wasn't anything to see due to thick pine tree cover. However, the cold air, combined with the nearby trees, snow and elevation did create a cool feeling of being in the wilderness. The downside of that, though, was that it was really cold. Despite the tree cover from the wind, the temperature was much lower and I felt frigid for most of that portion. Additionally, this was another 2 mile stretch and just felt really long. We took a couple breaks but motivation was low. Eventually we got closer and it became more promising seeing the first trail signs in over half an hour as well as starting to climb again. Getting to the top of Mt. Greylock was also extremely disappointing however, as while there were no more trees, a thick fog covered everything. There were absolutely no views to be had here today, the only thing I was hoping could save the hike. I literally couldn't even see 200 feet in front of me. It was also brutally cold up there, so after checking out the tower on top (maybe you can go in during the summer?) we made the trip back. The signs were way off and showed 6 or so miles back to the parking lot when it should have been around 3. This was concerning but I remained confident that the signs were wrong. We took the Cheshire Harbor trail back down, which was very similar to the trail at the beginning- a wide, wet and slippery mess. There was flowing water going all over the trail and made it difficult to get back down. Sometimes we even opted to go off the trail in order to avoid ice or water.
The signs had been wrong, and we returned to the parking lot at 10 miles and 4 hours, both longer than expected. I was glad to cross off the high point, but extremely disappointed that I didn't get to experience any fun terrain or incredible views. The 3-hour drive home felt long and I was pretty tired. We stopped by the same track as before, and this time Sam joined me for a track lap. I went barefoot and couldn't even finish the full lap on the track as it really hurt.
The video below shows off a little of everything I talked about- dry trail to start, wet and icy trail, crunchy snow, hard frozen snow with footprints, cold looking wintry conditions and a complete lack of views at the top. The quality is not great and it's somewhat shaky, but is definitely a huge improvement over the first one (although that's not saying much). I do like the shot of a frozen over pond at 14:17, as it really shows how cold it felt and looked that day.
Summary: Mount Greylock may be special, but I certainly did not have a great experience there. The combination of tough, snowy and icy terrain, brutally cold wintry conditions and the complete lack of views at the top made it hard to say any positive about this one and feel really disappointed. However, a huge portion of why I really didn't like this hike was the winter-like conditions of water, ice, snow and fog but even taking that out, the saddle ball summit still would have been disappointing and the terrain was pretty basic and unremarkable (and very flat-feeling). Mount Greylock is a probably a decent hike, I just had too many bad conditions come together on this but it's hard to imagine this being great even had I hiked it two months later (although I assume the views are spectacular). One hiker on alltrails said of the hike, "If you want to feel like Frodo bringing the one ring to the fires of mount doom, the trail between Saddle Ball and Mount Greylock can definitely help". Unless I missed a scene where Frodo walks for 30 minutes on a boring, flat, and viewless trail through the forest, I'm not sure how accurate this is. Mt. Greylock definitely has more to offer than my experience, but I was so disappointed I don't really have any interest in going back. Either way, I got the high point done but it was another unenjoyable one and not the reason I wanted to do high pointing in the first place.
High Point #3- High Point, New Jersey (1,804ft)
Strava Activity- 3.7 mi, 1hr12min, 560ft elev gain
I had gotten pretty lucky with Greylock as track season got really busy from early April and didn't conclude until Mid June. With school and track, there was no room for the time and effort hiking would take and it would have to wait until the summer. The week off with April vacation provided a time for easy training and allowed for one or two adventures, but HP #3 would have to wait for 2 months later. I never forgot about it, and planned enthusiastically for a 2-day trip with my friend Frank that involved lots of hiking in NY/NJ and possibly even some kayaking. He bailed on me on pretty short notice and I ended up (immediately after coming back from NC for track nationals as well, so I was less eager to leave) cutting out a lot of the planned activities and just going for a one day trip.
New Jersey was the next logical high point for me to get, especially as I could combine it with other sights/hikes like the Hudson Highlands. Being in the Northwest corner of NJ, it wasn't especially far away nor was it urban. I had initially considered adding on the CT high point, as neither would be long or difficult hikes, but given the amount of driving time it would add (it's really rural and hard to get to) I decided just to go for one as I had the entire summer to get the rest.
I tried to get up early to get as much as possible in that day without getting back really late. It started with a one shot drive to the NJ high point in High Point State Park (Sussex). The drive on the way back would at least be broken up by some stops. I had planned a 4:30AM departure but ended up going at 5:30, which was still good enough. The route brought me on various routes through CT and NY on some busy highways before dumping me out on more rural roads. It was pretty long, 3 hours in total but I don't remember feeling really tired or bored. Parked at the visitor center office where I used the bathroom and picked up the trail map before starting the hike.
NJ is a high point with many options and like many others, simply driving to the top is one. Considering it wasn't a super tall high point, I didn't want to waste time on flat trails so a 1-2 mile trail to the highpoint would do. I began the hike at the parking lot, crossed the street before walking across a field to get to the white-blazed Appalachian trail. From there it was mostly pleasant and just under a 2 mile walk to the high point. I wasn't expecting much so I was pleasantly surprised by some difficult rocky terrain in places. The weather was really nice in the morning, about 60 degrees so this was not a sweaty and hot hike by any means. It was fun to have a only slightly challenging and short walk through the woods especially as many others would be much harder. There was one point that opened up slightly and offered a view of the high point monument briefly. Halfway into the hike, I came upon an observation deck that offered great views of the monument, which appeared to be much further away than within a mile.
After that I continued on and soon took a turn off the Appalachian trail towards the high point which was only a brief section. This connected to a wider trail where I could see the monument right next to me to the right and I came out to a large parking right next to the monument. The views around were panoramic of green hills/small mountains and quite beautiful, something I wasn't really expecting in NJ. After walking around, I climbed to the top via the stairs which was decently long. The top was a disappointment as there were loud fans up there and the windows were pretty gross/blurry and the views were significantly worse than those at the base.
Finished up with that and decided to walk back on the road. Got pretty disoriented and ended up walking about a quarter mile in the wrong direction before getting back on track. The road was fairly quiet as the trail had been and I actually enjoyed that part as well. Plenty more driving that day as I added on a nice hike up Breakneck Ridge and a short visit to Kent Falls in CT (both about an hr drive from the previous destination). On the way home from there, my phone died and the car charger stopped working so I pretty much had to guess where to go and eventually found my way back to 95. I actually ended up getting back in time to watch the fun run, so that was nice.
High Point #4- Mt. Washington, New Hampshire (6,288ft)
This wasn't a huge deal, but instead of leaving comfortably in the early afternoon Thursday, we'd have to leave more towards 3 or 4. I wanted to arrive in the White Mountains in the early evening to relax before the big hike, get a quality dinner and use the pool in the hotel. I had also planned on going to the nearby Great Glen trails fun run which I was done years back and should be fun. Now we'd likely be getting there when it's dark, miss the fun run and have to get dinner on the way. The sleep window would also shorten significantly, something that was obviously important before the big hike. While I was going up for the hike, it was disappointing to not get in a little extra fun, which was really 100% Sebastian's fault as he told me pretty last minute. This didn't change much on the big day, but sure made getting there a lot less fun.
2) The Weather Forecast
I had been so excited for this one day and upon checking the temperatures, there were Thunderstorms forecasted for the entire afternoon up in the Presidentials. Normally, I wouldn't care but given my lack of experience, I didn't want be an idiot and put myself or others in danger. I also feel like I read that the hike shouldn't be done in Thunderstorms. I immediately started worrying that we'd have to do an alternate hike, maybe just a half traverse or just a Mt. Washington summit or whether that meant skipping the trip altogether. In the end, it meant too much to me and we kept the original plan.
3) I hadn't researched the Transportation
As cool as the Presidential Traverse is, the one thing that is an absolute pain in the ass is that it's one way and the roads to the start and end go much longer than the trail does. For example, the traverse is around 20 miles but the shortest drive length from start to end is about double that. Considering I only had one car, I had to figure how to get transportation from one end to another. I figured I would just Uber and that would be cheap, maybe there wouldn't be Uber at 5 in the morning to get me to the start but surely in a huge tourist destination like the whites, they must have cars running in the evening? Nope, no Uber. Looked at the other options, the AMC shuttle service. Sounds perfect! Only the schedule is extremely inconvenient for hikers attempting a one-day traverse. We had a strict 5AM start time to make sure we weren't finishing in the dark, and I don't remember exactly but the shuttle didn't run until at least 9 or so. It also didn't work out in the evening. In the end, there was only one other option left, some White Mountain Taxi service. They didn't run that early in the morning, so we'd have to get picked up after the hike. Sounds fine, only they charged $150 for a 40 minute drive. Really frustrated like both the above problems, but again, if I wanted to go and do this, there wasn't much of a choice.
Thursday rolled around. Picked Colby up first. We waited outside the Cooked Goose for Sebastian for an hour after he said he was getting out and finally made the trek to New Hampshire. Stopped for dinner at some decently nice rest area with only local chains. It got insanely dark in the final hour or so and we had a scare when a deer popped out of nowhere. Somehow got to the hotel at 10pm. I feel like all driving with some stops takes twice as long as it should. And of course, the pool closed at 10pm. They asked me to check in by showing that I had the debit card I booked the hotel with which was really lucky (that I had it on me), because what if I had booked it with my parent's card? The hotel was decent. I was too excited to fall asleep and none of us really got to bed until midnight, which was good because we only had to get up...at 3:30am!!
It might have 3:45 or so, but obviously not much sleep that night, probably not a great idea before a 20-mile hike with 9k feet elevation gain. I had a quick oatmeal before heading over to the Daniel Webster trailhead. I'm pretty sure it's a Presidential Traverse as long as you get a certain number of Presidential peaks, and other than that, you're free to take whatever route you want. I had no idea what I was doing, and after seeing that the FKT was mostly run starting from the Daniel Webster trailhead, I figured that was likely the fastest/easiest route (Note: the current FKT, broken after I did this hike, was done from the Valley Way trailhead where most others doing the hike came from that day). We got there just past the planned time and started at 5:20AM.
I broke my video into three parts, so that's what I'll break my write-up into as well.
Part I: Start to Madison Hut
The trailhead turnoff was somewhat difficult to spot and I ended up missing it and having to turn around. The usual trailhead parking was entirely closed off, and we had to park in a small grass/dirt area and take the "detour" trail. Parked, got out and started the hike.The detour trail was quite annoying and unenjoyable. It was basically a dirt road with high grass in the middle that was sometimes unavoidable and would brush against your leg. The problem was that the grass was really wet and just 10 minutes in my, my legs and feet were soaked. Not a great start nor is there much to write about this section. Boring, unremarkable terrain that can really be found in any forested area, and avoiding wet overgrown sections for much of it. There was a short bridge crossing over a stream, but thats all I can remember.
After one mile of that (17 minutes), we made the turn onto the real trail, the trail we would have begun at had there been no detour. We instantly began a significant climb towards the peak of Madison and the steep and wooded trail was already much more interesting than what we had come from. However, the next two miles weren't that actually all that great. While it was more fun to ascend now, we gained nearly 2K feet over the next two miles under treeline. This was pretty tiring this early in the hike, and I felt that by excessive sweating. Heat and humidity didn't help, nor did constantly running into spider-webs. I began to feel so gross, with my shirt slowly being covered in sweats and spider-webs on my skin that I took my shirt off. That wasn't a perfect solution either, as my backpack straps became soaked in sweat and would feel disgusting every time it shifted around. Probably one of the biggest drawbacks to summer hiking is that it can be really hot/humid and being soaked in sweat is no fun at all. I also wrote in my description that there were some bugs, but I can't really recall that (problems with writing posts so late).
Maybe 1.5 hours into the hike, we started getting our first glimpse of views of surrounding mountains and I was excited to break treeline soon. Climbing began to get even steeper and rockier, while heat/excessive sweat reduced as we became more exposed. I put my shirt back on at some point. We broke treeline and came out to a massive boulder field unlike any I've ever seen before. The views back in the direction we had come from were now stunning and suddenly, it felt like we were really high up. The boulder field was so much fun to scramble around on and was challenging as the boulders were much harder to traverse around on as opposed to dirt trail. According to strava, this quarter-mile section was 40+ percent grade. This was a very slowing moving mile due to both the terrain and grade, but this was far more exciting than pretty much any trail I had done in the past, so I enjoyed it. I tried to film as much as possible of this, but the footage came out really shaky as this section really required both hands to get around. There were a few spots where it was difficult to see where the trail went, and occasionally I would get in a bush area and have to backtrack. We slowly progressed towards a ridgeline and I was the first to break it.
Immediately upon breaking ridgeline, I was greeted with the best views I have ever seen, including Mountain Washington in the background with Jefferson, Adams and Madison somewhere to the side. It was hard to discern exactly which peak was which or whether or not I was on top of Madison already. Additionally, it was so exposed that it was suddenly extremely windy and I felt quite cold. I lingered there for a couple minutes, checked my map (which nearly was blown away by the wind) and waited for the others to catch up. We turned to the right and continued on, now on a much clearer and more discernible trail with the first AMC signs (with mileage). It was still fairly technical and steep and also seemed to go on for some time. Eventually, we got to a flatter section of trail in the middle of which lied the mount madison summit. There were no marking nor did it look like a summit, and I had no idea that I was even on it. We hiked on a mostly flat (although still very technical) ridge for a while before starting to descend which is where I realized the Madison summit was behind me. The trails had been mostly clear and in good condition other than the below-treeline trails but the Madison descent continued the technical boulder scrambling, except this time, the rocks were wet and very slippery. This wasn't the same insane boulder field as before, and there was space between rocks but it was still a large boulder field nonetheless and was impossible to get through without stepping mostly on rocks. I stopped filming here because I was slipping quite a bit and wanted to focus on getting down without a wipeout. There were plenty of close calls (my shoes also have no traction though) and I eventually went down pretty hard which hurt. I was relieved to get past this section to a short trail with some pine trees with the hut just behind.
![]() |
| Washington in the distance. |
![]() |
| Love the AMC signage. |
Waited up for the other guys and then went in the hut. I don't remember exactly, but I was surprised to find there was no food or trash in the hut. I believe there was a hose or sink for water refills and a bathroom, but it was certainly more crude than expected. Regardless, it was a nice place for a quick rest for the legs.
Part II- Adams, Jefferson and Washington
![]() |
| Jefferson, Adams and Madison in background (l-r) |
Part III: The Second Half
![]() |
| Monroe |
![]() |
| "Lake" of the Clouds |
![]() |
| Darkening skies |
![]() |
| Eisenhower |
![]() |
| Eisenhower Summit |
Ranking of Peaks (terrain, views, summit, overall satisfaction): Adams, Jefferson, Madison, Eisenhower, Washington, Monroe, Clay, Franklin (honestly have no idea what this summit is/looks like), Pierce (just rock slab in the forest)
High Point #5- Mt. Mansfield, Vermont (4,393 feet)
![]() |
| Cabot Creamery |
Slept in pretty late (9 or 10ish) and then continued to sleep/lay awake because it was pouring out until 11. Ate breakfast and got going on the hike super late at like 11:30. The one nice thing about it was that we could hike directly from the campsite and the 2-night minimum didn't require us to pack up just yet. Walked on the road a little before taking the Houghton trail, a half mile long pretty flat and boring trail leading out to the Stowe ski resort. The next half mile was pleasant, a slight downhill on gravel service/ski roads with better views and clear skies. We made a turn onto our first real trail, the Haselton trail after that. The Haselton trail was what got the hike really going. It was probably an average 20% grade on steep and rocky singletrack through the forest, which was definitely pretty tiring. It was hot and humid out and now that I was exerting a pretty good effort, I got really sweaty and took my shirt off. There also was just about nobody else on the trail (probably because I took my shirt off). This trail was only a little over a mile in the wooded portion, but a long and tiring one at that. There wasn't much break in the climbing at all and we gained about 1,500 ft before exiting the woods onto a grass ski slope again.
It was nice making progress towards the top of the mountain and first views started to come into sight. However, moving out of the woods got rid of the shade and it was suddenly brutally hot and exposed. The grade got even steeper on these ski slopes/gravel roads but it wasn't technical at all. Halfway up on the grass section, we saw a wooden stand with a guy standing behind, and it was quite a pleasant surprise to see that he was giving out free, ice cold and delicious lemonade. One of the strangest yet coolest encounters I've had hiking. He said he hadn't seen many other hikers as well and I talked to him briefly about other peaks. He took a photo of us and I ended up finding it on the merrell magic website later.
![]() |
| Lemonade Stand below |
Took in a minute to soak in the views before beginning the descent. We continued on, descending the other direction of the of the long trail. Unlike the final ascent, the descent was immediately steep and very technical, including some hands on rock scrambling. This was enjoyable, although its always much harder/out of control to go down instead of up. The trail quickly went back into the forest and the trail remained steep and rocky throughout. In a little over two miles, I had dropped 3000 feet in what felt like a long and exhausting time, coming out to a road. Waited up for Matt there before walking back on the road to the ski resort, walking back through the service roads and back on the houghton trail to smuggler's notch. It was actually really difficult to spot the trail coming from the other direction and it took some wandering out/backtracking to eventually get on. By the time we came out it was already 4pm, way longer than I had anticipated and we needed to get a move on. Packed up really quick, took a shower and unfortunately plans for camels hump or a local fun run were both scrapped due to the lack of time. We were in Burlington around 7pm and I decided to go for my run there, knowing I'd get to the campsite really late either way. My legs were exhausted but I enjoyed being on the Burlington bike path with incredible views of Lake Champlain. Despite being tired too, I made it progressive and dropped a bunch of low 6s/high 5s at the end.
![]() |
| Base of Mansfield, Stowe Resort |
![]() |
| Lake Champlain at Sunset |
It got dark driving over pretty soon. Google maps showed to get on a ferry which seemed really weird to me (apparently its totally normal, cheap and simple i just didn't want the hassle of figuring that out at the time) so I took an extra half hour detour south. Eventually crossed into the NY border, and I'll leave that for my Mt. Marcy/NY Portion of the post. To be continued...
Summary: Mt. Mansfield certainly had some sections of uninteresting terrain that felt like a slog, but I guess that depends on what route you take. The Haselton trail was surprisingly tough and the Long trail up to the summit was surprisingly easy and offered phenomenal views. However outside the mile and a half leading to the summit and the quarter mile after it the terrain or views were mostly unremarkable. I know this is for the specific hike I did, but only half an hour of the hike was really amazing. Overall it was a good hike with phenomenal views, but I certainly would have liked more challenging rock terrain/ascents for a longer portion of it. It's a bit too easy for the views that are offered, whereas the presidentials made you work for those views. This is probably middle of the road in these rankings. The incredible views and decent elevation profile put it above any of the first three but the lack of really challenging terrain ensures that it never really competes with the Presidential Traverse. A recommend, but there are almost certainly better hikes out there.
High Point #6- Mt. Marcy, New York (5,344 feet)
High Point #7- Mt. Frissell South Slope, Connecticut (2,380ft)
Found the red blaze and got going. Similar to NJ, there wasn't much elevation gain at first and the trail was mostly flat dirt single-track with some rocks in there. It had rained before and there was some on/off rain during the hikes and the terrain was pretty wet. This wasn't a problem at first on dirt, but when we got to rockier terrain, it made everything very slippery. Found a cool orange salamander on the trail. After a quarter mile, the terrain suddenly became rocky and steep. It was never technical, just the flat slabs or rock seen on many other trails. The grade actually got up to the 20-30% range, so for a quarter mile, there was about 300ft of climbing on the steep rock. This wouldn't be too difficult, but the wetness of everything made it somewhat slippery and slow going. The climbing leveled off as soon as we came out to an open rock area where the summit of Round Mountain (CT) lied, marked by nothing more than a cairn. It was really foggy out and there were no views to be had whatsoever.
Continued on following the red blazes and started to notice how overgrown a lot of the trail was, which was made even more annoying as all the plants were soaked and I'd constantly have water running down my legs. We encountered one human on the trail, who suggested to also get the Mt. Frissell summit and not just the high point which was just off the trail. There was another short section of steep climbing before coming to an intersection. Just 50 or so meters to the right lied the summit of Mt. Frissell (MA), viewless and surrounded by trees. It was actually marked by a laminated sign with a register below that I signed. I noted that the other signature from today, the guy who we had passed before, had written that he had completed the Seven Summits and was working towards the 50 high points which was pretty cool.
When we got back the guy from before was there and invited us into his camper across the street. I probably wouldn't have felt comfortable going in myself, but Frank went in first and I didn't want him to get murdered or raped. Worst case scenario, it'd still be 2 against 1. (obviously joking, but what's the right thing to do here? The guy seems like another friendly hiker, but at the same time it doesnt seem right to get in a vehicle with a complete stranger). The guy actually ended up being pretty nice and offered us drinks and said if we wanted, he would talk at our respective universities. He gave me a business card as well. Got out there and made a quick stop at nearby Bash Bish falls which was a really cool waterfall and the trail to get there was a steep and technical downhill for a half mile. It was raining pretty hard, so we didn't stay and made the 3-hour drive back to Westerly.
![]() |
| Bash Bish Falls |
Summary: This was definitely one of the less exciting and unremarkable hikes I went on, especially coming off three big mountains. It's kind of in the middle of nowhere and isn't all that fun to get. The views were still solid and the terrain fun and challenging in its own way, although the overgrown trails are pretty unacceptable and going on a rainy day obviously didn't add to the experience. This is a perfectly okay walk/hike but is so short, it can't really compete with most other high points. It's certainly in a nice area that is worth checking out but overall another one that is hard to recommend if not going for the high point.
High Point #8- Mt. Katahdin, Maine (5,267 ft)
Got going on the hike as it could certainly be a long one. It was little harder to keep a consistent pace as I had continually wait up for my company and I found that my rate of hiking was significantly slower than usually. I generally got far, far ahead before stopping for long breaks. The initial trail was rather easy, wide and not very technical. I do like a hike that starts out this way and the first part almost serves as a kind of warmup. It was a quarter mile to the junction of Helon Taylor and Chimney Pond and turning onto the Helon Trail did mark some increase in difficulty although it wasn't until over a mile in that the steepness and technical factor became quite difficult.
I remember almost nothing of the below-treeline ascent. It was pretty uneventful and I got pretty far ahead, determined to move along at a good pace. The trail was a steady 20% grade or so, but the real challenge was large boulders in the middle of the trail that required careful use of all four limbs. There were a decent number of rock obstacles and I would say the helon taylor trail was surprisingly difficult. Around 2.5 miles, I got past treeline and the views behind were pretty spectacular, just miles and miles of the Maine wilderness. Up to this point, I had been pestered by bugs, heat and constantly having to pass/getting stuck behind people then getting repassed but fortunately most of that ended here.
The hike to Pamola peak, while still steep and with plenty of rocks was fairly easy. Except for a few spots, the placements of rock was pretty to get around/through and there wasn't much of a challenge overall. There was some more trail through trees but eventually the trees stopped and there was only exposed rock ahead. The last mile or so of trail was all pretty much the same and it seemed to take forever to get to the summit. The surrounding terrain was pretty similar to that of the whites- lots of rocks and grass everywhere. The view instantly changed at the top of Pamola peak with the entire ridgeline of the Knife's Edge trail coming into view, trading the rocky and grass alpine views for those of only steep and jagged rock ahead. The views were probably best here and were pretty unique as opposed to the pretty similar feeling of the ascent. I did the first part of my video up to this point:
The initial descent down was very easy, neither steep nor very technical. The terrain once again felt very much like the whites, and felt similar to some section of the Traverse. The views were stunning here as well. The next turn was onto the saddle trail, which was instantly insanely steep and very slow going due to that. It wasn't technical but had a lot of gravel/sand which made slipping pretty easy. This was a short section but had a grade probably over 40%. Once we got past that, it was pretty easy from there on out. I had a quick PM issue immediately after that and was unable to get into the forest due to how dense the trees were. Filled my water bottle with ice cold stream water (I know you're not supposed to unless you have the materials to clean it, but it seemed clean enough) and soaked my feet as it was a pretty hot day.
![]() |
| Brutal descent on Saddle. |
It was around here that my watch was showing low battery and I kept the rest of the activity on my phone. My watch battery is pretty poor and I'm thinking about getting a new one that can support longer hikes as my phone's GPS data can be a little messed high in the mountains (I did the same thing on Marcy and when i looked at the phone data it had gone completely haywire and showed 70 miles with the map going crazy). Got to chimney pond campsite and checked that out for a little bit including chimney pond itself before moving. The rest of the hike was fairly similar to other descents after that. Tired and wanting to be done and without steep or technical terrain but enough to both that the legs were still taking a beating. The alpine forest was still pretty cool though and I enjoyed being in that. Took a little detour to another pond/lake before trudging on for a pretty boring last couple miles. Finished up around 2 and was grateful for the first time in any highpoint not to drive afterwards.
![]() |
| Chimney Pond |
![]() |
| Basin Pond. |
Summary: Katahdin isn't a super special hike on the surface, but there are a couple factors that push it ahead to be the second best high point/hike I've done. Most of it is no different from many other New England/Northeast peaks- difficult, steep terrain with great views but what really sets it apart is the knife's edge trail, easily the most brutally technical trail I've done and completely different from possibly anything on any Northeast hike. It's difficult but a blast to hike on that kind of terrain and adds quite a bit to the hike. I imagine a hike up Katahdin not using the Knife's edge would be enjoyable/worthwhile but add nothing extra seen in a typical Northern new england mountain. Additionally, being so far north the trees/overall scenery did feel more tundra/alpine like which was pretty cool and it was definitely enjoyable being in the Maine wilderness. Katahdin is so far out of the way it isn't something that can likely be done often, but it certainly a must-do at least once.
High Points Wrap-Up/Rankings
Essentially over the course of five months, mostly from late june-early august, I confirmed and got going on a big goal of mine and brought hiking into my life in a big way. Despite some decline in running success, this was a really fun endeavor to take on and I feel that completing all 8 was a big accomplishment, especially with my limited hiking experience in the past. I'm certainly still no hiking expert and probably appear like a rookie, but now have essential experience planning and completing some moderate hikes in the Northeast.While there were plenty of difficult miles in there, it wasn't the hiking itself that presented a challenge (although it will in the future) but rather the planning around getting to and completing each of them. I ended up doing a lot of the planning pretty last minute, but fortunately it all worked out for the best. The one thing I didn't like was the tired driving. Through the 7 high points and 6 trips (NY-VT were merged, I didn't have to drive in ME), I drove about 45 hours total and I'm sure at least of a third of that I was ready to die.
This was a bit of a money suck, but it was well worth it. Overall besides the driving, I have no complaints. I had several epic experiences, a few pretty good ones and a few mediocre ones as well. But the feat of having these 8 behind my back feels pretty good and gets me excited for more.
It's unfair to rank the high points exactly (variety of routes and conditions), note that in the rankings below I am ranking based on my personal hikes/experiences as recapped above in several categories. Each is ranked worst to best, with a worse ranking getting a higher number (ex. 8 is the worst/easiest ranking, 1 is the best/hardest).
Views
8. Jerimoth Hill
7. Mt. Greylock
6. Mt. Frissell South Slope
5. High Point
4. Mt. Mansfield
3. Mt. Marcy
2. Mt. Katahdin
1. Mt. Washington/Presi Traverse
Terrain
8. Jerimoth Hill
7. Mt. Greylock
6. High Point
5. Mt. Frissell South Slope
4. Mt. Marcy
3. Mt. Mansfield
2. Mt. Katahdin
1. Mt. Washington/Presi Traverse
Notes: If for best terrain among any part of the trail, the Knife's Edge would take this one, but the quantity of the terrain over the hike gives The Presidential Traverse the easy win.
Difficulty
8. Jerimoth Hill
7. High Point
6. Mt. Frissell South Slope
5. Mt. Greylock
4. Mt. Mansfield
3. Mt. Katahdin
2. Mt. Marcy
1. Mt. Washington/Presi Traverse
Youtube Videos
8. Jerimoth Hill
7. Mt. Frissell South Slope
6. High Point
5. Mt. Washington/Presi Traverse
4. Mt. Katahdin
3. Mt. Greylock
2. Mt. Marcy
1. Mt. Mansfield
Notes: 3-6 can definitely be interchanged, 4-5 have better shots being on nice mountains and with the gopro but I feel like the greylock video is just a much more concise/trimmed down vlog of the hike whereas 4-5 are obviously way too long and 5 is pretty shaky. High point is a decent but okay video, just not much to show. Frissell isnt very exciting and jerimoth hill is very blurry. The two I'm happy with are Marcy and Mansfield, especially Mansfield. They're much more trimmed down and there's a lot less raw/tedious hiking while still having plenty of beautiful shots.
Overall
8. Jerimoth Hill
7. Mt. Greylock
6. Mt. Frissell South Slope
5. High Point
4. Mt. Marcy
3. Mt. Mansfield
2. Mt. Katahdin
1. Mt. Washington/Presi Traverse
Notes: I would probably only do the Presidential Traverse again, due to just how many mountains there are out there.
Other Hikes/Runs
The highpoints made up the majority of my mountain/trail adventures for the year but I still did do a decent amount of other adventures. This is a highpoint recap, so there won't be full recaps for any of these.Mt. Tom (MA), May: Mt. Tom was a mostly easy 7 mile hike designed for a fun weekend activity. There wasn't a lot of challenge but the views were surprisingly really nice and a good portion of the hike took place on a ridgeline with very fun, technical terrain. Definitely a great small hike, only disappointment was the summit which was covered with radio towers and fences. (w/Frank and Matt)
Castle Craig (CT), June: A very difficult but fun run up East and West Peak in Meriden. Brutal, insanely technical climbs that were honestly a complete blast. The views in Western CT are always going to be of roads and buildings but if you looked the other direction, they weren't half bad.
Breakneck Ridge (NY), June: A short but pretty awesome hike with amazing views of the Hudson river and nearby Hudson Highlands. One brutally difficult and insanely technical mile of rock scrambling (1k feet elevation gain), a lot of fun.
![]() |
| Storm King Mountain, across the Hudson. A peak for another day... |
Talcott Mountain (CT), July: Enjoyable and challenging run in CT state parks. Had fun on the rocky, rolling terrain of Penwood State Park and while Talcott was a little more boring in comparison, the Hueblein Tower a the top was really cool. One of the best trail runs I've been on.
Camden Hills (ME), July: First day up to the top of Mount Battie auto road and back, fun with pretty great views. Second day, a brutal and hot ascent up Megunticook, later smashed my knee into a rock garden. Not so fun.
Acadia National Park (ME), August: 3 short and amazing hikes, easily a "bang for your buck" kind of thing. Packed a lot of fun terrain and views of the Atlantic on par with some of the better highpoints in just under an hour. Lots of fun scrambling on rock and iron rungs. Beehive, Precipice Trail and Beech Mountain. Love this place, want to attempt to get every peak here sometime in the future.
2019 Plans
| Eastern High Points on google maps- note that many of them line up well |



























































































































































































