Because that’s where the media looks. Fame and money. Runaway juries. That’s what gets the clicks.
Except that this jury was a runaway. It just ran away in favor of a defendant car driver and awarded zippy-do-da to the injured plaintiff. Ergo, no story, or at least no story that gets clicks.
Out of the Appellate Division (4th Department) comes a decision reversing a jury verdict in favor of the defendant.
The facts were simple: A car turned left in front of a motorcycle. The kind of turn you teach your children to fear when they learn to drive. You don’t want to involved in a t-bone. From any perspective. And certainly not from the perspective of a motorcycle.
The view of the turning driver was unobstructed and there was a clear line of sight. The driver admitted at trial that he “never saw the plaintiff or his motorcycle prior to the accident.” There was, in other words, no reason not to “see what what there to be seen.”
The jury, inexplicably, came back with a defense verdict. Maybe they hated lawyers. Maybe they hated lawsuits. Maybe the judge gave them the case late Friday afternoon and they wanted to get the hell out of the courthouse. Maybe they hated the plaintiff or hated motorcycles or hated the lunch that the court officers served to them. Maybe a million things.
Juries are funny that way. They don’t always do that which seems abundantly obvious. They engage in jury nullification, ignoring the law, or simply not listening to the law, or not caring because they have other agendas.
Some auto cases are straightforward. Like a hit in the rear. Or, in this instance, a left turn case.
The trial judge should have tossed the verdict out as against the weight of the evidence. That didn’t happen. So the appellate division did it.
Reversed, as the jury finding “that defendant was not negligent could not have been reached on any fair interpretation of the evidence.”
It’s a tough standard to meet. But the facts as laid out by the Fourth Department make it look like a no-brainer. The case, decided last week, is Cramer v. Schruefer. A new trial was ordered.
Harvard Law introduced today something called the Caselaw Access Project. All they did was take 360 years worth of American jurisprudence until 2018 and make it easily searchable by terms. Then you can see trends.
Our scope includes all state courts, federal courts, and territorial courts for American Samoa, Dakota Territory, Guam, Native American Courts, Navajo Nation, and the Northern Mariana Islands. Our earliest case is from 1658, and our most recent cases are from 2018.
Just that. Pretty cool, right?
Given all the noise that gets made in the press about personal injury cases I decided to pop the phrase “personal injury” into the search bar to see how much of an impact my little corner of the law is having on the courts.
Two fast observations: First, as you can see from this graph for the years 1900-2019, the number of personal injury cases has been plummeting for the past 20 years:
On the vertical axis to the left is the overall percent of cases in which the term comes up. On the bottom horizontal axis are the years, and you can set whatever years you want in order to find the trends. I used 1900 as my start date because I’m a sucker for round numbers. You can noodle with it and pick other years if you like.
When you go to the live site you get more data than mere screen grabs and can fine tune a bit. And for this we find that the peak year was 1996 when the term was mentioned in 3.4% of the cases. And that was at the peak.
Currently, personal injury is mentioned in just 1.9% of cases, a stunning drop of 44% in just 23 years.
You can also, if you like, look at the data in absolute numbers as opposed to percentages. You’ll find a similar drop looking at it that way.
The drop is even more stunning when you use the word negligence (which obviously would be used more often due to a greater variety of circumstances). This time I ran the chart from 1800 until today so that you see an even longer term trend, from 14% to 6.4%, with peak use of the word in 1907:
What are the reasons for the drop? I’ll probably write more on that another day. But safer products, safer cars and safety laws such as mandatory seatbelts are likely to be contributing factors.
One more graph for you, this showing how the number of injuries from car collision has also dropped — from its peak also in 1996. This from the National Highway Transportation Board:
Expect a wealth of analysis to come out of this new website as policy wonks look more intensely as to the trends in our courts. It would be easy to spend hours looking at this stuff. I spent only 30 minutes, but will return.
Quick pro tip for law students: Don’t go into personal injury law.
It’s a funny place to find a story on personal injury law — inside the pages of Outside Magazine. But when a good point is made, it makes no difference where that point is found.
Outside gets involved because the article is called: How We Talk About Drivers Hitting Cyclists. It seems that bicycle riders aren’t too keen on getting hit by vehicles that are much bigger than they are, and getting squashed or worse. And so, an outdoors magazine hits a junction with personal injury law.
Their story starts with a triathlete out for a spin getting bounced off the grill of a Ford F-150 and soaring through the air to an unhappy landing that was, thankfully, survived, albeit with significant injuries.
But the story isn’t really about that one rider, or the many other bicycle riders that have been hit and injured or killed by cars and trucks.
The story is about how the media writes about those crashes, with the subtle (mis)use of language leading to a shifting of blame, or a minimizing of the significance on how the crash took place:
News stories often play a key role in shaping public understanding of traffic safety. And when news stories victim-blame or fail to convey the larger context in which these crashes take place, they do deep injustice to the victims and the conversation about road safety in general.
In the past, I’ve noted that the word “accident” is a poor language choice to describe a motor vehicle collision or other mishap, as that word is the same one used for a deer that bolts into the road. Why use the same word for an unavoidable crash as you would for one that is avoidable with reasonable care?
“And I think it’s part of this sort of blame-game society in the sense that it’s always got to be somebody’s fault instead of the fact that maybe sometimes accidents happen,”
Well, yeah. It wasn’t Mother Nature at fault there. It was humans. And the question was who to hold accountable for the disaster. That assumes, of course, that Senator Paul actually cared about accountability.
OK, I digressed. Let’s return to the unintentional biases of language that gets used to whitewash responsibility.
Outside writer Joe Lindsey breaks it down further that I simplistically had on prior occasions, with these points that come from two studies on the use of language in media:
Two new studies on inaccuracy and subtle bias in mainstream-media reporting about driver-cyclist crashes highlight the extent of these issues. What they show make clear just how deeply rooted the problem is—and how difficult it will be to fix.
Those studies fixed on three issues related to language: First, words that indicated whether the cyclist or the driver was assigned blame for the crash; Second, the use of passive, clinical language that reduced the human role; and Third, whether the stories framed the crash as a one-off episode or put in a larger context of road safety.
In reviewing 200 serious crashes, researchers found that in 80% of them, news writers described the main actor in the crash as a vehicle —- not as a person:
“Sometimes the story would say that the person was hit by a car, which is passive,” says Tara Goddard, an assistant professor of urban planning at Texas A&M, who was involved in the study. This language distances the driver’s actions from the crash.
Cars, of course, don’t generally get up out of the driveway on their own to run someone down. A driver needs to be involved.
And then there’s the use of the word “Accident.” The other of the two studies found that in 189 news reports of cyclist fatalities in crashes in a Florida county over a ten-year period, that “accident” appeared in 48 of them; another 12 used the word “incident.” In 55 of the stories, no mention was made of a human driver.
Of course, except for those cases where nature has intervened (the deer bolting into the road example) virtually every crash involves human error of some kind. But the stories, oft times, simply don’t reflect that.
And third, there was the victim blaming. While this may be an age-old staple of both criminal and civil defense trial lawyers, the objective media writer doesn’t stand in the shoes of an advocate.
Why, for example, would a news writer mention that a cyclist who was hit by a truck moving 60 mph note that the rider wasn’t wearing a helmet? It wouldn’t matter, so why skew the reader toward a narrative that is utterly irrelevant?
Presenting factoids, the Outside piece argues, takes the light off of significant safety factors (for example, road design) to make the crash seem like a one-off instead of part of a larger community safety problem.
The desperate need for speed in reporting these days, with news cycles that have evaporated, means that initial information (often from anonymous police sources) is often both wrong and repeated.
But the limitations and problems of the need to file stories quickly are, by now, well appreciated by the press. And it means that they need to be doubly careful in that choice of words: Careful that crashes are not downgraded to mere accidents; that drivers/riders are held to blame instead of vehicles; that collisions are seen within the broader context of community safety; and that victims are not chastised as blameworthy based solely on irrelevant factoids.
After seeing who was in the car, the original accident report (more properly called a collision report) was deep-sixed and the Pirro vehicle magically disappeared from the second accident report. The cops called the Harley rider a fraud and listed it as a one-vehicle accident.
Except that someone already had a copy of that first report, and the cops were caught covering up the crash.
Apparently, a car veered into his lane and hit the mayoral SUV. I say apparently because that was the lede in the story:
On a Saturday morning in August 2015, Mayor de Blasio was in the back seat of a black NYPD Chevy Tahoe bound for an event in Harlem when a driver changing lanes slammed into his ride.No one was hurt. No big deal, right?
Except that the police decided to cover it up. Instinct perhaps?
Back to the story:
No one was hurt, but the commanding officer of the mayor’s executive protection unit, Howard Redmond, was furious. Text messages obtained by the Daily News show he immediately ordered the incident be covered up to protect de Blasio’s image.
“As per CO [the commanding officer] no one is to know about this,” Sgt. Jerry Ioveno texted members of the unit, referring to Redmond. “Not even the other teams.”
“No one is to know,” he repeated.
Why this would reflect badly on the Mayor is beyond me, even if the Mayor’s driver was at fault. He, after all, was a passenger.
But the NYPD was worried about optics. If there are bad optics, then yeah, maybe it does reflect badly. On the NYPD. And its driver. If the NYPD driver was actually the one at fault.
But the story just gets weirder:
Redmond allegedly ordered that the cop behind the wheel, Detective Edgar Robles, be officially listed as the driver of a backup SUV, text messages show. That way, the unit could more plausibly claim the mayor wasn’t in the vehicle involved in the collision, a source close to the executive protection unit said.
Then, buried down further in the article, it hits: It was the NYPD at fault. Not the other driver:
NYPD spokesman Phil Walzak told The News that the NYPD investigated the accident involving de Blasio’s SUV “and determined the NYPD was at fault. Far from a coverup, this in fact shows the exact opposite – the NYPD took this incident seriously.”
The text messages are almost comical in their ham-handed way of covering up the crash — successfully for years. Some of the texts:
“Is Eagle p—-d?” Ioveno asked in a text message, using de Blasio’s code name. “Not really,” a detective wrote.
“Redmond hell-bent that this doesn’t get out to anyone, we need to kill the story,” executive protection unit cop Jorge Bravo wrote.
“He went off on OPTICS of this detail – the little things (double-parking and crosswalk s–t),” Bravo added…
“No one is to know; also, Eagle was not in the limo … are we clear guys please?” Ioveno said, using the code word limo for the NYPD Chevy Tahoe.
And then came a second crash, this one involving city First Lady Chirlane McCray, multiple vehicles and disappearing witnesses. And in this crash, someone was hurt.
The NYPD went all in, it seems, on trying to cover this one up also. As per one of the attorneys involved:
“The way the police report is written, you can kind of tell they’re covering something up,” Grossman said. “If you see the diagram — it doesn’t make sense. … They seemed to whisk everybody away without anybody saying anything.”
And so it goes. Negligence happens and those who are supposed to document what happens decide to come up with “alternative facts” and hide the witnesses so that innocent victims are frustrated in their ability to find out what actually happened.
The more the world changes, the more it stays the same. Except that sometimes emails and texts help with the Big Reveal.
My first car was a 1982 Honda Accord hatchback. Five-speed stick. Roll down windows. Manual locks. No A/C.
I learned to drive stick when my older brother needed me to drive his manual transmission car back from Philadelphia to Long Island. I got a lesson on Saturday. And drove it solo out of Center City Philly to New York on Sunday. Only stalled once.
My theory in buying that no-frills Honda was simple: The fewer automated things, the fewer things would break. And nothing ever broke. It was a great car and I used it for many a trip back and forth to Buffalo during law school.
But cars and Manhattan are not a good match and when I moved there in 1986 it was time to kiss it good bye. When I needed a car I would rent one and those rentals were far cheaper than the cost of garaging it.
(Hang with me a bit here and I’ll get to the safety and personal injury stuff.)
When I moved to the suburbs after 13 years of city living it was time to motor up again. But I had a problem, and part of that problem was a pipestem driveway. And Mrs. NYPILB (she loves that acronym!) didn’t drive stick, didn’t know from clutches, and didn’t want to learn the three-pedal two-step. In twenty years of marriage that’s the worst I can say about her so I figure I’m pretty far ahead of the game.
Having a two-car family and a pipestem driveway would mean constant car shuffling. I let the fun of driving stick slip away since my car was mostly going to the train station anyway. And that’s just the way it was.
When Dear Daughter was old enough to drive, she followed in her mother’s footsteps.
But Dear Son thinks differently. He’s a car guy. Want to know what that car in front of you is? He’ll tell you in two seconds based on the tail lights. At night. Ask him what he wants to be when he gets older and he’ll tell you a McLaren owner. But he’ll settle for a Lambo if he has to.
Until he started talking car stuff, I had no idea that tail lights could be an art. Or that there really was much difference. I was simply oblivious since I’m not a car guy.
So with the lease being up on my Subaru Impreza hatchback, I needed to go car shopping. But I confess that I love this vehicle because of its all wheel drive and the car’s many safety features, which you can’t dismiss when you’re looking at teenagers. Dollar-for-dollar you get a lot of bang for the buck.
I took Dear Son with me to look at a couple of cars, including the next gen Impreza. Guess who wants to drive stick? Yeah.
But the salesman let me know the deal: If I want the stick and clutch, I can’t get the Eye Sight Driver Assist. What’s Eye Sight? That’s the computer that not only beeps when you change lanes without signaling, but more importantly will automatically brake when a car or pedestrian is too close in front.
So if a car coming at you in the opposing lane suddenly makes the dreaded left turn in front of you, or a drunk pedestrian steps off the curb in front, the computer might well react before you. Split seconds can make a difference. Literally.
As you might assume from the bare bones ’82 Honda I started with, I’ve never been one for tech features in a car — I’m the type that never uses the cruise control. Digital doodads don’t light my fire. I want to drive a car, not be driven. And I think self driving features are dangerous because they promote inattention.
That’s one of the things about driving stick — you can’t be inattentive. Unless you are cruising on the highway you are constantly engaged. You’ll never see someone driving stick and texting, or eating a hamburger, or even drinking coffee. Not in local traffic, anyway.
But there’s no getting around the fact that the Eye Sight Driver Assist is not only good tech, but tech that remains invisible until called into play. It’s part of the wave of advanced safety features that are coming as car companies automate their vehicles.
That tech, however, is incompatible with a manual transmission. You can choose between a valuable safety feature — one that will become far more ubiquitous as the years roll by — or the fun and engagement of driving stick. But you can’t have both.
(Another tech development that will help drive a stake through the stick is an app on your phone that allows you to remotely start your car minutes before you get there. When it’s 100 degrees outside, or 10 degrees, that’s going to be a valuable and desired feature. But manual transmissions get parked in gear, not neutral, and you can’t remotely start a car that’s in gear.)
Driving a manual transmission is not only fun, but a valuable skill. It allows you to feel how the car works, and be more engaged with your surroundings, even if you’re clueless under the hood.
Manual transmissions have, of course, been declining in the United States for several decades, due to ease of use for the automatic. Manual transmission used to at least have the advantage of being cheaper engines and better on gas, but even that has changed. The computers on the automatic now get better mileage than you can with the clutch.
When you add up the long term decline of stick due to ease of use of the automatic, with the breakneck speed of technological safety improvement, you get a recipe for stick-the-fork-in-it-its-done.
In ten years the manual transmission, beloved by a decreasing percentage of car drivers, will be little more than a specialty item that needs to be custom ordered. It pains me to say it, but the stick is dead. Ultimately killed by safety.
Subaru has announced its updated pricing and trim level changes for the 2020 Impreza. Tucked away in the press release, however, is a bit of bad news for enthusiasts: there’ll be one fewer Subaru manual transmission option available as we move into the 2020 model year.
Ouch. And the reason is, as noted above, incompatibility with the safety tech of their Eye Sight computer safety stuff:
Development costs to add a new manual transmission are high. The take rates for them now are low. They have no place in an “electric” or “electrified” future and prevent universal implementation of Subaru’s EyeSight safety technology.
And the Impreza is not, by any means, alone:
The Outback, Forester and Legacy have all lost their manual transmission options entirely. Even the base WRX could be CVT-only when the next generation materializes. (These developments should not surprise at a time where even the BMW M3, the ultimate driver’s car, barely kept its stick shift.)
If you want to drive a stick, or make sure your kid(s) learn, you’d better do it sooner rather than later.
