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

Overview

In Tennessee, the statute of limitations (SOL) sets the outer time limit for the state to begin a criminal case. For certain serious offenses, including Class B felonies (often discussed alongside “2nd degree” terminology in everyday language), Tennessee uses a specific SOL framework in Tennessee Code Annotated § 40-35-111(e).

DocketMath’s statute-of-limitations calculator helps you translate those statutory time limits into a date range you can track—useful for case triage, evidence review timelines, or verifying whether a charging deadline has run.

Limitation period

For the scenario described in your brief—Class B / 2nd degree felony treatment under Tennessee Code Annotated § 40-35-111(e)(2)—the SOL period is 1 year.

In other words, if the statute in question applies, the state generally must initiate prosecution within 365 days (practically, one year) of the relevant triggering event used by Tennessee law (often tied to the date of the offense and the statutory “commencement” concept).

How the calculator output behaves (high level)

DocketMath’s statute-of-limitations calculator is designed to make the SOL deadline concrete. When you enter a date, it will compute:

• SOL start date: usually based on the offense date (or the date you select as the triggering event)
• SOL end date: the deadline computed from the statutory period
• Time remaining / elapsed: helps you see whether the deadline has likely passed relative to today or a case filing date you enter

Because the SOL period here is 1 year, the computed end date will move one-for-one with changes to the start date. For example:

• If the offense date changes by 10 days, the SOL deadline changes by 10 days.
• If you enter a different “filed/charged” date, the calculator can show different “in time vs. late” outcomes.

Quick timeline example (illustrative)

Assume:

• Offense date: January 10, 2025
• SOL period: 1 year

Then the SOL deadline would land around:

• January 10, 2026 (subject to the calculator’s date computation rules and how “commencement” is treated in the inputs you provide)

Key exceptions

Tennessee’s SOL rules include statutory carve-outs that can extend or change the limitation period depending on the circumstances. Your jurisdiction data lists exceptions V2 and V3 associated with the short 1-year limitation.

Exception V2 (linked to § 40-35-111(e)(2))

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

This indicates that the baseline SOL period for the covered offense class is 1 year, but certain conditions under the same subsection can operate as an exception path. Practically, the key takeaway for your workflow is:

• Don’t assume “1 year” is the full story.
• Verify whether the charge facts place the case inside the subsection’s specific exception mechanism.

Exception V3 (linked to § 40-2-102(a))

Your jurisdiction data also references a second statutory hook:

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

Even though it is also listed as a 1-year item in the brief’s dataset, treat it as a separate statutory regime you may need to account for when you’re computing a deadline. In practice, this can matter if:

• the case theory relies on a particular procedural/commencement rule, or
• your inputs align more closely with one statute’s triggering mechanics than the other.

Checklist for using the calculator effectively

Use the following checklist before trusting the computed deadline:

Statute citation

The governing SOL provision for the situation described in your brief is:

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

You can review the statutory text here:
https://law.justia.com/codes/tennessee/title-40/chapter-35/part-1/section-40-35-111/

Related statutory citation also referenced in your jurisdiction data:

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

Use the calculator

To calculate a likely SOL deadline using DocketMath, start at:
/tools/statute-of-limitations

What to input

Depending on how DocketMath’s tool is set up in your workflow, you’ll typically provide:

• Offense date (or the date selected as the SOL trigger)
• Jurisdiction: **US-TN (Tennessee)
• Offense category / mapping: choose the option that corresponds to Class B / 2nd degree felony treatment under **§ 40-35-111(e)(2)
• (Optional) a comparison date such as charging/filing date to test whether the deadline has been met

How outputs change based on inputs (practical)

• If you move the offense date forward by 30 days, the SOL end date moves forward by about 30 days (because the period is 1 year).
• If you swap to an option that triggers an exception path (V2 or V3), the tool may adjust the computed deadline (even if the dataset labels both as “1 years,” the mechanics can still change).
• If you enter a later “filed/charged” date, the calculator’s comparison will shift from “deadline not reached” to “deadline likely passed” (or vice versa).

Output interpretation

When you run the calculation, focus on these outputs:

• Computed SOL deadline (the “end” date derived from the statute)
• Whether the prosecution date you entered is before or after that deadline
• Any exception indicators the tool surfaces based on your selected offense mapping and date inputs

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