Statute of Limitations for Rape / Sexual Assault (adult victim) in Maryland

6 min read

Published March 22, 2026 • By DocketMath Team

Overview

In Maryland, a time limit applies to when prosecutors (and, in some circumstances, victims through related civil avenues) can bring claims based on criminal conduct such as rape or sexual assault involving an adult victim. For criminal cases, the key question is usually straightforward: what statute of limitations (“SOL”) period applies and when does it start running?

For Maryland, the starting point for adult rape/sexual assault is the general statute of limitations for crimes in Maryland. Based on the jurisdiction data you provided, Maryland uses a general/default SOL period of 3 years for this category, and no claim-type-specific sub-rule was found. That means you should treat the 3-year period as the baseline unless a recognized exception changes it (discussed below).

Note: This page focuses on Maryland’s statute of limitations framework. It does not replace the text of the statute or charging decisions made by prosecutors in a specific case.

Limitation period

General rule: 3 years (default)

Maryland’s general SOL period is 3 years, tied to Md. Code, Cts. & Jud. Proc. § 5-106. Because you indicated no claim-type-specific sub-rule was identified, the practical takeaway is:

  • Baseline SOL: 3 years
  • Applies as the default to adult-victim rape/sexual assault unless an exception or special timing rule applies.

When does the clock start?

Maryland SOL analysis commonly turns on the date the limitations period begins—often linked to the offense date or, in some contexts, when the offense could be discovered. However, rather than guessing on that point, this guide is designed to help you use DocketMath to compute deadlines using the inputs that the calculator supports.

How to think in deadlines (without guessing)

If you’re trying to determine whether a prosecution is timely, you typically need to know:

  • Offense date (or relevant triggering date): the date that starts the SOL clock under the calculator’s logic
  • Type of filing: the tool’s output is keyed to the SOL calculation use case
  • Any known exception facts: if the tool supports exception toggles, enabling them will shift the deadline

Here’s a simple way to visualize how changes in inputs affect the output:

Input you changeLikely effect on SOL deadline
Triggering date moves laterDeadline moves later (same SOL length)
Triggering date moves earlierDeadline moves earlier
Exception applies (if applicable)Deadline may extend or the “clock” may be treated differently
Wrong jurisdiction selectedOutput becomes unreliable for Maryland deadlines

Key exceptions

Because your jurisdiction data indicates no claim-type-specific sub-rule was found, exceptions are where you can see real differences from the 3-year baseline.

1) Exception-driven SOL changes

Maryland law can recognize circumstances that pause the SOL (tolling) or otherwise affect the limitations analysis. Common categories in SOL practice include:

  • Tolling events (pauses while conditions prevent timely action)
  • Disability-related considerations (in some SOL systems, though the fit depends on the statute and claim type)
  • Special procedural events that can alter timing

Even when the general SOL is 3 years, the existence of qualifying facts can change the calculation.

Pitfall: Don’t assume that “3 years” automatically ends the analysis. If tolling or other exception facts exist, a court may treat the SOL deadline differently than a straight calendar calculation.

2) Practical evidence issues

SOL disputes often depend on documentation, timelines, and credibility of the relevant dates. When you compute deadlines, it helps to maintain a clear record of:

  • the earliest known date relevant to the triggering event
  • any event dates that might support tolling/exception claims
  • consistent documentation of dates (reports, statements, medical records, communications)

3) Adult-victim framing vs. statutory tailoring

You’re focusing on adult-victim rape/sexual assault. Your provided note (“No claim-type-specific sub-rule was found”) is a strong signal for this page’s structure: the default is the 3-year SOL in § 5-106. If future research reveals a statute specifically tailored to a particular offense element, that would be a different page—or an add-on—to update the tool logic and guidance here.

For now, keep the hierarchy clear:

  • Default: 3 years under Md. Code, Cts. & Jud. Proc. § 5-106
  • Then: check for recognized exceptions that can modify the deadline

Statute citation

Maryland’s general statute of limitations period referenced here is:

Use the calculator

DocketMath’s statute-of-limitations tool is designed to turn dates into a clear deadline estimate.

Typical inputs to use

On /tools/statute-of-limitations , you’ll generally be asked for information like:

  • Jurisdiction: Maryland (US-MD)
  • Relevant date (trigger date): the date that starts the clock under the tool’s logic for the SOL scenario
  • SOL category/use case: choose the option that matches the situation you’re trying to evaluate

Output you should expect

After you submit inputs, the calculator will produce:

  • a computed SOL deadline date
  • (often) an estimated remaining time relative to a “calculation date” if the tool includes it
  • a clear statement of the SOL length used—here, the default is 3 years under § 5-106 when no specific sub-rule is selected

How output changes when inputs change

Use these checks to validate the result:

  • If you update the triggering date by 30 days, your deadline should also move by about 30 days (unless a supported exception changes the calculation).
  • If you confirm Maryland as the jurisdiction, you should see the SOL length reflect the 3-year default.
  • If the tool offers exception/tolling toggles, enabling them should shift the deadline relative to the straight 3-year calculation.

Start here: ** /tools/statute-of-limitations

If you want a quick workflow:

  • Step 2: Select **Maryland (US-MD)
  • Step 3: Enter the relevant triggering date
  • Step 4: Review the generated deadline
  • Step 5: If you believe an exception might apply, update the exception-related inputs and recompute

Related reading