Statute of Limitations for Class B Misdemeanor in Alaska
6 min read
Published March 22, 2026 • By DocketMath Team
Overview
Run this scenario in DocketMath using the Statute Of Limitations calculator.
In Alaska, the statute of limitations (SOL) sets a deadline for the state to file a criminal case after an alleged offense. For a Class B misdemeanor, DocketMath uses Alaska’s general/default SOL rule: Alaska does not apply a shorter or longer time period for Class B misdemeanors based on offense subtype under the information available here.
Bottom line: the general SOL period is 2 years from the time the limitations clock starts, and that same period is the baseline used for Class B misdemeanors in this reference page.
Note: This page describes the general/default statute of limitations period. It does not identify a separate Class B misdemeanor-specific exception if that exception isn’t captured by the general rule and associated exceptions discussed below.
Limitation period
Default period for Class B misdemeanors (Alaska)
- General SOL Period: 2 years
- General Statute: **Alaska Statutes § 12.10.010(b)(2)
In plain terms, if the alleged conduct occurred and the state starts proceedings outside that 2-year window (subject to exceptions described in the next section), the case may be time-barred.
What you need to compute the deadline
To use DocketMath’s statute-of-limitations calculator (see /tools/statute-of-limitations), you typically provide inputs such as:
- Date of the alleged offense (the starting point for the SOL clock under standard rules)
- Whether a tolling/exception may apply (for example, situations that pause or extend the limitations period)
- Optional: the relevant filing-related date you want to compare against the SOL expiration date (e.g., complaint or charging date)
The calculator’s output changes based on the inputs:
- If you enter only the offense date (and no tolling), the output is a straight 2-year deadline.
- If you indicate a tolling/exception scenario, the expiration date may be pushed later to reflect the tolling period (when applicable).
Practical workflow (without legal advice)
- Find the offense date tied to the charge.
- Use DocketMath to compute the 2-year expiration date using Alaska Stat. § 12.10.010(b)(2).
- Compare the charging/filing date you’re tracking to the computed deadline.
- If you suspect a delay-pause factor, run the calculator again with the relevant exception/tolling input (if available in the tool) and document the assumptions you selected.
Warning: SOL calculations can hinge on details like the precise “trigger” date and whether any tolling applies. A one-day difference can change whether a filing is inside or outside the 2-year window.
Key exceptions
This section explains the kinds of factors that commonly affect SOL deadlines. Because this page is focused on the general/default period for Class B misdemeanors in Alaska, it does not claim that every exception below definitely applies to every scenario. Instead, treat these as the main categories you should check when the case timeline looks unusual.
1) Tolling or pauses in the limitations clock
Some circumstances can effectively stop, pause, or extend the time the state has to bring charges. In practice, SOL tolling often turns on events such as:
- periods when the defendant is not amenable to process,
- procedural events that legally affect timing,
- or other statutory circumstances that interrupt the clock.
Impact on the deadline: if tolling applies, the SOL expiration date moves forward by the duration of the tolling period.
2) Starting date disputes
Even when the “2 years” rule is clear, the starting date (the point the limitations clock begins) can be disputed.
- If the charging documents or incident record describe different relevant dates (e.g., a continuing course of conduct versus a single event), the SOL computation may change.
Impact on the deadline: shifting the start date by days or weeks can change the expiration date accordingly.
3) Multiple alleged events
If the underlying matter includes more than one alleged incident, SOL may apply differently to each event.
- A single case file can involve allegations that occurred on different dates.
Impact on the deadline: you may need to calculate SOL separately per alleged event date.
4) Procedural posture (what date counts)
Different documents may have different “timing” significance (for example, when a case is formally initiated).
- Many SOL workflows compare the limitation cutoff to the date of formal filing/charging.
Impact on the deadline: if you compare the wrong date (e.g., investigation date instead of charging date), your SOL conclusion may be off.
Pitfall: Using the date of the incident as the only date—while ignoring possible tolling or the charging date that actually triggers the SOL analysis—can produce an expiration date that doesn’t reflect the legal timeline.
Statute citation
The general/default statute of limitations period relevant here is:
- Alaska Stat. § 12.10.010(b)(2)
- General SOL Period: 2 years
The general rule above is the starting point for Class B misdemeanors when no offense-specific sub-rule is identified.
Source (reference): https://law.justia.com/codes/alaska/title-12/chapter-10/section-12-10-010/?utm_source=openai
Use the calculator
DocketMath’s statute-of-limitations calculator is designed to turn a timeline into a concrete deadline. To use it effectively for Alaska Class B misdemeanor SOL:
- Open the tool: /tools/statute-of-limitations
- Enter the date of the alleged offense.
- Select or indicate whether the calculator provides an option for tolling/exception scenarios relevant to your timeline.
- (Optional) Enter the date you want to test (such as a charging/filing date) so the tool can show whether it falls before or after the calculated SOL expiration.
How outputs change with your inputs
Use these scenarios as a guide:
Scenario A (default-only):
- Input: offense date only, no tolling indicated
- Output: a deadline 2 years after the calculated start point tied to the offense date.
Scenario B (tolling indicated):
- Input: offense date + a tolling/exception selection
- Output: an expiration date moved forward by the tool’s modeled tolling period.
Scenario C (different offense dates):
- Input: you run the tool once for each alleged incident date
- Output: multiple SOL deadlines, allowing you to compare each alleged event to the relevant charging date(s).
If you’re building a chronology for decision-making, save your runs and confirm you consistently use the same date definitions across calculations.
Primary CTA: /tools/statute-of-limitations
Related reading
- Choosing the right statute of limitations tool for Vermont — Tool comparison
- Choosing the right statute of limitations tool for Connecticut — Tool comparison
