How Virginia House Bill 1479 Changes Punitive Damages Law

For a Virginia torts exam, the short answer is this: House Bill 1479 creates a new statutory route to punitive damages in personal injury and wrongful death cases arising from felony hit-and-run conduct, now codified as Va. Code § 8.01-44.5:1. The trap is the verb. The statute says a jury or court may award punitive damages; it does not say punitive damages automatically follow once the plaintiff proves the driver fled.[1]

That distinction matters because the statute sits at the intersection of three rules students often blur together: the common-law standard for punitive damages, the felony hit-and-run statute, and Virginia’s separate DUI punitive damages statute. HB 1479 helps the plaintiff, but it does not erase every ordinary limitation on punitive damages.

The new statutory sentence students need to know

Section 8.01-44.5:1 applies in an action for personal injury or death arising from the operation of a motor vehicle when the defendant engaged in “conduct that constitutes a felony violation of § 46.2-894.” In that setting, the trier of fact “may award punitive damages” to the injured person or the personal representative of the deceased person.[1]

Every phrase in that sentence does work. “Personal injury or death” means the new claim is not a general punishment device for every hit-and-run. “Conduct that constitutes” points to proof of the underlying conduct, not necessarily a criminal conviction. “Felony violation of § 46.2-894” imports the hit-and-run statute’s threshold. And “may award” preserves discretion.

The hit-and-run statute itself requires a driver involved in an accident to stop, provide identifying information, and render reasonable assistance when the accident results in injury, death, or damage to attended property. A violation becomes a felony when the accident results in injury, death, or more than $1,000 in property damage.[2]

That creates one clean exam boundary. If the plaintiff suffered bodily injury or died, and the defendant’s flight satisfies the felony hit-and-run statute, § 8.01-44.5:1 is in play. If the case involves only property damage, the new punitive damages statute does not fit by its own terms, even though § 46.2-894 may still classify certain property-damage hit-and-run conduct as a felony.[1][2]

Why Doe v. Isaacs made this statute necessary

The gap HB 1479 addresses is easiest to see through Doe v. Isaacs. There, the plaintiff obtained a jury award that included $175,000 in punitive damages after a driver struck the plaintiff and left the scene. The Supreme Court of Virginia reversed the punitive damages award, holding that the defendant’s flight was gross negligence but did not rise to the common-law standard of willful and wanton conduct required for punitive damages.[3]

That is the old answer a careful student had to give: morally ugly conduct did not itself satisfy the punitive damages standard unless the plaintiff could show the kind of conscious disregard Virginia common law required. Fleeing after the collision aggravated the facts, but in Doe it did not transform gross negligence into willful and wanton misconduct.[3]

Section 8.01-44.5:1 changes that exam answer for qualifying accidents after its effective date. The plaintiff no longer has to rely only on the common-law route Doe rejected. The plaintiff can point to a standalone statutory punitive damages route tied to felony hit-and-run conduct.[1]

But the Doe problem is not replaced by a shortcut answer. A strong essay should still identify Doe as the old common-law obstacle, then explain that HB 1479 supplies a statutory argument when the case satisfies the new statute’s conditions. The better answer does not say “Doe is overruled.” It says the legislature created a separate statutory path for a defined category of injury and death cases.

“Conduct that constitutes” is not the same as “convicted of”

The statute’s trigger is not a criminal judgment. It does not say the defendant must have been charged with, pleaded guilty to, or been convicted of felony hit-and-run. It asks whether the defendant engaged in conduct that constitutes a felony violation of § 46.2-894.[1]

That phrasing matters in a civil case. A plaintiff can try to prove the relevant conduct in the tort action itself: the defendant was involved in the accident, knew or had reason to know of the accident, failed to stop, failed to give the required information, or failed to render required assistance, and the accident met the felony threshold. The civil court is not waiting for the criminal docket to produce a conviction before the punitive damages statute can be argued.

The phrase also prevents overstatement. “No conviction required” does not mean “no proof required.” The plaintiff still has to establish the conduct that would constitute the felony violation. On an exam, the easiest lost point is to treat flight from the scene as a label rather than walking through the statutory conduct.

The word “may” keeps punitive damages discretionary

The most important word in § 8.01-44.5:1 is “may.” Once the plaintiff proves the qualifying felony hit-and-run conduct in a personal injury or death case, the trier of fact may award punitive damages. The statute does not command that punitive damages be awarded.[1]

That makes the statute plaintiff-friendly without making it automatic. The plaintiff gets past the Doe gap by invoking a statute aimed at felony hit-and-run conduct. The defendant can still argue against the amount of punitive damages, the appropriateness of punitive damages on the facts, and whether the plaintiff proved the statutory trigger at all.

Virginia’s general punitive damages cap also remains in the background. Section 8.01-38.1 caps punitive damages at $350,000, and HB 1479 does not create a separate higher ceiling for felony hit-and-run cases.[4]

The DUI statute shows what the legislature did not say

The cleanest contrast is Virginia’s DUI punitive damages statute, § 8.01-44.5. In specified intoxicated-driving cases, including where the defendant’s blood alcohol concentration was at least 0.15 percent under the statute’s conditions, the defendant’s conduct “shall be deemed” sufficiently willful or wanton to support punitive damages.[5]

That is different statutory architecture. The DUI statute uses deeming language: when the statutory prerequisites are met, the willful-and-wanton character is supplied by statute. HB 1479 uses permission language: in a qualifying felony hit-and-run personal injury or death case, the factfinder may award punitive damages.[1][5]

A professor can hide a lot in that comparison. If the facts give a drunk driver with the statutory BAC threshold, students should analyze the DUI statute on its own terms. If the facts give a driver who leaves an injury scene, students should analyze HB 1479. If the facts give both, the answer should not collapse them into one general “punitive damages are available” sentence.

Effective date and prospectivity

HB 1479 is effective July 1, 2026. Because punitive damages affect substantive rights, accidents before that date should not be treated the same way unless the legislature clearly made the statute retroactive. Virginia courts apply statutes affecting substantive rights prospectively absent explicit retroactive intent, a principle reflected in McCarthy v. Commonwealth.[6]

So the date in the fact pattern matters. For an accident on or after July 1, 2026, the plaintiff can argue § 8.01-44.5:1 if the remaining elements are met. For an accident before July 1, 2026, the safer exam answer is to apply preexisting law and explain why the new statutory remedy should not be assumed to apply retroactively.

The unresolved issues are part of the answer

The statute is new enough that there are no Virginia appellate decisions interpreting § 8.01-44.5:1 in the hit-and-run punitive damages context. That should make students more precise, not more dramatic. The text gives several strong answers, but it leaves room for litigation around the edges.

• Unidentified driver: The statute does not expressly say how it applies when the hit-and-run driver is never identified. A plaintiff may have suffered injury or death from felony hit-and-run conduct, but civil punitive damages still require a defendant against whom the claim can be proved and collected.
• Civil proof versus criminal case: The plaintiff need not show a conviction, but still must prove conduct that constitutes the felony violation.
• Discretion: Even after the statutory trigger is met, the factfinder may award punitive damages; the statute does not require an award.
• Cap: Any punitive damages award remains subject to Virginia’s $350,000 statutory cap.
• Timing: The statute should be analyzed prospectively for accidents on or after July 1, 2026, absent explicit retroactive application.

Those points are not caveats to tack onto the end of an essay after announcing liability. They are the essay. HB 1479 creates the statutory punitive damages argument; the student earns the points by showing the limits of that argument.

Exam-ready synthesis

In a Virginia torts essay, analyze HB 1479 this way: § 8.01-44.5:1 gives a plaintiff a standalone statutory punitive damages argument in a personal injury or wrongful death action arising from conduct that constitutes felony hit-and-run under § 46.2-894. The plaintiff does not need a criminal conviction, but must prove the conduct that would constitute the felony. The remedy remains discretionary because the statute says the court or jury may award punitive damages. Any award is still capped at $350,000, and the statute should be treated as prospective for accidents on or after July 1, 2026.

Do not write that HB 1479 makes punitive damages automatic. Do not write that every hit-and-run qualifies. Do not write that Doe v. Isaacs disappears. The better answer is narrower and stronger: HB 1479 closes the Doe gap for qualifying felony hit-and-run injury and death cases, but the award remains discretionary, capped, prospective, and still largely untested in Virginia courts.

References

1. Va. Code § 8.01-44.5:1, Code of Virginia
2. Va. Code § 46.2-894, Code of Virginia
3. Doe v. Isaacs, 265 Va. 531, Supreme Court of Virginia, 2003
4. Va. Code § 8.01-38.1, Code of Virginia
5. Va. Code § 8.01-44.5, Code of Virginia
6. McCarthy v. Commonwealth, 73 Va. App. 630, Court of Appeals of Virginia, 2021