Some Maryland drivers may believe that there are varying degrees of seriousness when it comes to traffic infractions. For example, failing to signal when changing lanes is often viewed as less serious than running a red light, but running a red light might be considered less of a problem than driving drunk. Are these mere perceptions by motorists, or is there a real hierarchy when it comes to moving violations?
The answer may lie in the consequences of these violations. Take for example the car accident that happened last weekend in Fallston, Maryland. According to Maryland State Police, a woman driving an SUV was traveling south on Route 152 when she ran a red light at an intersection. Her vehicle collided with the front driver’s side of a Chevy Trailblazer that had the right of way. The crash caused the Trailblazer to spin around and collide with a pickup truck.
At some point during the collision the 17-year-old driver of the Trailblazer was ejected in the crash. She was flown to a hospital and listed in serious condition. The driver of the SUV that caused the accident was also rushed to a hospital. The driver of the pickup truck wasn’t injured, but his vehicle sustained some damage.
Many drivers fail to stop at a red light, whether it happens due to a distraction or because they speed up before reaching the intersection when the light is yellow, and they don’t make it through before it changes to red. Running a red light may seem insignificant to drivers in a hurry, but when cars collide as a result, serious injuries or even fatalities often follow. It’s then up to the driver who ran the red light to pay for the consequences.
Source: The Baltimore Sun, “Two injured in Fallston crash Sunday evening,” April 3, 2012
