Statute of Limitations for Class C / Petty Misdemeanor in Ohio
5 min read
Published February 18, 2026 • Updated March 22, 2026 • By DocketMath Team
Trust release 4
This page has legal or numeric text that still needs claim-level inventory before we can treat it as verified.
Overview
In Ohio, the “statute of limitations” (SOL) is the time limit the state generally has to file criminal charges after an alleged offense occurs. For Class C misdemeanors and petty offenses, Ohio’s limitations period is short—6 months—because the state must start a case quickly.
This guide focuses on the SOL period that applies to Class C misdemeanor / petty-misdemeanor style charges in Ohio, using Ohio Rev. Code § 2901.13 as the controlling statute. It’s written to help you run the DocketMath statute-of-limitations calculator effectively and understand how the time window changes based on key rules inside the statute.
Note: This is a general reference for Ohio’s limitations rules. It’s not legal advice, and the exact outcome in a specific case can depend on charging language, procedural history, and when particular events occurred.
Limitation period
For Ohio offenses covered by Ohio Rev. Code § 2901.13, the basic rule for Class C misdemeanors / petty offenses uses a 6-month limitations period.
What that means in practical terms
- Starting point (typical): the clock generally runs from the time of the offense.
- Time window: 0.5 years = 6 months.
- Effect: if the state files after the 6-month period expires (and no exception applies), the prosecution may be time-barred under the statute.
How to think about dates
When you use a calculator, you’ll typically provide:
- Date of the alleged offense
- (Optionally) date the charge was filed or the date a complaint/indictment was filed—depending on what the tool asks for
Then DocketMath compares the filing date to the computed expiration date based on the SOL length.
Quick reference table (Ohio: Class C / petty)
| Item | Value (Ohio) |
|---|---|
| SOL period for Class C / petty offense | 6 months (0.5 years) |
| Controlling statute | Ohio Rev. Code § 2901.13 |
Key exceptions
Ohio’s limitations statute contains exceptions that can extend the time the state has to prosecute. One of the most important ones for your planning is that § 2901.13 includes an exception noted as “V3” in the jurisdiction data.
Exception handling in the calculator
DocketMath’s statute-of-limitations calculator is designed to reflect these statutory nuances. Practically, that means:
- If no exception applies, the result stays at 6 months.
- If an exception applies (for example, a statutory condition captured by the calculator’s “exception V3” logic), the end date can move beyond the basic 6-month window.
Because the details of exceptions can depend on case-specific facts (such as whether particular procedural steps occurred, or whether certain events affect the limitations computation), the safest approach is to:
- run the calculator with the relevant scenario parameters, and
- confirm which exceptions the tool is applying based on your inputs.
Warning: Even when the basic SOL is only 6 months, exceptions in Ohio Rev. Code § 2901.13 can change the outcome. A missing input or an incorrectly selected scenario can produce an inaccurate expiration date.
Checklist for better calculator results
Use this quick checklist before you hit calculate:
Statute citation
The limitations period for Class C misdemeanors and petty offenses in Ohio is governed by:
- Ohio Rev. Code § 2901.13
- SOL period: 0.5 years (6 months)
- Exception reference: V3 (as reflected in the jurisdiction data)
Source (official Ohio Revised Code publication): https://codes.ohio.gov/assets/laws/revised-code/authenticated/29/2901/2901.13/7-16-2015/2901.13-7-16-2015.pdf
Use the calculator
To get a concrete expiration date (based on the 6-month SOL for Class C / petty matters and any applicable exception logic), use DocketMath’s statute-of-limitations calculator:
- Run it here: /tools/statute-of-limitations
- If you want to confirm your general workflow for legal-tech calculations, you can also review DocketMath’s supporting resources: /tools (for navigation to related utilities and guidance)
Inputs to provide (typical flow)
While the exact fields can vary by UI version, the standard inputs you’ll want are:
- Offense date
- The date the alleged conduct occurred.
- Filing date (if the tool supports a “compare to filing date” mode)
- The date the charge was filed (complaint, indictment, or information depending on context).
- Exception selection / scenario (if offered)
- For Ohio, this is where the calculator may incorporate exception V3 logic for § 2901.13.
How outputs change
- No exception selected:
- Expiration date = offense date + 6 months
- Exception selected (V3):
- Expiration date may shift beyond 6 months, depending on how the exception is triggered and computed by the statute logic implemented in DocketMath.
Practical interpretation of results
When DocketMath returns a computed expiration date, you’re essentially comparing:
- Charge filed date
- vs.
- Calculated SOL expiration date
A quick way to interpret:
- If filed on or before the expiration date → still within the SOL window (based on the calculator’s assumptions)
- If filed after the expiration date → outside the base SOL window (and you’d want to confirm whether any exception was properly applied)
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
