Skip to content

The Question

February 17, 2015

I’ve been struck by the way in which the coverage of the bus crash that seriously injured a teenager last Friday as she crossed the street with the legal right of way exposes a core philosophy of traffic violence apologists. This philosophy has mostly played out in Pete Donohue’s coverage in the Daily News, but it’s a common point of view anytime an incident like this becomes the subject of debate: Death and serious injury, it seems, are the cost of doing business in the big city.

J.P. Patafio of TWU Local 100 said, “The law of averages has it we’re going to get into an accident.” Donohue, arguing on Twitter, has essentially said the same thing. The occasional bus crash in which a pedestrian is maimed or killed is just an accident and not a crime, and not something that should concern the law in any meaningful way beyond, perhaps, a traffic ticket. Work it out in civil court if you want, but leave criminal charges out of it.

If you accept that philosophy — that in order to keep buses moving on New York City Streets people are going to die every once in a while — then you should have to answer a rather serious question:

If the occasional death or serious injury is the inevitable cost of keeping the city running, how many of your family members would you be willing to lose?

If we take this “law of averages” philosophy to its logical conclusion, then someone has to pay the ultimate price for the greater good. So who loses that lottery? Should it be you? One of your kids? How about a friend or coworker? Is it only okay if you don’t know the person? If you accept these as simply unpreventable accidents, then it’s on you to answer whose death is worth it and how many people have to be hurt.

It’s easy to dismiss street safety advocates as “a zealous bunch of bicycling advocates,” but they’re not the ones saying that keeping the economy humming and the traffic flowing requires some sort of burnt offering to the gods of mobility.

Right on Green, Part 1

February 9, 2015

First, a disclaimer: I sometimes go through red lights. Shocking, I know.

But a couple of points to tease out the details of that disclaimer:

1. I believe that laws for bikes need to be updated to reflect the fact that they are not cars, that resources ought to be deployed according to the threat, and that infrastructure — not punitive enforcement — will ultimately change behavior. But going through a red signal is still illegal, so that’s that. If I ever go through a red light and am stopped by the police, I’ll say I’m sorry, accept a ticket without argument, and pay the fine promptly.  I also have no desire to be one of those entitled cyclists who thinks it’s a massive injustice that he got caught doing something that everyone knows is illegal. My face on a Gothamist post with 816 comments? I’ll pass.

2. Although I occasionally go through red lights, I most certainly would never knowingly do so in the presence of a police car, no matter how safe the intersection. I don’t have a lot of love for the 5th Precinct’s penchant for ticketing cyclists at low-stakes T intersections, but I also don’t have a lot of sympathy for cyclists who get caught there. It’s not as if the cops are hiding behind a bush.

3. I never run red lights on 5th Avenue in Park Slope. First, some of the cross streets are set in such a way that it’s hard to see around the corner. Second, it’s a busy, narrow street that’s teeming with cars, buses, delivery trucks, and people on foot and on bikes, making it a bad candidate for any sort of Idaho Stop Law treatment most times of the day. Third, as a stroller-pushing papa who frequently takes his kids around the neighborhood on foot, I know all too well the experience of having someone on a bike come at you even at a distance he or she thinks is safe. Do unto others and all that.

So please keep those things in mind as you read the rest of this post. Read them again every now and then if it helps. Now on with the show…

I received a ticket after making a right turn on a green light.

Now, the officer who ticketed me didn’t write me a ticket for that; he accused me of going straight through a red signal in flagrant violation of the law — and, as you’ll soon see, the rules of time and space — but the truth of the matter is that I made a right turn on a green light and then received a red light ticket from an officer from the 78th Precinct.

Here’s what happened.

On Friday, January 31st, 2014, I rode my daughter, as I did nearly every day last school year, from our old apartment on 4th Avenue and Baltic to her pre-K on Lincoln Place between 5th and 6th Avenue. Our ride took us up St. Johns place, right on 6th, and then about half way down Lincoln Place to pre-K. A classroom sign-in sheet has me walking in at 8:30 AM to leave her with her teachers. I kissed her goodbye, left the building, and hopped on my bike, taking off down Lincoln Place.

The light ahead was red and there were a few cars stopped waiting for it to change. The bike lane on Lincoln Place is on the left side of the street and I needed to turn right, so I merged behind a car and waited too. When the light changed, the cars began moving and I slowly turned right onto 5th Avenue. Here’s the route:


As I turned the corner, I saw flashing lights coming from a car parked against the flow of traffic on the east side of 5th Avenue. A woman with a bike was stopped next to the car, so I figured it was one of two things: an officer responding to a crash or a red-light ticket sting. I stopped, saw that the woman was okay, and took this picture:


5th Ave and Lincoln Place looking southbound.

If you follow me on Twitter, you’ll know that I frequently take pictures of cops ticketing cyclists. If you follow constitutional law, you’ll know that taking pictures of cops ticketing cyclists is not a reason for the cops to then pull you over. Nevertheless, I continued northbound on 5th toward Bergen Street to make my way to work. But then I heard it: “CYCLIST, PULL OVER.” Okay, I thought. Taking a picture of a police officer is not a crime and I’ve done nothing wrong. I stopped in front of Gorilla Coffee at Park Place and 5th Avenue, about four blocks from Lincoln Place.

The officer exited his car and demanded to see my ID. I initially refused, and instead demanded to know what the officer thought I had done. He once again demanded to see my ID. Once again, I refused. I can’t say that I was as cool or calm as I could have been, but I also know that the police can’t just stop a person and ask for identification without saying why. I refused again, and demanded to know what the officer thought I did. At this point he told me that he observed me running a red light and that he would arrest me if I did not provide him with my identification. I told him that I did not run a red light, but he said he saw me go straight through the light on 5th Avenue, which would have had me traveling from a direction from which it would have been impossible for me to travel, given the location of my daughter’s daycare and my normal route to work. Here’s what he said I did:


For orientation, the officer’s car was parked along the curb next to the Chase Bank on 5th Ave when he said he saw me riding northbound on 5th before going straight through a steady red signal. Never mind that he was alone and occupied with ticketing another person on a bike, he said he saw me go through a red light. I pointed to my bicycle –a big, upright black Dutch bike with child seat in the back  — and said that he most certainly did not see me run a red light, since I had just dropped my daughter off on Lincoln Place.

At that point, the officer said that the woman he had been ticketing back at Lincoln Place told him that I had run the same red she did. I found this hard to believe, since, in case you’re just joining me, I DIDN’T RUN A RED LIGHT. She might have run a red light while going northbound on 5th Avenue, but I didn’t, nor could I have.  I told the officer that he wasn’t telling the truth. He said that he was. I then told him that for all I knew the woman was just intimidated and told him what he wanted to hear.

I want to be pretty clear here: I probably came across to this officer as a total asshole, that same kind of entitled cyclist I wrote about in my disclaimer, above. Stopped and threatened with arrest for not providing an ID and for running a red light I didn’t run? I never swore or lost my temper, but I definitely gave this officer a piece of my mind. I also must recognize the privilege aspect of this: I’m a white male who was stopped in Park Slope. Yelling at a cop and not immediately complying with an order isn’t probably going to land me in cuffs, at least not right out of the gate, so every choice I made was filtered through that knowledge.

At that moment, the woman who he had been ticketing back at Lincoln Place rode by on her bike. She had a striped scarf on, which you can kind of see in the picture above. The officer pointed at me and yelled to her, “Did he run a red light?” The woman, just as she passed, screamed, “NO!”

It didn’t matter. He demanded to see my ID again. Finally, I complied. I was no dummy. This cop wanted to write me a ticket, and I knew I’d have to make my case in court. I also didn’t want to wind up in jail; knowledge of the law and one’s rights can be cold comfort if you’re arrested by a cop who somehow thinks you did something you couldn’t have done. So I handed the cop my ID and he went back to his car. He returned with a ticket:


As you can see, the ticket says that I was going “N/B on 5th Ave @ Lincoln Place.” Just a quick reminder: I was going westbound on Lincoln Place, before turning right onto 5th and the light was green. The time written on the ticket is 8:44 AM. This is my first ticket in 17 years of riding a bicycle in New York City, and it’s for something I didn’t even do.

Anyway, both the officer and I parted ways. I headed to work, as I often do, via the Manhattan Bridge. As I arrived on the Manhattan side, I saw the Transportation Alternatives bike ambassadors doing one of their outreach sessions, giving out coffee and signing up new members. I stopped and told Luke, one of the ambassadors and now TA’s Brooklyn Outreach Coordinator, about my ticket. “A woman just came through here and signed up for membership because she said she had been ticketed, too,” he said. “Must have been the same officer.” I asked if this woman was wearing a dark jacket and a long striped scarf. Luke said yes.

So my wheels started spinning. Realizing TA couldn’t violate this woman’s privacy by giving me her contact information, I asked Luke if he would do me a favor and give her mine. He said that he would email her when he got to the office.

The next day, I got this email from the woman in the striped scarf, the one who had screamed “NO” when the officer asked her if I had run a red light:

Hi Doug,

Luke from TA forwarded your contact info yesterday. I was ticketed yesterday morning while riding up Fifth Avenue (at Lincoln Place). A number of cyclists passed while I was being written up and the officer caught one right behind me but not others.
The same officer continued north and I passed him talking to a cyclist outside of Gorilla Coffee. I’m sorry if that was you and if I had anything to do with your ticket. I did say aloud that you didn’t run a red light. I had a green and white striped scarf.
Good luck.
I wrote back and told her the circumstances of my ticket. It most certainly was not her fault. Here is part of her follow-up:

Hi Doug,

In your case, the officer was sitting in his car facing me or south when you rode by. He only saw you bike by; he didn’t see you run the red. However, because the light on Fifth Ave was red, he inferred that you ran the red, since myself and two other subsequent cyclists did exactly that.
I’m disappointed that he would write you a ticket that isn’t based on his own observations; this seems very wrong and also embarrassing. I can’t imagine a police officer backing down to admit fault so I would be happy to testify for your case.
As for me, I told him I left my wallet at home and didn’t have identification on me. He threatened to arrest me for not having ID, and I ended up showing him a photograph of my passport that was stored on my phone. Could you ask your attorney & TA volunteer whether a ticket without driver’s license is valid? I was told that it couldn’t be entered in the system; it does have my name and address however. I’m grateful for any response.
I forwarded her some names and contacts and thanked her for her help. Not too long after that, I submitted a plea of not guilty to the DMV.
In Part 2, I’ll pick up the story where it continues, one year later. Yes, one year later.

The De-Evolution of a DOT Slow Zone in Three Easy Steps

February 5, 2015

If culture eats policy for breakfast, what does this example of DOT policy do to the culture of reckless driving?

As Brad Aaron at Streetsblog reported, the Department of Transportation has “DOT has watered down some Slow Zone features,” partly in response to complaints about losing a handful of parking spaces and also as a result of Slow Zone signs being “hit and damaged at an unsustainable rate.” A robust gateway treatment is essentially the defining feature that is meant to a) distinguish a “Slow Zone” from a neighboring “Do Whatever You Want Zone” and b) slow down drivers as they turn corners. Remove the gateway treatment and, lacking other traffic calming features such as chicanes, the Slow Zone is more of a Suggestion Zone. If drivers even see the sign, that is.

Here’s an example from Union and Bond Street in Brooklyn. This is the Slow Zone gateway as it existed in October 2013:


Here it is in August 2014. It’s clearly been hit by a driver:


And here’s that same “gateway” in October 2014:


Basically, in the span of just one year, DOT gave up. That says something about its institutional culture, doesn’t it? But scroll back up through this post again. If you start in October 2014 with the sign on the sidewalk and end with the sign in the street, that’s the progression you’d want to see as far gateway design is concerned. And once that sign has been planted in the street, like a settler’s flag claiming land for the Kingdom of Pedestrians, you’d want to start moving toward a gateway design that looks something like this:


Design eats culture for breakfast.

Culture. Policy. Breakfast.

January 19, 2015

If you paid attention to the coverage of Vision Zero in 2014, you may have noticed one of DOT commissioner Polly Trottenberg’s most frequent refrains:

“One of my favorite lines comes from the former DOT commissioner from Massachusetts: ‘Culture eats policy for breakfast,’” said Transportation Commissioner Polly Trottenberg, “Culture is much more. You can change policy overnight. You can’t change culture overnight.”

Here it is again, in a different interview:

“Culture eats policy for breakfast,” said Trottenberg. “That’s one of my mantras in this business … meaning you can change policy, but culture is a more complex thing to change, and something that often takes more time and more effort.”

The phrase “Culture eats policy for breakfast” traces its roots to Peter Drucker, an influential Austrian-born business management consultant and author who died in 2005. Drucker actually said, “Culture eats strategy for breakfast, technology for lunch, and products for dinner, and soon thereafter everything else too” but that lengthy quote has been adapted and simplified as it’s flown around the corporate world.

In any company, organization, or even social movement, there’s always a conflict between those who would implement sweeping change quickly and those who feel that a piecemeal, step-by-step approach is more prudent. If you’re the head of a large city agency with a direct impact on the lives of millions of citizens, striking a balance between these two competing philosophies is key, lest big and noble policy goals get destroyed by something as simple as bad timing or a small group of people who simply aren’t ready to change.

But something always rubs me the wrong way anytime I hear Commissioner Trottenberg repeat her line about culture, policy and breakfast. When I match it up against the absence of truly innovative and original bicycle projects from DOT in 2014 — most of the protected bike lanes installed last year originated under the Bloomberg administration — it seems that what should just be a catchy piece of business advice may actually be a core philosophy that’s holding the city back from taking biking to the next level. “Culture eats policy for breakfast” has become a self-perpetuating, defeatist mantra that ignores how far the city has come, where it wants to go, and who wants to take it there. It removes design and engineering as primary drivers of cultural change, defers too much to those who seek a kind of selfish comfort in the status quo, and has consequences for other important policy goals beyond bikes.

Here are what I see as the biggest problems with “Culture eats policy for breakfast.”

1. The last administration changed the menu. 

In the waning months of Mayor Bloomberg’s final term, an August 2013 New York Times poll showed widespread support for bike lanes, bike share, and pedestrian plazas.

Image via NY Times.

Image via NY Times.

Even as far back as March 2011 — the same month Neighbors for Better Bike lanes filed their Article 78 lawsuit to remove the Prospect Park West Bike lane — a Quinnipiac poll showed that 54 percent of New York City voters viewed the expansion of bike lanes as “a good thing.” By July that number had risen to 59 percent. In August, a Marist poll showed 66 percent of New Yorkers supported bike lanes. Again, this was in 2011, when New York Magazine asked “Is New York Too New York for Bike Lanes?”

The New York Times poll proved what many advocates and policy leaders had long known, that the media-generated bikelash that had dominated the headlines for years never matched the reality on the ground. “People are voting with their feet, they’re voting with their pedals, and they’re voting with their dollars,” former DOT commissioner Janette Sadik-Khan was fond of saying. Howard Wolfson, who had long gone to the mat for the Bloomberg administration’s livable streets agenda, gave this valedictory comment late last year: “At some point it became obvious that this was a popular policy, that people were using bike lanes, that Citi Bike was being used. (Emphasis mine.)

“Culture eats policy for breakfast” takes the momentum accrued under Bloomberg and runs the risk of squandering it. The language accepts the idea that popular policies are still up for debate. Even worse, it reintroduces a debate that was settled a long time ago.

2. There’s more than one way to define culture.

Consider the following quote from DOT Director of Bicycle and Pedestrian Programs Josh Benson about the agency’s choice to install extra-wide parking lanes on streets with more than enough room to accommodate robust bicycle infrastructure:

People in the community might not initially value the importance of a street to the bike network until there’s some initial calming and the character changes,” DOT Director of Bicycle and Pedestrian Programs Josh Benson said, citing Vanderbilt Avenue in Prospect Heights and 44th Drive in Long Island City as examples where DOT later converted extra-wide parking lanes into bike lanes. “People don’t necessarily envision a street as a bike-friendly street,” he said. “Once you make an improvement, people take to it and opinions change.”

Riverside Drive, for example, is a major cycling route both for points along the Upper West Side and for recreational cyclists heading to the George Washington Bridge. Safe streets advocates have been packing community board meetings on the Upper West Side on all manner of traffic-calming and bike-related projects for months, oftentimes outnumbering opponents by a lot. So who is Benson talking about? Not that one should ignore people in the local community who can’t or don’t want to envision the benefits of a complete street, but incorrectly or imprecisely defining words like “culture,” “people,” and “community” fuels a myth that New York still isn’t ready for bike lanes. It makes “Culture eats policy for breakfast” a self-fulfilling philosophy.

3. It diminishes the importance of past institutional experience.

The Vanderbilt Avenue traffic calming project mentioned by Benson above began with the installation of wide parking lanes in 2006 before an upgrade to class 2 bike lanes in 2008. With everything that’s changed since 2006 — The Ninth Avenue bike lane, the city’s first on-street protected lane, wasn’t installed until 2007, for example — the interim step of installing wide parking lanes to build community acceptance for bike lanes may no longer be necessary. After all, none of the doom-and-gloom predictions that preceded previous bike lane installations came to pass, so DOT should by now be well versed in swatting down most community board complaints, including those related to the loss of parking. (More on that later.)

4. It removes DOT as a prime agent for rapid culture change.

It’s said that writing about music is like dancing about architecture. The same might be said of livable streets. Endless community board presentations and tabloid arguments about whether or not New Yorkers will sit and enjoy themselves in pedestrian plazas tend to yield diminishing returns. Instead, the debate can easily be settled by setting up some traffic cones and buying cheap lawn chairs at a hardware store. As former DOT policy director Jon Orcutt recently tweeted, “If your policy changes infrastructure, it will change culture.”

5. It fails to fully seize the moral imperative behind Vision Zero as a catalyst for change.

Some cities justify the expansion of their bike lane network because it will attract young tech workers and help the economy. Fairly or not, many people only thought that Bloomberg and Sadik-Khan wanted New York City to be like Copenhagen. Not that these are bad reasons to build bike infrastructure, but they’re unlikely to satisfy longtime residents who think that young hipsters are coming with their bikes to take away parking spaces.

Vision Zero, on the other hand, arms DOT with a very powerful justification for reconfiguring streets. Ending all fatalities and serious injuries must trump petty concerns about small amounts of free parking spaces.

Of course, Families for Safe Streets has fully seized this mantle, changing the conversation and earning a marathon-like victory to lower to the default New York City speed limit to 25 mph. But Families for Safe Streets can’t fight every fight, especially since they have their eyes trained on some pretty big fish this year. It’s going to be up to DOT to explain at the community board level why some concerns simply don’t warrant serious consideration in light of the moral urgency of Vision Zero.

6. There are consequences to waiting for the culture to change. 

The most obvious consequence of deferring too much to some notion of a change-resistant culture is that people will die. While we’re waiting for “the community” to get used to seeing Riverside Drive as a part of the bike network, people on bikes are still using it, more exposed than they need to be.

There are other consequences, some small, some big. The mayor has set a goal of 6 percent mode share for bikes by 2020, just five years from now. It won’t be achieved with extra-wide parking lanes. And if the city can’t touch parking to stop people from dying or get more people on bikes, then good luck removing all the spots needed to install a real bus rapid transit line.

* * *

“Culture eats policy for breakfast” does not and should not mean that one drifts in the tides of culture, waiting the for the currents to change. I don’t think Trottenberg sees it that way either, and it was certainly important to concentrate her department’s efforts on the speed limit change and the arterial slow zone program, but it doesn’t follow that bikes needed to get the short shrift as they did in 2014. DOT needs to use its power for positive change as well as the moral imperative of Vision Zero to demonstrate that there is no daylight between pedestrian safety projects and bike safety projects. One contributes to the other.

As I mentioned at the top of this post, “Culture eats policy for breakfast” originated in the business world, so I thought I’d turn to the business world for a deeper look. Here’s Bill Aulet, director of the Martin Trust Center for MIT Entrepreneurship and a senior lecturer at the MIT Sloan School of Management, writing at Techcrunch:

Some may believe that culture cannot be “engineered,” and that it just happens. It is true that culture happens whether you want it to or not. It is the DNA of the company and is in large part created by the founders – not by their words so much as their actions. So the very decision to not try to create a corporate culture, or worse, to not have company values, is in fact your choice of what culture will prevail – and not for the better. 

“Culture eats policy for breakfast” is not a philosophy. It’s an observation. It’s advice, and, applied correctly, fairly good advice at that. But if it’s allowed to be the guiding principle by which DOT operates, then eliminating all traffic deaths by 2024 — just nine (!) years from now — won’t happen. Remember John F. Kennedy’s 1962 announcement that the United States would put a man on the moon by the end of the decade? And remember how we did just that in 1969? It took boldness, experimentation, money, and manpower. Vision Zero needs to be like the Apollo program, but for streets.

“Breaking a bike is easy…”

January 8, 2015


Vélib’, the bike share system of Paris, will display this message at all of its 1,800 stations today. My French is terrible, but the caption for the cartoon on the right translates to, “Breaking a Vélib’ is easy…he can not defend himself.” The cartoon is by Jean Cabut, known by his pen-name of Cabu, who was one of the victims in yesterday’s attack on Charlie Hebdo.

It’s not for nothing that Vélib’ gets its names for the French words “vélo” and “liberté” – “bicycle” and “freedom.”

Thank You

December 29, 2014

2014 has been a pretty good year as far as livable streets in New York City go, most notably with the reduction of the city’s default speed limit to 25 mph. It’s a huge step in the right direction, a major victory for Families for Safe Streets, and a sign of good things to come.

This past year was also an interesting year for me here on the blog and off of it. I was privileged to meet so many loyal readers in the flesh at various events and, much to my delight, every now and then during my rides to and from work. I truly appreciate everyone’s comments, criticism, tips, and friendly hellos.

For the curious – or in case you missed them – here are my three most popular posts of 2014:

I’ll take that as advice for 2015 – apparently my readers like pictures of cute kids on bikes and long posts involving media criticism.

As this year ends, I’d be remiss if I didn’t put in a plug for the organizations that are working to make a safer city and that serve as my inspiration in so many ways. If you’re still looking to make a year-end charitable donation, the wonderful folks at Streetsblog and Streetfilms as well as Transportation Alternatives will put your money to good use. With all that we have left to do to advance Vision Zero and make a better New York City, I hope you’ll give them your support.

Have a safe and happy New Year.

The Critic

December 10, 2014

Brad Aaron at Streetsblog has an excellent takedown of the new victim-blaming public service campaign from the MTA. While I’m a safe streets advocate and agree with Brad’s criticisms, my initial reaction to the PSAs was largely filtered through my professional experience as a TV producer and writer.  My day job involves looking at images, writing words, and making sure that those two things add up into one coherent narrative. So when I saw “Cycling for Trouble,” a new bike safety public service announcement from the MTA, the first things I noticed were the glaring inconsistencies, ridiculous images, and downright incorrect information in its brief thirty seconds.

The ad begins with a young man getting ready for his ride. First he puts on gloves:


Note: gloves are not required when riding a bicycle in New York City. Yet.

Then he puts on his helmet:


Note: a helmet is not required for adults when riding a bicycle in New York City. Yet.

Then he makes sure his bike has tires:


Note: although not legally required, a bicycle equipped with tires is highly recommended.

Then he puts on his headphones and goes for a ride:


Look, I agree. Wearing headphones in both ears while riding a bike is Not a Good Idea… if you’re riding in the heart of Midtown, on Jay Street in Brooklyn, on in any other very congested part of the city. (Having an earbud in one ear is perfectly legal, however.) But on a pathway along an empty beach? Really? Is this the most effective visual way to convey that wearing headphones isn’t the smartest thing in the world? So even before the central message of this PSA has a chance to really get out there, any skeptic who stops to process this image – that is to say, any New Yorker – is likely to be taken out of the moment entirely.

Then there’s this mini-scene, where the guy slowly coasts through a quiet park – another place where wearing headphones isn’t really all that bad – as he points to perhaps to a pal or just someone he wants to notice him:


That’s quickly followed by this image:


The sequence above is very strange: A man who methodically prepares for his ride by putting on gloves, strapping on a helmet, and making sure his bike has tires suddenly morphs into a cocky-yet-clownish character from a bad comedy video? It’s just dumb and not very well thought out.

Then the man takes to the street where bouncing bold graphics tell us what he is listening to:


This, of course, is a total surprise if you can’t hear the techno-inspired beat that begins playing the moment the man puts on his headphones. It’s just so strange. Would listening to Serial or WFAN at a low volume be “Not Good”?


Anyway, apparently the music is so loud that it causes the man to go blind, since he crashes into the same bus that’s been right in front of him for at least a block:

This is just dumb on top of dumb, and makes me suspect that no one familiar with biking in New York City, or even bicycles in general, was involved in this spot’s production. Part of the reason wearing headphones in both ears isn’t a good idea is because it makes it harder to hear cars or other cyclists approaching from behind you. On the Manhattan Bridge, what bike commuter hasn’t been stuck behind a person huffing up the incline with a set of earbuds wedged into his noggin? There’s no amount of bell ringing or “On your left” loud enough to get that guy to hear you and move over, so you’re more or less screwed until Canal Street. But its pretty rare that I see an earbud-wearing cyclist coming from the opposite direction on the bridge and think, “I better be careful. That guy who clearly has me in his line of sight can’t hear me.”

Oh, and another thing: there hasn’t been a documented case of a headphone-wearing cyclist rear-ending a bus, at least not one resulting in serious injury or death. Believe me, if an idiot died doing something like this, it would be on the cover of the Post for a week. And that’s perhaps the biggest failure of this spot: in presenting a situation so unlikely it’s less common that getting killed by a falling air conditioner after being knocked over by an exploding Mister Softee truck, the message gets totally lost and subjects the entire piece to the wrath of Gothamist. Even WNYC got in on the act. That’s probably not the outcome the MTA expected when the idea for this PSA began.

Then there’s this image and catchphrase at the end of the spot:


I guess “Stay alert. Don’t crush bicyclists and pedestrians with your multi-ton vehicle” doesn’t have quite the same ring to it.


Get every new post delivered to your Inbox.

Join 105 other followers