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

5 min read

Published March 22, 2026 • By DocketMath Team

This article is for informational purposes only and does not constitute legal advice. Laws change frequently — verify all citations with current official sources.

Overview

In Indiana, “Blue Sky” laws are the state-level securities protections that sit alongside federal securities law. When someone alleges securities fraud under Indiana’s securities statutes, a key procedural question is how long the claimant has to file—because the statute of limitations (SOL) can bar the case even if the underlying allegations are strong.

For Indiana, the starting point for time limits is found in the state’s general limitations framework for crimes. Indiana Code § 35-41-4-2 sets out the default SOL period applicable to offenses governed by that section. In other words, unless a specific statute provides a different rule, the general limitations period controls.

DocketMath’s statute-of-limitations calculator helps you model the timing using Indiana’s baseline rules and the date fields you enter—so you can see when a claim may become time-barred under the applicable general SOL.

Note: No claim-type-specific sub-rule was identified for the securities fraud timing question in the provided jurisdiction data. The 5-year period below should be treated as the general/default rule rather than a bespoke rule for every securities theory.

Limitation period

General (default) SOL: 5 years

Indiana’s general limitation period is 5 years, reflected in:

Indiana Code § 35-41-4-2
General SOL period: 5 years

This “default” nature matters. If a different Indiana statute clearly prescribes a different timing rule (for example, by statute text specifying an alternative limitations period or by a separate limitations section that governs the particular charged offense or procedural vehicle), that statute would take precedence. With the information available here, the reliable baseline is the 5-year general period.

How the 5-year period affects case timelines

When you map a 5-year SOL onto real dates, you’re typically testing whether the filing date (or charging date, depending on the action type) falls within the 5-year window measured from the relevant triggering date.

Common date concepts you may see in SOL analyses include:

Event date (e.g., when the alleged misstatement or deceptive act occurred)
Discovery date (when the claimant discovered or should have discovered the facts)
Filing date (when the complaint/petition/charging instrument is filed)

Because SOL calculations depend heavily on the triggering date your matter uses, DocketMath’s calculator focuses on inputs you provide—letting you observe how changing the triggering date shifts the deadline.

Key exceptions

Indiana’s general SOL framework can be affected by exceptions such as tolling, amended filings, or other events that legally pause or reset the clock. This is also where practitioners often look for statute-specific rules rather than relying on a single “headline” duration.

Since the jurisdiction data provided here does not list a securities-fraud-specific exception, treat the following as an issue-spotting checklist rather than a guarantee that an exception applies:

Tolling or pauses in time
- Some legal events can pause the running of a limitations period.
Triggering-date disputes
- The case can turn on whether the clock starts at the event date, a discovery date, or another statutory trigger.
Procedural posture differences
- Different procedural vehicles (e.g., different types of claims or actions) can involve different SOL rules or different “start” concepts.
Amendments and relation back
- If a case is amended, the law sometimes allows an amended pleading to “relate back” to the original filing date—potentially affecting SOL analysis.

Warning: SOL exceptions can turn on statutory language and procedural facts. A calculation that assumes the 5-year clock starts on one date may yield a misleading deadline if the governing statute uses a different trigger or recognizes tolling.

If you want the most useful output from DocketMath, enter the date fields that match the timing theory you’re evaluating (for example, the alleged transaction date versus an alleged discovery date).

Statute citation

Indiana Code § 35-41-4-2 (general limitations framework) provides the baseline:

General SOL period: 5 years
Source (as provided): https://law.justia.com/codes/indiana/2022/title-35/article-41/chapter-4/section-35-41-4-2/

Use this citation as the anchor for any Indiana “Blue Sky” timing discussion where the claim is treated under the general default SOL rule.

Use the calculator

DocketMath’s statute-of-limitations tool can help you turn the Indiana 5-year general SOL into a concrete deadline.

Primary CTA: /tools/statute-of-limitations

Inputs to consider

Check the boxes for the inputs you know:

What to expect from the output

Once you enter your dates, DocketMath produces results you can interpret as:

The calculated SOL deadline (start date + 5 years under the general rule)
Whether your filing date falls before or after that deadline
How changing the start/trigger date shifts the deadline

Because the Indiana baseline is 5 years, the key variable that usually changes the outcome is the start date you select. Move the start date forward (e.g., from transaction date to discovery date), and the deadline moves forward too; move it earlier, and the deadline moves earlier.

Pitfall: If you use the wrong start date concept (for example, assuming discovery governs when the controlling rule starts at another event), your calculation can swing from “timely” to “time-barred” even though the law might treat the clock differently.

Quick scenario math (general rule only)

Under the general SOL:

Deadline = Trigger date + 5 years

So, if your trigger date were January 15, 2020, the general SOL deadline would land around January 15, 2025 (subject to how the tool handles exact day-of-month/time and any procedural details it prompts you to enter).