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

5 min read

Published March 22, 2026 • By DocketMath Team

Overview

Michigan’s statute of limitations (SOL) sets a deadline for when the state must file (or proceed with) a criminal case after an alleged offense. For a Class B felony—commonly referred to as a 2nd degree felony in Michigan practice categories—Michigan’s general rule is governed by the general SOL statute rather than a claim-type-specific carveout.

Per the jurisdiction data provided for this reference page:

  • General SOL period (default rule): 6 years
  • General statute: **MCL § 767.24(1)

Note: This page uses Michigan’s general/default SOL rule (not a special class-by-class sub-rule), because no offense-specific or claim-type-specific sub-rule was provided in the jurisdiction data.

For anyone using DocketMath’s statute-of-limitations calculator, the practical takeaway is straightforward: the output typically turns on (1) the offense date (or last act date, depending on charging facts) and (2) the baseline SOL length (6 years) under MCL § 767.24(1), with additional time sometimes added or subtracted when recognized exceptions apply.

Limitation period

Baseline period for a Class B / 2nd degree felony in Michigan

Under MCL § 767.24(1), the general/default SOL period is:

  • 6 years

This means the state generally must initiate the prosecution within 6 years from the relevant triggering date tied to the charge (commonly the date of the offense or the last day of conduct, depending on how the case is pleaded).

How the SOL “deadline” changes when you run the calculator

DocketMath’s statute-of-limitations calculator is designed to make the timeline concrete. Typically, the calculator uses these concepts:

  • Input: Offense date (start date)
    Changes the computed deadline directly, because the SOL runs forward from that date.
  • Input: Jurisdiction (Michigan)
    Selects Michigan’s baseline rule (here, 6 years).
  • Outputs: SOL “expiration” date window
    The calculator will compute a “latest possible” date under the baseline assumption and then adjust if you enable/enter exception inputs (when available).

In practical terms:

  • If the offense occurred earlier, the SOL deadline is earlier.
  • If the offense occurred later, the SOL deadline is later.
  • If an exception pauses, tolls, or otherwise modifies the running time, the effective expiration date can shift beyond the straightforward 6-year date.

Quick comparison table (baseline only)

ScenarioOffense dateBaseline SOL (6 years)What the baseline result changes
Earlier conduct2018-03-012024-03-01Deadline is earlier
Later conduct2020-08-152026-08-15Deadline is later

Warning: A baseline SOL calculation is not the whole story. Michigan law can treat certain circumstances as pausing or changing the SOL clock, so the calculator’s final output may depend on whether those exceptions are applicable and entered.

Key exceptions

Because this is a reference page built on the general/default SOL rule from MCL § 767.24(1), exceptions are the main place where the straightforward “6 years from the offense date” approach can change.

Below are categories of exceptions to watch for in Michigan SOL practice. This is not legal advice; treat it as a checklist for what to confirm using the statute and the case record:

  • Tolling / pause of the clock
    • Some circumstances can delay how long the SOL is considered “running.”
  • Defendant-related absence or evasion
    • Events that prevent normal prosecution can affect timing calculations.
  • Procedural events
    • Certain filing or continuation events can interact with timing depending on how the case is procedurally posture.

If you’re using DocketMath, the calculator’s value is that it helps you consistently translate these concepts into dates—but you’ll still need the underlying facts to determine whether an exception actually applies to your situation.

Checklist for calculator users (practical inputs to gather)

Pitfall: Don’t assume the “6 years” baseline always produces the true deadline. If tolling or other timing-altering circumstances exist, the effective SOL expiration date can move—sometimes by a lot—because SOL calculations can be fact-driven.

Statute citation

The baseline statute for Michigan’s general SOL period used here is:

  • MCL § 767.24(1) — **General statute of limitations (default)
    • 6-year limitation period (as provided in the jurisdiction data for this reference page)

Source used for jurisdiction data:

  • Michigan.gov (as indicated in the jurisdiction dataset)

Note: This page explicitly treats MCL § 767.24(1) as the general/default rule for the Class B / 2nd degree felony timeline presented, because no claim-type-specific sub-rule was provided.

Use the calculator

Use DocketMath’s statute-of-limitations tool to convert the 6-year rule into specific dates for Michigan.

Primary CTA: /tools/statute-of-limitations

When you open the tool, focus on these workflow steps:

  1. **Select Michigan (US-MI)
  2. Enter the offense date (the clock start)
  3. Confirm charge category as Class B / 2nd degree felony
  4. Apply exception inputs if the tool provides them
    • If the calculator includes tolling/exception fields, enter only the facts you can support (based on the record)

Example of how outputs change

  • If the calculator computes a baseline expiration date of 2026-08-15 from a 2020-08-15 offense date, then:
    • adding a pause/tolling period (if applicable) would likely push the expiration date later
    • leaving exceptions blank keeps the computed date at the 6-year baseline

To keep the results audit-friendly, consider saving:

  • the offense date you entered
  • the computed baseline SOL expiration
  • any exception fields you toggled or filled in
  • the tool’s final “deadline” output

If you want to see how DocketMath structures timing calculations, you can also review related functionality at: View more tools

Sources and references

Start with the primary authority for Michigan 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