Statute of Limitations for False Arrest / False Imprisonment in Ohio

6 min read

Published April 8, 2026 • By DocketMath Team

Overview

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

In Ohio, the statute of limitations (SOL) for a false arrest / false imprisonment-type civil claim is generally 0.5 years (6 months) under Ohio Rev. Code § 2901.13.

Ohio uses a shorter limitations framework for certain civil actions, and for false arrest / false imprisonment you typically rely on the general/default SOL rule in § 2901.13—because no claim-type-specific sub-rule was identified for this exact label in the provided guidance.

Practical takeaway: if the alleged unlawful arrest or detention ended on a particular date, the deadline usually starts from that end point (not from when someone later “realized” the harm).

Note: This page explains the general SOL rule associated with Ohio Rev. Code § 2901.13. If your situation involves different or additional claim theories (for example, negligence, civil rights theories, or other causes of action), a different statute and timeline could apply.

Limitation period

The default SOL period is 6 months. Under Ohio Rev. Code § 2901.13, the applicable general/default limitations period for the relevant category is 0.5 years (6 months).

How the clock is typically assessed (inputs → outputs)

In practice, people using DocketMath usually translate the situation into two dates:

  • Start date (event end): the date the restraint or detention ended (for example, the day of release from custody, the end of the allegedly unlawful confinement, or when the incident was no longer ongoing).
  • File-by date (output): the last day to file within the SOL window.

What you enter in DocketMath (what changes the output)

When you run DocketMath’s statute-of-limitations calculator, the most important input is typically the event end date. DocketMath then applies the 6-month default period from § 2901.13 to compute your calculated deadline.

In general, your results will move like this:

  • Later event end date → later deadline: if you input a release/accrual date that occurs later, the file-by date typically shifts later by about the same amount (6 months).
  • Earlier event end date → earlier deadline: if the restraint actually ended earlier than expected, the deadline may already be closer—or possibly already passed.

Quick timeline example (illustrative)

If an alleged unlawful detention ended on January 10, 2026, then using a 6-month SOL would likely produce a file-by date around July 10, 2026 (subject to the exact way deadline counting works under Ohio procedure and calendar rules). Because SOL deadline calculations can be sensitive to date-counting details, it’s a good idea to run your specific dates through DocketMath.

Key exceptions

Ohio’s short limitations period can be affected by issues that change either when the clock starts (accrual) or whether time is paused (tolling). This section is meant to help you spot possibilities—not to provide legal advice.

1) Tolling (pauses) and other timing adjustments

If Ohio law recognizes a reason to pause the SOL clock, your effective deadline can move later than the simple “end date + 6 months” calculation.

Common tolling-related concepts that may come up in Ohio practice include:

  • Legal disability concepts (situations where a person cannot sue due to incapacity).
  • Certain timing interactions involving government entities (if the defendant is a municipality or other public body, extra procedural steps and timing rules can affect when/if suit must be filed).

If a tolling theory might apply, the calculator’s base rule (6 months under § 2901.13) can be your starting point—but you’ll likely need to apply the specific tolling/accrual rules relevant to your facts.

2) Accrual disputes (when the clock starts)

Even with the correct 6-month period, people often dispute the accrual date—especially for restraint-related scenarios where:

  • detention continues over time, or
  • the restraint has multiple components or related events.

For the purposes of calculating your deadline, the “event end date” you enter should reflect when the restraint actually ended, not just when you first became suspicious or aware.

3) Claim-type differences (default vs. other causes of action)

Because no claim-type-specific sub-rule was found for “false arrest / false imprisonment” within the provided guidance, the default/general rule in § 2901.13 is the baseline.

However, if your complaint is built around additional or different causes of action, the applicable SOL may change. For example, certain statutory or civil rights theories can have their own timelines (sometimes longer).

Warning: Don’t assume every lawsuit about “wrongful detention” must use the same SOL. Using the wrong claim theory can lead to missing the deadline.

Statute citation

Ohio Rev. Code § 2901.13 is the general/default limitations statute referenced here.

  • General/default SOL period: **0.5 years (6 months)
  • Baseline for this page: because no special claim-type sub-rule was identified for “false arrest / false imprisonment,” the general/default period in § 2901.13 is the starting point.

Source: 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

You can calculate a practical file-by date using DocketMath’s statute-of-limitations tool:

  • Primary CTA: /tools/statute-of-limitations

What to enter in DocketMath

After opening the tool, provide the key date(s), generally including:

  • Event end date (recommended): the date the arrest/detention ended or the restraint concluded.

If DocketMath prompts you for additional context that can affect accrual, choose the option that most closely matches your scenario.

How to interpret the output

DocketMath will produce a calculated deadline (file-by date) based on the 6-month default period under Ohio Rev. Code § 2901.13, using your input date(s). It should also show how it mapped your input to the output deadline.

Quick checklist before you rely on the number

If your facts suggest tolling/accrual differences might apply, run the base calculation first, then verify whether and how those additional rules change the deadline.

Related reading