Statute of Limitations for Class C / Petty Misdemeanor in California

6 min read

Published March 22, 2026 • By DocketMath Team

Overview

In California, the “statute of limitations” (often shortened to “SOL”) sets a deadline for when the government can file a criminal case after an alleged offense. For Class C / petty misdemeanor conduct, the relevant deadline is generally governed by California’s default statute-of-limitations rule for misdemeanors.

This guide focuses on the general/default rule. Per your brief, no claim-type-specific sub-rule was found for a shortened or extended period specifically labeled “Class C / petty misdemeanor.” Instead, you should expect the general two-year misdemeanor SOL to apply in the typical scenario.

If you’re working through a timeline—say, from a reported incident date to an arrest date to when charges were filed—DocketMath’s statute-of-limitations calculator can help you convert those dates into a deadline framework quickly.

Note: This is a procedural timing overview, not legal advice. SOL issues can involve nuanced facts (for example, what date legally counts as “committed,” “charged,” or otherwise triggered).

Limitation period

Default SOL for misdemeanors (including petty/class C treated under the misdemeanor framework)

California’s general rule provides a 2-year statute of limitations for misdemeanors.

  • General SOL Period: 2 years
  • General Statute: California Code of Civil Procedure (CCP) § 335.1

Even when the offense is described in everyday terms as “petty” or “Class C,” the practical question is whether the conduct falls within the misdemeanor limitations framework. Under the information provided for this brief, the default period is the two-year rule (not a special shorter/longer petty-specific rule).

How the deadline typically works (conceptually)

In practice, you usually need to distinguish three date types:

  1. Event date (the alleged conduct date)
  2. Filing/charging date (when charges are filed or otherwise initiated)
  3. Possible tolling/exception dates (events that pause or extend the running of time)

DocketMath’s calculator is built around the main inputs you can often identify—especially the alleged incident date and the date charging occurred—then helps you estimate whether the filing looks timely under the baseline SOL.

Practical interpretation

  • If the charging date is more than 2 years after the relevant incident date (and no exception applies), the case may be subject to dismissal on SOL grounds.
  • If it’s within 2 years, SOL alone usually won’t be the basis for a time-bar argument under the default rule.

Warning: Even when the baseline SOL seems clear, courts may consider tolling or specific triggering concepts. Always verify the relevant “trigger” date with the case record.

Key exceptions

Based on the brief you provided, we are treating CCP § 335.1 as the governing default and not introducing claim-type-specific sub-rules for “petty/Class C.” That said, exceptions still matter because they can pause, extend, or otherwise affect the running of time.

Here are the exception categories you should keep in mind when working through deadlines:

1) Tolling events (time pauses)

Some procedural or factual situations can toll (pause) the statute of limitations. When tolling applies, the “clock” stops temporarily and the effective deadline moves later.

Common tolling themes in SOL analysis include:

  • certain defendant-related unavailability issues,
  • procedural delays tied to specific legal events, and
  • other legally recognized reasons the clock should not run normally.

Because tolling is fact-driven, the calculator output should be treated as a baseline estimate, not a final legal conclusion.

2) Trigger date disputes (what counts as “the start”)

The “start” can be misunderstood. For timing work, your accuracy depends on which date properly counts under the statute and the charging theory.

Be prepared to validate:

  • whether the incident date is correct,
  • whether multiple acts exist (and which one matters),
  • whether there are amendments or related filing events that change the timing question.

3) Procedural posture (what “charging” means)

Some people track “arrest date” while others track “filing date.” SOL analysis often turns on the date the legal process is initiated in a way the statute recognizes.

That’s why DocketMath emphasizes using the dates most directly tied to charging whenever possible.

Statute citation

The default statute of limitations rule described in your jurisdiction data is:

  • California Code of Civil Procedure (CCP) § 335.12-year general limitations period.

Your brief’s jurisdiction notes also specify:

  • General SOL Period: 2 years
  • No claim-type-specific sub-rule was found for “Class C / petty misdemeanor.”
  • Therefore, you should apply the general/default two-year rule unless another legally recognized exception changes the outcome.

Use the calculator

For this topic, use DocketMath’s statute-of-limitations calculator to translate your timeline into a deadline view.

Primary CTA: /tools/statute-of-limitations

Before you run it, gather these inputs:

  • Alleged incident date (YYYY-MM-DD)
  • Charging/filing date (YYYY-MM-DD)
  • ✅ (If the tool supports it) any pause/tolling flags you can justify from the record

If you want to compare “arrest date” vs “charging date,” run two calculations and compare outputs. The difference can be decisive.

What changes the output

Use DocketMath to explore how adjustments affect results:

  • Move the charging date later: the “timely vs. time-bar” status may flip.
  • Move the incident date earlier: the deadline moves earlier; more likely to be untimely.
  • Add tolling indicators (if applicable): the effective deadline can extend beyond the baseline 2-year window.

Even with a clear baseline, tolling and trigger-date issues are where practical outcomes diverge.

Note: If your inputs are estimates (for example, “sometime in April 2022”), tighten them using the charging document dates before relying on the calculator output.

To keep your workflow efficient, you can also review DocketMath’s related tools for date handling and workflow tracking at /tools before running the SOL calculation.

Sources and references

Start with the primary authority for California and confirm the effective date before relying on any output. If the rule has been amended, update the inputs and rerun the calculation.

Related reading