Regional Boards > Mid-Atlantic

I-66 HO/T Lanes

(1/103) > >>

froggie:
To separate what's likely to be another lengthy discussion, I chose to start a new thread about the recently-announced (really announced back in July by the Governor) plan to add HO/T lanes on I-66 outside the Beltway and convert I-66 inside the Beltway to HO/T lanes during peak hours.

VDOT has created a website for the Outside the Beltway project and has preliminary design options posted that will be presented at public meetings next week.  The plan is to expand 66 as needed/applicable so that there are 3 general through lanes plus 2 HO/T lanes in each direction.  There is an option that would keep space reserved in the median west of Vienna for future transit (the most popular option being an extension of the Metro Orange Line).  Several interchanges would be reconstructed.

A (lengthy) summary from west to east.  If I don't mention a specific interchange, the plan is to retain the interchange's existing configuration:

- The HO/T lanes begin just east of the Antioch Rd overpass (about 3/4mi west of US 15).  There are two options for HO/T lane access at US 15:  one would build a full HO/T-only interchange about 1/3mi west of US 15, connecting to VA 55 and Heathcote Blvd.  The second option would build a set of flyovers between the HO/T lanes and the mainline between Jefferson St and Catharpin Rd, with auxiliary lanes between the flyover ramps and the planned DDI at US 15.

- There would be no direct access between US 29 and the HO/T lanes.  Instead, HO/T access would be provided via a WB off-ramp/EB on-ramp at the University Blvd overpass.

- There is no direct access between 234 South and the HO/T lanes.  There's an option to build HO/T access connecting to Cushing Rd in the southeastern quadrant, but this would impact the Manassas Battlefield Park.

- A park-and-ride is proposed off Balls Ford Rd west of BUSINESS 234, with access to the HO/T lanes to/from the east.  The HO/T lane access would also connect to Balls Ford Rd.

- The rest areas east of 234 would be reconstructed with expanded truck parking.

- An eastbound auxiliary lane would be added between 29 and 28 in Centerville.

- The VA 28 interchange would see some major changes, all of which would eliminate the three signals along 28.  Common elements among the two options:

     - Direct HO/T lane connections from both directions of 66 to/from the north
     - A 2-lane flyover ramp from SB 28 to EB 66
     - A 2-lane ramp from WB 66 to NB 28
     - Widening the loop ramp from EB 66 to NB 28 to 2 lanes
     - Bridging Braddock Rd/Walney Rd over 28 with a half-interchange to/from the south (with left-side exit/entrance)
     - Direct ramps between Braddock Rd and 66 East (EB on-ramp/WB off-ramp)

- The main differences between the two options at VA 28 are ramp locations/geometry and how to handle HO/T connections between 28 South and 66 East.  One option provides direct ramps while the other would be indirect, using flyovers between the HO/T lanes and the mainline east of 28.

- One or two auxiliary lanes each direction would be added between VA 28 and Fairfax County Pkwy, depending on the option chosen.

- There's an option for an eastbound HO/T lane exit to the Fairfax County Pkwy C/D ramp, otherwise there is no direct access between the HO/T lanes and the Fairfax County Pkwy.  Instead, the existing HOV ramps at Stringfellow Rd would be perpetuated (no-median option) or relocated (median-space option).

- The existing half-interchange at Monument Dr would be converted into a full HO/T lane only interchange.

- One auxiliary lane in each direction would be added between Fairfax County Pkwy and US 50/Fair Oaks.

- The US 50/Fair Oaks interchange would generally retain its existing configuration with one exception:  the existing loop ramp from WB 50 to WB 66 would be replaced by a left-side flyover.  There is also an option for direct HO/T lane access between 50 West and 66 East.

- One auxiliary lane in each direction would be added between US 50/Fair Oaks and VA 123.  The eastbound auxiliary lane would be extended through the 123 interchange.

- At the 123 interchange, the existing loop from EB 66 to NB 123 would be replaced by a flyover.  This would eliminate the need for a C/D road.  Also the ramps from 66 to SB 123 would meet SB 123 at a traffic signal about 1200ft north of the existing ramp merge.  I presume this is to provide more room between the ramp and the intersection at Eaton Pl.  There is also an option for direct HO/T access between 123 and 66 East.  This access point would meet 123 at the same location as the ramp signal I just mentioned.

- One auxiliary lane in each direction would be added between VA 123 and VA 243/Nutley St.  The eastbound auxiliary lane would be a continuation of one beginning at US 50/Fair Oaks (mentioned above).

- There are two very different options for VA 243/Nutley St and Vienna Metro access:
     - Option 1 replaces the Nutley St interchange with a DDI.  Direct HO/T lane access would be provided to/from the west at the Vaden Dr overpass.  The loop ramp from Vaden Dr/Saintsbury Dr to EB 66 would be removed, as well as the EB C/D road.  The WB C/D road would be perpetuated.
     - Option 2 reconstructs the Nutley St interchange to include flyover ramps from NB 243 to WB 66 and SB 243 to EB 66.  The EB 66 to NB 243 loop is removed, so there would be a single EB off-ramp meeting 243 at a signal.  A bus-only ramp would be constructed between the HO/T lanes to/from the west and Vaden Dr.  The existing loop ramp from Vaden Dr/Saintsbury Dr to EB 66 and the EB C/D road would both be retained.

- One auxiliary lane in each direction is added between VA 243/Nutley St and the Beltway.

- There are two options at the Beltway, with the main difference being how many HO/T lane access options there are.  Both options replace the existing Inner Loop mainline to WB 66 loop with a 2-lane flyover and provide direct connections between the Beltway HO/T lanes and the 66 West HO/T lanes.  One option provides full access between the mainlines and the HO/T lanes with a complex conglomeration of ramps.  The second option does not provide access from the EB HO/T lane to NB 495 mainline or from the SB 495 mainline to the WB HO/T.  Also with the second option, EB 66 mainline access to the Beltway HO/T lanes is provided by a flyover ramp from the mainline to the EB HO/T lanes west of Dunn Loring.

1995hoo:
Do they have diagrams of the various options on that site? I'm having trouble getting parts of it to load and will try another browser if indeed they do have maps. I'd love to see what they have in mind for the Beltway interchange.

vdeane:
Must resist temptation to make I-366 joke...

froggie:

--- Quote ---Do they have diagrams of the various options on that site?
--- End quote ---

Yes...click on the link to the public meetings next week, then click on Public Presentations.  Be forewarned that there are 65 alternatives maps posted, as they're broken down by section in fairly decent detail.

1995hoo:

--- Quote from: froggie on January 24, 2015, 09:03:56 AM ---
--- Quote ---Do they have diagrams of the various options on that site?
--- End quote ---

Yes...click on the link to the public meetings next week, then click on Public Presentations.  Be forewarned that there are 65 alternatives maps posted, as they're broken down by section in fairly decent detail.


--- End quote ---

Thanks. That was indeed one of the parts of the site that gave me some trouble. I'm sure it was some issue on my end. PC seemed to be slow yesterday afternoon. I'll use an alternate browser or perhaps my iPad.

Edited to add: Loading just fine on the iPad. Thanks for the info.

Navigation

[0] Message Index

[#] Next page

Go to full version