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

6 min read

Published March 22, 2026 • By DocketMath Team

Overview

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

Idaho’s statute of limitations (SOL) sets deadlines for the State to file—or in some situations, to continue—criminal prosecutions. For a Class C / 3rd degree felony, Idaho uses a general/default SOL framework unless a specific exception applies.

For Idaho, the key starting point is Idaho Code § 19-403, which provides a general SOL period of 2 years for certain offenses, including many felony prosecutions when no longer-specific rule is triggered. In other words, no class-/charge-specific sub-rule for Class C / “3rd degree” was located in the materials provided, so the 2-year general period is the applicable baseline you should use for calculating deadlines.

Note: SOL rules can be affected by procedural events (like indictments, tolling, or defendant-initiated proceedings). This post explains the baseline period and the most common exception categories, but it’s not legal advice.

Limitation period

Baseline SOL for a Class C / 3rd degree felony (Idaho)

  • General SOL period: 2 years
  • General statute: Idaho Code § 19-403

Because the available jurisdiction data indicates no claim-type-specific sub-rule was found, treat this as the default SOL for a Class C / 3rd degree felony in Idaho: the prosecution must be started within 2 years of the applicable starting date determined under Idaho’s SOL rules.

What “2 years” means in practice

When you see “2 years” in an SOL context, the “clock” starts at the statute’s triggering point (often the date of the offense or another date specified by statute/rule). Exact starting dates can depend on how the charge is pled and how Idaho treats the offense conduct timing.

To keep calculations consistent, DocketMath’s statute-of-limitations calculator uses clear inputs (like “offense date”) so you can see the computed deadline in one place.

Inputs that change the output (what to enter in DocketMath)

When using DocketMath’s statute-of-limitations tool, you typically work with these inputs:

  • Offense date (or the date the alleged criminal conduct occurred)
  • Case action date (e.g., filing/charging date), if you want a pass/fail view
  • Tolling/exception flags, if you’re assessing whether an exception category may apply (more on that below)

How the output changes:

  • Move the offense date forward → the SOL deadline moves forward.
  • Compare the charging/filing date against the computed SOL deadline → you’ll get a “within SOL” vs. “outside SOL” result, assuming no tolling/exception.
  • Toggle an exception/tolling flag → the deadline may shift, depending on the nature of the exception category you select.

If you’re not sure whether an exception could apply, start with the baseline 2-year calculation first; then evaluate whether your fact pattern includes exception triggers.

Key exceptions

Idaho SOL practice includes multiple concepts that can extend or pause timelines. The most common categories to look for are:

1) Tolling for absence or concealment

Many jurisdictions toll SOL when the defendant is absent from the state or cannot be located. Idaho has its own tolling approaches; these can effectively extend the filing deadline beyond the baseline.

2) Procedural events that affect timing

Certain procedural steps (for example, if proceedings are initiated and later resumed) can alter how SOL is measured, especially where statutes speak to the validity of the prosecution and the timing of subsequent actions.

3) Exceptions based on the nature of the offense or circumstances

Some offenses have different SOL rules than the general period. Your provided jurisdiction data indicates no class-/charge-specific sub-rule was found here—meaning the default 2-year period is the baseline—but that does not eliminate the possibility of exceptions tied to:

  • specific conduct details,
  • victim-related circumstances,
  • or statutory categories outside the general rubric.

4) Boundaries and evidence issues

Even when a baseline applies, disputes often arise over:

  • the event date that starts the clock,
  • whether the alleged conduct falls squarely within the charged classification, and
  • whether an exception applies based on the record.

Warning: A SOL deadline can be extended by events that are easy to miss in the paperwork (for instance, administrative delays, service issues, or filings that change the case posture). Always map the actual timeline of case filings and any relevant defendant status events.

Exception checklist (practical screening)

Use the following checklist to quickly identify whether you should investigate exceptions:

Statute citation

Based on the jurisdiction data supplied for this topic:

  • General/default SOL: 2 years
  • No class-specific/claim-specific sub-rule was found for Class C / 3rd degree felony within the provided materials.

Use the calculator

DocketMath’s statute-of-limitations tool helps you translate the 2-year general period into a clear deadline using your case timeline: /tools/statute-of-limitations.

Step-by-step

  1. Go to the tool: /tools/statute-of-limitations
  2. Select Idaho (US-ID).
  3. Enter the offense date (this drives the baseline 2-year deadline).
  4. (Optional) Enter the charging/filing date to test whether it falls:
    • within the calculated SOL deadline, or
    • after the deadline.
  5. If you are assessing possible exception/tolling categories, toggle the relevant option(s) available in the tool, then re-check the computed deadline.

How to interpret the output

  • If the charging date is before or on the calculated deadline: the charge is generally within the baseline SOL window (absent exceptions).
  • If the charging date is after the calculated deadline: it may fall outside the baseline SOL window, and you should review whether any statutory exception/tolling could apply.

Note: DocketMath is designed to compute deadlines from the rule you select. When an exception might be in play, the most reliable workflow is: (1) compute the baseline, (2) then compute again with exception/tolling assumptions, and (3) compare both results to see how much the timeline shifts.

Related reading