Statute of Limitations for Federal Tort Claims Act (FTCA) in Kentucky
6 min read
Published March 22, 2026 • By DocketMath Team
Overview
If you plan to bring a claim under the Federal Tort Claims Act (FTCA) in Kentucky (US-KY), one of the first deadlines to track is the statute of limitations—the time limit for filing your lawsuit in federal court.
For FTCA cases, the limitations rules function as a federal timing framework. Kentucky’s state limitations rules (for example, for personal injury) generally do not control FTCA filing deadlines. Instead, the FTCA has its own time limits, and Kentucky-specific procedural concepts mainly matter after the federal deadline is met (or missed).
That said, because your questions may involve Kentucky timelines and Kentucky law concepts, DocketMath’s statute-of-limitations calculator for US-KY is designed to show a clear “default” timeline based on Kentucky’s general limitations statute, which can affect related state-court or supplementary timing in practical workflows.
Note: This page uses Kentucky’s general/default limitations period identified by the jurisdiction data. It does not claim a special FTCA sub-rule for a particular claim type, because none was found in the provided jurisdiction data.
Limitation period
Kentucky default/general period (as used by the calculator)
DocketMath uses the following default limitation period for US-KY:
- General SOL period: 5 years
- General statute: KRS 500.020
- Claim-type-specific sub-rule: Not found in the provided jurisdiction data, so the default applies.
In plain terms: if you’re computing a Kentucky-based limitations window using DocketMath’s statute-of-limitations tool, you should start from a 5-year deadline derived from KRS 500.020 and then adjust only for whatever triggers/exceptions your scenario requires (see “Key exceptions”).
What the calculator output typically depends on
When you use a statute-of-limitations calculator, the output usually turns on two inputs:
- Start date (trigger date): the date your clock begins running (often tied to when the injury occurred, harm was discovered, or the wrongful act concluded—exact trigger logic depends on the governing rule you’re applying).
- Jurisdiction: here, US-KY.
- Default period: automatically set to 5 years based on KRS 500.020 (per this Kentucky jurisdiction data).
As a result:
- If the start date moves later, the end date also moves later (because the limitation window extends forward).
- If you change the jurisdiction, the end date can shift because the governing general period can change.
Practical checklist before you file
Before relying on any calculated deadline, gather:
- Date of the event or harm (and any “discovery” date if your situation involves discovery timing under the relevant legal regime)
- Date you first considered filing
- Date you actually filed (or plan to file)
- Forum: federal vs. state, since FTCA is a federal statute even when your underlying facts are Kentucky-based
Pitfall: A calculated “end date” is only as good as your chosen trigger date. If you use the wrong start date (for example, the date someone first told you about a harm instead of when the harm occurred), you can end up with a deadline that is off by months or years.
Key exceptions
Even when a jurisdiction has a clear general/default limitation period, real-world deadlines can change due to exceptions. Because this page is anchored to KRS 500.020 as the Kentucky general rule found in the jurisdiction data, treat exceptions as scenario-dependent—they can either extend or sometimes bar the claim depending on the doctrine.
Here are the kinds of exceptions commonly encountered in limitations timing workflows, and what to look for when you run your calculation:
- Tolling (pauses in the clock):
- Some legal situations temporarily “stop” or “pause” the running of a limitations period.
- Examples in many legal systems include certain notice requirements, disabilities, or procedural events.
- Accrual timing disputes (the start date question):
- Often the biggest practical issue is not the length of the limitation period (here: 5 years) but when the clock starts.
- You may need to document why your chosen trigger date is defensible under the governing rule.
- Multiple claims with different triggers:
- If facts involve separate acts or continuing harm, one part of the timeline may start earlier than another.
- A single lawsuit can include claims that are not all “born” on the same date.
- Procedural posture changes:
- If there are transfers, dismissals, or refilings, you may need to reassess whether and how limitations continues to matter.
Because the provided jurisdiction data did not identify any FTCA-claim-type-specific Kentucky sub-rule, DocketMath’s calculator should be treated as using the general/default 5-year period from KRS 500.020, then layered with exceptions only where your case facts and governing law supply them.
Warning: Exceptions are where many deadline errors happen. If your scenario involves disability, notice/timing requirements, or ongoing conduct, you should verify the exception logic before treating the calculator output as final.
Statute citation
DocketMath’s Kentucky default/general statute-of-limitations period for this jurisdiction is:
- KRS 500.020 — General limitation period: 5 years
Per the jurisdiction note provided:
- No claim-type-specific sub-rule was found in the provided Kentucky jurisdiction data.
- Therefore, the 5-year general/default period applies as the base rule used by the calculator.
Use the calculator
Use DocketMath’s statute-of-limitations calculator to generate a practical deadline window for US-KY:
Open the statute-of-limitations calculator
Inputs you’ll typically control
Check these before you run the tool:
- Jurisdiction: US-KY
- Start/trigger date: the date you believe the clock begins
- Default SOL period: automatically treated as 5 years (from KRS 500.020)
- Exceptions/tolling notes: if your tool workflow supports it, capture the exception facts you plan to account for (for example, a pause event date)
How changing inputs changes outputs
Use this quick “what-if” guide while testing your numbers:
- ✅ If you select a later start date, the computed deadline moves later (same 5-year length).
- ✅ If you adjust the trigger date by a few weeks, you’ll see a corresponding shift in the output end date.
- ✅ If you include an exception/tolling adjustment (when available in the tool workflow), the end date may extend beyond the simple 5-year calculation.
Example workflow (conceptual)
- Choose the Kentucky jurisdiction (US-KY)
- Enter your best-supported start date
- Let the tool apply the 5-year default
- Review the calculated deadline and document the trigger-date reasoning
Pitfall: Avoid “back-solving” without clarity. If you only enter a date because the result “looks right,” you may lock yourself into the wrong trigger date.
When you’re done, save the output and keep the inputs you used—future amendments to your trigger-date assumptions often require recalculating the end date.
Sources and references
Start with the primary authority for Kentucky 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
- Choosing the right statute of limitations tool for Vermont — Tool comparison
- Choosing the right statute of limitations tool for Connecticut — Tool comparison
