Auto Accidents

The Rear-End Presumption and the Rebuttals That Actually Land

The rear-end presumption is rebuttable, not conclusive. Defense counsel have a settled menu of ways to chip at it, and the data record is what forecloses each one before it gets traction.

Two cars stopped at a rear-end collision on a city street

The rear-end collision looks like the easiest liability case on the desk, and often it is. But the presumption that does the work is rebuttable, not conclusive, and defense counsel have a settled menu of ways to chip at it. Knowing the menu, and the evidence that closes each option, is the difference between a quick liability admission and a comparative-fault fight you did not see coming.

Where the presumption comes from

Most jurisdictions attach a presumption or at least a strong inference of negligence to the following driver in a rear-end crash. The doctrinal hooks vary, following-too-closely statutes, assured-clear-distance rules, the basic-speed law, but the effect is similar: a driver who strikes the vehicle ahead is presumed to have failed to maintain a safe distance or a proper lookout. In practice, that shifts the burden of production to the defense to come forward with evidence of a non-negligent explanation. It does not shift the ultimate burden of persuasion, and it does not make the case self-proving.

Treat the presumption as a starting position, not a finish line. The cases that go sideways are the ones where plaintiff counsel relied on it and did nothing to foreclose the rebuttals below.

The four rebuttals that actually get argued

Defense theories in rear-end cases cluster into a predictable set:

  • The sudden stop. The lead driver braked abruptly and without reason, or stopped in a live traffic lane. This is the most common theory and the one juries find most intuitive.
  • The sudden emergency or cut-in. A third vehicle changed lanes into the gap, or an unforeseeable hazard forced the following driver's hand. This overlaps with phantom-vehicle issues when the cutting-in car never stopped.
  • Mechanical failure. Brakes failed without warning. This one is only as good as the maintenance record behind it, and it often backfires.
  • Non-functioning equipment on the lead car. Brake lights out, a disabled vehicle without hazards, an illegal or unlit stop. This is a genuine comparative-fault argument, not a pure defense.

Close each rebuttal with evidence, not argument

The sudden-stop defense collapses against the same principle that created the presumption: a following driver must leave enough distance to stop safely even if the car ahead brakes hard. A lawful stop for traffic, a light, or a pedestrian is foreseeable. Lock this down with the following distance and speed, which is exactly where an event data recorder pull earns its keep. The airbag control module on both vehicles captures pre-impact speed, brake application, and throttle in the seconds before impact, and it will usually show the following driver never braked or braked far too late.

For the cut-in or phantom-vehicle theory, corroboration is everything. Dashcam footage, a contemporaneous statement to the responding officer, and independent witnesses either support the story or expose it as after-the-fact reconstruction. A cut-in raised for the first time at deposition, with no mention in the crash report, is impeachment waiting to happen.

Mechanical failure invites its own discovery. Demand the maintenance and repair history, any prior brake complaints, and the post-crash inspection. A driver who claims surprise brake failure but skipped scheduled service has handed you a negligence theory that survives even if the brakes really did fail. The defense that was supposed to excuse the driver becomes proof of inattention to a known duty.

The presumption gets you to the courthouse. The event-data pull, the dashcam, and the maintenance file are what keep the following driver from talking his way back out of it.

Watch the genuine comparative-fault opening

The one rebuttal that deserves respect is the lead vehicle's own conduct: an unlit stop on a dark highway, brake lights that were out, a driver who stopped in a travel lane to make an illegal turn. These are real allocation arguments, and in a modified-comparative jurisdiction they can matter enormously if they push the plaintiff over the bar. Get ahead of them. Inspect the plaintiff's brake lights, pull the vehicle's own data, and be candid with your client about any conduct that a jury could weigh. The same allocation dynamics that show up in commercial-vehicle and motorcycle cases apply here: fault is rarely all-or-nothing once the defense has a credible hook.

Rear-end cases remain among the most winnable on liability. They stay that way when you treat the presumption as the opening move and build the data record that forecloses the rebuttals before the defense has a chance to develop them.

The LawyersTrend Brief · Fridays

One weekly email. Every new article.

Friday mornings — every PI article we publish that week, plus rankings updates and key verdicts. Free. One-click unsubscribe.