Statute of Limitations for Class B / 2nd Degree Felony in South Dakota

6 min read

Published March 22, 2026 • By DocketMath Team

Overview

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

In South Dakota, the statute of limitations (SOL) sets a deadline for the State to file (or proceed with) criminal charges. For many offenses, the deadline is governed by a general limitations rule found at SDCL 22-14-1.

This post focuses on the general/default limitation period stated in South Dakota law: 3 years. The jurisdiction data provided for this topic does not identify a separate, charge-specific sub-rule for “Class B / 2nd Degree Felony,” so this article treats the 3-year general SOL as the applicable rule for your use case. If you need a definitive answer for a particular charge, you’ll want to verify the exact offense label and elements in the South Dakota statutes.

Note: This is a reference overview, not legal advice. SOL calculations can be affected by case facts (for example, when the alleged conduct occurred, what was charged, and whether any statutory tolling applies).

Limitation period

Default SOL: 3 years under SDCL 22-14-1

South Dakota’s general criminal limitations period (per the provided jurisdiction data) is:

  • General SOL period: 3 years
  • General statute: SDCL 22-14-1

Because no charge-type-specific sub-rule was found for “Class B / 2nd Degree Felony,” you should treat 3 years as the default clock unless you identify a statutory exception or a recognized tolling event.

How to think about the timeline (practical workflow)

Use a “backwards” approach—start from the date charges were filed (or the date you are checking for) and count:

  1. Find the offense date (the date the conduct occurred, as alleged).
  2. Determine the relevant deadline = offense date + 3 years.
  3. Compare your deadline to the filing / charging date (or procedural milestone you care about).
  4. If the dates fall beyond 3 years, you then check whether any exception/tolling could pause or extend the SOL.

Common inputs for the DocketMath SOL calculator

When you use DocketMath’s statute-of-limitations calculator (primary CTA: /tools/statute-of-limitations), you typically enter:

  • Offense date (or start date of the conduct, depending on the situation)
  • Jurisdiction: South Dakota (US-SD)
  • SOL rule selection: default/general rule (since this topic is using the general/default period)
  • Target date: the date you want to compare against (often the charge filing date)

The calculator output will change if you adjust the target date or the offense date, but the base SOL stays 3 years under SDCL 22-14-1 for this default framework.

Checklist: before you rely on the 3-year number

Key exceptions

South Dakota SOL rules can include circumstances that extend, pause, or otherwise affect the limitations deadline. Even when the default period is 3 years, a case may still proceed if a statutory exception applies.

Because this specific topic brief didn’t include additional charge-specific sub-rules, the “key exceptions” you should look for are typically statutory tolling provisions and procedural events that the SOL statute recognizes.

Here are the categories you should actively check in the case record:

  • Tolling events tied to the defendant’s status
    For example, if the statutory scheme allows an SOL pause during certain periods (such as absence from the state or other defined circumstances), that can affect the running time.

  • Discovery or reporting conditions (when applicable)
    Some SOL structures in criminal law include special rules when facts are concealed or discovered later. Not every offense has this, but it’s a category to verify against the statute.

  • Procedural interruptions or re-filing scenarios
    If charges were dismissed and later refiled, the limitations calculation may depend on how the statute treats interruptions or the effect of earlier filings.

Warning: SOL exceptions are highly statute- and fact-specific. A correct “3 years” default under SDCL 22-14-1 can become incomplete if tolling applies—so you should review the exact statutory language that governs the specific procedural posture of the case.

Practical “exception check” approach

Use this order so you don’t miss the obvious:

  1. Start with the default: offense date + 3 years
  2. Review the charging chronology: filing dates, amendments, dismissals, and re-filings
  3. Look for statutory tolling triggers: anything the State cites to extend the SOL
  4. Confirm the exact charged offense label and its statutory mapping
    This matters because SOL treatment often tracks the charged offense framework, not just the everyday description.

If you want the cleanest workflow, run the base calculation first with DocketMath, then use your case timeline to test whether any tolling/exception events could shift the result.

Statute citation

South Dakota’s general/default criminal statute of limitations for the period discussed here is:

  • SDCL 22-14-1
    General SOL period: 3 years

Because the jurisdiction data indicates no charge-type-specific sub-rule was found for “Class B / 2nd Degree Felony,” this post uses SDCL 22-14-1’s general 3-year period as the default rule.

Use the calculator

You can calculate the deadline using DocketMath’s statute-of-limitations tool here: [ /tools/statute-of-limitations ].

Before you run it, decide what your “comparison date” should be:

  • If you’re checking whether charges were timely, enter the charging / filing date as the target.
  • If you’re evaluating exposure based on a known event window, enter the relevant milestone date you care about.

What to expect from the output

With the default/general SOL rule applied, the calculator should reflect:

  • Base period: 3 years (per SDCL 22-14-1)
  • Deadline logic: offense date + 3 years, then compare to your target date

To see how outputs change:

  • If you move the target date later, you’ll more likely fall beyond the 3-year deadline.
  • If you move the offense date earlier, the deadline gets earlier, making timeliness less likely under the default rule.
  • If you switch away from the default/general rule (only if your workflow identifies a different SOL rule), the output can change materially—so confirm the selected rule before relying on results.

Quick runbook:

Sources and references

Start with the primary authority for South Dakota and confirm the effective date before relying on any output. If the rule has been amended, update the inputs and rerun the calculation.

Related reading