2 day, 534 miles via I-95, I-495, US 29, I-70, I-695 (near Baltimore), I-83, US 30, US 222, I-78, US 22, PA 33, US 209, I-84, I-90, I-290 (near Worcester), I-495 (near Boston) amd MA 2A.
This was a grueling weekend, primarily due to the fatigue from the previous weeks, the complicated route to our overnight stop and the heavy traffic on I-84 through Connecticut. This route, which took us west of Baltimore, Philadelphia and New York, is not the shortest way to get to MA, but it has the very significant advantage of avoiding all of that urban traffic.
Day 1: Lorton, VA, to Milford, NY
This was arguably the most complicated route we have ever taken in a single day. We got lost twice, sort of. My original intent was to take I-495 north, west of DC, but somehow got it into my head that I-95 went west of DC, too. So when I got to that massive interchange in Springfield, VA, where all sorts of major roads meet, I followed the I-95 north signs. I was happily cruising along a few miles later and saw the exit for Mt Vernon. That woke my brain up and made me realize that I was going to pass DC to the east, at a cost of some 10 extra miles. Had I known I was going to go that way, I would have continued up I-95 to just south of Baltimore. But I had planned on going north on US 29, west of I-95, and didn’t want to make on-the-fly changes to my plans, so I continued on to US 29 which turns out to be rather commercial the first few miles. I certainly would have saved time by going I-95. Next time.
The second “lost moment” was in York, PA. The Google map told us to take Exit 18 off of I-83, the GPS told us to take Exit 19 – neither of which were signed to connect to US 30. So we continued on 2 more exits to the US 30 connection. When I looked back at the route, I saw the US 30 runs parallel to I-83 for several miles and I could have cut off 4 or 5 miles by following either the map or the GPS. But I really need to take a close look at those shortcuts before I take them. Shortcuts usually spell trouble for RVs.
We stayed the night at Kittatinny River Beach Campground in Milford, NY. This is a canoeing/kayaking center first and a campground second. I got the impression that many of the campers (which included a lot of tents) were there for the river experience. But the nice couple next to us were there for antique car shows. There was one show that weekend a few miles west of Milford, and one right in Milford starting on Monday.
The campground was water and electric only, which is fine for a night. It actually makes setting up/tearing down much faster.
Day 2: Milford, NY, to Littleton, MA
These 231 miles were easy to navigate. Almost the entire route was on familiar roads. Jett could just sit back and enjoy the ride, except that she didn’t. The traffic was heavy – it always is on I-84 – and most of I-84 was very bumpy, as usual. We tried to stop for gas at the Charlton Service Plaza on the Massachusetts Turnpike, but couldn’t find the diesel. It turns out that diesel is offered on the auto side only on the last pump or two. Message to the Massachusetts Turnpike: some signs indicating where the diesel is located would be useful.
But we actually didn’t need the refueling stop. We made it to our campsite at the Boston Minuetman Campground in Littleton without incident and without the low fuel light appearing.
I will report on the campground after we settle in.
Thus ends the QTE.
Hey, Massachusetts, we’re here! And pissa glad that we made it safely.











































































QTE post-mortem
The QTE was our first attempt at traveling long distances while I continued to work. The strategy was to travel only on weekends and for me to find a good internet connection during the week. So how did that work out for us?
I think if I had to choose one adjective to describe the QTE it would be “exhausting”. Working all week and then traveling all weekend (with me doing all the driving) left me with very little down time. Each travel segment was long, by GTW standards: we averaged nearly 300 miles per travel day as compare with around 200 miles per hop on the GTW. In addition to being long, almost every travel day required a refueling stop, which meant extra planning. And the need for speed meant that we couldn’t afford any scenic side trips, so much of the journey was through parts of the country that we had little interest in seeing.
The high points were: the Grand Canyon (again), Branson, MO, and Lake Havasu City, AZ. Branson was not exactly as I expected, but certainly didn’t disappoint us with the entertainment it offered. It isn’t Las Vegas, but that isn’t necessarily a bad thing. Lake Havasu City – or, more specifically, Lake Havasu and the surrounding desert – was our first experience with intense desert heat. The body wilts quickly under 115-degree heat, but it was interesting to experience it for the day.
The low points were: Georgetown, KY, and the cheap motels that I booked in an attempt to get better internet access than I could get at the RV parks. Georgetown would have left a better impression if it hadn’t poured, but even if the weather had been sunny the RV park would have been a downer. The cheap motels were a waste of money. Lesson: you get what you pay for and that includes internet access. Even when I paid extra for internet and asked for a room near the router the service was mediocre. The best service I got on the GTE was at the RV park in Williams, AZ. Service everywhere else – at both the hotels and the RV parks – was mediocre. I could do my job, but it was difficult.
The bottom line is that working while traveling, while feasible, is exhausting and difficult. We may do it again in October when we head south for the winter, but that remains to be seen. It is not clear that my company will continue to let me work remotely. If they don’t then the work-while-traveling problem disappears, to be replaced by the how-to-pay-for-the-travel problem.