Statute of Limitations for Federal Tort Claims Act (FTCA) in Georgia

5 min read

Published March 22, 2026 • By DocketMath Team

Overview

If you’re considering a Federal Tort Claims Act (FTCA) lawsuit connected to an incident in Georgia, timing is usually the decisive issue. Under the FTCA, claims have to be filed within a specific statute of limitations period measured from when the claim accrues.

For Georgia-related guidance, many people look to Georgia’s general limitations framework as part of their planning. In Georgia, the general statute of limitations for personal injury actions is found at O.C.G.A. § 17-3-1, which provides a 1-year general period for certain tort claims. This guide focuses on that Georgia general rule and how it affects the “when can I file” timeline you’d track using DocketMath.

Note: This post is for information and planning purposes. It doesn’t provide legal advice, and FTCA accrual and exceptions can be fact-specific.

Also, no claim-type-specific sub-rule was found for this Georgia default in the materials you provided—so the discussion below treats the general/default 1-year period as the governing baseline for this page.

Limitation period

The Georgia general default period (1 year)

Georgia’s general statute of limitations for applicable tort actions is 1 year under:

  • O.C.G.A. § 17-3-1
    (Georgia’s general limitation rule for the relevant category of tort claims)

How this typically shows up in practice (timeline view):

  • Start from the date your claim accrues (often tied to when you knew—or reasonably should have known—the facts giving rise to the claim).
  • Count forward 1 year.
  • Your filing date must fall within that window, or the claim risks being time-barred.

What “inputs” matter in a DocketMath statute-of-limitations calculation

When you use DocketMath (via /tools/statute-of-limitations), the core input is usually your key date, such as:

  • the date of the incident (if that’s when accrual is clear), or
  • a later date tied to discovery/knowledge (if accrual is disputed or delayed)

Then DocketMath applies the configured period (1 year for the Georgia general default period used here).

Output behavior to watch:

  • If you move your assumed accrual date forward by even weeks, your calculated deadline moves forward by the same amount (because the rule is a fixed duration).
  • If you choose the date of incident but the facts suggest accrual depended on knowledge, your deadline may be earlier than it should be—so your input choice affects the result.

Quick example (illustrative)

  • Incident/known facts: March 1, 2025
  • General period: 1 year
  • Calculated deadline (baseline): March 1, 2026

If you instead enter an accrual date of June 15, 2025, the baseline deadline becomes June 15, 2026.

Key exceptions

Georgia’s general 1-year rule is the baseline described above, but exceptions can change the outcome. Below are the categories of timing doctrines that frequently affect real-world deadlines. This isn’t an exhaustive list—rather, it’s a checklist of what to verify before relying on a single calculated end date.

Exceptions and adjustments that can matter

  • Accrual disputes
    The biggest swing factor is the accrual date—when the clock starts. Even with a fixed statutory period (like 1 year), the timeline depends on what date you can reasonably justify as accrual.

  • Tolling (pauses/interruptions)
    Some circumstances can pause limitations. Whether tolling applies depends on the legal basis and the facts. If tolling is potentially relevant, your effective deadline may extend beyond the baseline.

  • Multiple plaintiffs or related claims
    Different plaintiffs can accrue at different times. Likewise, some claims may be treated differently based on their elements and how the facts connect to the injury.

  • Administrative prerequisites under the FTCA framework
    FTCA litigation involves procedural steps before filing a lawsuit. Even if a limitations period exists in the background, the timing interplay between administrative steps and court filing can be critical.

Pitfall: A “1-year” deadline can look straightforward, but the calculated deadline is only as good as the accrual date you enter. Many timing losses happen because the accrual date assumption is wrong.

Practical checklist before you rely on the 1-year default

Use this quick set of questions to stress-test your deadline:

Statute citation

Georgia’s general statute of limitations period used as the baseline for this page is:

  • O.C.G.A. § 17-3-1
    General SOL period: 1 years (Georgia general/default period for the relevant tort category covered by the statute)

Source: https://law.justia.com/codes/georgia/2021/title-17/chapter-3/section-17-3-1/?utm_source=openai

No claim-type-specific sub-rule was identified in the provided jurisdiction notes for this page, so this section treats the 1-year period as the general/default rule for the purpose of the calculator and baseline timeline.

Use the calculator

To generate a Georgia-based deadline for this general/default 1-year period, use DocketMath’s statute-of-limitations calculator:

How to use it (inputs and expected output)

  1. Select the jurisdiction: Georgia (US-GA)
  2. Select the rule set: FTCA (Georgia general/default baseline using O.C.G.A. § 17-3-1)
  3. Enter the key date:
    • the incident date, or
    • the date you believe the claim accrued (e.g., discovery/knowledge date), depending on your fact theory
  4. Review the calculated deadline:
    • DocketMath will compute a deadline using the configured 1-year limitation period.

How changing inputs changes the result

  • If your accrual date is moved later, your deadline moves later by the same elapsed time (because the period is fixed at 1 year).
  • If you enter the date of incident but the correct accrual date is later, the output will understate your time window.

Warning: Don’t treat a single calculated date as “guaranteed safe.” If any tolling or accrual dispute could exist, you should model alternative accrual dates to understand the deadline risk profile.

Related reading