Statute of Limitations for Class D / 4th Degree Felony in South Carolina

6 min read

Published March 22, 2026 • By DocketMath Team

Overview

In South Carolina, the statute of limitations (“SOL”) sets a deadline for the State to file—or sometimes re-file—criminal charges. For a Class D / 4th Degree felony, the relevant limitation period is typically 3 years.

DocketMath’s statute-of-limitations calculator helps you model how the SOL deadline changes based on key timeline inputs (like the offense date and the triggering “start” date). Use it to understand the calendar mechanics—not to decide whether a case should be dismissed.

Note: This article is a reference guide to South Carolina’s SOL framework. It’s not legal advice and doesn’t replace case-specific review of charging documents, tolling events, and procedural history.

Limitation period

For a Class D / 4th Degree felony, South Carolina’s general limitations rule provides a 3-year SOL.

What the “3-year” clock means in practice

Think of the SOL deadline as a calendar date derived from an offense-related starting point, commonly tied to when the crime was committed. In a basic timeline:

  • Offense date (example: 2022-06-15)
  • 3-year SOL expiration (example: 2025-06-15)
  • If prosecution/charging occurs after the expiration date (and no tolling applies), the charge may be time-barred.

Because the calculator uses your inputs to compute a deadline, even a small date shift can change the output by days or months.

Typical inputs the calculator uses

When you use DocketMath’s statute-of-limitations tool, you’ll generally input:

  • Offense date
  • **Jurisdiction (US-SC)
  • Charge level / felony class (here, Class D / 4th Degree felony)
  • Optional timeline markers that can affect the analysis (depending on how the tool is configured)

Output you should expect

DocketMath will compute a calculated SOL expiration date using South Carolina’s 3-year rule for this class level, then show how the result changes if you adjust dates.

Check the output date and compare it to the relevant procedural milestone you care about (often the filing/charging date).

Key exceptions

South Carolina’s SOL isn’t always a clean “offense date + 3 years.” Certain statutory exceptions and tolling concepts can alter the analysis. Even if the baseline period is 3 years, exceptions can extend or otherwise affect the deadline.

Exception categories to watch for

The statute references exceptions, including a specific exception mapping shown in DocketMath’s jurisdiction data. For South Carolina’s 3-year framework, the data includes:

  • GS 15-1 — 3 years — exception V1
  • South Carolina Code of Laws §16-1-20 — 3 years — exception V3

Even without going into every fact pattern, here’s how to approach exceptions practically:

1) Identify what “starts” the clock and what interrupts it

Exceptions often relate to circumstances such as:

  • the time when the offense is deemed to have occurred (or when the charge is effectively triggered),
  • whether the accused is absent or otherwise unavailable,
  • whether particular statutory circumstances toll the SOL.

In other words, don’t assume that only the offense date matters.

2) Confirm which statutory provision applies to your charge

Different provisions can apply depending on:

  • the offense category,
  • the charging wording,
  • whether the case involves a particular type of conduct governed by a specific section.

DocketMath’s goal is to give you a structured way to compute the baseline and then reflect the statutory exception logic available in the tool’s model.

3) Track procedural timing precisely

If the SOL is the issue, “what happened when” becomes crucial. Common pitfalls include:

  • using the wrong “filing” date (complaint vs. indictment vs. information),
  • overlooking amendments or re-filings,
  • missing an exception-related event tied to a specific date.

Pitfall: Many SOL disputes turn on the distinction between the date the offense occurred and the date prosecution was initiated. If you enter only one date, your output may look precise but still be incomplete for real-world deadlines.

Quick comparison: baseline vs. exception-affected outcomes

ScenarioBaseline SOL (3 years)Exception impactWhat DocketMath helps you do
No exception appliesOffense date + 3 yearsNoneCompute the expiration date
Exception/tolling appliesOffense date + 3 yearsDeadline may shift later (or clock may be handled differently)Recalculate using the tool’s exception logic and dates
Wrong provision/charge level usedOffense date + 3 yearsHigh risk of mismatchEnsure you select the correct charge class for this SOL model

Statute citation

South Carolina’s limitation framework for felonies includes a 3-year period as reflected in the jurisdiction data for this class level:

When you’re working from a SOL standpoint, citations matter because exceptions and special timing rules often live in the statute text and accompanying subsections.

Use the calculator

To model the SOL timeline for a Class D / 4th Degree felony in South Carolina, use DocketMath’s SOL calculator:

How to use it effectively (inputs that change the output)

Use these practical steps to keep your calculations grounded:

  • Enter the offense date
    This is the anchor date. A shift of even a few days will shift the computed expiration date.
  • Select the jurisdiction: US-SC
  • Select the charge level/class: Class D / 4th Degree felony
  • Enter the relevant procedural date(s) you want to compare (if the tool asks)
    • Example: the date the State initiated prosecution (based on the tool’s defined “comparison date” concept).
  • If the tool supports exception toggles/inputs, use them to reflect the statutory exception category your facts align with (as represented in the tool’s model).

Reading the result

After calculation, compare:

  • Calculated SOL expiration date vs.
  • Your chosen prosecution/filing milestone date

If your milestone date is earlier than the expiration date, the baseline SOL timing generally supports timely charging. If later, the baseline suggests a time-bar—subject to exceptions/tolling logic.

Warning: SOL calculations are date-driven and can be sensitive to procedural details (like the exact charging date). Treat the calculator output as a timing model and verify the underlying dates in your case documents.

Related reading