Talk:Interstate 66

Untitled

I'm curious if it's worth mentioning any of the problems and unique situations I-66 has within Northern Virginia. Most notable is the fact that it has only two lanes of traffic within the beltway, and that this traffic is highly regulated by HOV and other traffic control measures. I'm told that this solution was adopted as a compromise with Arlington County, whose residents did not desire the road. I haven't done enough research into the matter to know for certain.

Also the road is heavily congested throughout both rush hours, as the only interstate to enter the city from the west, and this has led to all sorts of zaniness locally. For instance, after the intersection with US Route 50 at Fair Oaks, the road drops from 4 lanes to 3 (through the beltway), but there is a 4th "shoulder lane" open only during rush hour. The congestion extends out well past Fairfax into Loudon county, and plans to expand it to at least three lanes as far as route 29 at Gainesville have met with limited success.

Also not mentioned is that Metro's Orange Line bisects the highway from Vienna until it goes underground, somewhere further in.

Is any of this worth mentioning in the article? I can do some research to make sure I'm not making stuff up, but living within hearing distance of the road, I feel like it deserves more discussion than a mere mention of a failed 266 project. The congestion on it is certainly a source of major concern and strife for Northern Virginia residents like myself, and is a major political issue.

Also I'm a bit miffed at the map. It shows Centreville and Oakton, which are respectable locales, but it leaves ot Fairfax and Manassas. As a resident of Vienna, VA, I would also complain about the choice of leaving my hometown out, though it all but overlaps with Oakton.

I-66 disputes

You're right to believe that the many of the restrictions on I-66 within the beltway are compromises between the state, the FHA, and the residents of Arlington who didn't want this road at all. They originally planned 66 to be an 8 lane highway, splitting into two 6 lane highways (I-66 and I-266) in Arlington around Spout Run. Eventually a compromise was reached in the [ Coleman Agreement | http://www.idea66.com/downloads/Coleman-Decision.pdf ]. The original compromise limited the highway to 4 lanes, excluded trucks from the road at all times, and set the rush hour HOV restriction to 4 passengers cars, buses and people coming and going to Dulles Airport and emergency vehicles, and also mandated construction of the subway line in the median. Most of the Coleman restrictions were eased since then, and in 1999 the Coleman Restrictions of no widening of the highway were removed. [1]. And now the State and the Federal government is trying to alter I-66, though there is still community opposition in Arlington. [2]

I-66 vs US 66

I-66, if extended, should cross former US 66 near Baxter Springs, Kansas where it is marked a "historic route", it will also come close to the historic road in Missouri which should, by the end of 2005, be designated a scenic byway. Does anyone know, would this cause AASHTO to oppose I-66 being designated through here? Should this be placed in the article? - Rt66lt 04:01, September 5, 2005 (UTC)

I-666

I don't see that happening anytime soon. Who would want to ride on a highway numbered 666 anyways?
JesseG 23:17, 21 December 2005 (UTC)

I'll be damned if I know! - Paul Robinson (Rfc1394) 21:44, 16 July 2006 (UTC)

East Extension?

I read at the bottom of an article I found here (at the bottom of the page) that Maryland and Delaware may eventually have the route extended to Dover. I added this info before but it got deleted. Anyone know if it can be trusted?-Jeff ^(talk) 04:24, 27 February 2006 (UTC)

Absent a primary source, I'm inclined to discount it. All we have so far is the say-so of one person who is identified only by name, not by title. Doctor Whom 14:27, 27 February 2006 (UTC)

It feels a little speculative yet. Now, if Maryland or Delaware were to have the info on an official site, or a newspapre article were to mention it, etc., then it's worth putting in, IMHO. —C.Fred (talk) 02:53, 28 February 2006 (UTC)

More Cities in small Map

I have restored the map I created for this article more than 2½ years ago that someone (a vandal?) removed. Based on comments here, I have added the (major nearby) cities of Fairfax, Manassas and Warrenton, plus the Town of Vienna to the map. Paul Robinson (Rfc1394) 21:42, 16 July 2006 (UTC)

I've moved the map off to the right-hand side in the major cities section, since it illustrates minor cities and intersections with other interstates. I've bumped the other images down to Notes, though on my screen width, it causes an interaction with the future road template. —C.Fred (talk) 04:45, 17 July 2006 (UTC)

Former railroad * Roosevelt Bridge

I had an old street map (currently misplaced) which showed a railroad running north from what is now Crystal City, approximately where the Blue Line runs through Arlington Cemetery, and finally around the east side of Rosslyn where I-66 is now located. (This is not to be confused with the old W&OD railroad west of Rosslyn). Assuming I won't be able to find my old map, can anyone else provide details? When was the railroad replaced? If I'm not mistaken, the Roosevelt Bridge predates the rest of the I-66 route, no? The part where I-66 exits the bridge (heading west) is where that old railroad would have been. -- Gyrofrog (talk) 21:59, 9 April 2007 (UTC)

This was the Rosslyn Connecting Railroad (no article yet). --NE2 23:53, 9 April 2007 (UTC)

Interesting, thanks. I'm wondering, when was the railroad torn up, and when was I-66 built in its place? Did this portion precede the rest of I-66? I'm not sure whether this info would be better suited for this article or the one about the T. Roosevelt bridge (if either). I couldn't find these details on the external sites. -- Gyrofrog (talk) 14:31, 10 April 2007 (UTC)

It would be best suited for Rosslyn Connecting Railroad, with short mentions on other related articles. I'm not sure when it was abandoned, but it seems to have been fairly late. Here's a map showing it. --NE2 14:44, 10 April

2007 (UTC)

Route 66 Photo

The photo titled "I-66 at its western terminus, where it splits from I-81" is actually a photo of route 81. The cars are shown driving on route 81. Trust me on this; I take it every day to go to work. It does show the entrance ramp to route 66. Shouldn't this photo be transferred to the route 81 article? —Preceding unsigned comment added by 204.111.109.106 (talk • contribs)

I trust you; I took the photo. It's fine on this article, as it would show no purpose on the I-81 article other than showing a junction. Here, it shows a terminus of the road in question, which is I-66. (We really like good termini pictures). If you want to one morning (Sun would be in the east, shining west) get a picture of the I-81 split from I-66 westbound showing the signs, be my guest. The times I've travelled through there have been in the late day/evening, which makes for terrible (but silhouetted) pictures, or mine just weren't good. I mean, I could get one sometime in the next week I suppose. But to answer your question- no, it fits here. --MPD ^{T / C} 03:56, 11 December 2007 (UTC)

Well, then, maybe the photo could be re-titled. Perhaps "I-81 at its junction with I-66". The only place I-66 itself actually "shows" in the photo is the bridge over I-81. Of course, the exit sign shown on I-81 indicates that the exit will take you to I-66. —Preceding unsigned comment added by 204.111.109.106 (talk) 23:17, 11 December 2007 (UTC)

Better? --MPD ^{T / C} 23:34, 11 December 2007 (UTC)

Please, trust me again when I say thank you very much, and thank you for all the effort involved in taking the photo and placing it here for all of us. —Preceding unsigned comment added by 204.111.109.106 (talk) 01:46, 13 December 2007 (UTC)

Exit list

To me it looks okay. But the ELG evaluations count it not compliant. I dnon't see anything wrong. Its not p to me; up to those who manages ELG.--Freewayguy ^{Msg USC} 02:34, 4 July 2008 (UTC)

The only issue I could see is that it's not split up by state, but it's been established before that not all the guidelines established in the ELG are required. So I'm saying it doesn't need attention. --MPD ^{T / C} 04:09, 4 July 2008 (UTC)

Every rule has its exception, and I think this is one case where splitting the list by state would hurt readability, because the column boundaries would shift. It has section breaks, which provides a way to jump to one state or the other, and the DC portion is relatively short. —C.Fred (talk) 15:24, 4 July 2008 (UTC)

To MPD: Your reverting Exit 44 to Manassas is splitting hairs. 20136 (Bristow) is a long, thin Zip code, the most northern part of which is actually north of 66, although I'll give you that the "town center" is south of 28. I looked on Google Maps, and, technically, 44 is within a few hundred feet of the 20109/20136 boundary. But I use it every day to come back to my house - in Bristow. :-)
--Tim Sabin —Preceding unsigned comment added by Timsabin (talk • contribs) 02:48, 10 May 2009 (UTC)

WP:DC Template

I personally think the traffic reporter at 9 is a pretty good source. If there is a map (a clear one) that shows 66 in DC, I would like to see it, because alot of people think that 66 ends at the TR Bridge. - NeutralHomer • Talk 13:29, 27 August 2008 (UTC)

The Route Log and Finder List (an official publication of the FHWA -it's here) lists 1.48 miles of I-66 in DC. I-66 is also signed past the Constitution Avenue exit. I would hope that the FHWA knows more about their own roads than a channel 9 traffic reporter. Xenon54 14:08, 27 August 2008 (UTC)

Well, I was wrong on that one. :S Actually, most people in this area (not just me and the traffic reporter) think that 66 ends at the TR Bridge. Sorry for the confusion on that one. Thanks for the correction and linkage. Take Care...NeutralHomer • Talk 14:49, 27 August 2008 (UTC)

No big deal, don't sweat it. Glad we could help :) --MPD ^{T / C} 16:14, 27 August 2008 (UTC)

HOV Designation and Rules

I moved a paragraph that describes the HOV status of I-66 (good stuff, BTW!) to it's own subsection. I also added a paragraph about the current "clean special fuel" exemption that allows hybrids (and other non-gasoline vehicles) to access the HOV lanes. I wasn't sure where to put this new subsection, so I put it under the Virginia section of the Route Description section. If this isn't the right place for it, let's have a discussion and move it to where it belongs. --Tim Sabin (talk) 00:39, 17 May 2009 (UTC)

In 2012 Gov. McDonnell ended the annual review of Clean Special Fuels (hybrid) SOV exemption and extended the free HOV for Clean Special Fuels indefinitely until the end of the program. There is no certain end of program yet, but conversion to HOT-3 lanes without free SOV access is proposed.TBILLT (talk) 16:55, 30 January 2016 (UTC)TBILLT

Fact?

This article says that 66 is the only Interstate to enter the district..What about 395? --Jayson (talk) 23:11, 31 July 2009 (UTC)

The article says I-66 is the only two-digit Interstate to enter the District. I-395 is a three-digit Interstate. —C.Fred (talk) 23:33, 31 July 2009 (UTC)

What about 95 over the Wilson Bridge? Technically it enters the District for ~300 feet, IIRC. Xenon54 (talk) 00:32, 1 August 2009 (UTC)

Hrm. Change the text to say the only one with interchanges in the District? —C.Fred (talk) 00:46, 1 August 2009 (UTC)

That's a good idea. Xenon54 (talk) 01:07, 1 August 2009 (UTC)

Mileage

The mileage in the infobox and the mileage in the exit list don't match up. I recently fixed the DC exits, and removed the mileage that proved to be incorrect. If anyone has access to good resources and can fix this that would be great. -- c16sh (talk to me) 02:22, 24 October 2012 (UTC)

External links modified

Hello fellow Wikipedians,

I have just added archive links to one external link on Interstate 66. Please take a moment to review my edit. If necessary, add {{cbignore}} after the link to keep me from modifying it. Alternatively, you can add {{nobots|deny=InternetArchiveBot}} to keep me off the page altogether. I made the following changes:

• Added archive https://web.archive.org/20110804223018/http://www.roadstothefuture.com/roadsnova/266.html to http://www.roadstothefuture.com/roadsnova/266.html

When you have finished reviewing my changes, please set the checked parameter below to true to let others know.

This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check}} (last update: 18 January 2022).

• If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
• If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers. —^{cyberbot II}_{Talk to my owner:Online} 06:47, 29 August 2015 (UTC)

Requested move 8 March 2019

The following is a closed discussion of a requested move. Please do not modify it. Subsequent comments should be made in a new section on the talk page. Editors desiring to contest the closing decision should consider a move review after discussing it on the closer's talk page. No further edits should be made to this section.

The result of the move request was: not moved. No consensus to do so at this time. (non-admin closure) Calidum 04:55, 14 March 2019 (UTC)

---

Interstate 66 → Interstate 66 (Virginia–District of Columbia) – While this may be the only Interstate 66 that currently exists, I think it would make sense to disambiguate it from the once-proposed Interstate 66 to the west, Interstate 66 (Kansas–Kentucky). This would be similar to how the article for I-895 in Maryland is titled Interstate 895 (Maryland) even though it's the only I-895 currently in existence, there were proposed I-895's in New England and NJ-PA, as well as decommissioned I-895's in New York and Delaware. Needforspeed888 (talk) 01:36, 8 March 2019 (UTC)

• Oppose. The extant highway is the obvious primary target. There are reasons why I-895 may require a suffix, but this isn't the place to discuss its title. As far as I-66 is concerned, no disambiguation is required here. —C.Fred (talk) 01:44, 8 March 2019 (UTC)
• Oppose. The primary topic is the actual road. Disambiguation is necessary for the 3-digit interstates because there can be more than one of those with the same number. There cannot be more than one 2-digit interstate with that name. A hatnote pointing to the proposed interstate of the same name is adequate here. Rreagan007 (talk) 02:00, 8 March 2019 (UTC)
• Oppose. There is only one current road of this designation. Famartin (talk) 02:04, 8 March 2019 (UTC)
• Comment: Although I support disambiguation like this, it goes against USRD policies and usual practices. Morriswa (Charlotte Allison) (talk) 16:30, 8 March 2019 (UTC)
• Oppose. I am sure that the overwhelming majority of people who look up I-66 on Wikipedia are interested in this one, so that a hatnote suffices for the previously proposed other one. I disagree with the analogy to I-895 both for the reasons noted above and because New York used the designation as recently as 2017. Doctor Whom (talk) 17:56, 11 March 2019 (UTC)
• Oppose. I think among all the other oppose statements there is a compelling case for not merging and simply adding the hatnote to this article --hulmem (talk) 18:17, 11 March 2019 (UTC)

---

The above discussion is preserved as an archive of a requested move. Please do not modify it. Subsequent comments should be made in a new section on this talk page or in a move review. No further edits should be made to this section.