Statute of Limitations for Securities Fraud (state Blue Sky laws) in Arizona

Overview

Arizona’s “Blue Sky” securities rules are enforced through a mix of state statutory remedies and, in some cases, criminal enforcement. When people talk about the “statute of limitations for securities fraud” in Arizona, they often mean a time limit on filing a case—but the applicable clock depends on the type of proceeding (criminal vs. civil) and the elements alleged.

This page focuses on Arizona’s general criminal statute of limitations for offenses under Arizona law, including fraud-type conduct charged as crimes. Under the data available for this jurisdiction, the default/general period is 2 years, keyed to Arizona’s general criminal SOL rule. No claim-type-specific sub-rule was identified for securities-fraud labels within this source set, so the analysis below treats this as the general/default rule.

If you want to compute dates quickly, use the DocketMath calculator linked below: /tools/statute-of-limitations .

Limitation period

Default general SOL in Arizona (criminal)

• General SOL period: 2 years
• General statute: **A.R.S. § 13-107(A)
• What this means in practice: absent a specific exception, the state must generally commence a criminal prosecution within 2 years from the relevant start date defined by the statute.

How the start date affects the outcome

Even with a 2-year baseline, the practical question is: what starts the clock? In most limitations systems, the “clock” does not always begin at the same moment for every case. Common triggers can include:

• the date of the alleged offense,
• discovery-related triggers (where a statute or case law provides one), or
• other statutory “commencement” rules.

Because the only clearly identified rule here is the general/default 2-year period, you should treat this page as your starting point, not a final determination.

DocketMath input → output

Using DocketMath, you can model a basic timeline.

Typical inputs you’ll use:

• Alleged offense date (or the date you want to treat as the trigger)
• Filing/charging date you want to test
• Optional: tolling or exception toggles if you have a specific basis to model (details depend on the exception discussed below)

Typical output you’re looking for:

• whether the filing date falls within 2 years of the trigger date, or
• the earliest likely deadline (trigger date + 2 years), assuming no exception.

Key exceptions

Arizona’s limitations framework includes exceptions and tolling concepts that can extend or pause the SOL, but they are not universal for all crimes or all fact patterns. Since this page is anchored on the general/default rule (2 years under A.R.S. § 13-107(A)) and no securities-fraud-specific sub-rule was found, the “exceptions” section here is best used as a checklist of where to look next.

Common categories to evaluate (before relying on a flat 2 years)

• Statutory tolling provisions: some circumstances can pause the limitations period.
• Defendant-related circumstances: absence from the state, concealment, or other conduct can sometimes affect timing rules.
• Procedural posture: amendments, re-filing, or other procedural steps can raise questions about whether the prosecution was “commenced” within the limitations period.

A practical fact-check list

When you’re applying the 2-year baseline, gather these facts early:

• The exact date of the alleged fraudulent act or omission you’re anchoring to.
• The date the case was commenced (filing of charges vs. other milestones).
• Any facts that could support tolling or exception theories, such as:

  • periods when the defendant was not reachable in a legally relevant sense,
  • concealment-related facts, and
  • whether any statute specific to the charged offense modifies timing.

If you’re using DocketMath to estimate, keep your assumptions explicit—then rerun the calculation using alternative triggers if you have competing dates (for example, “transaction date” vs. “last contact date”).

Statute citation

The governing general criminal statute of limitations used for the default analysis here is:

• A.R.S. § 13-107(A) — 2-year general statute of limitations for covered offenses.

This rule is the basis for the “general/default period” presented throughout this page.

Source reference (Arizona criminal statute of limitations overview):
https://www.findlaw.com/state/arizona-law/arizona-criminal-statute-of-limitations-laws.html?utm_source=openai

Use the calculator

Want a fast, reproducible SOL timeline? DocketMath’s statute-of-limitations tool can help you model “deadline = trigger date + SOL period,” and test filing dates against that deadline.

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

How to run a baseline 2-year model

1. Open **/tools/statute-of-limitations
2. Set:

   • Jurisdiction: US-AZ
   • SOL period: 2 years (the general/default rule)
3. Enter your trigger date (commonly the alleged offense date you’re anchoring to).
4. Enter the filing/charging date you’re evaluating.
5. Review:

   • whether the filing date is within 2 years, and
   • the computed deadline under the baseline assumption.

Adjusting inputs to see how outcomes change

SOL outcomes are sensitive to dates. Try these common scenario variations:

• Earlier trigger date: use the earliest transaction date you can support → deadline moves earlier.
• Later trigger date: use the last related act/omission date → deadline moves later.
• Compare two filing dates: if there are multiple procedural events, test each to see which one “wins” under the baseline.

If your facts suggest a possible exception, run the calculator again while documenting the exception’s assumed legal effect (and make sure the legal basis for the modification exists before relying on the results).

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