Cambridge Civic Journal Forum

July 27, 2012

City Council to discuss last December’s fatal bicycle crash

Filed under: Cambridge,cycling,Deaths,MIT,transportation — Tags: , , , , , , , , , , , , , , , , , , , — jsallen @ 12:35 pm

On Monday, July 30, 2012, the Cambridge City Council is to discuss a City Manager’s report on the December, 2011 fatal truck/bicycle crash at Vassar Street and Massachusetts Avenue. (I commented on that crash in an earlier post in this Forum).

The city has posted the agenda of the meeting. The City Manager’s report on the crash is on that agenda.

I’ve posted that report here — indented, with my comments unindented:

July 30, 2012

To the [City Council]:

In response to Awaiting Report Item Number 12-63 relative to a report on safety issues at the intersection of Massachusetts Avenue and Vasser [sic] Street, Director of Traffic, Parking and Transportation Susan E. Clippinger reports the following:

In response to the fatal bicycle crash on December 27, 2011, the Traffic, Parking + Transportation Department conducted a review of the intersection that included the operation of the traffic signal, signs and pavement markings of the intersection, and a review of the crash history of the location.

Using both the Massachusetts Department of Transportation and Cambridge Police Department crash information, TP+T reviewed 19 incidents involving bicycles which occurred in the 5 years between 2007 and 2011 (excluding the fatality which was under investigation). The purpose of the review was to determine if a common type of crash was frequently occurring and if engineering measures could be implemented to prevent future crashes.

A Policy Order Resolution from the May 14 City Council meeting (third page here) describes Vassar Street and Massachusetts Avenue as the second-worst intersection for crashes in the city, and reports 55 crashes, with 24 involving “cars” (which I take to mean all motor vehicles). Clippinger reported on 19 bicycle-motor vehicle crashes over a 5-year period — however, single-bicycle, bicycle-bicycle and bicycle-pedestrian crashes are just as real. Perhaps Clippinger did not report on 5 of the bicycle-motor vehicle crashes because evidence was too sparse, but on the other hand, what about the remaining 31? All 55 crashes were serious enough that police reports were filed. Also, bicycle crashes of all kinds, especially those not involving motor vehicles, are greatly under-reported to police.

A couple years ago in a national Webinar, the City’s bicycle coordinator, Cara Seiderman, said that there had been no crashes on the Vassar Street sidepaths. Evidently, she excluded intersections, and even so, her statement was incorrect. There had been at least two bicycle-pedestrian crashes on the sidepaths in which someone was taken away in an ambulance. Following each of these crashes, one of the parties e-mailed me, having read my online comments about the sidepaths. There have almost certainly been additional crashes.

Clippinger’s report continues:

We found that in 17 of the 19 crashes, the bicycle was proceeding through the intersection and was not turning left or right. In eight of the 19 crashes, the vehicle was turning right. A common cause of this type of crash is that either the driver fails to yield upon turning or the bicycle is traveling too fast to stop in time for a vehicle that is in the process of turning.

Clippinger places the responsibility on the motorist to look to the right rear to yield to bicyclists who are foolishly overtaking on the right. Bike lanes to the right of right-turning traffic at intersections, as here, encourage bicyclists to make this mistake.

It also appears that most of these crashes were minor; only two crashes resulted in the cyclist’s being transported to the hospital.

17 of the 19 cyclists described in the report evidently were lucky. Such “coffin corner” crashes are often fatal when the right-turning vehicle is a large truck or bus. However, Clippinger doesn’t report how serious any of the injuries were, whether or not the cyclists were transported to the hospital. To be fair, she may not have had access to this information. It’s hard to get.

Based on the limited information we have on the location and direction of the cyclist involved in the December 27 crash, TP+T determined that this crash is not consistent with the crashes experienced previously at this location. Further, we determined that the traffic signal operation, signs, pavement markings, and layout of the intersection did not contribute to this crash.

I agree that this was a different type of crash. However, features of the intersection almost certainly contributed to the crash. As I noted in my review of the Tech article — and as reported by eyewitnesses — the right turn was difficult for the trucker because of a bulbout and street furniture on the corner. It is likely that the driver was looking into his right side-view mirror to make sure that the truck cleared the street furniture, and so failed to see the bcyclist. To clear the street furniture, the truck crossed the centerline on Vassar Street, placing it in head-on conflict with traffic in the oncoming left-turn lane, one of the possible locations of the cyclist. The layout of the intersection had nothing to do with this?

However, I think that the cyclist most likely was crossing in front of the truck from right to left. In that case, he had been riding wrong-way on the Vassar Street sidepath, and then turned to his right across the street. The sidepath and connecting bike lane enable this conduct. He could have been looking to the right for traffic, and failed to notice the truck on his left. Also, his brakes may have functioned poorly in the wet.

Clippinger concludes:

TP+T remains fully committed to improving the safety of our roads for all users, particularly for pedestrians and bicycles. We continue to research causes of crashes citywide, and each year we use that information to make engineering improvements we feel will reduce the number and severity of crashes.

“We feel”. I’d prefer a stronger report, examining all types of crashes, and a bicycle program guided by careful research rather than feelings.

May 18, 2012

Reports on December, 2011 fatal truck/bicycle collision

Filed under: Cambridge,cycling,transportation — Tags: , , , , , , , , , , , , , , , , , , , — jsallen @ 10:59 pm

(Note: this post has been updated since first placed online, because readers have asked for images to clarify the location and details of the incident. Also see comments following this post. Review of the reports, images and comments has led to some changes in the post, as well.)

The MIT student newspaper, The Tech, has obtained and posted copies of some of the police reports on the truck-bicycle crash on Dec. 27, 2011 which resulted in the death of an MIT graduate, Phyo Kyaw, ’10. I comment here on the Tech story about the crash, and the police reports it links to.

I study bicycle crashes — it’s part of what I do in my profession, but I offer the following comments for free as, I hope, some small service to the MIT community and to the public at large. [Disclaimer, if needed: I am an MIT alumnus. That is, to some extent, why I take the trouble to write this.]

To sum up what I’m about to say, there’s enough blame to go around. Also, the crash investigation failed to look into a number of significant issues or to frame the legal issues accurately. It shows considerable bias toward the truck driver. The Tech‘s reporting missed on a few points. Specifics follow.

The Google satellite view below shows the intersection. The truck was turning the same corner as the tourist “trolley” bus with the green roof shown in the satellite view. This view is from the west, and so north is at the left in the image.

Massachusetts Avenue and Vassar Street, Cambridge, Massachusetts, USA

Massachusetts Avenue and Vassar Street, Cambridge, Massachusetts, USA. Note that north is to the left in this image.

(Cambridge Civic Forum’s blog software won’t let me embed the actual Google view, in which you could scroll around, look from other angles, zoom in and out etc. but you can link to the Google view here.

Now we add Kyaw on his bicycle. He may have been traveling toward Massachusetts Avenue on Vassar Street and stuck the truck head-on, as shown by the arrow coming down diagonally from the upper left in the image below — or traveling toward MIT on the sidewalk of Massachusetts Avenue, as indicated by the arrow at the lower left — or crossing the street from MIT, but not in the crosswalk, as indicated by the arrow pointing straight down from the top. The semitrailer truck crossed the centerline of Vassar Street as it turned. The crash occurred at night, in the rain.

Update: surveillance video excludes Kyaw’s approaching on the sidewalk of Massachusetts Avenue. Damage to the bicycle confirms that it was struck on its left side. Kyaw most probably then was traveling westbound in the eastbound bike lane on Vassar Street and cut across the street in front of the truck.

Massachusetts Avenue and Vassar Street, indicating possible direction of travel of bicycle

Massachusetts Avenue and Vassar Street, indicating possible direction of travel of bicycle

Here is the intersection seen in a Google Street View from the direction of the approaching truck. The three arrows, again, show directions from which Kyaw on his bicycle may have been approaching the intersection. (Update: but not the leftmost arrow in the photo.)

Intersection seen from direction of truck, with arrows indicaing possible approaches of Kyaw on bicycle.

Intersection seen from direction of truck, with arrows indicaing possible approaches of Kyaw on bicycle.

You may also view this Street View in Google Maps.

Here is the Massachusetts State Police diagram showing the final location of the truck, and of Kyaw (to the left of the trailer, on Vassar Street).

Massachusetts State Police diagram

Massachusetts State Police diagram

As also described in the Massachusetts State Police accident reconstruction report, the bicycle contacted the truck’s front bumper and came to rest under the dual tandem left rear wheels of the cab. It evidently was dragged quite a distance farther than Kyaw. The report indicates that Kyaw was not riding in the bicycle lane on Vassar Street (also assuming that he was traveling head-on toward the truck) — but does not indicate that the truck had crossed the centerline of that street. There is similar bias later in the report. As described in The Tech:

“The possible cause of this collision was the encroachment of the bicycle into the path of the turning tractor trailer unit,” the [Massachusetts State Police vehicle accident examination] report [page 6] said.

Encroachment of the bicyclist into the path of the truck when the bicyclist was described as on the right side of the street and the truck partially on the left side? Encroachment means that a vehicle is where it isn’t supposed to be. The bicyclist was encroaching, then?

Different considerations apply if Kyaw was not approaching the truck head-on; I’ll discuss them later.

The reconstruction report goes on to say that

…roadway design and engineering did not precipitate or contribute to this collision.

Nonsense. Though they are not mentioned in any of the reports, a bulbout and street furniture on the corner made the turn difficult for the truck, forcing it across the centerline of Vassar street. The truck driver may have been looking in his right rear side-view mirror to make sure that the rear of the trailer cleared the obstacles.

The Tech goes on to say:

Kyaw’s bicycle’s final position was not in a bicycle lane, the report said. Local laws do not require bicycles to travel in the bicycle lane, and it is common for left-turning bicycles to travel in Vassar’s left lane.

The observation about the law is correct other than that it’s state law, but the last part of the quote is incorrect and misleading. Assuming that Kyaw was traveling along Vassar Street toward the truck, he was in the left-turn lane. Bicyclists must merge out of the bike lane to go straight or turn left without conflict with through and right-turning traffic, or with traffic stopped at the curb. I happen to have a Web page with photos of this very intersection illustrating that point.

Again, however, Kyaw may not have been traveling head-on toward the truck. Then the bike lane is irrelevant, because he then would have been crossing the street, and it is impossible to cross the street while remaining in a bike lane.

The Tech also stated that

The reconstruction report cited contributing factors of “moderate to heavy rainfall,” Kyaw’s nonreflective clothing, Kyaw’s presumed high speed, and the lack of a front light on the bicycle.

A headlight is required by law. The lack of a headlight makes sense as a contributing factor, assuming that the truck driver was looking in Kyaw’s direction, placing some of the responsibility for the crash on Kyaw. Reflective clothing is not required by law. A reflector or reflective material only works if headlights are aimed at it. Rain also may have affected Kyaw’s ability to see. Eyeglasses were found at the scene, and when beaded with rain, they spread glare. Kyaw, like the truck driver, may not have been looking ahead. To merge toward the center of the street, Kyaw should have looked back over his shoulder for overtaking traffic.

The Tech continues:

Kyaw was wearing a helmet at the time of the accident, Cambridge Police report #5 said. The bicycle was “not equipped with a front-facing light,” and its front white reflector was partially obstructed by brake and shifter cables, the report said. Massachusetts law requires bicycles to have a front light at night.

Cables obstructing a reflector don’t seem a likely explanation. They’re too narrow unless the reflector is very small. How the position of the cables could be determined from a bicycle that had gone under a truck also isn’t at all clear. The reflector may, however, have been obstructed by Kyaw’s hand, or its reflective properties compromised by dirt or beads of rainwater. The truck’s headlights were in any case not aimed at Kyaw to light up the reflector as the truck rounded the corner. A large truck’s cab is so high above the headlights that a bicycle’s reflectors barely work if the bicycle is close, see explanation here. A vehicle ahead of Kyaw, or car headlight glare behind him, made worse by a wet or fogged windshield on the truck, may have concealed him.

And, again, if Kyaw was not headed toward the truck head-on, the front reflector is irrelevant.

Kyaw’s 21-speed bicycle appeared to be set at the gear combination that was as hard to pedal in as possible, indicating travel “at a fairly fast pace,” police report #5 said. On the other hand, if Kyaw was intending to turn left and was approaching a red light, it is also possible he was slowing down, or had even come to a stop.

The fifth Cambridge police report includes this statement but also indicates that the shifter for the rear derailleur was in the second-highest position, not the highest.

The discussion of Kyaw’s speed would have benefited from interviews with people who knew his riding style, if they could be found. There are many bicyclists who ride in high gear at a low cadence. On the other hand, he might have been strong and fast, yet still foolish enough to ride at night without a headlight. In this case, he would have been heading into an intersection with a major street against a red light at high speed. I consider that unlikely.

Still, all this brings up the issue of educating bicyclists. I’ve advocated for decades that institutions of higher education provide bicycling instruction to incoming students. Avoiding death or brain injury to even one student every couple of years would more than pay for this. Think of the wasted educational investment, and the loss of future alumni contributions. But I digress.

According to Cambridge Police Report #1, the truck driver “stated that he was traveling westbound on Mass. Ave. when he attempted to take a right turn onto Vassar St. [The driver] said that the light was green and his right directional light was on. Moments later, [he] said he felt the impact of something hitting his truck. He stopped and got out of his truck to investigate and observed that he had been in a collision with a bicycle.

This doesn’t indicate which way the driver was looking — not a very informative statement from him. Did the police ask?

According to the reconstruction report, MIT provided video that showed the truck did activate its right directional signal.

(As indicated in a comment with the article, the video did not show Vassar Street, so it didn’t show Kyaw’s approach).

The police reports say little about the condition of the truck other than that its brakes worked. Was its windshield clean? Were all the mirrors in good working order? Were the headlights aligned? Was the driver’s view ahead obstructed? Etc.

The Massachusetts State Police accident reconstruction report says almost nothing about the bicycle, but page 2 of the fifth Cambridge report describes the locations of scrapes and other damage to the bicycle. These are consistent with the truck’s striking the left side of the bicycle and dragging it on its right side. The front fork was bent to the right, suggesting that the bicycle was struck from the left — except that the front fork and wheel were crushed under the wheels at the rear of the truck’s cab. as shown in the still below from a television news report. I have labeled the locations of the bicycle — the saddle is facing the camera; of a shoe; and of where Kyaw lay following the crash. He had been removed by the time the video was shot.

Locations of bicycle, shoe and Kyaw following crash

Locations of bicycle, shoe and Kyaw following crash

The reports are incomplete in describing the bicycle. Of most importance, what was the condition of the bicycle’s brakes? Even when a bicycle has been damaged by going under a truck, it is possible to examine brake shoe and rim wear, and to determine whether a brake cable had frayed and parted. It is often possible to operate the brakes and determine whether they were in good adjustment.

The bicycle was an under $200 model sold through big-box stores, which are notorious for poor assembly of bicycles — here is the best description of it I could find online. It does have aluminum rims, which brake much better than steel rims in the wet, but how well was the bicycle maintained, and were the brakes working properly at the time of the crash? The police reports say nothing about this.

Though the Massachusetts State Police accident reconstruction report and vehicle inspection report really ought to be definitive on the topics they are supposed to cover, police reports which have not yet been released may possibly fill in some of the missing information.

I hope that my comments have been informative and helpful. — John S. Allen

(Update: please click on the link below to read Paul Schimek’s comments and my replies to them. Paul has suggested that Kyaw was approaching on the Massachusetts Avenue sidewalk. Based on further review of damage to the bicycle, I think that Kyaw may have been cutting the corner from right to left across the path of the truck.)

September 15, 2011

Concord Avenue, Under Construction

Filed under: Cambridge government,cycling,Fresh Pond,planning,transportation — Tags: , , , , , , , , , , — jsallen @ 1:33 pm

I just rode Concord Avenue last Sunday to see what was happening there.

I had thought that the construction project would have been completed by now, but it isn’t.

The image below is of the east end of the section under construction. I find a bit of irony here in that the “Bikes May Use Full Lane” sign is placed at the start of a project which intends to get bicycles off the road, and also it is nonstandard — diamond-shaped like a warning sign which is supposed to be yellow, but white like a regulatory sign, which is supposed to be rectangular (as with speed-limit and no parking signs). The message is a regulatory message: it is law.

Looking west at the east end of the Concord Avenue section under construction

Looking west at the east end of the Concord Avenue section under construction

Construction barrels divide the narrowed roadway into two lanes, rather than the three planned for when construction is complete. As the westbound bikeway is incomplete, I rode west on the roadway. Motorists still were able to overtake me without leaving their lane, as they were when the roadway was wider, with three travel lanes and a bike lane on either side. I was passed by a number of cars, no problem. I had one conflict with a driver who moved out of a side street into my path. Such conflicts will be much more common when bicyclists are riding in sidewalk space.

The road surface was very bumpy because the street has not yet been repaved. The effort is going into construction of the bicycle sidepaths at this time.

I shot video of my rides. It’s HD video and you will want to view it full screen to get all the details. This is the link to the video of my westbound ride. And here is my eastbound ride.

One other thing I hadn’t expected is that the south-side (eastbound) path was almost completely empty, except for me, though it was nearly finished, and unobstructed — on a warm, sunny Sunday afternoon when there was heavy bicycle and pedestrian traffic in Fresh Pond Park and on the Minuteman path.

I can say that if much traffic does appear on the south-side path, the situation will be very confused. There is no buffer between the 5′ wide bikeway (closer to the curb) and the wider walkway away from the curb. There was supposed to be a 2-foot-wide buffer, as I recall. Also, the concrete pavement of the pedestrian section, farther from the curb, is smoother. The bumpier asphalt pavement adjacent to the curb is supposed to be for eastbound bicyclists, in defiance of AASHTO guidelines, which require a 5′ spacing or a barrier, and also in defiance of normal path and road rules, which require riding on the right side. The City’s scheme would have eastbound bicyclists riding on the left side of the combined bikeway and walkway. Meanwhile, there also will be westbound bicyclists using this path to avoid the much worse path on the other side of the street, and probably keeping to the right as is usual.

As the path is behind a high curb, bicyclists who want to cross Concord Avenue will have to wait at the crosswalks rather than to merge into the roadway. At the few crosswalks, there is no waiting area (for example, at 1:24 in the eastbound video). Because the bikeway is between the walkway and the street, bicyclists and pedestrians who are waiting to cross the street will block the bikeway, and other bicyclists will have to divert onto the walkway.

As the concrete pavers of the pedestrian section and the asphalt of the bicycle section age and settle, a step could develop between them, just as on the parts of the Charles River paths, widened with asphalt next to the old stone retaining wall along the riverfront. Many bicyclists have gone down as a result.

Many aspects of the Cambridge bicycle program can be described as ideologically driven, and defying national and state design standards. Placing a longitudinal seam along a bikeway, and directing traffic to keep left, are merely incompetent.

Other than what I have described in this post, the project looks as though it will turn out as I expected, with the foreseeable problems I’ve already described in my earlier post; the right hook and left cross conflicts, inability to cross to the south side at most locations without dismounting in the street to lift the bicycle over a curb; resulting wrong-way riding on the north side, etc.

The party line about the Concord Avenue project, which I have in writing from two City employees (here and here) and verbally from a member of the Cambridge Bicycle Committee, is that “bicyclists will be riding in exactly the same place as they are now.” This statement turns a blind eye to the encouragement of wrong-way riding, and the keep right/keep left confusion. It ignores bicyclists’ crossing and turning maneuvers, and motorists’ being trapped by the curbs and forced to turn across the path of bicyclists; it denies that motorists block sidepaths so they can see approaching traffic in the street. Saying that “bicyclists will be riding in exactly the same place as they are now” is like saying that a bird in a cage, hanging in a tree, is in exactly in the same place as a bird sitting in that tree and free to fly off.

What really burns me up is that the City employees designing bicycle facilities appear to have no concept of how bicyclists actually are going to use them, or of the potential hazards. It’s all about “build it and they will come” and that means, build just anything they think will attract novice cyclists and children, and to hell with design standards and safety research. I see shoddy and incompetent mimicry of European designs, and astonishing hubris. So far, the Concord Avenue bikeway is half built with one side completely open, and very few bicyclists have come, except for me, and I was there on a discovery tour.

Save

Save

November 3, 2010

Specific issues with Western Avenue project

Filed under: Cambridge government,cycling,planning,water — Tags: , , , , , , , , , , , , — jsallen @ 2:24 pm

In this post, I’m going to examine some of the drawings of its Western Avenue project which the City of Cambridge has provided.

All of the illustrations below are from the City’s conceptual design booklet.

Western Avenue concept drawing

Western Avenue concept drawing

The cars shown parked at the left are real cars, in the original photograph that was modified to show the conceptual design. Typical sedans are about 5 1/2 feet wide, not counting the side-view mirrors, but common light trucks are as much as 6 1/2 feet wide. Big trucks and buses can be 8 1/2 feet wide.

The cars shown parked at the right are drawings added when the photo was modified. All of them are micro-cars, very much smaller than the cars on the left — only about 4 1/2 feet wide.

Bicyclists complain about “door zone” bike lanes — where opening car doors pose a threat. On the other hand, the door zone serves an important function. A motorist can open the car door without its protruding directly into the path of motor traffic, and can walk around the car.

In the drawing below, I have copied the nearest car in the original drawing into each travel lane. This drawing shows too little clearance between parked vehicles and moving ones to allow motorists safely to walk around to the street side of their vehicles or open the doors. The right lane as shown is especially tight, even with micro-cars parked on the right and ordinary sedans in the travel lanes — though Western Avenue is a designated bus and truck route.

Western Avenue concept drawing, modified

Western Avenue concept drawing, modified

To show how wide the left lane is at present, the white line in the foreground replaces the gray patch that is dimly visible in the original drawing, covering up the location of the present lane line.

The parts of the illustration that are from the original photo are to scale — including the cars I have copied into the travel lanes. The drawn-in elements are conceptual, and some are not to scale.

The drawing below, also from the City, is dimensioned, showing a 36-foot wide roadway. The elements are to scale: 10.5 foot travel lanes, 7-foot parking lanes and mid-sized cars 6 feet wide, not counting the mirrors — like a a Ford Taurus. This drawing shows more room between vehicles than the right lane in the photo, but on the other hand, the parked cars are tight against the curbs, and no trucks or buses are shown.

Cross-section of street with cycle track

Cross-section of street with cycle track

Now let’s look at an overhead drawing, which shows a typical treatment at an intersection.

Western Avenue at Jay Street

Western Avenue at Jay Street

Let’s put more cars and some bicyclists and pedestrians into the picture. I’ve put three bicyclists on the blue strip which represents the cycle track. Two are headed with traffic and one is headed opposite traffic. (Off-street facilities encourage two-direction traffic, and this is particularly so on a one-way street where there is no opposite-direction paired street conveniently nearby.) There also is a group of pedestrians standing on the bulbout before the intersection. Excuse me if the bicyclists and pedestrians look like ants, I’m no Picasso.

Pedestrians and parked cars conceal  right-way bicyclists from drivers of cars A and B, increasing the risk of a “right hook” collision. Also, Car B  is blocking the right-hand travel lane. Such blockages will increase congestion. The more bicyclists, the more often turning motorists will have to wait in the position shown. At present, motorists can keep moving as they prepare to turn right, because they can merge behind a bicyclist before reaching the intersection.

Car C in the drawing must wait far back from the intersection, what with the separate sidewalk and cycle track. Then, on reaching the intersection, as shown in the illustration below, the car must block the cycle track as the driver scans for traffic. If more than one car is in line, both the sidewalk and the cycle track will be blocked at the same time.

Western Avenue at Jay Street, cycle track blocked

Western Avenue at Jay Street, cycle track blocked

Presently, without the cycle track, this kind of blockage happens only for the sidewalk. It is more troublesome and hazardous for bicyclists than pedestrians, because bicyclists are faster, and farther away when the driver must first see them, and can be hidden by buildings or by pedestrians on the sidewalk. The crash rate for wrong-way cyclists on cycle tracks like this one is very high — research in Finland, Sweden and Germany has shown it to be about 10 times as high as for right-way travel on the street. Right-way travel on a cycle track located, like this one, behind parked cars, and with unsignalized intersections and driveways, has been shown only two or three times as hazardous.

There is also a much greater risk of collisons with pedestrians, and with other bicyclists, than when riding in the street. This cycle track has about 6 feet of width where bicyclists are clear of car-door hazards or plantings — very substandard for a two-way facility.

There is a question what the wrong-way bicyclists will do when they reach Franklin Street and the cycle track ends. Most likely, they will go up onto the sidewalk or ride opposite traffic in the bike lane.

Finally, let’s look at the intersection of Western Avenue and Memorial Drive. At present, Western Avenue has four travel lanes approaching the intersection.  The rightmost lane is a right-turn-only lane which the City describes as underutilized. I agree with that description — even in the evening rush hour, I have been able to filter forward to the intersection on my bicycle in that lane.

The City proposes to change that lane into a cycle track, so right turns are made from the next lane to the left. In this connection, I question the City’s conclusion that its plan will not increase congestion. In the evening rush hour, traffic already queues on Putnam Avenue and Memorial Drive, all the way back to River Street. Even one vehicle waiting to turn right, while bicyclists overtake on the right, will block all other vehicles in the lane behind it. This is aside from the issue of institutionalizing the “right hook” — placing all responsibility for bicyclists’ safety on the motorists, and stripping away bicyclists’ defense of merging into the line of right-turning traffic.

Western Avenue at Memorial Drive, conceptual drawing

Western Avenue at Memorial Drive, conceptual drawing

I suggest instead that bicyclists be encouraged to travel along the left side of the right-turn lane, by means of shared-lane markings and signage, or better, if there is room, a through bike lane.

The question remains of how to handle opposite-direction bicycle traffic. It does not admit of an easy answer.  At this point, I’m most inclined to try to address it on River Street.

And, I’ll add: the sacredness of on-street parking is the issue that makes the problem insoluble. If parking could be removed form one side of Western Avenue, a contraflow bike lane would be an option.

There is no such issue on River Street, because there are many parallel streets in Cambridgeport that allow travel in the opposite direction.

Signing off…

October 29, 2010

Burning bridges

Filed under: Cambridge government,planning — Tags: , , , , , , , , — jsallen @ 8:59 am

I have removed my most recent post.

Though it was factual — and passed muster with Robert Winters, who manages this forum — it did not address the main issue that motivates me to post here: my intense frustration with some directions which the Cambridge bicycle program is taking. My post was an expression of frustration rather than a description of current issues, and as such, it created more heat than light.

In the post, I asked whether Jeff Rosenblum was a builder of bridges. I think that was a fair question, but on the other hand I have burned some, and not only with him. I am no longer a member of the Massbike Technical Advisory Committee. Executive Director David Watson had already explained to me that my presence on that committee was getting in the way of Massbike’s work with governments. My recent post was the last straw for him.

I had already considered resigning for a couple of months. I regret that I did not have the courage to ask for a resignation. Instead, I backed myself into this situation. In the light of some of my posts in this forum, it may come as a surprise to my readers, but confrontation does not come easily for me. Sometimes I do not manage it well, and it bursts out.

Massbike and its predecessor organization, the Boston Area Bicycle Coalition, have been a major part of my life over the years. I have been on the Board of Directors, been President, attended hundreds of meetings and public hearings, written large reports under contract. I part from Massbike with considerable regret. On the other hand, I am also feeling much relief with this change. I had become increasingly frustrated with some directions Massbike is taking. I was increasingly uncomfortable as a member of the Technical Advisory Committee, and Massbike leadership was increasingly uncomfortable with me.

My underlying drive, my lifetime quest, as I must acknowledge to myself, is as a journalist. When I see something that disturbs me, my primary instinct is to provide information, to explain my concern, to try to make it understandable to other people. I am highly uncomfortable with biting my tongue in the interest of political expediency and compromise.

I have now freed myself from that obligation as it involves bicycling issues in Massachusetts, and so I think I will now be able to do a better job here on this forum. I offer my heartfelt thanks to Robert Winters for hosting this forum and for his support.

I’ll sign off with a quote, which I think is apt:

“The basis of our governments being the opinion of the people, the very first object should be to keep that right; and were it left to me to decide whether we should have a government without newspapers or newspapers without a government, I should not hesitate a moment to prefer the latter. But I should mean that every man should receive those papers and be capable of reading them.” –Thomas Jefferson to Edward Carrington, 1787. ME 6:57

October 27, 2010

Western Avenue proposal: ill-considered

Filed under: Cambridge government,cycling,planning — Tags: , , , , , , , , , , , — jsallen @ 12:35 am

Cambridge has posted its preferred design proposal for Western Avenue.

Conceptual Design Selection booklet, October 2010. This NEW booklet details the current draft proposed conceptual design. Online/ download: http://www.box.net/shared/g4hl7zupht

Conceptual Design roll-plan. This shows the draft proposed conceptual design in plan form.
Online/ download: http://www.box.net/shared/9emm0tq29j

Neighborhood Walk this Thursday, Oct 28, 5:30pm, Andala Cafe, 286 Franklin Street

Community-wide Public Meeting, Wed Nov 3, 7:00pm (open house 6pm), Cambridge Senior Center, 806 Masssachusetts Avenue.

Cambridge continues with its plan to slow traffic by making streets narrower, and so more stressful and hazardous for motorists, while moving bicyclists onto glorified sidewalks where it is difficult or impossible for crossing and turning motorists to see them. The repeated invitations for right-turning motorists to turn across the path of through-traveling bicyclists in this proposal leave me breathless, especially where groups of pedestrians will wait on a bulbout, concealing through-traveling bicyclists. Also, the proposed cycle track will greatly encourage contraflow bicycle travel without making any reasonable or safe provision for it. If you have any doubt about the hazard of contraflow travel on a bicycle sidepath, here’s a link to a study which addresses it. There also will be the same issues of snow clearance as already occur on Vassar Street. It is predictable that bicycle-pedestrian collisions will be a problem, as they have been on Vassar Street.

The word “protected”, in traffic engineering used to mean, for example, a left-turn traffic signal phase where opposite-direction traffic had a red light.

Now in the Cambridge proposal it is being used to mean “motor traffic turns right across through bicycle traffic, with interrupted sight lines and no traffic signal.”

The word “protected” sure sounds good, if you don’t know that the treatment under discussion results in increased crash rates.

“Traffic calming” in very ancient times (50,-100 years ago) used to mean traffic-law enforcement. Despite the availability today of efficient tools such as license-plate cameras to record speeding and traffic-signal violations, Cambridge chooses a hardware solution — narrow lanes, which make for more stressful, difficult and dangerous driving conditions — to address the software problem of poor motorist behavior, and emphasizes the point by using bicyclists as obstacles.

Cambridge’s message to its motorists, delivered by creating an obstable course: drive real slow, and look back over your right shoulder when you turn right, or you might kill one of our highly valued and highly vulnerable bicyclists, and it’s all your fault if you do, because, you see, they are protected.”

Please don’t peg me as a naysayer. I made suggestions for alternative treatments in an earlier post, which led to a lively and welcome discussion.

Also see Paul Schimek’s post on this blog.

I hope to see good citizen participation at the public events.

Your comments on this post are welcome too.

June 22, 2010

Comments on Cambridge’s Western Avenue project

Filed under: Cambridge government,cycling,planning — Tags: , , , , , , , , , , , — jsallen @ 12:01 pm

This post contributed by John S. Allen

Note as of May 20, 2015: The document linked in the paragraph below is no longer on the City’s Web site. It has been retrieved from the Internet Archive.

Western Avenue is a major one-way arterial street, a truck and and bus route, the only direct route from the Central Square of Cambridge to Allston, Brighton and other points west. Western Avenue presently needs full-depth reconstruction, which also provides the opportunity to reconstruct sewers. The City of Cambridge has recently posted conceptual drawings showing three ways to reconstruct Western Avenue. These and additional information are posted on the City’s Web site.

View Google Map

Western Avenue is lined with typical Boston-area “three-decker” apartment buildings for most of its length. These date back to the early decades of the 20th Century. There are a few businesses as well. Between Pleasant Street and Memorial Drive, Western Avenue presently has two travel lanes, with parallel parking on both sides, except at bus stops and at the right turn lane before Memorial Drive. There is a bike lane for part of the way.

The construction of a Massachusetts Turnpike extension interchange just across the Charles River in Allston in the mid-1960s led to an increase in traffic on Western Avenue and on River Street, which carries traffic in the opposite direction. The much-despised Inner Belt limited-access highway – Cambridge’s equivalent of Boston’s Central Artery – was never built. Governor Francis Sargent vetoed its construction in 1971. It would have diverted traffic from Western Avenue, but it would have split Cambridge in half, just as the old Central Artery separated downtown Boston from the waterfront.

Western Avenue and River Street join at Central Square in Cambridge, but they diverge from each other toward the river. They do not form a convenient one-way pair for short trips.

Western Avenue presents a difficult problem of accommodating all interests, as an arterial lined with residences. Accommodating through traffic including trucks and buses conflicts with the interest of residents in safe walking conditions, in peace and quiet, and in on-street parking.

I am writing this to comment on three conceptual drawings which Robert Winters has sent me. These were posted on a Cambridgeport neighborhood e-mail list. I’ll make my own suggestions after discussing them.

Concept 1

Western Avenue, Concept 1

Western Avenue, Concept 1

Note as of May 20, 2015: The 2010 Cambridge Bike Trends report has been moved from its original location to a different location on the City’s Web site.

Concept 1 is the most conservative. It keeps the two travel lanes but has a bike lane and bulbouts on the right side. This design would presumably somewhat increase the appeal of the street to young and timid bicyclists. However, the bike lane, like most bike lanes in Cambridge, is in the door zone of parked cars. Cambridge’s recent report on bicycle trends showed that doorings amounted to 20% of all reported car-bicycle crashes, the highest percentage I have seen anywhere. Bicycle facilities that encourage riding in the “door zone” do nothing to resolve this problem and probably increase it. Educating cyclists to avoid riding in the “door zone” becomes more difficult when bicycle facilities direct cyclists to ride there.

Due to the total width’s being unchanged in the Concept 1 proposal, Western Avenue would remain suitable for longer-distance through bicycle travel at normal speeds for adults who make regular use of a bicycle. Shorter-distance neighborhood bicycling would not be encouraged because, as mentioned, Western Avenue is one-way and River Street does not make a convenient two-way pair with it for shorter trips.

The drawing shows a bus shelter. A bus shelter is nice in wet weather, but this one is shown on a long bulbout (at sidewalk level) in the no-parking zone currently occupied by the bus stop. With this arrangement, buses will have to stop in the right-hand travel lane and bike lane, blocking them.

The bulbout on the right side of the street shortens crossing distances for pedestrians – but the drawing shows no bulbout on the left side of the street, where there is parallel parking but no bus stop. Why not? At bus stops, there could be bulbouts on the left side only, resulting in the same crossing distance but still allowing buses to pull to the right and avoid blocking other traffic.

All in all: Concept 1 would only improve conditions for pedestrians and for people waiting for buses, and clear the way ahead of buses by blocking other traffic. Conditions would worsen for other motorists and for bicyclists.

Concept 3

Western Avenue, Concept 3

Western Avenue, Concept 3

Concept 3 shows a so-called “cycle track” – a bicycle path – at the right side of the street, located behind the bus shelter and parked cars. I use the quotes because the term “cycle track” has been used to describe various types of facilities. All they have in common is that they parallel roadways like sidewalks.

The “cycle track” would be fitted in by narrowing the travel lanes and eliminating the bike lane on the street. The drawing does not show whether the “cycle track” would be intended for one-way travel or for two-way travel. Two-way travel would occur in any case, because many bicyclists would perceive the “cycle track” as a safe facility, separate from motor-vehicle traffic.

Research on bicycle paths adjacent to streets in Germany, Sweden, Finland, the USA and Canada has shown alarming increases in crash rates above those for riding in the street, due to increased conflict with motor traffic at intersections and to conflicts with pedestrians and other bicyclists everywhere. These results have been confirmed in a recent study in Copenhagen. There are exceptions when the paths are very carefully engineered, with traffic signals to prevent conflicts and with adequate width, but this one does not meet those requirements. The “cycle track” as shown would be partially in the door zone on the right side of motor vehicles, and would be crossed frequently by motorists making turns into and out of side streets — with sight distance problems due to the parked cars; also by pedestrians getting in and out of cars, going to and from bus shelters and preparing to cross Western Avenue. People on inline skates and skateboards, and pedestrians overflowing the sidewalk, would also use the “cycle track.”

One effect of Concept 3 would be to discourage longer-distance through bicycle travel, and to encourage shorter-distance, low-speed bicycle travel by children and novice cyclists. This encouragement would be purchased at the expense of a higher construction cost, more crashes, increased congestion of motor traffic, and making future reconfiguration expensive. Also, it is very difficult to keep a “cycle track” at sidewalk level clear of snow and ice though winter; probably only a single sidewalk width would be plowed, as with the existing “cycle tracks” on Vassar Street; plowed snow would melt back onto the surface and refreeze. Transitions from street level to the “cycle track” typically also are difficult to keep clear of ice and plowed snow.

The bus stop in Concept 3 is just like that in Concept 1, but the travel lanes are narrower, making it even more difficult for other traffic to overtake stopped buses. Placing a cycle track behind a bus stop was shown in the recent Copenhagen study to lead to an increase of 17 times in bicycle-pedestrian crashes, and 19 times in injuries.

Concept 3 is at the very least ineligible for Commonwealth funding, and probably unlawful, because required signage would not comply with the Massachusetts Project Development and Design Guide. A procedure does exist through the Federal Highway Administration to legalize projects that are not within design standards, and to exempt non-standard treatments from liability. The procedure defines new treatments as experimental, and requires that research data be collected, so that non-standard designs may serve to direct the standards-setting process. That is very desirable outcome from the installation of non-standard treatments, of which Cambridge has not taken advantage despite its having installed a number of such treatments.

Concept 5

Western Avenue, Concept 5

Western Avenue, Concept 5

Concept 5 shows Western Avenue with a bike lane, only one so-called “car lane” and back-in angle parking on the left side. Vehicles would have to stop and back up to enter the parking spaces. The bike lane would not be in the “door zone”, because all the parking would be on the other side of the street, but buses would block the bike lane and the one general-purpose lane. Truckers making deliveries would block it for extended periods of time, as trucks would not fit into the back-in parking spaces. Other vehicles might just be able to squeeze by, it’s not clear, but even so, a reduction from two lanes to one would result in gridlock, absent a Cambridge Big Dig to divert traffic.

General comments

What happened to concepts 2 and 4? What did they show? Or does the City just like odd numbers?

I have put the term “car lane” in quotes. There is no such thing as a “car lane”, and it is odd for the City to use this term. Cars are not the only vehicles — there are also trucks, buses, motorcycles, motor scooters, bicycles, and yet others. All may use these lanes under Massachusetts law. However, narrowing the roadway and creating a separate bikeway, as in Concept 3, will recruit motorist animosity to chase bicyclists off the road.

The conceptual drawings are notable for what they do not show. They are far from a complete plan. Though there is some technical data on existing conditions in other documents which the City has provided, there is no analysis of traffic capacity and volumes or signal timing to go with the different concepts. Good decisions about street layout can not be made without this information.

It is clear, however, that all three options for Western Avenue would increase congestion, due to the placement of the bus stops. Option 3 would increase congestion further due to conflicts between cyclists and turning motorists. Option 5 would create congestion all day long.

Transportation reformers like to point out that building road capacity results in an increase in traffic. In practice, if demand exceeds road capacity, traffic does indeed increase — until congestion prevents it from increasing further. An increase in capacity may lead to development and make longer trips convenient. Cambridge is already a built-up area, and development has occurred elsewhere as the Turnpike has encouraged commuting to/from distant suburbs.

Western Avenue can’t comfortably accommodate all current uses. Reducing its capacity, as in the proposed concepts, isn’t going to solve its problems. Only draconian measures – extreme taxation of motor vehicles and motor fuel; a major build-out of public transportation to serve suburban commuters; removal of on-street parking from one side of Western Avenue, and/or a Cambridge Big Dig to provide an alternative route – would relieve Western Avenue of the competing pressures that have resulted in its intractable problems.

Removing parking on one side of Western Avenue would allow a contraflow bikeway behind a median barrier, so the street would be two-way again for bicycle trips. University Avenue, in Madison, Wisconsin, offers an example of such a treatment. I don’t think it would be as successful on Western Avenue, though, because University Avenue is much wider, making room for an ample with-flow bike lane and discouraging wrong-way travel in the contraflow bikeway. Another possibility if parking were removed on one side would be a bus/bike lane — but this would have to be policed with license-plate cameras, or else Massachusetts motorists would ignore it.

What can be done until/unless political will builds to make the needed changes?

If Western Avenue is to remain one-way, then the bus turnouts should remain. Bicycle accommodation on the left side of one-way roadways is not a new idea; it is common in New York City and has been used recently on Commonwealth Avenue in Boston. It might make sense here, and would avoid conflicts with buses. But then there is the issue of transition from/to the right side, and especially to get to the right of left-turning traffic before Memorial Drive and the Western Avenue Bridge. Traffic-signal timing and special (experimental) bicycle signals in the block before Putnam Avenue could ease the transition back to the right. A bike lane on the left side would still most likely be in the door zone, though there would be fewer door openings.

The simplest improvements, and those which can be done now, would be to leave Western Avenue with two travel lanes but to place shared-lane markings in the right lane and bulbouts only at the left side if there is a bus stop on the right. Strict speed-limit enforcement would be helpful, too. In the last block between Putnam Avenue and Memorial Drive, it would be helpful to remove parking entirely on the right side, so as to relieve congestion caused by the large volume of traffic turning from Putnam Avenue and the long red on the traffic signal at Memorial Drive. Perhaps the removed parking can be accommodated off-street, so as not to decrease the number of parking spaces, which are held sacred by business owners and residents. There appears to be space for parking around the city-owned generating plant in the last block before Memorial Drive. Synchronization of traffic signals also would be very helpful, as well as strict speed enforcement and a lower speed limit. These might be enforced by means of license-plate cameras if the objection to them as an intrusion on privacy can be overcome. Since when is speeding on a public way a private matter?

Comments on presentations

Now, some comments on presentations and meeting summaries from the task force studying Western Avenue:

Note, as of May 20, 2015: all three of the documents linked in this section are no longer online, or possibly have moved to different addresses. The versions now linked have been retrieved from the Internet Archive.

The April 15, 2010 presentation most addresses design goals: Notes on this presentation are also online.

“Pedestrian safety a main concern.” The cycle track option will decidedly worsen pedestrian safety.

“Design goals: safe, efficient pleasant” Choose any two as long as one of them isn’t “efficient”. All three of the proposed concepts would reduce efficiency.

Page 47 (page 8 of PDF): shows narrowed travel lanes and cycle tracks on a street that extends to the vanishing point in the background without any cross traffic or parking. The apparent goal of narrowing the travel lanes is to reduce travel speed and make the sidewalks more pleasant for pedestrians, though it’s unclear just where pedestrians would be going on this endless street without destinations. On a street with cross traffic and multiple, conflicting uses, narrowing the traveled way results in seriously decreased efficiency. Reduction in speed is best achieved by rigid enforcement, rather than by reducing efficiency.

Page 10 of PDF, lower left: shows a bus blocking the bike lane, because a bulbout has been placed at the bus stop, exactly what will happened with Concepts 1 and 3 for Western Avenue.

Page 11 of PDF: shows 3 different kinds of inconsistent and nonstandard markings for speed humps and speed tables.

Some notes on the public meeting summary from March 31, 2010:

goal #22, page 6 of PDF:

“Undertake reasonable measures to improve the functioning of the city’s street network, without increasing through capacity, to reduce congestion and noise and facilitate bus and other non-automobile circulation.”

Not achieved, all of the concepts increase congestion. Concept 3 produces gridlock.

Goal 23, page 6 of PDF:

“Encourage all reasonable forms of nonautomotive travel including, for example, making improvements to the city’s infrastructure to support bicycling and walking.”

The concepts generally improve walking conditions, though concept 3 drastically increases conflicts between bicyclists and pedestrians and will predictably increase the crash rate.

Preliminary project goals, page 7 of PDF:

“Ensure corridor is safe for all users • Maintain adequate traffic flow • Reinforce residential character • Appropriate traffic speed • Improve conditions for walking, bicycling, and transit riders.”

None of the concepts furthers all of these goals. Achieving goals of reinforcing the residential character and improving bicycling conditions is particularly difficult.

Conclusion

Improving conditions on Western Avenue isn’t going to be easy. The City’s concept drawings show three plans which, at best, improve conditions for pedestrians, but which worsen them for motorists and which either effect little change or worsen them for bicyclists. Some alternatives are more promising, but any that are to effect major improvements are unlikely to be politically palatable until and unless the price of motoring gets much higher.

April 30, 2010

Concord Avenue: City’s position, and comments

Filed under: Cambridge government,cycling,planning — Tags: , , , , , , , , , , — jsallen @ 3:20 pm

On April 27, Kelly Dunn, Community Relations Manager of the Cambridge Department of Public Works, sent the e-mail below to a number of people. One was Jessica Eckhardt, who lives near the project area. The sections below in quotes are Ms. Dunn’s e-mail and the other sections are Ms. Eckhardt’s and my response.

Dear Jessica,

Thank you for your input and suggestions regarding the cycle tracks on Concord Ave.  I hope I can address some of your concerns.

A few years ago a comprehensive planning study of the area was completed.  The Concord-Alewife Study examined the current support system for pedestrians and cyclists in the area, and looked at how we might enhance access through additional connections in the Alewife Quadrangle.  I encourage you to take a look at the study:  http://www.cambridgema.gov/cdd/cp/zng/concalew/concale_plan_all.pdf

We like what that study says, but on the other hand, your statement changes the subject. That study contains no mention of “raised bike lanes”.

As projects move forward, we hope to be able to implement some of the connections noted in the study. Regarding the overall design of Concord Avenue, there are a few things to note. The reconstruction that will happen is a complete right-of-way reconstruction, with reconstruction of sidewalks, curbs and drainage systems; this would happen in any case and is not being done specifically to create the raised bike lane.

So, the “raised bike lane” just sorta happened?  No, the City is consciously taking advantage of the need to reconstruct the street and sewers to create the so-called “raised bike lanes”.

Why the quotes? By definition, both technical and vernacular, there is no such thing as a “raised bike lane”. Any lane is part of the roadway, at roadway level. A bike path is separate from the roadway, and standards for safe design apply to it too.  Under the proposed design, neither the street nor the paths meet design standards that apply in the Commonwealth of Massachusetts.

The raised bike lane is just that: bicyclists will be in the exact same location as they are now.

That statement turns attention away from the issues by discussing location instead of behavior. The statement makes a host of assumptions, first of which is that cyclists only need to ride in the bike lane. Yes, you can be in the exact same place, but your options are very different if you are behind a curb.

Consider access to and from the eastbound “raised bike lane.”  To reach it from most entrances on the north side, cyclists will have to cross most of the way, dismount, lift their bicycles over a curb and remount. Eastbound cyclists on the south side will have to hop down a curb at most places to turn left. The difficulty and danger of crossing the street will strongly encourage wrong-way riding, a practice which Cambridge has correctly disparaged in the past and is ignoring with this project.

Also, cyclists may now merge out of the bike lane to allow motorists to turn right without conflict. This option is denied with the “raised bike lanes”.

This is not a sidewalk path and bicyclists and pedestrians are separated by a street furniture zone, where street trees and street lights are located.

We do anticipate pedestrians spilling over or choosing to use the “raised bike lane” for travel – also cyclists using the pedestrian strip. In some places, the available width for both is only 10 feet. Still, the most disturbing issue with riding on a sidewalk-level facility is not so much the conflicts with pedestrians. It is the conflicts with motor vehicles — when riding the right way and much more so when riding the wrong way.

No matter what the design, the north side of Concord Avenue cannot be a safe location for the novice and child cyclists the City wants to attract. There is heavy turning and crossing traffic, at way too many locations. We have suggested extending the multi-use path on the south side — which has its benefits and drawbacks — the most notable benefit is safety for the inexperienced and child cyclists, with only one driveway crossing in the same distance.

At intersections and driveways, the facility is a regular in-street bike lane.

This is inaccurate and reveals a serious misunderstanding. The design drawings show the facility coming down to street level within a few feet of each street or driveway. To operate as a bike lane, it would have to come down at least 100 feet farther away, so that cyclists and motorists could negotiate lane position before and after the intersection. The City is not unfamiliar with this concept, which it used in its Vassar Street project. With, on average, one driveway or street every 100 feet, allowing merging distance around intersections and driveways would leave the westbound facility a bike lane just as it is now, for almost the entire length of the project.

There will be added signage reminding motorists to yield to cyclists.

Right-turning motorists will have to stop and wait, rather than merging into the bike lane before turning. Expect congestion, and mistakes. Signs or no signs, left-turning motorists will be unable to see past vehicles in the westbound lane. The best a left-turner can do is to creep forward until his or her vehicle’s hood provides a warning to cyclists that they need to yield.

There is nothing about the design that changes where cyclists travel over a standard bicycle lane.

This statement ignores the need to cross the street, among others, as already discussed.

Turning movements are always a concern, on all roads, whether there are bicycle facilities or not. There is no evidence that a raised bike lane with this design would make the situation worse; to the contrary, it increases the visibility of the cyclist, as well as decreases the likelihood of other dangerous behaviors such as motor vehicles parking in the bike lane.

That is an astonishing statement. Such evidence has existed for decades. It follows from human factors analysis (e.g, that drivers do not have x-ray vision, as already discussed), and from safety studies on both sides of the Atlantic. See for example this review of research results. And, a recent, extensive study in Copenhagen confirmed substantially-increased crash rates for cyclists, motorists and pedestrians alike.

If everything about positioning is the same, how can a height difference of 6 inches — or less, when the facility slants down before a street or driveway — make the cyclists more visible, especially to left-turning traffic? Will the child cyclists be more visible? Will any cyclists be visible when to the right of vans, trucks and buses?

As to your concern about motor vehicles parking in the bike lane, there is ample parking in the adjacent industrial area, and besides, the bike lane is too narrow to park in. Parking there is rare, illegal and subject to fines and towing. If there is no bike lane, any illegal parking will be in the travel lane instead or with one wheel up over the curb in the “raised bike lane”.

It’s important for cyclists to feel safe; especially riders with children and others who would not choose to ride on major streets with high volumes and high speeds of traffic.

We find it very distressing that the City proposes to attract unsuspecting cyclists including children onto a facility that crosses 24 driveways and 7 streets in 3000 feet, with known and serious crash risks, by making them feel safe — when the option exists for a path with only one, signalized intersection on the other side of the same street. Is it acceptable to make people feel safe when actually creating hazards for them? There is a vernacular term for this action: “Pied Piper” and also a legal term.”attractive nuisance.” We vote to re-examine the project on the basis of true safety, rather than an illusion of safety.

The City is committed to supporting and promoting sustainable transportation, and making it available and accessible to all. Raised bicycle lanes have been proven to be safe, effective facilities, which enable more people to choose to bicycle.

We support sustainable transportation too. We ride our bicycles almost every day, and we desire real safety improvements. Please cite your sources and clarify whether you are stating that a “raised bike lane” with so many intersections and immediately behind a high curb has been shown safe.

The project will also have important benefits to other users, especially pedestrians, who will have a greater buffer from motor vehicle traffic and improved street crossings. It is also expected that narrowing the curb-to-curb width of the street will help to reduce speeds, which are currently excessive.

Then we would be trying to use the cyclists and the car-bike conflicts as a shield, sacrificing one group for the benefit of the other. See especially the table on page 3 of the Copenhagen study, which was limited to the most carefully-designed street-corridor separated bicycle facilities. It found streets with these facilities more hazardous than other streets — for cyclists, motorists and pedestrians alike. Many features of the Concord Avenue design increase the hazard far beyond that of the Copenhagen facilities. Please, Ms. Dunn, show us your evidence to the contrary. We can’t just take your word for what you say, when public safety is at stake.

Yes, speeds are sure to decrease when the motorists are brought to a complete halt to wait to turn right across the “raised bike lane” and to a crawl to try to avoid collisions when turning left.  Speeds could easily be controlled with traffic enforcement or with other measures, for example, raised pedestrian crossings.

One of the primary goals of the project is to improve conditions for people walking and biking on Concord Avenue, while maintaining vehicular capacity.  The number of travel lanes will remain the same as today.

A “raised bike lane” is not a bike lane. The number of lanes will be reduced by two. A cyclist, who has the right to use the roadway under the laws of the Commonwealth, will no longer have eastbound and westbound bike lanes on the road. Also, capacity for motor vehicles will be reduced because motorists will have to stop before turning right, and will have to creep forward (we hope) while turning left, to yield to cyclists they can not see.

The conditions for cyclists and pedestrians will deteriorate with the snow in winter and no place to put it.  Even if the “raised bike lane” is cleared, it will remain partly coated with slush and ice.

A community meeting was held last spring and the project has been reviewed by community groups, the city’s bicycle and pedestrian committees, the disabilities commission, and the committee on public planting.

The Cambridge bicycle program likes push the envelope by imitating European practice. People who are not familiar with the research literature can easily be convinced that the grass is always greener in Copenhagen, and that all such innovation is positive. This project also plays into the widespread public misperception that bicycling on sidewalks is safe. Some European designs are faulty, and this project in addition reflects a poor imitation of European practice. It will create a situation far worse than possible alternatives, and a perception of safety without really increasing safety. That is not positive innovation.

I (Jessica) am requesting meeting minutes and a copy of the flyer that was supposedly distributed around my neighborhood. I also ask why Massbike was not informed of the construction project.

If you would like, I can add your email to my public notification list; you can also check the progress of upcoming work at our website as well: http://www.cambridgema.gov/TheWorks/

Thank you again for your comments.  I will be sending out periodic construction updates at the work progresses.  If at any time you run into issues, feel free to contact me or Dan Vallee, project manager.

Sincerely,

Kelly

Kelly Dunn

Community Relations Manager

Cambridge Department of Public Works
147 Hampshire Street
Cambridge, MA 02139
T:  617.349.4870
F:  617.349.4814

kdunn *at* cambridgema *dot* gov

www.cambridgema.gov/theworks

[All contact information here is already available on the Internet; e-mail address has been altered to avoid contributing to harvesting by spam robots.]

« Newer Posts

Powered by WordPress