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

Overview

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

In Tennessee, the statute of limitations (SOL) sets a deadline for the state to bring criminal charges. For a Class C / 3rd Degree felony, Tennessee generally uses a relatively short limitations window compared with many other felonies.

DocketMath’s statute-of-limitations calculator can help you model the timeline using the relevant Tennessee rules—especially the 1-year limitations period that applies here.

Limitation period

Baseline SOL for Class C / 3rd Degree felony in Tennessee

For a Class C felony (often referred to in practice as a “3rd degree felony”), Tennessee Code Annotated provides a 1-year limitations period.

• SOL period: 1 year
• For: Class C felony / 3rd-degree felony
• Primary authority: **Tenn. Code Ann. § 40-35-111(e)(2)

What “1 year” means in practice

SOL periods are measured from the time the statute specifies the clock starts. While the general framework is straightforward, two practical points often determine whether a prosecution is timely:

• Start date matters: The SOL clock depends on the triggering event defined in the statute or exception.
• Filing vs. arrest vs. indictment: Different steps in a criminal case can occur on different dates. The limitations analysis typically turns on when the prosecution commenced under Tennessee’s procedural framework.

Because SOL disputes often hinge on the exact date the clock started, DocketMath’s calculator is designed to help you compare potential dates and see how the output changes.

Key exceptions

Tennessee’s limitations framework includes exceptions that can extend (or otherwise affect) when the SOL clock applies. For Class C felonies, the Tennessee statute includes provisions that function as extensions and carve-outs depending on the situation.

Exception mechanics that can change the deadline

Below are two Tennessee provisions you should know because they affect timing outcomes in practice:

• Tennessee Code Annotated § 40-35-111(e)(2) — 1 year — exception V2

  • This is the core rule providing the 1-year period in the Class C felony category.
  • In a calculator workflow, this is often the governing “bucket” for the category you selected.

• Tenn. Code Ann. § 40-2-102(a) — 1 year — exception V3

  • This provision operates as an additional timing rule used in certain circumstances.
  • In some fact patterns, it can yield a separate 1-year endpoint that overlaps with—but is not identical to—the main limitations provision logic.

Checklist: inputs that commonly drive exception outcomes

When you use DocketMath to model SOL, these inputs are frequently what determine whether you stay within the deadline or exceed it:

Statute citation

The governing Tennessee provision for the 1-year SOL period for Class C felony / 3rd degree felony is:

• Tennessee Code Annotated § 40-35-111(e)(2)
  https://law.justia.com/codes/tennessee/title-40/chapter-35/part-1/section-40-35-111/

Related timing rule that may come into play in certain situations:

• Tenn. Code Ann. § 40-2-102(a)
  (Used in DocketMath’s exception logic as V3 alongside the primary V2 reference bucket.)

Use the calculator

DocketMath’s statute-of-limitations tool is built to translate the legal timeline into a clear “deadline vs. date” comparison.

How to run a basic Tennessee Class C / 3rd-degree felony calculation

1. Open: /tools/statute-of-limitations
2. Set:

   • Jurisdiction: **Tennessee (US-TN)
   • Offense class: Class C / 3rd degree felony
   • SOL rule: **Tennessee Code Annotated § 40-35-111(e)(2) (1 year — exception V2)
3. Enter dates:

   • Offense-related trigger date (the date your timeline uses as the SOL start)
   • Prosecution/charging date to test for timeliness
4. Review the output:

   • The calculated end date (SOL expiration)
   • Whether the chosen prosecution date falls before or after the expiration

How outputs change when you adjust inputs

Here’s what typically happens when you change certain inputs:

• If you move the trigger date later by 30 days, the SOL expiration date generally moves later by about 30 days as well (for a 1-year rule).
• If you choose a different exception bucket (e.g., V3 via Tenn. Code Ann. § 40-2-102(a)), you may see a different computed end date—even when both rules show a 1-year period—because the operative trigger or computation framework may differ.

Quick sanity checks (before you rely on the result)

• Confirm the case truly fits Class C (not just a “third-degree” label from a complaint summary).
• Ensure the “date you’re testing” is the correct one for your timeline (a SOL analysis can hinge on the charging/prosecution commencement step).
• Recheck time zone/date formatting—especially if you’re copying dates from documents.

Primary CTA: /tools/statute-of-limitations

Related reading

• Choosing the right statute of limitations tool for Vermont — How to choose the right calculator
• Statute of limitations in Singapore: how to estimate the deadline — Full how-to guide with jurisdiction-specific rules
• Choosing the right statute of limitations tool for Connecticut — How to choose the right calculator