To win a liability claim, you cannot just prove that someone did something wrong. You must also prove that their wrong action directly caused your injury. This connection is called proximate cause, and it is often the most disputed part of any lawsuit.
Think of it this way. If a driver runs a red light and hits your car, the link is obvious. The driver’s fault and your broken arm are tied together by a single event. But what if the driver runs that red light, misses you by inches, and you get so angry that you punch a wall and break your hand? The driver was wrong, but was that wrong action the legal cause of your broken hand? Probably not. The law says there must be a reasonable, direct chain of events between the fault and the harm. If that chain is broken by something unexpected or by your own choice, the defendant is not responsible.
Courts use two tests to decide if proximate cause exists. The first is cause-in-fact, often called the “but-for” test. You ask: But for the defendant’s action, would the injury have happened? If the answer is no, then cause-in-fact exists. For example, but for the driver running the red light, you would not have been hit. That part is usually straightforward.
The second test is more complicated. It asks whether the injury was a foreseeable result of the defendant’s action. Foreseeable does not mean the defendant had to predict the exact injury. It means that a reasonable person could have seen that some kind of harm was likely. If you slip on a wet floor in a grocery store, the store should foresee that someone might fall and break a bone. That is foreseeable. But if you slip, fall, and the impact knocks a shelf over, and that shelf crushes a rare violin you were carrying, the store might argue that the broken violin was not foreseeable. A typical shopper does not carry an expensive violin through the produce aisle. The injury to your body was foreseeable. The damage to the violin may not be.
Proximate cause also cuts off liability when an intervening event happens between the fault and the injury. An intervening event is something that occurs after the defendant’s action but before your injury. If that event is something a reasonable person would expect, the defendant is still on the hook. For example, if a driver knocks down a power line, and then a rainstorm causes the live wire to shock a pedestrian, the driver is still liable because storms are common and predictable.
But if the intervening event is a wild, unpredictable act—say a terrorist bomb explodes at the exact moment you are lying on the pavement after being hit by a car—the driver is not liable for the bomb injuries. The bomb was not foreseeable. The law has to draw a line somewhere, otherwise defendants would be responsible for every weird thing that ever happens, no matter how remote.
Plaintiffs often lose on proximate cause when they cannot show a tight link. Imagine you are in a car accident caused by the other driver. You have a minor whiplash. Months later, you develop chronic back pain. Is the accident the cause? You need medical evidence that the accident directly led to that specific condition. If you had a pre-existing back problem, the defense will argue that your injury was caused by your old condition, not the crash. The court will look at whether the accident made your condition worse in a measurable way. If you cannot separate the effects, the proximate cause chain is broken.
Even more common are cases where someone is hurt doing something dangerous after the initial fault. Suppose a landlord fails to fix a broken stair. You know it is broken, but you try to jump over it anyway. You fall and break your ankle. The landlord was wrong for not fixing the stair, but the court may find that your choice to jump over it was an intervening cause. Your own action broke the link. Landlords are not required to protect you from your own careless decisions, only from risks you could not reasonably avoid.
Proximate cause is not about fairness in some abstract sense. It is about practical limits. The law cannot chase responsibility forever down a chain of events. At some point, the connection becomes too remote or too weird. If you want to win a liability claim, you must show not only that the other person was wrong, but that their wrong was the direct, natural, and foreseeable reason you got hurt. That is what it means to “show who was wrong” in a way the law can act on.
Every liability claim comes down to this: Did the defendant’s mistake set off a chain that led reasonably and directly to your injury? If the answer is yes, you have a case. If the chain has too many twists, turns, or outside influences, you may have nothing but a bad memory.
