Statute of Limitations for Class C / 3rd Degree Felony in Michigan

6 min read

Published March 22, 2026 • By DocketMath Team

Overview

In Michigan, the statute of limitations (SOL) sets a deadline for the state to file criminal charges or (in some contexts) to bring the case to prosecutorial action. For a Class C / 3rd degree felony, Michigan generally uses a six-year limitations period under the state’s general felony SOL rule.

This page focuses on the default rule Michigan applies when no special, claim-type-specific SOL exception is triggered. Based on the jurisdiction data provided, no separate class-based sub-rule was found for a specific felony degree beyond the general framework—so the general default period is what you should expect to see applied most often.

Note: This is general information about Michigan’s SOL structure. SOL rules can be affected by case history (for example, whether proceedings were previously started) and by specific procedural events. For anything time-sensitive, verify the timeline against the charging and case-docket record.

Limitation period

Default SOL for Class C / 3rd degree felony

Michigan’s general SOL for felonies uses a 6-year period.

  • General SOL period (default): 6 years
  • Applies to: the typical situation where you’re analyzing whether prosecution was initiated within the statutory deadline
  • Outcome if the deadline is missed: the defense may seek dismissal based on SOL, assuming the facts support that the statutory period has expired and no exception applies

When you start counting the clock

The practical challenge is determining the correct start date for SOL calculation. The statute itself uses concepts tied to the offense conduct and prosecution timing. In day-to-day use, that usually means you’re looking for:

  • the date the offense occurred (or the date the offense is treated as having occurred), and
  • the date charges were filed / prosecution began in a way recognized by Michigan’s procedural rules

Because SOL timing depends on specific facts and procedural posture, DocketMath’s calculator is designed for transparency: you provide key dates, and the output shows the expiration date and whether a proposed filing date falls before or after that deadline.

A quick “timeline” example

Here’s a simplified example to show how the math typically works (not legal advice):

ItemExample dateWhat it affects
Offense dateJan 15, 2020Used as the starting point for the SOL period
Default SOL period6 yearsThe statutory duration
Estimated SOL expirationJan 15, 2026Benchmarks whether prosecution is timely
Filing date to checkMar 1, 2026If after expiration, it suggests untimeliness under the default rule

Key exceptions

Michigan’s SOL framework includes circumstances that can extend, toll, or otherwise affect the limitations period. The most accurate way to handle exceptions is to identify what procedural events actually happened in the case.

Because the content brief specifies “no claim-type-specific sub-rule was found” and provides only the general SOL period, this section stays practical and focuses on what to look for when you suspect an exception may be in play.

Common categories to verify in the record

Check whether any of the following appear in the case chronology:

  • Prior attempts to prosecute: If the state previously filed something and the case later changed posture, the timeline may be affected under Michigan law.
  • Defendant-related procedural events: Certain events can alter the limitations analysis depending on what the statute says and how courts interpret it.
  • Jurisdictional or procedural milestones: SOL analysis often depends on what counts as “initiating” prosecution under Michigan practice for the given stage.

Warning: Don’t assume “6 years” automatically controls. Even when the general SOL is 6 years, Michigan law can recognize situations that change the effective timeline. A correct SOL determination requires aligning the statutory trigger and the procedural record.

How this affects DocketMath outputs

DocketMath’s calculator is built around the default rule (6 years) given in the jurisdiction data and your inputs. If you later discover that an exception or tolling event likely applies, the calculator result may need to be adjusted or re-run with the correct controlling dates tied to the exception.

Statute citation

Michigan’s general statute of limitations for criminal prosecutions provides the default 6-year felony period.

  • General statute: **MCL § 767.24(1)
  • General SOL period (default): 6 years
  • Jurisdiction source (provided): https://www.michigan.gov

This rule is the baseline for analyzing timeliness of prosecution for a Class C / 3rd degree felony when no exception is triggered.

Use the calculator

DocketMath’s Statute of Limitations calculator helps you estimate the SOL expiration date using the default 6-year period for Michigan felonies.

Primary CTA: **/tools/statute-of-limitations

What you’ll typically input

Use the calculator to define your timeline. Common inputs include:

  • Offense date (the date you’re treating as the statutory starting point)
  • Proposed filing date (the date you want to test for timeliness)

What the output changes when dates change

The calculator output is driven by two core mechanics:

  1. Offense date shifts the expiration date
    • Move the offense date forward by 30 days → expiration date typically moves forward by about the same amount.
  2. Filing date determines whether the prosecution is “before” or “after” expiration
    • A filing date that falls even a day after the estimated expiration suggests the default 6-year limit has run, absent an exception.

Interpreting the result

When you run the calculator, you should look for:

  • Calculated expiration date under the default 6-year rule
  • Timeliness indicator (e.g., timely vs. potentially time-barred) based on whether the proposed filing date falls on or before that date

If the result indicates a borderline timeline, revisit the record for facts that might affect the SOL analysis (especially any procedural events that could change the controlling start/stop dates).

Related reading