Posted On: December 30, 2009 by Baker Associates

Semi Tips, Floods Road with Grape Juice

Things turned sour in Portersville, Pennsylvania on Monday when a semi that was reportedly being driven by an intoxicated driver tipped over, spilling a flood of grape juice onto Route 79. Like many accidents involving semi trucks, this one caused the road to be shut down for an extended period of time while road crews worked to clean up the debris. The driver of the semi was arrested for having a blood-alcohol level of three times the legal limit. The company who employed the driver meanwhile issued a statement saying they do not condone such behavior.

While the company may not condone the behavior, they may very well be liable for any damages caused by the driver’s actions. Semi trucks generally carry heavy loads that have the potential to cause lots of damage to the roadway, other vehicles, or other persons if they are driven in a negligent or reckless manner. Victims who suffer injuries as a result of accidents such as the one described above need to know not only how to recover for their losses but who they can recover from.

Even though the driver is directly responsible for his or her actions in a situation where he or she chooses to drive while intoxicated, the company who employs the driver may also be responsible for at least part of the damages depending on the circumstances surrounding the wreck. For example, if the company was aware of prior similar incidents involving the same driver and continued to allow him to drive for the business, that company’s likelihood of being liable for any damages caused would increase dramatically. This is significant because the company is likely to have a greater ability to pay for any damages than the driver, especially if a jury determines that the situation warrants the imposition of punitive damages which have the capability to reach into the millions of dollars.

Source: http://www.newyorkinjurynews.com/2009/12/29/truck-accident-notice-semi-truck-flipped-over-on-i-79_200912291902.html

[an error occurred while processing this directive]