To Bollard or not to Bollard

A few weeks ago, the new trail connection from Harrison Street to the Custis Trail was completed (see post here). As you can see from this photo, there is a bollard installed at the end of the connector by the sidewalk on Harrison Street. That got me thinking about bollards on trails. Having given it some thought, at least for the areas where I generally ride in this region, I think they are a waste of money and effort, serve no purpose and sometimes create a hazard.

The picture above shows the Harrison St. end of the new connector. Note the bollard installed in the middle of the trail. Presumably it is there to prevent cars from driving on the trail. (Please note that this picture was taken before this project was ultimately completed. There is a curb cut that will be built here to allow access to the trail from the street.) Other bike riders who read this blog are welcome to comment, but in all my years of riding the trails, I have never encountered any unauthorized vehicles on the trails. Maybe that means the bollards are working!? Well, except for the fact that there are numerous locations that have no bollards, and I've never seen vehicles in those areas either. Here are a couple that are near my house (click on any photo for a larger version): Note that this one has the post hole and base, which presents a hazard in and of itself. This bollard has been missing for years along this well traveled road, yet I have never noted any cars turning onto the path. Here's another. This one used to have a bollard, and one can see where it was removed and paved over to provide a smooth surface (although it's difficult to see in the photo, sorry). I have never encountered any cars trying to drive on this trail. Here's a W&OD crossing in Loudoun County. Note there is no bollard even though the trail is easily wide enough to accommodate a motor vehicle. Here's a case where the bollard proved to be an impediment. The plow was unable to plow the final 30 yards to the sidewalk after the recent snow, because this bollard was in the way. I have saved the dumbest one for last. A few months ago, this new connection was built along the W&OD in Fairfax County near milepost 10. It connects the trail to a residential street called Malraux Drive (link to map here). This photo shows the intersection of the connector with the W&OD trail. There are bollards on both ends of the connector! And not small ones, either. Both of them are heavy steel construction that probably cost hundreds of dollars to install. One could make an argument for the bollard at the other end, where the connector meets the street, but this one--at the connection of two trails--is senseless. In fact, it is worse than senseless: it's a hazard. I remember one day when I was pulling my daughter on the trailer bike, I got very nervous that I would smash her hand on the bollard as I negotiated this corner. I didn't thankfully.

So all in all, I think that bollards are one of those institutional inertia issues. They've always been put in, and no one questions why. So now I'm questioning why. Here are the key points of consideration:
- Based on my experience, they seem to address a non-existent problem
- They cost money, which could be saved if they were not installed. Perhaps the savings could be used for better signage
- They can present a hazard to cyclists
- They require maintenance, which is an additional cost. Or if not maintained, they break or eventually are removed and/or lost.
- They can impede the movement of authorized vehicles, such as snow removal, maintenance or emergency vehicles.

My recommendation would be that bollards not be included in future trail improvements (and be removed from locations where they are a hazard or impediment). Should it turn out in the unlikely event that unauthorized vehicles become a problem, the bollard could be installed at a later date.

Comments

[Froggie]

The comments thus far on WashCycle suggest that Steve's experience is the exception rather than the rule.

Personally, I see no problem with having the stantions in there. IMO, they do not incur a large additional cost, and the potential "hazard to cyclists" is overstated.

[Paul McCray]

We have had a number of incidents on the W&OD Trail when a car has driven up the path, usually by mistake. To my knowledge though we've never had damage beyond some ruts in the turf beside the trail and never had a trail user injured due to a vehicle on the path. We took out our bollards and gates 15+ years ago just to eliminate any chance of accidents and to ease access for police, fire, rescue and maintenance.

[washcycle]

Steve, check out this photo of a place where a car drove on the ART and damaged the bridge.

http://www.thewashcycle.com/2009/12/anacostia-riverwalk-trail-bridge-damage-under-east-capital-street.html

And also here, where the google streetview vehicle drove up onto a trail.

http://maps.google.com/?ie=UTF8&hq=&hnear=307+Kentucky+Ave+SE,+Washington,+District+of+Columbia,+20003&ll=38.966291,-76.922858&spn=0,359.986922&z=17&layer=c&cbll=38.967336,-76.921802&panoid=Dg1hUMy5PFBktIgK1Nqscw&cbp=12,192.98,,0,9.95