News:

While the Forum is up and running, there are still thousands of guests (bots). Downtime may occur as a result.
- Alex

Main Menu

Driving a Box Truck North from NC to Providence

Started by LisaW, May 04, 2014, 05:27:11 PM

Previous topic - Next topic

OracleUsr

How are you going to get on the GSP, would be my first question.  Unless you are using the Delmarva Peninsula, you're going to go way out of your way to avoid the NJTP, and you're going to be tolled out the wazoo as it is. 

And if you ARE using the Delmarva Peninsula (I agree it's not a good idea from southern NC) how are you going to use the Cape May Ferry?  I can't imagine them letting a large truck on the ferry.
Anti-center-tabbing, anti-sequential-numbering, anti-Clearview BGS FAN


LisaW

So in response to what OracleUsr just posted and others have referred to, I wonder if my initial question doesn't even apply.  Perhaps I'm just confused in thinking the GSP is even on a route that would make sense for us.   The route suggested by PHLBOS is interesting.   Thanks again everyone.

jeffandnicole

Quote from: OracleUsr on May 06, 2014, 01:13:42 AM
And if you ARE using the Delmarva Peninsula (I agree it's not a good idea from southern NC) how are you going to use the Cape May Ferry?  I can't imagine them letting a large truck on the ferry.

Large 18 wheel Tractor Trailers are permitted on the ferry!  It's pricey though...a one way trip can be as much as $113!

For Lisa's rental truck, the price would be $44 or $50.  Plus the additional car, which is $44.  Plus the additional passanger, who would be charged $10.  So for the single trip, the fare for 2 vehicles and 3 people would be no cheaper than $98!!!  Makes those NYC tolls look like a bargain suddenly.

Here's the complete Cape May-Lewis Ferry fare schedule: http://www.capemaylewesferry.com/SchedulesandFares/Fares/tabid/109/Default.aspx#over


PHLBOS

#28
Quote from: jeffandnicole on May 05, 2014, 04:34:20 PMThe 12' Penske truck isn't 12' high...it refers to the length of the interior.  The actual height of this particular truck isn't more than 10 feet.
Good to know.

Quote from: jeffandnicole on May 05, 2014, 04:34:20 PMAs for the GSP, there are no height restrictions pertaining to vehicles, which means the minimum height is 13' 6".  Large buses use the GSP all the time and there isn't a problem.
The 13' even clearance I was referring to earlier occurs here, at the right lane & shoulder.  Granted, if one just stay out of the far-edge lanes, there shouldn't be an issue.

Truth be told, in all the years I've used the GSP (north of Exit 129) for holiday travel; I've rarely seen trucks (even rental tracks/vans) on that road.  Maybe, those vehicles are on that road at different times than when I'm there.

Nonetheless, since the OP's origin & destination is nowhere near the GSP corridor; why even bother using it at all? 

My listed alternate between Baltimore & Suffern, NY (where I-287 & I-87 come together) not only eliminates using the GSP but it also keeps the OP clear of the NJ Tunrpike construction area (which does back up at times) and saves some money tollwise.  A win-win IMHO.
GPS does NOT equal GOD

spooky

Quote from: PHLBOS on May 06, 2014, 09:02:30 AM
My listed alternate between Baltimore & Suffern, NY (where I-287 & I-87 come together) not only eliminates using the GSP but it also keeps the OP clear of the NJ Tunrpike construction area (which does back up at times) and saves some money tollwise.  A win-win IMHO.

I would also think that the reduced chance of congestion by going further outside of NYC would be desirable, especially if one isn't familiar with driving a box truck.

LisaW

PHLBOS - Thanks for your suggestion.  I'm trying to map that route now using google and/or aaa.   Do you suggest staying on 95 through the DC area, or 295?   It looks like both meet up with 695W.    Or, google is suggesting 495-270-15 to get up to Harrisburg/81N.   Anyone have thoughts on that?   Thanks again for the help.

froggie

The south and east side of the DC beltway (the part that is cosigned as both 95 and 495 and goes across the Woodrow Wilson Bridge)) is longer, but certainly less busy than the north and west side.  If you're going through the DC area, stick with 95.  Do not follow that Google suggestion, as 270 is often as congested as the Beltway.

PHLBOS

Quote from: froggie on May 06, 2014, 04:45:32 PM
The south and east side of the DC beltway (the part that is cosigned as both 95 and 495 and goes across the Woodrow Wilson Bridge)) is longer, but certainly less busy than the north and west side.  If you're going through the DC area, stick with 95.  Do not follow that Google suggestion, as 270 is often as congested as the Beltway.
Ditto.  Just follow I-95 North (including the Woodrow Wilson Bridge & eastern part of the Capital Beltway) up until the I-695/Baltimore Beltway interchange and take I-695 West/Towson exit (49B).  Note: it's a Left Lane Exit.
GPS does NOT equal GOD

LisaW

Is the 83N-81N-78E pretty straightforward?  Once we get to 78E we are on roads we have traveled before, but we've never come up on 83.  Thanks so much!

Duke87

83 exits itself a couple times near Harrisburg. Otherwise it is straightforward, yes.
If you always take the same road, you will never see anything new.

froggie

Personally, I prefer 30 to Lancaster and 222 to Allentown over 83/81/78, even with the traffic north of Reading.  That was my normal route north during my DC-Vermont runs...

PHLBOS

Quote from: froggie on May 07, 2014, 08:03:49 AM
Personally, I prefer 30 to Lancaster and 222 to Allentown over 83/81/78, even with the traffic north of Reading.  That was my normal route north during my DC-Vermont runs...
The 83/81/78 routing was taking into consideration & under the impression that the OP was seeking an all-expressway route.   
GPS does NOT equal GOD

LisaW

What kind of roads would we be on if we did 30-222?   Would prob prefer expressway to lots of traffic lights, but if there's a better alternative we're open to it.   Hoping that it being a Saturday will help overall on the entire route with traffic.   We fly down to NC tomorrow, so last few hours for me to make final route decision.  As I've said before, thanks so much to all who have offered opinions.  I'm sure our trip will be easier because of it.

Chris19001

I'd recommend taking the inner loop of the Baltimore Beltway to 83N, to 81N, to 84E.  You are toll free, well clear of the NYC traffic, and can work down towards Providence once you are in Hartford, CT.  I'd steer clear of I95 in an unfamiliar box truck in NJ and NYC traffic however possible.  Good luck regardless of your route.

Henry

Quote from: Chris19001 on May 07, 2014, 12:28:31 PM
I'd recommend taking the inner loop of the Baltimore Beltway to 83N, to 81N, to 84E.  You are toll free, well clear of the NYC traffic, and can work down towards Providence once you are in Hartford, CT.  I'd steer clear of I95 in an unfamiliar box truck in NJ and NYC traffic however possible.  Good luck regardless of your route.
Another good way to go is bypass I-95 using I-895 (Baltimore Harbor Tunnel) and I-495 in Wilmington, DE. Then take I-476, I-81, I-84, I-384 and US 6. Then again, there's no limited-access companion to US 6, which the original I-84 route to Providence would've done, but it's still the most direct route from Hartford.
Go Cubs Go! Go Cubs Go! Hey Chicago, what do you say? The Cubs are gonna win today!

PHLBOS

Quote from: Chris19001 on May 07, 2014, 12:28:31 PM
I'd recommend taking the inner loop of the Baltimore Beltway to 83N, to 81N, to 84E.  You are toll free, well clear of the NYC traffic, and can work down towards Providence once you are in Hartford, CT.  I'd steer clear of I95 in an unfamiliar box truck in NJ and NYC traffic however possible.  Good luck regardless of your route.
Unfortunately, there's no direct highway access to Providence from Hartford.  I-384 (aka the original I-84) only goes do far and US 6 isn't always a freeway from Manchester, CT to Providence.  Since the OP has now clearly stated that they want to avoid traffic lights (& likely narrow roads as well); that option's likely off the table.

As far as I can tell the only all-expressway routing from the Hartford area to Providence would be to take I-691 East off I-84 and follow to I-91 North to CT 9 South and follow that to I-95 North.  It's a bit round-about in terms of linear direction but it does work.

Quote from: LisaW on May 07, 2014, 12:24:10 PM
What kind of roads would we be on if we did 30-222?   Would prob prefer expressway to lots of traffic lights, but if there's a better alternative we're open to it.
30 does have some traffic lights prior to it becoming an expressway but such is only for a short distance.  OTOH, 222 north of Reading, as Froggie mentioned, does narrow down to an undivided road and has traffic lights from there to the Lehigh Valley.  That can get congested.

Quote from: Henry on May 07, 2014, 01:10:26 PMAnother good way to go is bypass I-95 using I-895 (Baltimore Harbor Tunnel) and I-495 in Wilmington, DE. Then take I-476, I-81, I-84, I-384 and US 6. Then again, there's no limited-access companion to US 6, which the original I-84 route to Providence would've done, but it's still the most direct route from Hartford.
Too much money toll-wise in MD, DE & PA.
GPS does NOT equal GOD

1995hoo

Quote from: froggie on May 07, 2014, 08:03:49 AM
Personally, I prefer 30 to Lancaster and 222 to Allentown over 83/81/78, even with the traffic north of Reading.  That was my normal route north during my DC-Vermont runs...

I agree with this. Depending on the time of day, I sometimes exit at Pennsylvania Route 61 and connect to I-78 that way to avoid Allentown traffic and because it offers a decent number of places to stop for lunch. PA-61 is not freeway- nor expressway-grade and it is a little out of the way compared to going all the way to Allentown; I've used it solely because I've gotten stuck in traffic several times when I've gone directly to Allentown.

To connect from I-83 to US-30 in York, PA, don't go all the way to the US-30 exit. It's out of the way. Instead, take Exit 19 (marked for PA-462, Market Street) and go straight at the light at the bottom of the ramp. It'll take you directly to US-30, where you make a right. Doing this essentially cuts off a long redundant segment that's sort of like making a long U-turn; it also avoids driving on Arsenal Road (who wants to drive on a road that shares a name with those tossers....)

Anyway, US-30 and US-222 in that area are very good roads, pretty much freeway-grade until you get past Reading. I recall the speed limit being mostly 65 mph the last time I went that way. I doubt they'll post 70 mph on those segments. You do need to watch the signs closely around Lancaster (follow the signs towards Reading) and again as you approach Reading (high-speed TOTSO).
"You know, you never have a guaranteed spot until you have a spot guaranteed."
—Olaf Kolzig, as quoted in the Washington Times on March 28, 2003,
commenting on the Capitals clinching a playoff spot.

"That sounded stupid, didn't it?"
—Kolzig, to the same reporter a few seconds later.

jeffandnicole

Whichever route you choose...good luck and hope it's quick and easy!

Let us know which route you decided on when you're all settled!

cpzilliacus

#43
Quote from: LisaW on May 06, 2014, 04:04:14 PM
PHLBOS - Thanks for your suggestion.  I'm trying to map that route now using google and/or aaa.   Do you suggest staying on 95 through the DC area, or 295?   It looks like both meet up with 695W.    Or, google is suggesting 495-270-15 to get up to Harrisburg/81N.   Anyone have thoughts on that?   Thanks again for the help.

Please do not take I-295/D.C. 295/Md. 201/Baltimore-Washington Parkway/Md. 295.  Most of it is only two lanes each way and subject to congestion 7 days a week.

Unless there is a crash, taking I-95/I-495 around the south and east sides of D.C. or I-495 around west and north sides are better alternatives.  The I-95/I-495 south and east side is (IMO) the best.
Opinions expressed here on AAROADS are strictly personal and mine alone, and do not reflect policies or positions of MWCOG, NCRTPB or their member federal, state, county and municipal governments or any other agency.

PHLBOS

Quote from: 1995hoo on May 07, 2014, 01:13:51 PMAnyway, US-30 and US-222 in that area are very good roads, pretty much freeway-grade until you get past Reading. I recall the speed limit being mostly 65 mph the last time I went that way.
Outside of Lancaster City limits, the posted speeds on both the freeway segments of US 30 & US 222 are 65.
GPS does NOT equal GOD

Duke87

Quote from: cpzilliacus on May 07, 2014, 02:44:33 PM
Please do not take I-295/D.C. 295/Md. 201/Baltimore-Washington Parkway/Md. 295.  Most of it is only two lanes each way and subject to congestion 7 days a week.

Besides, trucks are not allowed on the Baltimore-Washington Parkway (MD 295).

83/30/222/78 does shave about 20 miles off of 83/81/78, but the time savings are minimal and there is a slight bit of additional headache involved (which I imagine driving a truck may magnify somewhat). It's a good route but I wouldn't say it is a better route.
If you always take the same road, you will never see anything new.

LisaW

Our journey is complete.   We did 95-695-83-30-222-78-287.    It was easy through Richmond, then again once we got onto 78.  We had intermittent downpours from Richmond through PA,  which never help a long drive.  Despite some traffic and construction, the 95-695 leg seemed like a good choice.  30-222 really cost us some time as traffic at times was at a crawl.  But who's to say if we had gone 83-81-78 that we'd have done much better.  It was probably the first time we've ever sailed right through CT on 95.  Our mapped route estimated 13 1/2 hours.  It took us just under 16 hours, with 3 very quick gas/pee stops.  We made it home safely, so it can only be considered a successful journey.   Thanks again to all of you for your discussions and suggestions.

cpzilliacus

Quote from: LisaW on May 11, 2014, 03:01:30 PM
Our journey is complete.   We did 95-695-83-30-222-78-287.    It was easy through Richmond, then again once we got onto 78.  We had intermittent downpours from Richmond through PA,  which never help a long drive.  Despite some traffic and construction, the 95-695 leg seemed like a good choice.  30-222 really cost us some time as traffic at times was at a crawl.  But who's to say if we had gone 83-81-78 that we'd have done much better.  It was probably the first time we've ever sailed right through CT on 95.  Our mapped route estimated 13 1/2 hours.  It took us just under 16 hours, with 3 very quick gas/pee stops.  We made it home safely, so it can only be considered a successful journey.   Thanks again to all of you for your discussions and suggestions.

Glad you did well.   

Next time, you might consider getting the Inrix smartphone app (works on Andriod and Apple devices), which lets you look at congestion ahead, and modify your route accordingly. 
Opinions expressed here on AAROADS are strictly personal and mine alone, and do not reflect policies or positions of MWCOG, NCRTPB or their member federal, state, county and municipal governments or any other agency.

froggie

Quote30-222 really cost us some time as traffic at times was at a crawl.  But who's to say if we had gone 83-81-78 that we'd have done much better.

In my experience (and I did it extensively for 4 years), 30-222 functions better than 83-81-78, hence why I suggested it.  The only real downside to this routing is 222 north of Reading, though it usually clears out after the first traffic signal past Kutztown.

1995hoo

Quote from: PHLBOS on May 07, 2014, 02:51:37 PM
Quote from: 1995hoo on May 07, 2014, 01:13:51 PMAnyway, US-30 and US-222 in that area are very good roads, pretty much freeway-grade until you get past Reading. I recall the speed limit being mostly 65 mph the last time I went that way.
Outside of Lancaster City limits, the posted speeds on both the freeway segments of US 30 & US 222 are 65.

That's pretty much what I said when I said "mostly 65 mph." "Mostly" means there are places where it isn't 65. I just didn't remember the precise locations where it was lower.
"You know, you never have a guaranteed spot until you have a spot guaranteed."
—Olaf Kolzig, as quoted in the Washington Times on March 28, 2003,
commenting on the Capitals clinching a playoff spot.

"That sounded stupid, didn't it?"
—Kolzig, to the same reporter a few seconds later.



Opinions expressed here on belong solely to the poster and do not represent or reflect the opinions or beliefs of AARoads, its creators and/or associates.