You are not logged in.
Pages: 1
Rokud, you started this thread asking for a reasonable explanation of why cyclists would ride in the northbound multi-vehicle traffic lane (there is no such thing as a 'car' lane on Great Northern), instead of the two-way bike lane. There are at least two:
First, the northbound bike lane makes cyclists uncomfortable because it requires you to ride in between two opposing lanes of traffic and too close to both of them. (Have you ever driven your car on a road where you were forced to drive in between two opposing lanes of traffic? I can't think of an instance when I have. It's weird and uncomfortable.)
Second, the bike lane is oddly designed, and for cyclists who happen to encounter this street for the first time, it's not immediately obvious where you're supposed to ride OR where/how you're supposed to safely enter the lane. I remember being confused by the lane markings the first time I happened to ride along Great Northern.
These reasons may sound unreasonable to YOU, but if you really want to understand someone else's behavior, walk (or ride) a mile in their shoes. Why don't you hop on a bike and try cycling up Great Northern a few times in the northbound bicycle lane, especially when there are both bicycles and cars traveling southbound on either side of you. You might feel safe enough doing that, but it will probably demonstrate to you that reasonable minds can disagree about whether that northbound bike lane is actually safe to ride in - especially when it is perfectly legal to ride on the right side of the road in the lane shared with other vehicles.
If anybody is using DiNotte lithium-ion batteries with your lights, check out this product recall information:
I am glad this posting stimulated some debate, which was my objective. I am frankly not sure whether I think strict liability is the best rule to apply in motorist-cyclist collisions, but I AM sure it's an interesting idea that merits discussion.
Strict liability, for practical purposes, makes it easier to establish liability in a civil case because it does not require the jury to determine that a person's conduct was negligent in order to find that they are liable for damages. The jury still has to make a variety of other findings - namely, that the defendant's conduct actually caused damages, the amount of the damages, etc. - thus, there's no reason to be concerned that in a strict liability situation the cyclist could just fall down, go to court, and win money from a random motorist who wasn't even there. The "onus of responsibility" in our system is currently on the cyclist - both legally, because the cyclist will have the burden of proof to establish liability, and practically, because we are essentially invisible to motorists much of the time and, if we want to arrive intact at our destination, have to assume we won't be seen or taken into account and cycle accordingly.
Tom, you are correct that a strict liability rule in Texas would make it pretty much irrelevant whether the police issue a citation to the driver. In the current system, a citation is not a legal requirement for a civil claim, but as a practical matter, the fact that no citation was issued is a strong argument for the defense. With no citation, a jury will be less likely to find the defendant was negligent; and thus, in turn, an insurance company will be less likely to pay the claim before it is filed in court or presented to a jury.
The reason I thought the use of strict liability in some European countries was intriguing was that the author of the article suggested that a strict liability rule was causing drivers to exercise more caution around cyclists and pedestrians, resulting in an overall reduction in accidents. Stripping it to its essentials, the population of motorists who hit cyclists can be divided into two groups: those who were negligent, and those who were not. A strict liability rule would impose potential liability on all these motorists -- with two consequences: (1) it would be far easier for cyclists to recover damages from the negligent motorists, since liability would not longer be based on arguments about whether the motorist was passing at a safe distance, whether it was reasonable to keep driving even though "the sun was in my eyes," etc. and (2) non-negligent motorists would be faced with potential liability for hitting cyclists. Note that under strict liability, at least as it would work in Texas and most places in the U.S., the defendant still has the opportunity to prove that the cyclist's own negligence contributed to the damages, reducing whatever money award the cyclist gets either partially or entirely (depending on the percentage assigned to the cyclist's conduct). Strict liability as a legal rule in our civil justice system has not been employed because people think it's "fair" to impose liability on the non-negligent defendants. Instead, it's based on a social policy judgment: the rule of strict liability creates incentives for people to exercise much more care than they otherwise might, in a dangerous situation. For example, if you handle highly explosive materials, you will be strictly liable for damages they cause, because society wants you to do more than exercise "reasonable care" -- society basically wants you to exercise all possible care to avoid an accident. The policy question here is whether getting behind the wheel of an enormous hunk of metal, in the presence of pedestrians and cyclists who can be killed by an accident that barely scratches your fender, ought to require you merely to exercise "reasonable care," or to be especially cautious.
As for my "God forbid..." comment: in the current political and legal climate in Texas and many other places in the United States, the overwhelming trend is toward laws and legal standards that make it harder for any plaintiff (regardless of the type of case) to recover damages from a defendant. My comment was not intended to suggest that "it's obvious that we need these laws and anybody who opposes them is obviously not doing God's work." Rather, I was making a rather flippant reference to the fact that it's extremely unlikely that anytime in the near future, Texans would be willing to consider a change in our legal rules that would make it easier for cyclists to obtain legal damages from drivers who injure them - no matter how sensible or helpful such a change would be.
From the following article - http://www.guardian.co.uk/commentisfree … ngholidays
"There is another important factor at work in the Netherlands and in Austria, Denmark, France, Germany, Italy, Sweden and several others European countries. It's the principle of strict liability. This puts the onus of responsibility on drivers in civil compensation cases in the event of a collision – not on the cyclist or pedestrian as is the case here. It does not affect criminal cases. Furthermore, as Roadpeace reports (pdf), in several of these countries children and the elderly are deemed not liable for their actions in civil cases. As far as I can see, this is bound to focus drivers' minds."
Of course, God forbid we pass any laws in Texas that make it easier to hold people accountable for their actions; it would probably be about as easy to get the Texas legislature to create strict liability for killing a cyclist as it would be to get them to legalize marijuana.
Saw this item in one of the legal updates I read & thought it would be of interest. Note that the cyclist ran a red light, and will only recover $450,000 of the $1.8 million because the jury found her 75% at fault for the accident.
"A Missouri University student whose leg was amputated following a 2005 accident should receive $1.8 million, a jury has decided. The student was struck by a vehicle while crossing an intersection and then hit again and dragged by a Columbia Water and Light truck. Jurors determined that the driver of the first car and the City of Columbia were to blame for 25 percent of the accident." Greg Mitchell, Columbia Missourian 10/28/2008
Thanks guys; we thought we had the serial number but now I can't find it. :( No recent photos.
It was stolen from in front of the UT School of Nursing, on Red River at MLK.
To the stinking weasel who stole my blue & yellow Trek 7000 hardtail mountain (now commuter) bike:
May you be too stupid to realize it's got commuter tires on it, take it out on a trail, and endo;
May your fully-loaded panniers fall off the rear black cargo rack;
May your hand slip while trying to use the Pedro's bottle opener where the water cage should be, so that your brew spills and you cut yourself;
May your feet slip off the yellow ATAC clipless pedals, causing you to slip and bruise your nads on the top tube;
May the severed end of the lock fly up and hit you in the eye; and
May you have the same trouble we've been having lately getting it to shift to the largest chain ring.
And to everybody else: If you see a bike around town fitting this description, would you please do whatever you can to help me get it back?
Aggravated to have to resort to my car,
Alicia Butler
What about something to empower us against the "cyclist had no helmet therefore getting run over by an inattentive motorist was their own fault" argument? Several states (DE, FL, MA, NY, RI, VA) have statutes that specifically say that the fact that a cyclist was not wearing a helmet is not evidence of negligence. Of course, these are in conjunction with helmet-related laws (either requiring them, or stating that local governments can require them), which may or may not be a can of worms people want to take on this session.
treybiss - What has happened with your ticket?
I think it's important that we get the City to impose only the $20-40 fine and not treat riding on the sidewalk as a traffic offense that goes on your driving record. I'm a lawyer, bike commuter & triathlete: On a pro-bono (no fee) basis, I would be willing to help someone challenge treating such a ticket as a traffic offense so we can get some helpful court precedent on the issue. For info about me - http://www.txtort.com/about.html (To be clear, my office is in Dallas, but I live & bike in Austin!).
Pages: 1
[ Generated in 0.103 seconds, 7 queries executed - Memory usage: 571.52 KiB (Peak: 587.32 KiB) ]