Category Archives: Bicycle facilities

How not to restripe

Gordon Renkes has produced a video showing conditions following restriping at Tamarack Circle in Columbus, Ohio, USA. Here’s a Google overhead view of this rather unusual circular street. Click away the caption balloon to get a better view. You may enlarge this view, or go to the full-featured Google page by clicking on “View Larger Map under the image.


View Larger Map

The teardrop pointer is at the location of the Google Street View below, of Tamarack Circle before the restriping. (I downloaded the image instead of embedding the Google image, in case Google redoes the Street View).

Google Street view of Tamarack Circle before restriping

Google Street view of Tamarack Circle before restriping

Before the restriping, with the very wide right lane, motorists probably parked most of the way to the corner, and many cyclists probably rode in the door zone.

Here’s the video showing condition following the restriping:

The design does encourage cyclists to ride outside the door zone of parked cars. But, as the video shows, the striping confuses motorists. Among other things, the striping instructs them to right-hook cyclists. In the video, one motorist even right-hooks another. Ohio law says:

“Approach for a right turn and a right turn shall be made as close as practicable to the right-hand curb or edge of the roadway.”

Striping which incites violations of the law risks liability claims.

Creating right-turn pockets to resolve the problems would require removal of a few parking spaces before each entering street.

If parking were on the left at the inside of the curve, sight lines at intersections with streets at the outside would be better (though worse at driveways at the inside, and for drivers exiting parking spaces, due to the curve). A combined bike lane/right turn lane (still “experimental”) would be needed due to width limitations.

Boston Globe: Reality Check Time

The caption with the picture below in the Starts and Stops column of the Metro section of the June 17, 2012 Boston Globe reads:

Cyclists stopped for a red light in the “bike box” on Commonwealth Avenue in the Back Bay. They provide the cyclist a safe space to wait ahead of cars at traffic signals.

Photo which appeared in the Boston Globe Metro section, June 9, 2012

Photo which appeared in the Boston Globe Metro section, June 9, 2012

(The Globe story may be behind a paywall, but you can probably access it through a public library’s Web site using your library card number.)

The smiling cyclists show that this is a posed photo; the photographer evidently only thought of the large puddle in the foreground as an artistic touch. How about the car encroaching into the bike box in the background?

Well, yes, OK, waiting in the bike box might be safe — drivers are unlikely to encroach on a cyclist who is already waiting in the bike box. The problem is with getting into the bike box. The Globe columnist, Eric Moskowitz, never considered that bicyclists approaching the bike box on a red light are encouraged to swerve sharply left across multiple lanes of motor vehicles, with no way to know when the light will turn green. A waiting motorist will not see the swerving cyclist if looking to the left for traffic at the wrong moment. A tall vehicle in one lane will conceal the cyclist from a driver waiting in the next lane.

Portland, Oregon has hosted a study of bike boxes, which found that this is actually a rare problem in Portland, because cyclists are smart enough not to swerve into the bike box. Instead, if the light is red, they wait at the right curb, blocking other cyclists behind them. I saw the same thing on Commonwealth Avenue. As I said before, the Globe photo is posed.

But on the green light, there’s another problem. Bike boxes and the bike lanes which lead to them invite cyclists to overtake waiting motor vehicles on the right, risking getting struck by a right-turning vehicle. A bicyclist was right-hooked and killed in Portland, Oregon, on May 16, 2012 but apparently that news didn’t reach the Globe’s columnist, or didn’t make an impression on him. Now a letter from the City of Portland is conceding that car-bike crashes have increased at some of the intersections where bike boxes were installed. So much for the Globe’s assertion of safety.

Conscientious bicycling advocates have been warning about the “right hook” problem for decades, based on the difficulty which motorists have in looking into their right rear blindspot, while also checking the intersection ahead.

Swerving across is illegal too: here’s the Massachusetts law, in Chapter 89, Section 4A. It applies to bicyclists, the same as other drivers. Every state has a similar law.

When any way has been divided into lanes, the driver of a vehicle shall so drive that the vehicle shall be entirely within a single lane, and he shall not move from the lane in which he is driving until he has first ascertained if such movement can be made with safety.

Bicycling advocates, planners and government officials who promote bike boxes have simply chosen to pretend that this traffic law doesn’t exist, or can be ignored. Same for the limits of human abilities.

Now, I wouldn’t be fair in making this criticism if I didn’t suggest alternatives.

The one I favor is for cyclists to merge before reaching the intersection. That can be facilitated by signal timing at the previous intersection to allow cyclists to merge across when motor traffic is stopped, and a clear lane into which to merge.

Other suggestions have been to prohibit right turns, or to install special signals to warn cyclists that the light is about to change. Denver’s retired bicycle coordinator, James Mackay, has described some of the measures used in European cities.

These measures will, however, result in more delay, for both cyclists and motorists.

It may be more practical just to designate another street as the one for through bicycle traffic, My favorite suggestion at this Back Bay location would be Newbury street, configured as a two-way bicycle boulevard with a bridge over the Muddy River to connect it with the Fenway area.

Danish story, video and comments on the Albertslund-Copenhagen “bicycle superhighway”

A reader pointed me to a news story on the politiken.dk blog about the Copenhagen/Albertslund “bicycle superhighway” which is getting attention and publicity. The reader’s comments on my previous post read:

Yeah, its kind of joke, but to be fair they are not called superhighways in Danish but Super bicycle tracks, and even then most agree that they are not really that super. There is a video of the entire route here if you scroll down a bit:

http://politiken.dk/debat/skrivdebat/ECE1615543/er-koebenhavns-nye-cykelsti-virkeligsuper/

The two next ones which will open are another story though, as they mostly have their own right of way, and use viaducts or bridges to cross streets.

So, better things may be on their way, but…I ran the article through the Google translator, and it appears in the link below in (sort of) English. The page includes the sped-up video of the entire route.

http://translate.google.com/translate?sl=auto&tl=en&js=n&prev=_t&hl=en&ie=UTF-8&layout=2&eotf=1&u=http%3A%2F%2Fpolitiken.dk%2Fdebat%2Fskrivdebat%2FECE1615543%2Fer-koebenhavns-nye-cykelsti-virkelig-super%2F&act=url

Here’s the video — warning, Shell diesel fuel ad at start, and you can only stop the video when you click on it, see the ad again and click on it to open a bigger ad! This workaround was needed to make the video visible on this page.

The one unifying factor of this route is an orange line painted lengthwise to identify it. The first part of the route is relatively tame. Barriers, unprotected intersections and other hazards pile up near the end.

Some representative quotes (I’ve translated from Googlish to English, thanks to an online dictionary and my knowledge of the neighbor language, German.):

From the article:

“I did not expect that I just had to detour on ordinary roads in residential neighborhoods. I did not see much of the green wave that is supposed to be in town. I do not think you can call it a super bike path,” the [politiken dk test rider] concluded.

From comments on the article:

- The section of tunnel under Motorring 3 is dark and miserably lighted. There are many riding schools (which, incidentally, should be forced to close and move out into a rural area!). The tunnel is usually filled with horse s***, and because you can not see in these tunnels due to poor lighting, you can only hope that you do not ride through any of it.

*****

- In the westbound direction, at the pitch-dark tunnels, you have to negotiate two sets of barriers. The point of these, other than to impede traffic, I do not know. But when you have to use all your mental energy to get through these, they constitute more of a hazard than a safety precaution.

*****

I have commuted between Roskilde and the northwest part of Copenhagen 2-3 times a week on a recumbent trike with an electric assist motor for 6 months (http://ing.dk/blogs/pedalbilen). When I used the “super path” the trip was about 3 km and 15 minutes longer. Especially the part of the route in Albertslund is very indirect and inconvenient. There are detours, barriers and ramps in most places, and it will for example not be possible to ride in a velomobile, as far as I can judge. The new route is comfortable and free of exhaust, but as commuter route it gets a failing grade compared with Roskildevej [a parallel, 4-lane divided but not limited-access highway with one-way sidepaths].

*****

- I didn’t see anything which shows that cyclists have priority over the other traffic. Unfortunately, the only thing new that I see is approximately 100 meters of new asphalt in two places near Rødovre, so that it is easy going. There are simply no real improvements for cyclists in relation to other road users! You can still find barriers, sharp turns, bumps and traffic lights. Why is there no new cycle path, e.g. along the western forest road, so you do not have to drive through neighborhoods with pedestrians and children playing? Why are barriers not turned 90 degrees, so users of the route have right of way?

Even if there were brand new asphalt on the entire route it would never merit the title “super”. Only when a route enables more or less continuous travel at high average speed (which motorists know from motorways) does it, in my opinion, deserve the massive marketing it is currently getting.

*****

…Bus passengers cross the bikeway. It seems quite unreasonable that there are no islands at bus stops where passengers have to wait when they get on and off. Thus cyclists must stop, and so, so much for the “super bike path”.

The Photoshop School of Traffic Engineering strikes again!

The Photoshop School of Traffic Engineering strikes again, this time in Minneapolis.

For background, please read the Minneapolis blog post: http://www.ouruptown.com/2012/08/potential-cycle-track-coming-to-36th-street

Also please read John Schubert’s comment on that post.

I’ve added a comment too — still in moderation as I write this, and I repeat the comment here, slightly edited and with this introduction.

The location described in the blog post, 36th Street at Dupont Avenue, is shown in the Google map below. If the full image doesn’t appear, clicking to refresh the page will probably fix that. The image is zoomable and draggable, but by clicking on “View Larger Map”, you may enlarge it, look down from different overhead angles, and switch in and out of Google Street View.


View Larger Map

36th Street is part of a grid system. Smaller, lightly-traveled 35th Street is one of several that could instead be configured as a bicycle boulevard (also called neighborhood greenway) like those in Berkeley, Eugene, Portland and Seattle, so bicyclists use the street as a through route while only slow, local motor traffic uses it. That is popular with residents and avoids the problems with sight lines which John Schubert has described.

Now for some comments on the pictures in the Minneapolis blog post. They are examples of of what I call the “Photoshop School of Traffic Engineering”, Or the “Anything Goes” school. Well, anything goes in a Photoshopped picture but not necessarily in reality.

Here’s the first picture from the blog post:

Photoshopped illustration of proposed "cycle track" on 36th Street in Minneapolis

Photoshopped illustration of proposed “cycle track” on 36th Street in Minneapolis

The caption for this photo in the blog post reads “[a] possible cycle track is being considered for 36th Street in Minneapolis.” As we’ll see though, the rendering in the picture is hardly possible.

In the picture, there’s already a sidewalk on both sides but now also a special lane so pedestrians can walk in the street. To make room for this and the bikeway, the blue car in the right-hand travel lane is squished to about 3 feet wide and that lane is about 8 feet wide. The text describes the bikeway as 10 feet wide, but it measures as about 12 feet wide based on the size of the bicycle wheels. 36th Street has a cross street every 300 feet, also entrances to back alleys and driveways in almost every block, but the picture shows maybe one intersection (note crosswalk lines) in the distant background. That is unreal. There’s some need for people to get in and out of all those cross streets, alleys and driveways.

Now, the other picture:

Another Photoshopped illustration of the proposed bikeway

Another Photoshopped illustration of the proposed bikeway

The caption in the blog post reads “[a] rendering of how a cycle track on 36th Street could look east of Dupont Avenue in Minneapolis.” Again, no, it couldn’t.

The bikeway is shown at a more realistic width. I’m not sure though how three travel lanes, a parking lane, 3-foot buffer and 10-foot-wide bikeway fit into a street which now has only two travel lanes and two parking lanes. Also note the car about to turn right across a lane of traffic and then across the bikeway at the one intersection shown. The lane with the closest car in it is shown as a lane of traffic, not a parking lane, or there would be signs and markings to indicate that. Assuming though that it is a parking lane and the turning car isn’t cutting off the closer one, then the closer one is still hiding approaching bicyclists from the turning one, whose driver must look to the right rear to see them as they get closer — remember, they may be traveling at speeds up to 25 miles per hour. The bikeway is outside the field of view of the turning driver’s right-hand rear view mirror. Some vehicles have no windows behind the front seat, and so the bikeway would be in a complete blind spot. I just got back from Montreal where I rode bikeways like this and it’s hair-raising with heavy two-way bicycle traffic in such a narrow space. I also had repeated conflicts with motorists turning across my path, using intimidation to try to make a gap for themselves in the stream of bicyclists. It’s safer to ride on 36th street just as it is now, and a bicycle boulevard would be better choice yet, especially for slower and more timid bicyclists. As John Schubert says in his comment on the blog post, there are better ways to make bicycling inviting.

The proposed design isn’t about improving traffic conditions, for bicyclists or anyone else. It’s about a social agenda: creating the appearance of safety for naive bicyclists to increase bicycle mode share, and making motoring more difficult. Actually, motorists would instead use the smaller parallel streets. Elimination of parking on one side of the street to create the bikeway is unlikely to be popular with residents. Snow clearance also is difficult with barrier posts and parked cars in the middle of the street.

The Montreal bikeways are the subject of a widely-publicized research study claiming a safety advantage, but the study has been demolished, see http://john-s-allen.com/reports/montreal-kary.htm

A ride on Comm Ave., Boston, Massachusetts, USA

Comm Ave. Boston: Kenmore Square, Mass Ave. underpass from John Allen on Vimeo.

This is a 4-minute continuous video of a bicycle ride in Boston, eastbound on Commonwealth Avenue through Kenmore Square, to and through the underpass at Massachusetts Avenue. I recommend that you view it on Vimeo site, in full-screen high definition.

Gordon Renkes and I each had a camera, so you can see both a forward and rearward view. We rode safely, and mostly by not using the special bicycle facilities.

Some highlights:

  • The block pavers, bricks and the granite curbstones used as borders for crosswalks made for a very bumpy ride across Kenmore Square and the next intersection.
  • The bike lane for the first block after Kenmore Square was unusable, due to double-parked vehicles. In the next block, it was unsafe, due to the risk of opening car doors and walkouts. One trucker was accomodating enough to park entirely outside the bike lane, inviting bicyclists to run the gauntlet between the truck and parked cars Gridlock Sam-style. We didn’t take the invitation.
  • As we waited for a traffic light, a cyclist raced past us on the right, entering the narrow channel between a row of stopped motor vehicles and one of parked cars. If anyone had walked out, or a car door had opened, the cyclist would likely have had too little time to react, and he would have had no escape route. At least he (and the pedestrian he could have struck) would have been fortunate in that one of the waiting vehicles was an ambulance.
  • There is a bike box along the route, and revealed an issue that I hadn’t noticed before. If the traffic light is red, you’re supposed to filter forward in the bike lane on the right, then swerve across two lanes of traffic to the middle of the 4-lane wide bike box, to be in line with the bike lane which is to the left of 2 lanes — see Google satellite view — note that this is an angle shot from the west. If the light is green, you could merge either before or after the intersection, but there is an advantage in merging before the intersection, as the counterexample of the video shows. You also don’t know when the light is going to change — so in either case, you make a widely divergent choice — merge left, or head for the bike lane at the right — based on insufficient information, and if the light is red, you also could be swerving abruptly across two lanes of traffic just as the light turns green.
  • The buffered bike lane in the underpass makes for an easier ride through the underpass, but where it connects to a narrow left-side bike lane outside the underpass, there is little clearance for motor traffic in the next lane, which is the faster of two travel lanes. There also is a risk of left-hook collisions. I used to ride in the right lane, claiming the lane, and that was simpler and less stressful.

More general comments:

  • The block pavers, bricks and curbstones buried in the street are not bicycle-specific, but certainly not bicycle-friendly. I predict that they will be paved over within a few years as they deteriorate.
  • The attempt to engineer a “bicycle friendly” or “low-stress” solution on busy, crowded Commonwealth Avenue is like ornamenting a pig with lipstick, costume jewelry and a party dress. The bicycle-specific measures, except the bike lane in the underpass, fly in the face of the way traffic works, and the way it uses this street. Experienced, competent cyclists like Gordon and me know how to avoid the hazards, but they worsen our experience anyway — it is in Kenmore Square (during another ride) that I first heard the call “get in the bike lane” in Boston. Less knowledgeable bicyclists garner a false sense of security, following the painted lines, and expose themselves unnecessarily to risk.
  • Meanwhile, other, better solutions beckon. I have long advocated that Boston designate and improve alternative routes on lightly-traveled streets for through bicycle travel. That would be especially easy in Back Bay, with its grid layout. My candidate for an alternative to Commonwealth Avenue would be Newbury Street, the next one to the south, a shopping street which could make a very nice bicycle boulevard, and which, with a little bridge across the Muddy River, would also connect under the Bowker Overpass into the Fenway area. A worse solution also has been proposed: the City is considering a so-called “cycle track” — a bikeway behind a row of parked cars — on the next Street after Newbury Street, Boylston Street. More about these topics later…

Link to my letter to Senator Scott Brown

My letter to a staffer of Senator Scott Brown about the mandatory sidepath provision in the Federal Tranportation Bill is online. Feel free to re-use it, or parts of it.

Mandatory sidepath laws, state by state

I don’t like mandatory sidepath laws for bicyclists, but I like the one in the Transportation Bill, applying to roads on Federal lands, even less.

(d) BICYCLE SAFETY.—The Secretary of the appropriate Federal land management agency shall prohibit the use of bicycles on each federally owned road that has a speed limit of 30 miles per hour or greater and an adjacent paved path for use by bicycles within 100 yards of the road unless the Secretary determines that the bicycle level of service on that roadway is rated B or higher.

I have had a look at state laws on the Internet.

I’m pleased to report that I couldn’t find the ones which Dan Gutierrez earlier listed on his map for Colorado, Hawaii, North Dakota and Louisiana. Dan has updated his page: these laws appear to have been repealed.

The national trend has been for repeal of these laws. While the states have been repealing them, the Federal Transportation Bill, as of March, 2012, includes a provision which is more draconian than any of the remaining state laws, in that it would ban bicycles on a road even if the path is unusable. It might be called the “you can’t get there from here” law, to quote a New England expression. See my previous post for the details.

States with mandatory sidepath laws are shown in red in Dan Gutierrez's map

States with mandatory sidepath laws are shown in red in Dan Gutierrez's map

Mandatory sidepath laws, as far as I can determine, now are on the books in only 7 states: Alabama, Georgia, Kansas, Nebraska, Oregon, Utah and West Virginia. All except for Oregon require the path to be usable; the Oregon law has been explained to me as not actually having any effect, because government agencies will not take on the legal burden of having to defend paths as being safe.

Some of the laws have additional limitations on where path use can be made mandatory. See comments below. The boldface is mine.

Alabama:

Section 32-5A-263
Riding on roadways and bicycle paths.

(c) Wherever a usable path for bicycles has been provided adjacent to a roadway, bicycle riders shall use such path and shall not use the roadway.

Georgia

Note discretionary application, and design standard and destination accessibility requirement for the paths.

O.C.G.A. 40-6-294 (2010)

40-6-294. Riding on roadways and bicycle paths

(c) Whenever a usable path has been provided adjacent to a roadway and designated for the exclusive use of bicycle riders, then the appropriate governing authority may require that bicycle riders use such path and not use those sections of the roadway so specified by such local governing authority. The governing authority may be petitioned to remove restrictions upon demonstration that the path has become inadequate due to capacity, maintenance, or other causes.

(d) Paths subject to the provisions of subsection (c) of this Code section shall at a minimum be required to meet accepted guidelines, recommendations, and criteria with respect to planning, design, operation, and maintenance as set forth by the American Association of State Highway and Transportation Officials, and such paths shall provide accessibility to destinations equivalent to the use of the roadway.

Kansas

8-1590.
(d) Wherever a usable path for bicycles has been provided adjacent to a roadway, bicycle riders shall use such path and shall not use the roadway.

Nebraska

60-6,317. Bicycles on roadways and bicycle paths; general rules; regulation by local authority.

(3) Except as provided in section 60-6,142, whenever a usable path for bicycles has been provided adjacent to a highway, a person operating a bicycle shall use such path and shall not use such highway.

Oregon

My understanding, based on a sicussion with former Oregon state bicycle coordinator Michael Ronkin, is that this law is never enforced, because state and local authorities will not risk ruling that a path is suitable.

814.420: Failure to use bicycle lane or path; exceptions; penalty.

(1) Except as provided in subsections (2) and (3) of this section, a person commits the offense of failure to use a bicycle lane or path if the person operates a bicycle on any portion of a roadway that is not a bicycle lane or bicycle path when a bicycle lane or bicycle path is adjacent to or near the roadway.

(2) A person is not required to comply with this section unless the state or local authority with jurisdiction over the roadway finds, after public hearing, that the bicycle lane or bicycle path is suitable for safe bicycle use at reasonable rates of speed.

Utah

Note that this applies only where signs have been posted directing bicyclists to use a path.

41-6a-1105. Operation of bicycle or moped on and use of roadway — Duties, prohibitions.

(4) If a usable path for bicycles has been provided adjacent to a roadway, a bicycle rider may be directed by a traffic-control device to use the path and not the roadway.

West Virginia

§17C-11-5. Riding on roadways and bicycle paths.

(c) Whenever a usable path for bicycles has been provided adjacent to a roadway, bicycle riders shall use such path and shall not use the roadway.

Bikes, Cars, Light Rail, E. Jefferson St., Phoenix, Arizona

Build it and they will…wait. Well, at least they’re supposed to wait.

If you click on the title in the image or caption, you can view this at a higher resolution.

Bikes, Cars, Light Rail, E. Jefferson St., Phoenix, Arizona from John Allen on Vimeo.

An intersection with light rail, motor vehicles and bike lanes requires bicyclists to cross from one side to the other of a multi-lane street, resulting in delays of 2 to 3 minutes. Alternative solutions are described.

No rules?

Quite by chance, I encountered an advocate of “shared space” and had a conversation with him at the start of a ride I undertook to illustrate the concept. The advocate expressed that there are “no rules” in this kind of space, which is dominated by pedestrians. Do you agree?

Ian Cooper comments on the C&O Towpath

Cyclist Ian Cooper offers a report on the C&O canal towpath, which I have mentioned in a previous post. Supreme Court Justice William O. Douglas deserves a lot of credit for preserving the canal as a park, but as Ian reports, it does not make the grade as a bicycle facility.

Ian Cooper with Trail-a-Bike rig on the C&O towpath trail

Ian Cooper with Trail-a-Bike rig on the C&O towpath trail

Aside from the issues of safety and of priorities which Ian raises, do the parts of the path which are “paved” with pebbles the size of golf balls meet the National Park Service’s criteria to prohibit cyclists from parallel roads, introduced into the current transportation bill in Congress?

An article in the Pittsburgh Tribune-Review newspaper seconds some of Ian’s comments, while indicating that improvements are in the works. The effectiveness of the improvements is certainly open to question: more gravel will not eliminate dropoffs or necessarily provide a good or durable riding surface. The article includes the photo below.

Rough conditions on the C&O towpath trail

Rough conditions on the C&O towpath trail, Paul Christensen photo for the Tribune-Review

An online article by a bicycle tourist also reports some difficult conditions on the trail.

Ian says about that article:

The first image on the left of the page shows a little of how muddy it can get, though it can be worse than this when the path gets very narrow and bumpy. This is a different area of the trail (farther north than my ride), and again this is very wide and non-grassy in comparison with some of the trail south of Harper’s Ferry and Point of Rocks, MD. The author tells how safety is a real issue on the trail due to the bad condition of the surface.

In both the above images, the wide trail allows you to choose a path through the mud. This isn’t always the case in the part my daughter and I cycled. Sometimes you just have to stop and walk. Sometimes you get no warning, hit a pothole or a mud patch and have to rely on skill to maintain control.

Here are Ian’s comments on his own ride:

I know the C&O well. Here on the Maryland side it’s not paved, and I think anyone doing more than 10 mph on it would be taking a grave risk. I cycled with my daughter from DC to Harper’s Ferry June 2nd – 3rd, 2011 with my daughter on a Trail-a-Bike behind me. I will never use it again, as the National Park Service has stated that it must remain unpaved, as it is to retain its historical attributes as a canal towpath. The only reason I didn’t give up on using it during that trip is that I have a lot of experience cycling in winter conditions, so I had confidence that I could counter-steer and retain balance during times when the bike lost traction in the mud. Also, we were heading north, so we were cycling on the canal side of the trail, where the drop-off was only 10ft. I dread to think what might happen if a less confident or less skilled cyclist lost control going southward and fell into the river.

We averaged 5mph. On regular roads, I would have done the trip in less than half the time (in part because the road goes pretty much straight there, while the ‘so-called’ multi-use trail takes a dog-leg approach alongside the river). Also, this trail is overgrown with weeds, is ‘paved’ with loose pebbles the size of golf balls, and is 4 ft wide in places with mud patches and 10+ft drops on each side. In my view it is the worst bike trail I’ve ever seen and is literally a death trap for cyclists (which is presumably why bike trail advocates avoid referring to it as a bike trail). Sadly, most so-called bike infrastructure is poorly designed, poorly implemented and lacking in funding for maintenance. I have yet to see a bike trail or bike path that is well designed, well implemented and well maintained. Until I do see such a thing, I am 100% against such follies.

The photo below was taken around 12 noon on June 3 somewhere near White’s Ferry and is the only image I have showing the actual trail. It shows what should be considered a ‘good’ part of the trail in this area – this part is wide, relatively flat and has only a gentle slope away to the canal on one side. As you can see, even though there’s perhaps 8ft of trail, most of it is grassed over and there’s only two thin tracks of usable surface. Sometimes the trail gets so treacherous that the wet and slippery grass in the middle becomes the safest place to ride.

A better section of the C&O towpath trail

A better section of the C&O towpath trail

The C&O has few road crossings, it’s true. But if you use it in May or June, before the flood season is completely over (and presumably before any yearly maintenance is carried out before the summer season), you see it at its worst, when it is difficult just to maintain control of the bike. At some points, especially the stretch between Seneca and Point of Rocks, MD, it is quite literally frightening. In many places the trail is very narrow, it has a steep ten foot drop on one side to the old canal, and a steep twenty foot or more drop on the other side to the river (sometimes both at the same time). In May and June, the trail is so overgrown that stinging nettle bushes often thrust out into the trail. The trail is filled with pebbles and rocks, and overgrown grass and stinging nettles sometimes make all but a section between 6 and 12 inches wide unusable. This thin section can be muddy, it can change from dry to wet very quickly, it can be deeply rutted from use by previous cyclists, and other parts can be washed out so badly that cyclists can experience sudden potholes. It is extremely treacherous.

In my view, this stretch of the C&O Canal towpath should be closed as a multi-use path as its lack of adequate maintenance means that it is only a matter of time before a cyclist or a runner gets killed on it.