Seeking Advice on Drive to Cape Cod

[Anonymous]

Anonymous wrote:I do this drive a couple of times a year. Leave at 4:30 if you can at all swing it. On a normal day you'll be in NJ in about 2 hours, which is unthinkable any other time of day.

Starting this early it almost never makes sense to take the Tappan Zee. Go for the GW bridge, but keep a map app on to redirect you if there's construction or accidents.

I don't know that I've ever done the same route through CT twice. Some combination of 15 and 95 is the way to go, so long as you get there early enough.

The bridges over the canal are a crapshoot. Traffic there will depend more on the day of the week than the time of day.

Getting up early really makes the difference. Traffic gets worse as the day goes on, so every delay compounds itself with delays further north. Taking alternate routes like the Tappan Zee or up to 84 in CT only "saves" time by going around the most congested areas. I find that leaving a half hour earlier will save up to 2 hours in travel time, whereas byzantine detours might shave 30 minutes off a traffic-clogged nightmare.

I agree with all of this. I’ve done this drive 3-4 times a year. I typically monitor the routes as I go through NJ, 9 times out of 10 I go over the GW. I aimed to be in my car driving with kids in pjs in the back BY 5 at the latest. My goal was always 430, but getting last minute food/snacks/electronics always takes me longer than hoped and I know myself well enough to not get up before 4.

[Anonymous]

Anonymous wrote:

Anonymous wrote:I do this drive a couple of times a year. Leave at 4:30 if you can at all swing it. On a normal day you'll be in NJ in about 2 hours, which is unthinkable any other time of day.

Starting this early it almost never makes sense to take the Tappan Zee. Go for the GW bridge, but keep a map app on to redirect you if there's construction or accidents.

I don't know that I've ever done the same route through CT twice. Some combination of 15 and 95 is the way to go, so long as you get there early enough.

The bridges over the canal are a crapshoot. Traffic there will depend more on the day of the week than the time of day.

Getting up early really makes the difference. Traffic gets worse as the day goes on, so every delay compounds itself with delays further north. Taking alternate routes like the Tappan Zee or up to 84 in CT only "saves" time by going around the most congested areas. I find that leaving a half hour earlier will save up to 2 hours in travel time, whereas byzantine detours might shave 30 minutes off a traffic-clogged nightmare.

I agree with all of this. I’ve done this drive 3-4 times a year. I typically monitor the routes as I go through NJ, 9 times out of 10 I go over the GW. I aimed to be in my car driving with kids in pjs in the back BY 5 at the latest. My goal was always 430, but getting last minute food/snacks/electronics always takes me longer than hoped and I know myself well enough to not get up before 4.

Totally worth it, unlike some other places.

[Anonymous]

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:I do this drive a couple of times a year. Leave at 4:30 if you can at all swing it. On a normal day you'll be in NJ in about 2 hours, which is unthinkable any other time of day.

Starting this early it almost never makes sense to take the Tappan Zee. Go for the GW bridge, but keep a map app on to redirect you if there's construction or accidents.

I don't know that I've ever done the same route through CT twice. Some combination of 15 and 95 is the way to go, so long as you get there early enough.

The bridges over the canal are a crapshoot. Traffic there will depend more on the day of the week than the time of day.

Getting up early really makes the difference. Traffic gets worse as the day goes on, so every delay compounds itself with delays further north. Taking alternate routes like the Tappan Zee or up to 84 in CT only "saves" time by going around the most congested areas. I find that leaving a half hour earlier will save up to 2 hours in travel time, whereas byzantine detours might shave 30 minutes off a traffic-clogged nightmare.

I agree with all of this. I’ve done this drive 3-4 times a year. I typically monitor the routes as I go through NJ, 9 times out of 10 I go over the GW. I aimed to be in my car driving with kids in pjs in the back BY 5 at the latest. My goal was always 430, but getting last minute food/snacks/electronics always takes me longer than hoped and I know myself well enough to not get up before 4.

Totally worth it, unlike some other places.

It is, but it is a solid 9 hour drive without traffic and absolutely minimal stops (depending on where you are heading on the Cape, we go to my parents in Chatham).

[Anonymous]

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:I do this drive a couple of times a year. Leave at 4:30 if you can at all swing it. On a normal day you'll be in NJ in about 2 hours, which is unthinkable any other time of day.

Starting this early it almost never makes sense to take the Tappan Zee. Go for the GW bridge, but keep a map app on to redirect you if there's construction or accidents.

I don't know that I've ever done the same route through CT twice. Some combination of 15 and 95 is the way to go, so long as you get there early enough.

The bridges over the canal are a crapshoot. Traffic there will depend more on the day of the week than the time of day.

Getting up early really makes the difference. Traffic gets worse as the day goes on, so every delay compounds itself with delays further north. Taking alternate routes like the Tappan Zee or up to 84 in CT only "saves" time by going around the most congested areas. I find that leaving a half hour earlier will save up to 2 hours in travel time, whereas byzantine detours might shave 30 minutes off a traffic-clogged nightmare.

I agree with all of this. I’ve done this drive 3-4 times a year. I typically monitor the routes as I go through NJ, 9 times out of 10 I go over the GW. I aimed to be in my car driving with kids in pjs in the back BY 5 at the latest. My goal was always 430, but getting last minute food/snacks/electronics always takes me longer than hoped and I know myself well enough to not get up before 4.

Totally worth it, unlike some other places.

It is, but it is a solid 9 hour drive without traffic and absolutely minimal stops (depending on where you are heading on the Cape, we go to my parents in Chatham).

Travel time doesn't matter to people who like that area, or have family and friends in that area.

[Anonymous]

It was 9 1/2 hours for us from Hyannis but with a ton of traffic 1 quick lunch break and 1 restroom stop.

It is a mystery why the map apps refuse to recognize the Tappan Zee bridge.

[Anonymous]

Do whatever WAZE or Google Maps says at 5 am on the morning you leave. Keep the app up the whole time (bring your car charger). We go up to Connecticut and Rhode Island at least 2-3 times a month. We don't plan ahead. We pull up the app and does what it says. (And I mean it about keeping the app open the whole time. Sometimes it can save you 2-3 hours if the app senses a problem ahead and diverts you.)

[Anonymous]

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:I do this drive a couple of times a year. Leave at 4:30 if you can at all swing it. On a normal day you'll be in NJ in about 2 hours, which is unthinkable any other time of day.

Starting this early it almost never makes sense to take the Tappan Zee. Go for the GW bridge, but keep a map app on to redirect you if there's construction or accidents.

I don't know that I've ever done the same route through CT twice. Some combination of 15 and 95 is the way to go, so long as you get there early enough.

The bridges over the canal are a crapshoot. Traffic there will depend more on the day of the week than the time of day.

Getting up early really makes the difference. Traffic gets worse as the day goes on, so every delay compounds itself with delays further north. Taking alternate routes like the Tappan Zee or up to 84 in CT only "saves" time by going around the most congested areas. I find that leaving a half hour earlier will save up to 2 hours in travel time, whereas byzantine detours might shave 30 minutes off a traffic-clogged nightmare.

I agree with all of this. I’ve done this drive 3-4 times a year. I typically monitor the routes as I go through NJ, 9 times out of 10 I go over the GW. I aimed to be in my car driving with kids in pjs in the back BY 5 at the latest. My goal was always 430, but getting last minute food/snacks/electronics always takes me longer than hoped and I know myself well enough to not get up before 4.

Totally worth it, unlike some other places.

It is, but it is a solid 9 hour drive without traffic and absolutely minimal stops (depending on where you are heading on the Cape, we go to my parents in Chatham).

Travel time doesn't matter to people who like that area, or have family and friends in that area.

Ahh, yes it does when your hamstrings are cramping, babies are screaming and you are just entering Rhode Island. There’s no denying the drive is rough if you go straight thru. I’m the Chatham driver. Yes, it’s worth it, but it ain’t fun.

[Anonymous]

Re the Cape Canal Bridges — how backed would you expect them to be around 10 pm on Thursday July 1?

[Anonymous]

Anonymous wrote:Re the Cape Canal Bridges — how backed would you expect them to be around 10 pm on Thursday July 1?

Honestly? bumpah to bumpah for a long while.

[Anonymous]

Anonymous wrote:

Anonymous wrote:Re the Cape Canal Bridges — how backed would you expect them to be around 10 pm on Thursday July 1?

Honestly? bumpah to bumpah for a long while.

LOL. Even at 10 pm? Hmm. It’s easier for me to do a nighttime drive than a morning drive. But I guess if my kids are asleep in the back, I can deal w/ traffic. Thanks!

[Anonymous]

Anonymous wrote:Re the Cape Canal Bridges — how backed would you expect them to be around 10 pm on Thursday July 1?

I think they will be fine at 10 pm. The holiday is Monday and people coming Thursday would likely already be on the cape by 10 pm. I'd probably do the Bourne as that gets less Boston traffic, but see what maps tells you.

[Anonymous]

Anonymous wrote:

Anonymous wrote:Re the Cape Canal Bridges — how backed would you expect them to be around 10 pm on Thursday July 1?

I think they will be fine at 10 pm. The holiday is Monday and people coming Thursday would likely already be on the cape by 10 pm. I'd probably do the Bourne as that gets less Boston traffic, but see what maps tells you.

+1

[Anonymous]

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:We are traveling to Cape Cod for 4th of July week. Current plan is to leave at 5 a.m. from NW DC in the hopes of beating at least some traffic (I know this is wishful thinking). My question for those of you who regularly travel to the Cape: what bridge do you take over the Hudson River, the GW or Tappan Zee? If you take the Tappan Zee, what route do you take to get there? Thanks in advance.

Tappan Zee. NJT to Garden State to 84E, over the bridge, to Wilbur Cross/Merrit. From there you can take 84 in CT. Into MA and drop south to the Cape on 495 from the MA Turnpike or cross over to 95N around Norwalk and then follow that into Providence, and take 195 to the Cape off 95N

THIS can be a nightmare due to Mass traffic coming south.

All of the options have been set down on the responses. I really think be able to adapt and adjust becomes the key. No route is perfect and all routes are very much subject to traffic/accident/construction issues.

Leave at 3 am for the best outcome!

OMG. The tool from the other thread is back. No one from MA goes south in the summer. In fact, most people I know from MA have a place in FL for Dec to March, and A place at the Cape for the rest of the year. Will you give it up and stop trying to ruin the MA threads? Jeff should have banned you by now.

This poster is such a strange GUY.

Wait, are you saying people from Boston don’t go to the Cape or MV/Ack in the summer? That’s idiotic. Some of them fly, many, many drive. Every weekend.

[Anonymous]

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:We are traveling to Cape Cod for 4th of July week. Current plan is to leave at 5 a.m. from NW DC in the hopes of beating at least some traffic (I know this is wishful thinking). My question for those of you who regularly travel to the Cape: what bridge do you take over the Hudson River, the GW or Tappan Zee? If you take the Tappan Zee, what route do you take to get there? Thanks in advance.

Tappan Zee. NJT to Garden State to 84E, over the bridge, to Wilbur Cross/Merrit. From there you can take 84 in CT. Into MA and drop south to the Cape on 495 from the MA Turnpike or cross over to 95N around Norwalk and then follow that into Providence, and take 195 to the Cape off 95N

THIS can be a nightmare due to Mass traffic coming south.

All of the options have been set down on the responses. I really think be able to adapt and adjust becomes the key. No route is perfect and all routes are very much subject to traffic/accident/construction issues.

Leave at 3 am for the best outcome!

OMG. The tool from the other thread is back. No one from MA goes south in the summer. In fact, most people I know from MA have a place in FL for Dec to March, and A place at the Cape for the rest of the year. Will you give it up and stop trying to ruin the MA threads? Jeff should have banned you by now.

This poster is such a strange GUY.

Wait, are you saying people from Boston don’t go to the Cape or MV/Ack in the summer? That’s idiotic. Some of them fly, many, many drive. Every weekend.

m

Clear reading comp problem as the important issue is the swing north and then getting in with Boston traffic coming south via 495 from the Mass Pike. That is as bad as some of the Conn traffic. The dummy pp assumed the other pp was talking about Mass traffic coming all the way south from Mass to Nj and beyond. Silly. Mass traffic to the Cape is an issue.

[Anonymous]

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:We are traveling to Cape Cod for 4th of July week. Current plan is to leave at 5 a.m. from NW DC in the hopes of beating at least some traffic (I know this is wishful thinking). My question for those of you who regularly travel to the Cape: what bridge do you take over the Hudson River, the GW or Tappan Zee? If you take the Tappan Zee, what route do you take to get there? Thanks in advance.

Tappan Zee. NJT to Garden State to 84E, over the bridge, to Wilbur Cross/Merrit. From there you can take 84 in CT. Into MA and drop south to the Cape on 495 from the MA Turnpike or cross over to 95N around Norwalk and then follow that into Providence, and take 195 to the Cape off 95N

THIS can be a nightmare due to Mass traffic coming south.

All of the options have been set down on the responses. I really think be able to adapt and adjust becomes the key. No route is perfect and all routes are very much subject to traffic/accident/construction issues.

Leave at 3 am for the best outcome!

OMG. The tool from the other thread is back. No one from MA goes south in the summer. In fact, most people I know from MA have a place in FL for Dec to March, and A place at the Cape for the rest of the year. Will you give it up and stop trying to ruin the MA threads? Jeff should have banned you by now.

This poster is such a strange GUY.

Wait, are you saying people from Boston don’t go to the Cape or MV/Ack in the summer? That’s idiotic. Some of them fly, many, many drive. Every weekend.

m

Clear reading comp problem as the important issue is the swing north and then getting in with Boston traffic coming south via 495 from the Mass Pike. That is as bad as some of the Conn traffic. The dummy pp assumed the other pp was talking about Mass traffic coming all the way south from Mass to Nj and beyond. Silly. Mass traffic to the Cape is an issue.

If we are talking about reading comprehension, the OP asked about the DC area to the Hudson river bridges - which one and route to them. So Boston traffic to the Cape seems irrelevant to this particular part of the route.