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

Overview

Arizona’s statute of limitations (often abbreviated “SOL”) sets a deadline for the state to file (or proceed with) a criminal prosecution. For a Class B felony / 2nd degree felony, Arizona uses a general/default SOL rule that applies when no special, claim-type-specific rule is identified.

In practical terms, DocketMath’s statute-of-limitations calculator helps you translate that general rule into a concrete date range by using the timeline facts you provide—such as the date the alleged offense occurred and (optionally) other procedural dates that can affect how a case moves through time.

Limitation period

Default rule for Arizona felonies (general SOL)

For the matter you described—Class B / 2nd degree felony—the jurisdiction data points to the general SOL period of 2 years.

That means:

• The prosecution generally must be brought within 2 years of the triggering event defined by Arizona SOL law.
• The general rule is drawn from A.R.S. § 13-107(A).

How the deadline is typically interpreted

Arizona’s SOL framework is statute-driven rather than discretionary. Even so, calculating the “end date” usually requires you to nail down the correct start point (the “trigger”) and then add the statutory period.

When using DocketMath, the output date changes based on the inputs you provide:

• If your “offense/incident date” moves forward → the SOL expiration date moves forward by the same amount.
• If you use a different “trigger date” (for example, a later date tied to the statutory triggering event) → the SOL expiration date adjusts accordingly.
• If an exception/tolling applies → DocketMath can help you model the effect by accounting for additional time (when your inputs include the relevant procedural dates and the calculator’s logic supports them).

What to have handy before calculating

To get a useful SOL window, gather:

• The date of the alleged offense (or the date that best matches the statutory trigger for SOL purposes).
• Any key procedural dates you know already (e.g., charging date, arrest date, or other case milestones), if you plan to model changes under exceptions.

You’ll get the most accurate result when your inputs reflect the facts most consistent with Arizona’s SOL triggering and exception rules.

Key exceptions

The jurisdiction data you provided indicates no claim-type-specific sub-rule was found for “Class B / 2nd degree felony,” so this page treats A.R.S. § 13-107(A) as the default starting point.

Still, SOL outcomes in real cases often shift because Arizona law recognizes circumstances that can affect timing. Here are the types of factors you should check for when you’re doing a SOL calculation or reviewing case documents:

1) Tolling or suspension events

Certain events can pause (or effectively extend) SOL time. These may include specific conduct by the defendant or procedural circumstances recognized by Arizona law.

Practical impact on calculations:

• The expiration date may move later than “offense date + 2 years.”
• Your calculator run should reflect any tolling periods if the inputs and logic support them.

2) Multiple offenses or amended charges

If the case involves amended information/indictment or multiple counts, the SOL question can become count-specific:

• One count might expire while another still remains within the window.
• The “trigger” date may differ depending on the count’s facts.

3) Misalignment between “incident date” and “SOL trigger”

A common source of error is using an incorrect start date.

• If Arizona defines the SOL trigger differently than “the day something happened,” a baseline calculation could be off.

4) Procedural commencement vs. investigation

SOL is tied to prosecution timing, not just investigation activity. That distinction matters:

• An investigation can run for months, but SOL analysis usually focuses on when the prosecution is commenced (as the statute and relevant Arizona rules reflect).

If you’re building a timeline in DocketMath, use the charging/prosecution milestone dates you have, not just the date evidence was gathered.

Statute citation

The general/default SOL period is governed by:

• A.R.S. § 13-107(A) — provides the general statute of limitations framework and supports the 2-year general period for the category described in your jurisdiction data.

Per the jurisdiction data provided for this page:

• General SOL Period: 2 years
• General Statute: **A.R.S. § 13-107(A)
• Source reference (overview context): https://www.findlaw.com/state/arizona-law/arizona-criminal-statute-of-limitations-laws.html?utm_source=openai

Use the calculator

DocketMath’s statute-of-limitations tool is designed to convert the statute into an expiration window you can read quickly.

Baseline run (general rule only)

1. Open: /tools/statute-of-limitations
2. Select Arizona (US-AZ).
3. Choose the relevant offense category option that corresponds to Class B / 2nd degree felony.
4. Enter the trigger/offense date you want to model.
5. Run the calculation to get:

   • A baseline SOL expiration date using the general 2-year period under A.R.S. § 13-107(A).

Expected result:

• Expiration date = trigger date + 2 years (subject to the calculator’s handling of date conventions).

Scenario runs (if you have exception-related timeline facts)

If you know dates that may relate to tolling/suspension issues:

• Add those dates in the calculator fields (if supported by the calculator UI).
• Re-run to see how the deadline changes.

How the output changes:

• If a tolling period is applied → the expiration date typically shifts later.
• If no exception inputs are provided → the calculator should reflect the default 2-year rule.

Quick checklist before trusting the output

Related reading

• Choosing the right statute of limitations tool for Vermont — Tool comparison
• Statute of limitations in Singapore: how to estimate the deadline — How-to guide
• Choosing the right statute of limitations tool for Connecticut — Tool comparison