Statute of Limitations for Class D / 4th Degree Felony in District of Columbia

Overview

In the District of Columbia, the statute of limitations (often “SOL”) sets a deadline for the government to file a criminal charge. For a Class D / 4th Degree felony, DocketMath’s statute-of-limitations calculator uses the general/default SOL found in the D.C. Code.

Per the jurisdiction data you provided, D.C. uses a general 3-year limitation period for this category, and no claim-type-specific sub-rule was identified for a different deadline for Class D / 4th Degree felony charges. That means the calculator output should reflect the general rule rather than a special shortened or extended period.

Limitation period

Baseline SOL for Class D / 4th Degree felony (District of Columbia): 3 years.
DocketMath treats this as the default limitation period unless an exception applies (see next section).

What “3 years” typically means in practice

Use this baseline to anchor expectations on questions like:

• How long after the date of the alleged offense a charge may be filed.
• How the deadline changes when you account for a tolling event (if one applies).

How the calculator affects the deadline

When you use DocketMath → /tools/statute-of-limitations, you’ll typically enter:

• Date of offense (the event date)
• (Optionally, depending on the tool UI) tolling-related dates or event markers that the calculator supports

Output behavior you should expect:

• If you enter only the offense date, the tool applies the 3-year general period and calculates the baseline “SOL expiration” date.
• If you add supported tolling inputs, the SOL expiration date may be pushed out by the amount of time the tool calculates as excluded/tolled under the applicable rules.

Checklist for your input gathering:

Key exceptions

Because the District of Columbia SOL landscape includes tolling and other doctrine-based adjustments, the most common reason a charging deadline differs from the baseline is an exception that alters timing.

For Class D / 4th Degree felonies in D.C., your starting point remains the general SOL period—3 years—but you should look for whether any of the following kinds of events apply:

• Tolling events: Certain circumstances can pause or extend the running of the SOL.
• Procedural milestones: Filing, service, or other litigation steps sometimes affect how time is measured depending on the governing rule.
• Jurisdiction-specific adjustments: D.C. procedural statutes and related doctrine may recognize time exclusions in defined situations.

What to do if you’re unsure whether an exception applies

To keep your timeline analysis grounded:

• Use DocketMath first to compute the baseline 3-year deadline.
• Then review the case record for any events that could change SOL running time.
• If you identify a plausible tolling event, re-run the calculator using the tool’s supported tolling inputs.

This workflow helps you avoid the two most frequent errors:

1. Assuming “3 years” is the final word without exception checks.
2. Assuming an exception applies automatically without tying it to a specific timing event the tool can model.

Statute citation

The controlling general/default statute for the limitation period used by DocketMath here is:

• D.C. Code § 23–113(a)(1) — provides the general 3-year limitation period for covered offenses under the default rule.

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

Because you indicated no claim-type-specific sub-rule was found, DocketMath applies this general 3-year period as the baseline for Class D / 4th Degree felony SOL computations in the District of Columbia.

Use the calculator

To calculate the SOL deadline with DocketMath, start here:

• Primary CTA: DocketMath — Statute of Limitations calculator

Step-by-step input guidance

1. Enter the offense date

   • Use the date the alleged conduct occurred.
   • If there are multiple alleged conduct dates, run separate calculations for each relevant date.

2. Run the baseline calculation

   • With only the offense date entered, the calculator uses the general 3-year SOL rule (D.C. Code § 23–113(a)(1)).

3. Add exception/tolling inputs if available

   • If the tool provides fields for tolling events (or time exclusions), enter the specific dates tied to those events.
   • Re-check the result to see whether the expiration date moves forward from the baseline.

How to interpret the output

Most SOL calculators will present something like:

• A baseline SOL expiration date (3 years from offense date)
• An adjusted expiration date (if tolling inputs are provided)

Use this comparison:

• If the adjusted expiration date is later than the baseline, that suggests the model has accounted for a time exclusion.
• If both dates match, either no tolling inputs were provided or none were recognized by the calculator’s structure.

Practical “sanity check” rules

• A 3-year SOL means the baseline should land about 36 months after the offense date (subject to the tool’s date-handling rules).
• If the computed deadline is shorter or longer without any tolling inputs, confirm the calculator inputs—most errors come from entering the wrong event date.

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