Cambridge Civic Journal Forum

December 19, 2012

City of Cambridge Seeks Members for Three Transportation Advisory Committees

Filed under: Cambridge,transportation — Tags: , — Robert Winters @ 2:13 pm

CITY OF CAMBRIDGE SOLICITING MEMBERSHIP APPLICATIONS
FOR THREE TRANSPORTATION ADVISORY COMMITEES

Application deadline is Friday, January 11.

BICYCLE COMMITTEE
This committee works to improve conditions for bicyclists in the City of Cambridge and promote bicycling as a means of transportation. Activities include organizing and participating in public events such as biannual community bike rides; reviewing plans for road construction; commenting on proposed development projects; creating promotional materials to encourage bicycling in the city; and working with City departments on network planning. This committee generally meets on the second Wednesday of each month from 5:30–7:30pm at City Hall Annex, 344 Broadway.

PEDESTRIAN COMMITTEE
This committee works to promote walking and to help create a more comfortable, safe, and pleasant environment for walking in Cambridge. It advises on the design of roadway projects and policies related to traffic calming, traffic signals, and sidewalk design. It also identifies intersections and other locations where it is difficult to walk, makes suggestions about proposed development projects as they affect people on foot, and undertakes other activities to promote walking. This committee generally meets on the fourth Thursday of each month from 6:00–8:00pm at City Hall Annex, 344 Broadway. (November and December meetings are on the third Thursday.)

PUBLIC TRANSPORTATION COMMITTEE
This newly established committee will advance an agenda for a robust public transportation system for those who live and/or work in Cambridge. The committee will be composed of a cross section of stakeholders including businesses, large institutions, commuters, persons with disabilities, low income, elderly, youth, students, and advocates. The committee will guide city positions and policies regarding long term sustainable funding for transit by the Commonwealth, service planning for expansion or modification of bus routes, and service reliability and improvements including ways to better design our street network to prioritize bus transit. This committee will generally meet on the first Wednesday of each month from 5:30–7:30pm at City Hall Annex, 344 Broadway beginning in 2013.

Beginning in 2013, in place of individual committee meetings, these three committees will meet jointly on occasion to advise the city on higher level sustainable transportation policy.

APPLY
Applications are sought by dedicated individuals who live or work in Cambridge. Members are expected to attend monthly meetings as well as engage in projects outside of regular meetings. To apply, please prepare a cover letter indicating which committee you are interested in, a description of your interest in the topic, and any specific issues you would like to contribute time to working on. Please be sure to include your mailing address, phone number, and email. Send to:

Robert W. Healy, City Manager
c/o Jane Maguire,
Community Development Department
344 Broadway, Cambridge, MA 02139
Email: jmaguire@cambridgema.gov

Application deadline is Friday, January 11.

Appointments are made by the City Manager and are for two years of service. For more information, call 617-349-4610.

December 3, 2012

Enjoying? the Concord Avenue “raised bike lanes”

The Cambridge City Council meeting on December 3, 2012 is to address issues of debris on the Concord Avenue “raised bike lanes”. These replaced conventional bike lanes at street level. I put the term “raised bike lanes” in quotes because a bikeway behind a curb is not a bike lane. By definition, a lane is at street level, so it is possible to merge to and from other lanes. Rather, this is a nonstandard bicycle path.

This post supplements comments which I posted on my own blog before Concord Avenue was reconstructed. The photos here are stills from video shot during a ride westbound at mid-day on November 20, 2012, with moderate motor traffic and very light bicycle traffic.

First photo: Crosswalk just west of the Alewife Brook Parkway rotary is backing up motor traffic. This already generates traffic jams with light bicycle traffic. The City expects the bikeways to attract more cyclists and to lead to a major increase in bicycle traffic.

Crosswalk backs up traffic on Concord Avenue

Crosswalk backs up traffic on Concord Avenue

Next photo: The westbound bikeway crosses 8 streets and 24 driveways in 3000 feet. The most persistent hazard on the westbound bikeway is of “right hook” and “left cross” collisions. The van in the photo not only is turning across the bikeway; it also might be hiding another vehicle preparing a left turn from ahead. The bikeway places bicyclists where they are defenseless against these threats. I say more about them, and how to avoid them, in my earlier blog post.

Right hook and left cross threat on Concord Avenue bikeway

Right hook and left cross threat on Concord Avenue bikeway

Next — bus stop. When the bike lanes were at street level, bicyclists could pass a stopped bus on the left, or wait behind it. Motorists also usually could pass a stopped bus. Passing would have been even easier with bus turnouts on the westbound side, where there is only one travel lane. Now that the roadway has instead been narrowed, converting the conventional bike lanes into “raised bike lanes”, buses must completely block the travel lane, and passengers getting off a bus step down directly into the path of bicyclists. A 2007 research study in Copenhagen showed an increase in bicyclist-pedestrian collisions of 17 times, and of injuries of 19 times, when bus stops were placed outside bikeways like this. More about that study.

Bus stop on Concord Avenue, with green paint

Bus stop on Concord Avenue, with green paint

That study was published well before construction on the Concord Avenue bikeway began. Not only that, the City’s bicycle coordinator repeatedly points to Copenhagen as a model of what Cambridge should do.

To resolve conflicts between bicyclists and passengers descending from buses, the City first painted bicycle markings. Those markings, however, suggest that bicyclists have priority, and these markings also may not be directly in front of a bus’s door when it opens, to warn the passengers. At some later time, green carpet painting was added. This is normally used to indicate where motorists yield to bicyclists (see Federal Highway Administration interim approval), but here it is intended to indicate where bicyclists must yield to pedestrians, a confused and contradictory message. This bus stop is at a driveway. Traffic has worn away some of the green paint and you can see the bicycle marking which was painted over.

Bicycle marking under green paint at bus stop on Concord Avenue

Bicycle marking under green paint at bus stop on Concord Avenue

One problem to be discussed at the City Council meeting is that snow clearance is not practical on the westbound bikeway, because of its repeated ups and downs. Ice also puddles there. Here’s a photo from another blogger, dr2chase, showing winter conditions on the westbound bikeway. dr2chase’s blog has many more photos.

dr2chase's photo of winter conditions on the Concord Avenue bikeway westbound

dr2chase’s photo of winter conditions on the Concord Avenue bikeway westbound

dr2chase also has made the point that snow clearance is much more practical on the eastbound bikeway, which has only one driveway entrance in its entire length. Here is his photo illustrating that:

drchase's photo of the eastbound bikeway in winter

drchase’s photo of the eastbound bikeway in winter

The bikeway on each side is designated as one-way. People are likely to use both of them for two-way travel, and not only in snow season, because a cyclist must stand in the street to lift the bicycle over the curb of the eastbound bikeway at most locations. Also note the seam between asphalt and concrete running down the middle of the photo above. It is intended to separate bicyclists from pedestrians. It won’t, especially with two-way bicycling, and over the years, it will deteriorate so it traps bicycle wheels. dr2chase and I have both made the point that a properly-designed, designated two-way bikeway on the south side of Concord Avenue, adjacent to Fresh Pond Park, would have made good sense, connecting with the existing bikeways in the park and crossing only one driveway in its entire length — at a signalized intersection. I also would have liked to keep the street at its previous width, with street-level bike lanes, to allow efficient through travel and make it possible to reach the eastbound bikeway without lifting a bicycle over a curb.

The next photo illustrates the crossing-the-street issue. Note the driveway at the right rear, and that there is no break in the curb on the far side of Concord Avenue. To cross without stopping in the street, and to avoid having to double back, cyclists will most likely ride eastbound in the westbound bikeway. That is illegal and hazardous: motorists pulling out of side streets and driveways look in the opposite direction for traffic.

The mailbox adjacent to the 5-foot-wide bikeway adds a nice touch as well. Nick it with your handlebar, and you go down hard. Even without such obstructions, 5 feet is minimal for one-way travel. This mailbox is one of a large number of fixed-object hazards adjacent to the bikeway.

Mailbox, and curb on far side of Concord Avenue

Mailbox, and curb on far side of Concord Avenue

Not all hazards are fixed-object hazards. There are these trash barrels.

Trash barrels on westbound bikeway on Concord Avenue

Trash barrels on westbound bikeway on Concord Avenue

Behind the trash barrels, you may have noticed a car discharging passengers. A cyclist who regularly rides Concord Avenue reports that delivery vehicles also now stop in the bikeway.

Car stops in bikeway to discharge passengers, on Concord Avenue

Car stops in bikeway to discharge passengers, on Concord Avenue

My next photos show what I call the X-merge, or double-cross merge.

Normal traffic law requires a driver to maintain a constant lane position when another driver is overtaking. Here’s an excerpt from the Massachusetts law:

Except as herein otherwise provided, the driver of a vehicle passing another vehicle traveling in the same direction shall drive a safe distance to the left of such other vehicle and shall not return to the right until safely clear of the overtaken vehicle; and, if the way is of sufficient width for the two vehicles to pass, the driver of the leading one shall not unnecessarily obstruct the other.

Bicyclists may overtake on the right, according to another section of the law:

…the bicycle operator may keep to the right when passing a motor vehicle which is moving in the travel lane of the way…

When a bicyclist is directed to merge from right to left at an arbitrary location, and a motorist to merge from left to right at the same location, they are both violating the law. Green paint here is used to direct cyclists and motorists to operate illegally.

X-merge on Concord Avenue

X-merge on Concord Avenue

I avoided right-hook threats by merging in behind the stopped car so the next vehicle turning right could safely pass me on the right.

Avoiding the X-merge on Concord Avenue

Avoiding the X-merge on Concord Avenue

Before Blanchard Road, a traffic island narrows the roadway. The bike lane, between the through travel lane and right turn lane, is too narrow to allow safe clearance on both sides. Note in the photo below that the narrow median on the far side of Blanchard Road allows much more room to the left of the bike lane. The traffic island predates the reconstruction: the bike lane has been shoehorned in by narrowing the other lanes. Concord Avenue is wide enough to accommodate turning traffic without the island’s being so wide.

Wide traffic island at Blanchard Road narrows bike lane on Concord Avenue

Wide traffic island at Blanchard Road narrows bike lane on Concord Avenue

Well, enough. You get the idea. I’ll finish with a couple of quotes. Here’s one from MarkS, commenting on dr2chase’s blog post:

I don’t know why they wasted the time and money to put these tracks in in the first place. I find a bike lane much more convenient, and in some ways safer — clearly safer than that abomination on the north side of Concord Ave — the “outgoing” side. And, if ever we decide to re-design the situation, the expense of doing so will be significantly — and that’s an understatement — more than it would be to just re-paint the lines where the bike lane would have been.

Here’s another quote, from dr2chase:

…the west-bound side is about the most ineffective botch I have ever seen. But the eastbound side is quite nice (with the exception of the scary-high curbs). One extremely-low-traffic intersection, no driveways, hence none of those risks, and so wide that (with current bike/ped traffic levels) there is little harm in riding the wrong way on the good side. Technically illegal, but vastly safer, and I cannot fault someone for making the safer choice.

I agree! And have a look at the video online!

Save

Save

Save

November 14, 2012

Cycle track disease is contagious!

It crosses over from Cambridge to hit the slippery slope (literally) in Somerville.

Please see my extended comments here: http://john-s-allen.com/blog/?p=4862

July 27, 2012

City Council to discuss last December’s fatal bicycle crash

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

(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

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

May 4, 2010

“Urban Revolutions” event at MIT

What follows here is a very long post, but Robert Winters has given me a free rein. I haven’t seen any other news coverage of the “Urban Revolutions” event, so here goes. Despite its length, this is not a transcript — though I quote the speakers liberally, I have summarized much of the session. If you see a “more” prompt just below, click on it so see the rest of my account. Thanks Robert!
(more…)

« Newer Posts

Powered by WordPress