Statute of Limitations for Product Liability in Maryland

5 min read

Published April 8, 2026 • By DocketMath Team

Overview

Run this scenario in DocketMath using the Statute Of Limitations calculator.

Maryland’s statute of limitations (SOL) for product liability claims is generally 3 years under Md. Code, Cts. & Jud. Proc. § 5-106.

In Maryland, product liability lawsuits typically proceed under the state’s general limitations statute rather than a specialized, claim-type-specific SOL for every product theory (for example, strict liability vs. negligence). For this page, the timing rule is the default 3-year period because no claim-type-specific sub-rule was found in the available jurisdiction data.

Note: “Product liability” can be pleaded in different ways, but Maryland’s SOL analysis often starts with the general statute. Use DocketMath to map your key dates to the 3-year window under § 5-106.

For the calculator, use: /tools/statute-of-limitations.

Limitation period

Your baseline deadline is 3 years from the trigger event used for SOL purposes under Md. Code, Cts. & Jud. Proc. § 5-106.

Because SOL rules are date-driven, the most actionable step is choosing (and documenting) the trigger date you plan to use in the calculation. Different “trigger date” choices—like the date of injury onset versus the date the injury was discovered (or should have been discovered)—can change the end date.

Practical way to estimate the 3-year period

A simple planning approach:

  • Choose your trigger date (common candidates include the date of injury onset, or the date the injury was discovered/should have been discovered).
  • Add 3 years to estimate the outer deadline.
  • Then consider whether any exceptions or tolling arguments plausibly apply based on your facts.

How this works in the DocketMath calculator

DocketMath’s statute-of-limitations calculator is designed for this kind of SOL math. It generally takes your trigger date and computes the end of the 3-year period under the default rule.

Typical inputs and how they affect outputs:

  • Trigger date (required):
    • Earlier trigger date → earlier SOL expiration
    • Later trigger date → later SOL expiration
  • Tolling/exception dates (if you enter any):
    • Adding tolling inputs can extend the calculated end date
    • Leaving tolling inputs blank keeps the result focused on a straightforward “+3 years” estimate

If you don’t have clear exception facts, the calculator’s default run will reflect the general 3-year SOL in § 5-106.

Key exceptions

Maryland’s SOL framework includes concepts that can affect when the clock starts or whether the running of time is paused. In product liability cases, these issues often turn on the specific facts, especially around when the injury was known or reasonably knowable.

While this page is grounded in the general 3-year default rule (because no claim-type-specific sub-rule was identified), you should still evaluate potential fact patterns that may shift the outcome:

  • Discovery-related arguments (knowledge/when it should have been known):
    • If your claim depends on the injury being discovered later, the trigger date may not be the same as purchase/installation/use/manufacture dates.
    • You can use DocketMath to compare assumptions by running calculations using different plausible trigger dates (for example, “onset” vs. “discovery”).
  • Tolling events (circumstances that pause the running of time):
    • Some legal circumstances may “pause” the SOL clock.
    • If tolling could apply, your SOL expiration date may move outward depending on the dates and duration.
  • Ongoing harm vs. a single-injury framing:
    • If harm continues or worsens over time, parties may dispute which date should control for SOL timing.
    • Trying multiple trigger-date scenarios in DocketMath can help you see how much factual disagreement might matter.

Checklist before using a calculated deadline

Before relying on any computed SOL date, confirm your timeline details:

Warning: Small differences in the trigger date can materially change the result. Use DocketMath to test assumptions (e.g., injury onset vs. discovery) rather than locking onto a single date without checking the underlying timeline.

Statute citation

Maryland’s general SOL for claims covered by the general limitations statute is found at Md. Code, Cts. & Jud. Proc. § 5-106, which provides a 3-year limitations period.

Under the provided jurisdiction data, no claim-type-specific sub-rule was found, so the applicable default timing rule is the general 3-year period under § 5-106.

Use the calculator

Use DocketMath to calculate your estimated end date under the default 3-year SOL in Md. Code, Cts. & Jud. Proc. § 5-106.

Primary CTA: /tools/statute-of-limitations

Step-by-step (how to run the estimate)

  1. Open /tools/statute-of-limitations and select Maryland (US-MD).
  2. Enter your trigger date (the date you believe should start the SOL clock under the general 3-year rule).
  3. Review the calculated SOL expiration date based on the 3-year period.
  4. If you think a tolling/exception theory may fit the facts, run a second calculation using alternative dates/inputs and compare the outcomes.

What to watch for

DocketMath typically shows:

  • The calculated SOL end date under the 3-year general rule
  • How the input dates drive the result

If your timeline is close to the deadline, treat the output as a planning estimate to help you act early—not as a substitute for case-specific legal evaluation.

Related reading