Statute of Limitations for Adult Sexual Assault / Rape (civil) in Arizona
5 min read
Published March 22, 2026 • By DocketMath Team
Overview
In Arizona, the civil statute of limitations for adult sexual assault or rape is often discussed alongside criminal deadlines, but civil timing rules are their own system. This post focuses on the general/default limitations period identified for Arizona in the provided jurisdiction data: 2 years, tied to A.R.S. § 13-107(A).
A key takeaway upfront: we did not find a claim-type-specific sub-rule for adult sexual assault/rape in the provided data. That means the 2-year period below is presented as the general rule, not a special rule tailored to a particular civil label.
Note: This article explains the general limitations framework and how to use DocketMath’s calculator. It does not provide legal advice, and real-world outcomes can turn on specific pleading details and procedural posture.
Limitation period
General SOL period (default): 2 years
- General statute: **A.R.S. § 13-107(A)
- Time window: 2 years from the relevant triggering event (often discussed as the date of the injury or discovery, depending on the claim and context)
Because this topic is frequently misunderstood, here’s how to think about the “inputs” that typically drive the output when you use a limitations calculator like DocketMath:
What you usually need to enter
Most limitations calculators require some version of:
- Start date: the date the clock begins (for civil claims, this could be the date of harm, discovery, or another legally recognized trigger)
- Jurisdiction: here, **Arizona (US-AZ)
- Claim type (if the tool has it): for this post, no claim-type-specific sub-rule was found, so the tool uses the general 2-year rule
How outputs change
If you change the start date by:
- 1 day → the “deadline date” shifts by 1 day
- 1 month → the deadline shifts by about 1 month
- 6 months → the deadline shifts by about 6 months
That’s why the start date is the most influential input. If the start date is uncertain (for example, whether the trigger is discovery versus occurrence), the safest workflow is to run multiple scenarios in DocketMath and review which deadlines become implicated.
Practical checklist before you calculate
Use this quick checklist to prepare:
Key exceptions
Arizona law has a wide range of doctrines that can affect deadlines (for example, tolling concepts and special rules tied to particular circumstances). However, this post does not enumerate claim-type-specific exceptions for adult sexual assault/rape beyond the general/default period you provided.
What we can still do practically is highlight how to approach exceptions without assuming they apply:
1) Exceptions can change “when the clock starts”
Even when the base SOL is 2 years, an exception may alter the trigger event. That can move the deadline forward or backward depending on the doctrine.
2) Exceptions can “pause” or “toll” time
Some legal doctrines can suspend the running of a limitations period during certain periods. If tolling applies, the deadline often becomes later than a simple “start date + 2 years” calculation.
3) Exceptions can be claim-specific
Because the provided data did not confirm a claim-type-specific sub-rule, treat adult sexual assault/rape exceptions as fact-dependent and verify the specific basis for any tolling or altered trigger before relying on a single computed date.
Pitfall: Using only “2 years from the incident date” can be wrong if your situation involves a different legally recognized trigger or a tolling basis. Run calculations using the start date you believe applies—and be ready to adjust if the governing trigger is disputed.
Statute citation
- A.R.S. § 13-107(A)
- General SOL period: 2 years (default rule used here)
This post uses A.R.S. § 13-107(A) as the statute tied to the general/default 2-year limitations period provided in the jurisdiction data. For transparency, the underlying source you provided is:
If your matter is strictly civil (rather than criminal timing), your jurisdiction’s civil limitations provisions may still differ. That’s why you should treat this as a timing framework based on the provided jurisdiction data, and validate the rule that corresponds to the specific type of action you are analyzing.
Use the calculator
DocketMath’s statute-of-limitations calculator is designed to turn an identified “start date” into a computed deadline using the jurisdiction’s applicable limitations period. Use it here: /tools/statute-of-limitations.
Steps
- Go to the DocketMath statute calculator: **/tools/statute-of-limitations
- Select or confirm:
- Jurisdiction: **Arizona (US-AZ)
- Default SOL: 2 years (since no claim-type-specific adult sexual assault/rape sub-rule was found in the provided data)
- Enter the start date relevant to your fact pattern.
- Review the calculated deadline date.
Suggested input strategy (especially when triggers are disputed)
If you’re not certain whether the start date is the date of the incident or another legally recognized trigger, test scenarios:
- Scenario A: start date = incident date → compute “baseline deadline”
- Scenario B: start date = discovery/knowledge date → compute “discovery-based deadline”
- Scenario C: start date = alternative triggering date → compute “alternative deadline”
Then compare which deadlines fall inside key procedural planning windows (e.g., before any filing deadlines you must meet for other reasons).
Output interpretation
The calculator output is a deadline date based on the computed SOL. If the calendar deadline matters (for instance, filing logistics), treat the computed date as a core reference point and confirm any filing-day rules through reliable procedural resources.
Related reading
- Choosing the right statute of limitations tool for Vermont — Tool comparison
- Choosing the right statute of limitations tool for Connecticut — Tool comparison
