Roads you're tired of driving

[roadfro]

For me, it is US 95 between Las Vegas and Fallon (en route to Reno). Growing up in Vegas and attending college/now living in Reno, I made that drive about 4 times per year for several years. Most of the time, I'd be traveling with someone who has no interest in satisfying my want to drive a different path--mainly because most alternatives go out of the way enough to add 1-2 hours minimum, and that's a lot for a drive that already takes about 6-7 hours. I am now at the point where more of my trips to see family, I will fly instead.

Vegas to Ely is tolerable, for some reason.

That is getting into the area around Great Basin National Park. Between the SR 318/375 turnoff and US 6/50 at Ely, US 93 is a Nevada Scenic Byway.

[corco]

I usually take 318 between Vegas and Ely (and even forgot that 318 wasn't 93), and even that I'm weirdly okay with, but yeah, going through Caliente is legitimately pretty though I've only done it once

[agentsteel53]

I-5.  There's only two interesting parts on the whole damn road, Burlington to Bellingham, Wash., and Redding, Calif., to Medford, Or.  The rest of it I wouldn't mind if I never had to drive again.

I'd throw in the Grapevine, too.  it's about as interesting as Siskiyou Pass, for all definitions of interesting.  (last time I drove Siskiyou, there was freezing fog.  hooray.)

and yes, I-5.  between exit 32 and whatever the 580 split is.  done it so many times.

I-8 is getting up there.

US-395 does not get old as readily.

[J N Winkler]

When I was at KSU getting my undergraduate degrees, there were three somewhat reasonable routes between Wichita and Manhattan.  I never really got tired of the shortest and best of the three (US 50 to US 77), but since my years at KSU largely overlapped the upgrade of US 50 to Super Two cross-section with full shoulders, passing lanes, and Portland cement concrete pavement, I often drove the two alternates rather than deal with long detours or workzones on US 50.

I liked the other routes (K-15 to I-70, and Turnpike to K-177) so little that I was usually happy to go back to US 50-US 77 in spite of the construction.  K-15 is arrow-straight and boring since it essentially just grazes the western side of the Flint Hills, and the US 56 dogleg is annoying.  K-177, on the other hand, is full of reduced-speed curves which are spaced just widely enough that you can't get away with setting cruise control for the median speed to cut down on pedal movement.  (As part of the current T-WORKS program, KDOT is developing a partial relocation of the length of K-177 between Council Grove and I-70, which has a number of blind hills and substandard horizontal curves.  No improvements are planned for K-177 between the Turnpike and Strong City, which is far less suitable for high-speed travel.)

[OCGuy81]

Most of the 5, with the exception of Redding to Weed. 

I have a house up in Bend, OR.  It's a great place, but the drive is a bit trying at times, especially with young kids and the boring stretches of the 5 from the Grapevine to Sacramento, and again from Sac to Redding.  From Redding north to where I generally veer off onto 97? Beautiful!

[Zmapper]

I-25 between Fort Collins and Denver.

60 miles of little more than a endless string of remote three-car-garage subdivisions with the mandatory green bluegrass lawn, oil wells, RV dealerships, and generally poor driving behavior. At least where I-25 is only 4 lanes wide north of Longmont, everyone drives with only 1/2 to 1 second between consecutive vehicles, which greatly helps the abysmal safety record. Unless its like 3am on a Tuesday morning, the 75 MPH speed limit is but a relic of the past.

[roadman65]

I-10 from I-75 to Pensacola.
Colonial Drive (FL 50) in Orange County, FL.
I-75 from FL Turnpike to FL 200.
I-4 from FL 44 to I-95 (it seems like the longest stretch of I-4 to travel)

[corco]

I-25 between Fort Collins and Denver.

60 miles of little more than a endless string of remote three-car-garage subdivisions with the mandatory green bluegrass lawn, oil wells, RV dealerships, and generally poor driving behavior. At least where I-25 is only 4 lanes wide north of Longmont, everyone drives with only 1/2 to 1 second between consecutive vehicles, which greatly helps the abysmal safety record. Unless its like 3am on a Tuesday morning, the 75 MPH speed limit is but a relic of the past.

I never came to really mind that one- though the drivers are pretty bad especially once you're inside 470. I drove 287 from Laramie to FoCo so many times and then on down to Denver- usually that Laramie to Fort Collins part felt like it took forever and then once I got on I-25 I felt like I was "in Denver" and the rest of the drive flew by. As long as there are frequent exits and I feel like I'm making progress, I never get too bored.

I almost always took 287 to the Owl Canyon cutoff if going from Laramie to Denver because I-25 from Cheyenne to Fort Collins was really boring to me.

[pianocello]

I have thoroughly gotten tired of I-80 (and I-88) going east from Omaha towards Chicago.

Seconded. Especially the part between Davenport and Iowa City.

Another one I've gotten tired of is I-74 between the Big X (Colona, IL) and Peoria.

Both of these are because of the number of times I've been on them and their boringness.

[mgk920]

For me, I would say the WI 26/US 151 corridor between Oshkosh and Madison, WI and I-(41)/94 (et al) between Milwaukee and Chicago.

The only things that keep US 10 west of Appleton and US(I)-41 between Appleton and Milwaukee from the list is that they are interesting and scenic drives.

Mike

[realjd]

I'm bored with almost any route I've driven more than a few times, particularly freeways. Lately it's the drive between Palm Bay and Orlando that I've been sick of. I am fully excited about the future of self driving cars. The day I can tell my car to take me someplace far away, crack open a beer, and break out my iPad, I'll be happy.

[mtantillo]

I-95 between Richmond and DC, and I-64 between Richmond and Hampton Roads.  I drive this way often for fun and for work, and its a pretty boring drive to begin with, and the traffic (especially on weekends) is brutal. 

[ftballfan]

I-96 between Grand Rapids and Brighton
Any road connecting Northern Indiana with Indianapolis
Ohio Turnpike

[InterstateNG]

I-96 between Grand Rapids and Brighton

That nearly arrow straight portion between M-6 and Portland is brutal.

I really grew tired of I-94 between Ann Arbor and Benton Harbor.

[cpzilliacus]

I-95 between Richmond and DC, and I-64 between Richmond and Hampton Roads.  I drive this way often for fun and for work, and its a pretty boring drive to begin with, and the traffic (especially on weekends) is brutal. 

Exit I-95 soutbound at 125, follow U.S. 1/U.S. 17 for a short distance, then left on U.S. 17 (Mills Drive; becomes Tidewater Trail).  There are a few signalized intersections, but traffic is not bad, and once you are past U.S. 301 at Port Royal, it's a four-lane divided highway all the way to I-64 in Newport News.  Don't go too much over the speed limit, and especially watch the speedometer through Tappahannock and passing Saluda.

Or just take Md. 5 (Branch  Avenue) south from D.C., then follow 301 south from Brandywine and Waldorf, across the Gov. Nice Bridge to U.S. 17. 

You may  not be able to go quite as fast, but it is a much easier drive.

[adt1982]

I've only done it 3 times in the past 8 months, but I am already sick and tired of I-70 across Missouri.

[J N Winkler]

I've only done it 3 times in the past 8 months, but I am already sick and tired of I-70 across Missouri.

Once is all it takes:  forty-foot medians plus 250 miles at a LOS which would be considered mediocre on an urban freeway.

[kphoger]

I-35 between Des Moines and Ames, Iowa.  It would be fine if you took all the other cars off the road.

[sp_redelectric]

US 93 in Missoula County!

Funny - I was going to say 93 north of Missoula up to Polson.  However I haven't driven it in years and now that a significant portion of it has been widened to four lanes it's probably much better now.

50 miles of just drab nothingness, especially near Ninepipes.  And very few places to pass a slowpoke (again, that's been fixed now).

Oregon 18 between McMinnville and Lincoln City is another road I'm tired of driving...few passing places, not really much to look at.  Especially McMinnville to Sheridan, all you can do is sit in one 20 mile long conga line and just plod along until you hit the Polk County line and get one shot to pass the idiot doing 50 MPH the entire time.

I-5 from Portland to Salem also a road that it takes just a couple of people to turn it into a nightmare.  Lately I've resorted to taking the backroads, such as Butteville Road, Oregon 219 or Oregon 221.  (99E, on the other hand, is worse than I-5.  The large number of, shall I say "foreign" drivers on that road, seem to think the speed limit is in kilometers per hour.)

[Laura]

I-70 eastbound only from Frederick to Baltimore, Md. Driving that segment west is exciting, because hypothetically I could keep driving it to the wild west, but eastbound has a clear terminus: Baltimore, home. Signaling the end of an adventure and back to everyday life. For this I dislike and have grown weary of the last segment of I-70 east.

[cpzilliacus]

I-70 eastbound only from Frederick to Baltimore, Md. Driving that segment west is exciting, because hypothetically I could keep driving it to the wild west, but eastbound has a clear terminus: Baltimore, home. Signaling the end of an adventure and back to everyday life. For this I dislike and have grown weary of the last segment of I-70 east.

I don't drive that segment of I-70 all the way very often, but at least it is three lanes each way, unlike the long segment of I-270, which is two lanes each way from I-70 south to Clarksburg.

As an aside, did you know that the section of I-70 between Md. 144 (Exit 59 on the westbound side only) and U.S. 40 (Exit 82 on the eastbound side only) was very nearly all arterial U.S. 40 (Baltimore National Pike) prior to about 1975?  SHA rebuilt the arterial U.S. 40 into I-70 "in place" (which is one of the reasons why it is posted as I-70/U.S. 40 even now).

[NWI_Irish96]

#1 by far is US 31 through Kokomo.  November can't get here soon enough!

#2 is the 2-lane stretches of I-65 in Indiana, but especially between Sellersburg and Greenwood. 

[Rushmeister]

#2 is the 2-lane stretches of I-65 in Indiana, but especially between Sellersburg and Greenwood. 

I'm right there with you.  Whenever I drive from Indianapolis to Florida, the absolute worst part is between Indy and Louisville.  If only Indiana could (or would) fast-track I-65 six-laning. 

If the duration of the widening project around Lebanon and south to Zionsville is any indication, I-65 could be six lanes throughout the state by around 2060. (I might still be alive then.  It's hard to say.)

[Pete from Boston]

The Mass Pike from Sturbridge to Boston.  There really isn't a practical alternative (95 is even worse between New Haven and Providence) and it marks the annoying first leg to get out of Mass., or the endless last hour when I'm not quite home yet.  It tires me just thinking about it.

MA 24 is straight, boring, and soaked with spees traps.  Plus its northern end, which seems "almost home," is in fact still 20 miles from home for me.

Fortunately 84 east of Hartford is the only road in CT I truly tire of.  Pretty much the entire rest of the state is duplicate ways to NY, leaving a fresh road available at all time.

[WichitaRoads]

When I was at KSU getting my undergraduate degrees, there were three somewhat reasonable routes between Wichita and Manhattan.  I never really got tired of the shortest and best of the three (US 50 to US 77), but since my years at KSU largely overlapped the upgrade of US 50 to Super Two cross-section with full shoulders, passing lanes, and Portland cement concrete pavement, I often drove the two alternates rather than deal with long detours or workzones on US 50.

I liked the other routes (K-15 to I-70, and Turnpike to K-177) so little that I was usually happy to go back to US 50-US 77 in spite of the construction.  K-15 is arrow-straight and boring since it essentially just grazes the western side of the Flint Hills, and the US 56 dogleg is annoying.  K-177, on the other hand, is full of reduced-speed curves which are spaced just widely enough that you can't get away with setting cruise control for the median speed to cut down on pedal movement.  (As part of the current T-WORKS program, KDOT is developing a partial relocation of the length of K-177 between Council Grove and I-70, which has a number of blind hills and substandard horizontal curves.  No improvements are planned for K-177 between the Turnpike and Strong City, which is far less suitable for high-speed travel.)

I was unaware of the realignment plans north of Council Grove. I tend to greatly enjoy 177, as I drive to CG every other week. I know that the curves hamper speed control, but I'm still able to hit average of 65 on the road. Death-wish prone, I suppose, but I've really yet to see any law enforcement out there. Just can't get enough of the Flints.

I've tried 50 to 77, and 56. Usually, I used that as a route home in the opposite manner, of course. I get sick of 77 south of Herington, and 50 is okay.

The road I'm sick of is I-135 to Salina. I'd gladly take Old 81 anyday to avoid that.

ICTRds