Statute of Limitations for Class B / 2nd Degree Felony in District of Columbia

Overview

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

In the District of Columbia, the statute of limitations (SOL) sets the time limit the government has to file a criminal case after an alleged offense. For a Class B / 2nd Degree felony in D.C., the starting point is typically the general rule for felonies, found in D.C. Code § 23–113(a)(1).

Per the jurisdiction data provided for this topic, no claim-type-specific sub-rule was found for this offense category; that means the analysis below uses the general/default SOL period rather than a specialized shorter or longer limit tied to a particular label of felony.

Limitation period

Default SOL for this felony category (general rule)

For felonies subject to D.C. Code § 23–113(a)(1), the general SOL period is:

• 3 years

That period begins to run from the event the statute uses as its triggering point (commonly the date of the offense). DocketMath’s statute-of-limitations calculator focuses on the time window, using dates you provide.

How to use dates correctly

To get a useful output from the calculator, you’ll typically provide:

• Offense date (the alleged act date)
• Filing date (the date charges were filed, if you want to test whether they appear timely)
• (Often) an optional tolling/extended-date input if your workflow accounts for delays

Then the calculator will compute:

• the end of the SOL window (i.e., latest “safe” filing date under a straightforward timeline), and/or
• whether a given filing date falls within 3 years.

What changes the result?

Even with a fixed 3-year baseline, the calculator’s result can change when you input or model additional timing factors, such as:

• a tolling effect (if applicable under D.C. law and your inputs),
• a different triggering date than the one you assume (for example, discovery-based triggers or other statute-specific timing in other contexts), or
• charge timing that doesn’t align neatly to a single alleged offense date.

Because this page is using the general/default rule, you should treat the computed 3-year window as the baseline unless you have identified a specific exception or tolling factor that applies to your facts.

Key exceptions

The general 3-year period is the baseline, but D.C. criminal SOL analysis can involve exceptions and tolling doctrines. Here are the categories you should look for when reviewing timing:

• Tolling provisions: Some legal events can pause (or extend) the SOL clock.
• Special statutory circumstances: Certain offenses or procedural events can create different timing rules than the default.
• Later-filed charges: If charges are amended or re-filed, the timeline question can shift from “initial event” to “charge filing” depending on the procedural posture.

Practical checklist for exception review

Before relying on a computed deadline, confirm you’ve checked:

If any box is uncertain, the most reliable approach is to align your inputs with the dates and procedural events that match how the SOL issue would be evaluated in the case record.

Statute citation

The default statute of limitations period for the felony category covered by this page is:

• D.C. Code § 23–113(a)(1) — 3 years (general felony SOL period)

Source: https://law.justia.com/codes/district-of-columbia/2014/division-iv/title-23/chapter-1/section-23-113/

Use the calculator

DocketMath’s Statute of Limitations calculator is designed to turn the baseline rule into a concrete deadline.

Inputs to expect

Use dates that match your record:

1. Offense date (when the alleged felony conduct occurred)
2. Filing date (when charges were filed)

   • If you’re doing a “timely/untimely” check, this is critical.
3. Optional (depending on your workflow):

   • Tolling/adjustment dates if you’re modeling a pause or extension

How the output works (baseline logic)

Because the default period here is 3 years under D.C. Code § 23–113(a)(1), DocketMath will compute the SOL end date by applying:

• Offense date + 3 years
• then compare that to your filing date (if provided)

How outputs change

• If you move the offense date forward, the SOL end date also moves forward (shorter window remains the same length, but occurs later).
• If you move the filing date forward past the computed end date, the case will show as outside the 3-year window under the default model.
• If you enter tolling/extension inputs, the SOL end date can shift later—changing the “timely/untimely” result under the calculator’s assumptions.

For a fast workflow, start with the simplest baseline first (offense date and filing date). If your result is close to the deadline, that’s when it’s especially worth checking whether any tolling or other timing complication applies to your specific situation.

Primary CTA

Use the tool here: /tools/statute-of-limitations

Related reading

• Choosing the right statute of limitations tool for Vermont — Tool comparison
• Statute of limitations in Singapore: how to estimate the deadline — How-to guide
• Choosing the right statute of limitations tool for Connecticut — Tool comparison