« Can Washington DC Learn from NYC’s Equality Drive in Cycling? | Main | Planning Board Sends Bicycle Master Plan to Montgomery County Council for Consideration »


Feed You can follow this conversation by subscribing to the comment feed for this post.

So basically, everywhere you could envision making someone cross the street is going to be a surface cross and likely rely on goodwill for people to yield.

We know how that goes. And when the collisions come they'll say they can't do a light because it'll lead to too many backups and if we're lucky they'll put in the overpasses they should have at the outset just 20 years from now.

And holy crap, how is it still that any of it really runs along the sidewall? If its still anything like what was proposed earlier you might as well just allow cyclists on the shoulder at all times. Parts of the Custis sometimes come close to that but only a few hundred feet at a time and there's still plenty of separation.


My impression is that there will be a lot of underpasses and overpasses for the trail. If you watch the video, that's a little more clear. The only place I saw at-grade crossings were at Nutley Street. Some of those are traffic light controlled, and others are not.


"At the January 4th Meeting, there were only 4 speakers, but the first one recommended adding a bike connection from Balls Ford Road to Bull Run Drive over Bull Run, which is already part of the plan."

To the best of my knowledge, there still is no real "plan" to connect the I-66 Trail in Fairfax County across Bull Run with a future "I-66 Trail" in Prince William County, which would be built as a sidepath along Balls Ford Rd.

As I and several others have repeatedly commented to VDOT regarding this I-66 Outside the Beltway express lanes project, the lack of any I-66 Trail connection across Bull Run is likely to remain a significant gap in the regional I-66 Trail for many decades to come.

Sadly, this highway project will build new I-66 roadway bridges across Bull Run, and VDOT already owns considerable nearby right of way at its dual I-66 rest areas to connect trails along those roadway bridges to the east ends of Balls Ford Rd and Vandor Ln.

In addition, this project is doing nothing to create long-missing and much-needed ped/bike access under I-66 at Sudley Rd/Business 234. The NVCC Manassas Campus, on the north side of I-66, can only be safely reached by auto or bus.

Why not put the "Potential Noise Barrier (Height to be Determined)" [see latest design in https://wtop.com/dc-transit/2019/03/i-66-toll-lane-bike-trail-layout-comes-into-focus/slide/1/] where the 50-inch tall concrete barrier is proposed to go? Then they wouldn't have to consume more of anyone's back yard. They could add a tall mini-mesh chain link fence (or other secure barrier)) where the Noise Barrier was proposed to go, to keep burglars-on-bikes out of the yards. A Noise Barrier can be cheap -- e.g., steel I-beams pile-driven (vertically) into the ground, and then slabs of concrete lowered between the I-beams.

The comments to this entry are closed.

Banner design by creativecouchdesigns.com

City Paper's Best Local Bike Blog 2009


 Subscribe in a reader