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

5 min read

Published March 22, 2026 • By DocketMath Team

This article is for informational purposes only and does not constitute legal advice. Laws change frequently — verify all citations with current official sources.

Overview

In Ohio, the statute of limitations (SOL) for bringing a criminal charge is governed by Ohio Rev. Code § 2901.13. For a Class B / 2nd degree felony question, the core issue is usually timing: how long the State has to file the charge after the offense (or after certain triggering events).

DocketMath’s statute-of-limitations tool can help you compute the end date based on the relevant SOL period and the input dates you provide. For Ohio, the SOL period for this category is 0.5 years under the applicable rule set used by DocketMath (see “Limitation period” and the exception noted below).

Note: SOL calculations can hinge on details like the exact offense date and whether any exception applies. This page explains the rule structure and how DocketMath approaches the math—rather than offering legal advice.

Limitation period

Baseline SOL: 0.5 years

For Ohio Rev. Code § 2901.13, the relevant SOL period for this class (Class B / 2nd degree felony) is 0.5 years.

In practical terms, a “0.5 years” SOL is treated as half of a year for calculation purposes. If you start with an offense date of, for example:

Offense date: January 1, 2026
Half-year SOL window: ~6 months
Calculated SOL deadline: around July 1, 2026 (subject to how the tool rounds dates)

Because date handling matters, always use actual calendar dates (not approximate “about” dates) when running a DocketMath calculation.

Inputs that change the output

DocketMath’s statute-of-limitations calculation generally depends on these inputs:

Offense date (the starting point)
Whether an exception is selected/triggered (see “Key exceptions”)
Your jurisdiction selection: **Ohio (US-OH)

Changing any of those inputs can shift the computed deadline. The most common shift is selecting an exception that extends or alters the SOL window.

Quick reference: timing math at a glance

Item	Ohio rule used here	Effect on deadline
Baseline SOL for this felony category	0.5 years	Moves the deadline to ~6 months after the starting date
Exception applies	“Exception V3” in the DocketMath rule set	Can change whether/when the deadline extends or behaves differently

Key exceptions

Exception V3

Under the rule set provided for this Ohio SOL category, the applicable exception is listed as:

Ohio Rev. Code § 2901.13 — 0.5 years — exception V3

What this means for calculations is straightforward: if “exception V3” applies to the facts of the case and you select it in DocketMath, the tool’s computed deadline will follow the exception logic rather than the baseline 0.5-year window.

How to think about exceptions (without guessing facts)

Because exceptions are fact-dependent, avoid running a SOL calculation based on assumptions. Instead, use a checklist approach:

Warning: If an exception does not actually apply, an SOL deadline computed using an exception may be too late—which can materially change the outcome of a timing question.

Practical approach

If you’re building a case timeline (for review, drafting, or internal case management), it’s often useful to compute two dates:

Baseline SOL deadline (0.5 years)
Exception-based deadline (V3 logic)

Then compare those dates with the charge filing or other relevant milestone dates you’re tracking.

Statute citation

The governing statute for Ohio’s criminal statute of limitations framework is:

Ohio Rev. Code § 2901.13

Source (Ohio’s official code publication):

https://codes.ohio.gov/assets/laws/revised-code/authenticated/29/2901/2901.13/7-16-2015/2901.13-7-16-2015.pdf

This page’s Ohio-specific calculation parameters for Class B / 2nd degree felony are captured as:

SOL Period: 0.5 years
Exception: V3

Use the calculator

DocketMath’s statute-of-limitations tool is designed to turn the statute’s timing rule into a usable deadline.

Primary CTA: **Use the calculator

Recommended workflow (quick and repeatable)

Select Ohio (US-OH) in the tool.
Enter the offense date you want to start from.
Choose whether you’re applying exception V3.
Run the calculation and capture:
- the baseline SOL deadline, and
- the exception-adjusted deadline (if applicable).

What you should watch for in the output

To avoid surprises, review these elements in the calculator results:

Rounding/normalization of “0.5 years” into calendar dates
Whether the tool shows a baseline-only date or an exception-adjusted date
The date label the tool uses (e.g., “deadline” vs. “end of limitations period”)

Pitfall: Many SOL timelines look “close enough” when converted to months, but a difference of even a few days can matter—especially when you’re comparing the deadline to a filing date or other docket milestone.

Example input/output behavior (conceptual)

If the offense date is in January and you use 0.5 years, the output typically lands around mid-year. When you enable exception V3, the deadline may move later or follow a different computation path—so your comparison against filing dates should always align with the exception selection.