Direct Answer
There is no single FAA-specific statute of limitations that caps every kind of enforcement. Two distinct timeliness rules matter most. For certificate actions (suspension or revocation), the NTSB's rules of practice include a “stale complaint” rule at 49 CFR §821.33: if the FAA's complaint alleges offenses that occurred more than 6 months before the FAA advised the respondent of the reasons for the proposed action, the respondent may move to dismiss, and the FAA must then show good cause for the delay or that a sanction is warranted in the public interest. For civil penalties (money), the general federal statute of limitations in 28 U.S.C. §2462 sets a five-year outer boundary, running from the date the claim first accrued.
Two practical wrinkles keep this from being a clean countdown: the §821.33 clock measures how long the FAA delayed after it had reason to act (not the age of the conduct), and a continuing violation — like an ongoing recordkeeping gap — can accrue separately for each day it persists. Because timeliness is genuinely fact-specific and forum-specific, whether a deadline bars a particular claim is a legal question for an aviation attorney. What you control is the evidence those arguments rely on: records that are current, complete, and dated.
“How long does the FAA have to come after me?” is one of the most-searched questions in aviation enforcement, and the honest answer is that it depends on what kind of action the FAA is bringing and on how your timeline looks in the records. There is no tidy, one-size clock. Instead there are two rules that operate on two different tracks — and a handful of doctrines (continuing violations, the timing of when the FAA “knew”) that make a simple date-counting exercise more complicated than it first appears.
This article does three things: it lays out the two rules in plain English (verified against the regulation and statute, not a forum post), it clears up the myths that trip operators up, and it explains the one part of this you can actually control before anything ever happens — the dated records that any timeliness argument is built on. It pairs naturally with our explainer on what to do when you receive an FAA Letter of Investigation and the broader map of compliance action vs. formal enforcement.
A necessary disclaimer before we go further
This is general compliance-document information, not legal advice, and FileFlo is a compliance software company, not a law firm. Enforcement is fact-specific. Whether a statute of limitations or the stale-complaint rule actually bars a given allegation depends on the precise facts, the forum, the type of action, and how the relevant doctrines apply — all of which are legal questions. If you have received any FAA correspondence, or believe an enforcement matter is possible, consult an experienced aviation attorney before relying on any timeliness argument. Nothing here should be used to decide how to respond to the FAA or NTSB.
The Two Timeliness Rules — On Two Different Tracks
The single most useful thing to understand is that FAA enforcement splits into two broad tracks, and each has its own timeliness rule. Certificate actions — where the FAA seeks to suspend or revoke a certificate — are appealed to an NTSB administrative law judge under the NTSB's rules of practice, which include the stale-complaint rule. Civil penalty actions — where the FAA seeks money — proceed under the FAA's own rules of practice and, as a general matter, against the five-year federal statute of limitations. Mixing the two up is the source of most confusion.
NTSB "stale complaint" rule
49 CFR §821.33Where it applies
Certificate actions (suspension / revocation) appealed to an NTSB law judge
What triggers it
The FAA’s complaint alleges offenses that occurred more than 6 months before the FAA advised the respondent of the reasons for the proposed action.
What it means in practice
The respondent may move to dismiss the stale allegations. The FAA must then show good cause for the delay, or that a sanction is warranted in the public interest, or the law judge dismisses the stale allegations and adjudicates the rest.
General federal civil-penalty limitations period
28 U.S.C. §2462Where it applies
Civil penalty (money) actions for fines, penalties, or forfeitures
What triggers it
The government must commence an action within five years from the date when the claim first accrued.
What it means in practice
Functions as the outer boundary for a civil-penalty action on a given violation. A continuing violation can accrue separately for each day it persists, which can extend the practical exposure window.
A third path: compliance action, not enforcement at all
Not every FAA concern becomes a timed enforcement action. Under the FAA's Compliance Program, many minor or first-time issues are resolved through documented corrective action rather than a penalty or certificate action — which never reaches the timeliness rules above. We cover that distinction in compliance action vs. enforcement and letter of correction vs. warning vs. investigation.
The timeline you can prove starts with the records you keep
Every timeliness argument depends on dates — and dates depend on records that exist, are complete, and can be produced on demand. The free FAA Readiness Score shows you where your recordkeeping has gaps that would weaken any chronology, across training currency, maintenance releases, duty/rest, required management, and drug-and-alcohol records. No signup; under 3 minutes.
Run the Free FAA Readiness ScoreThe NTSB Stale-Complaint Rule, in Detail
The stale-complaint rule is the one most people mean when they ask about an FAA “statute of limitations,” so it is worth reading closely. It appears in the NTSB's rules of practice for certificate actions at 49 CFR §821.33. Here is the structure of the rule, in plain English.
The 6-month trigger
The rule applies where the FAA’s complaint states allegations of offenses that occurred more than 6 months before the FAA advised the respondent of the reasons for the proposed action. The clock is the gap between the conduct and that advisement — not simply the age of the conduct.
The respondent moves to dismiss
When the trigger is met, the respondent may file a motion to dismiss the stale allegations. This is a defense the respondent raises — it is not something the law judge applies automatically — which is one reason having counsel matters from the outset.
The FAA gets a chance to justify the delay
In response to the motion, the FAA must show either that good cause existed for the delay in advising the respondent, or that the imposition of a sanction is warranted in the public interest notwithstanding the delay or the reasons for it.
If the FAA cannot, the stale allegations are dismissed
If the FAA fails to make that showing, the law judge dismisses the stale allegations and proceeds to adjudicate the remaining (timely) portion of the complaint. So a finding of staleness can narrow a case rather than end it entirely.
A special path for qualification cases
Where the complaint alleges a lack of qualification, the rule has a separate step: the law judge first determines whether a disqualification issue would exist if all the allegations — stale and timely together — were assumed true. If so, the motion is denied; if not, the standard good-cause / public-interest analysis applies.
Read the rule, then call your attorney
The summary above is a plain-English reading of the rule's structure and is not a substitute for the text or for legal advice. The precise mechanics — timing of the motion, what counts as “good cause,” how the public-interest showing is evaluated, and how appellate review works — are exactly the kind of details an aviation attorney handles. If the rule might apply to your matter, that is a conversation to have with counsel, not a decision to make from a blog post.
Notice what the rule is really about: it is a check on the FAA sitting on allegations after it had reason to act. That is why the timeline of when the FAA knew what it knew matters as much as the date of the conduct — and why a clean, dated record of when issues arose and when they were resolved on your side helps frame the picture. For the document-request mechanics that often surround these timelines, see our guide to FAA records requests during a Part 135 investigation.
Myths vs. Reality: Where Operators Get the Clock Wrong
Most of the bad timeliness assumptions come from treating these rules like a simple expiration date. They are not. Here are the misconceptions we hear most, alongside what the rules actually say.
The myth
The clock starts the day the violation happened.
The reality
For the §821.33 stale-complaint rule, the 6-month measure is the gap between the offense and when the FAA advised the respondent of the reasons for the proposed action — not the age of the conduct alone. A complaint can describe older events and still survive if the FAA acted promptly once it had a basis, or shows good cause / public interest.
The myth
If it is more than 6 months old, the FAA automatically loses.
The reality
No. A stale-complaint motion gives the FAA the chance to show good cause for the delay or that a sanction is warranted in the public interest. If it makes that showing, the allegations proceed. Timeliness is a defense to be argued, not an automatic bar.
The myth
The 6-month rule and the 5-year rule are the same thing.
The reality
They are different rules on different tracks. §821.33 (6 months) is the NTSB stale-complaint rule for certificate actions; 28 U.S.C. §2462 (5 years) is the general federal limitations period for civil penalties. They apply in different forums under different procedures.
The myth
A continuing recordkeeping gap can only count from the first day it appeared.
The reality
A continuing violation can be treated as a separate offense for each day it persists. An ongoing documentation gap can therefore keep generating fresh exposure — which is a reason to close gaps the moment you find them, not just before an audit.
The myth
Timeliness is something my records can prove on their own.
The reality
Your dated records establish the chronology a timeliness argument needs — but whether a limitations period bars a claim is a legal question. Records give your attorney the evidence; the legal conclusion is the attorney’s.
Where Records Actually Help a Timeliness Argument
You cannot change when the FAA acts, and you should not try to argue a limitations question yourself. But you can make sure the one input every timeliness argument depends on — a clean, dated chronology — exists in evidence. Here is how good records support that, without ever crossing into legal advice.
Contemporaneous dates on every record
Timeliness arguments live and die on dates: when conduct occurred, when a check was current, when a record was created. A record dated at the time of the event is far stronger evidence than one reconstructed later — and it is what lets your attorney frame how old an allegation truly is.
A documented open-and-close trail for every deficiency
Whether an issue was a one-time event or a continuing violation often turns on when it was opened and when it was resolved. A clear corrective-action record — what was wrong, what was done, and the date it closed — establishes that an issue ended rather than persisted.
Instant retrieval in the order requested
When a timeliness question arises, you and your counsel need the relevant records immediately — not after a week of digging. Records that can be produced on demand, in the sequence asked for, turn a chronology argument from a scramble into a fact pattern.
Completeness, so there are no silent gaps
The most damaging timelines are the ones with holes — a missing entry that looks like an unresolved problem. Surfacing every expiring record before it lapses keeps the file complete, so the chronology your attorney works from has no unexplained blanks.
The honest line: records do not win a statute-of-limitations argument — your attorney does, on the law and the facts. What records do is supply the facts. A timeline you can prove with contemporaneous, dated documents is a far stronger foundation than one reconstructed from memory after a Letter of Investigation arrives. The work that pays off is the work you do before anything happens.
Go deeper on enforcement and the rules around it
FileFlo: the dated proof layer behind your timeline
FileFlo is a compliance document intelligence platform — a proof layer that sits alongside your existing stack and keeps the documents those systems produce current, complete, time-stamped, and instantly retrievable. It classifies over 600 document types against the governing regulations, tracks expiration windows on every medical, training check, and equipment inspection, surfaces each one 90/60/30 days before it lapses, and produces an inspector-format binder on demand. The result is a clean, dated chronology — the raw material any timeliness analysis is built on.
What FileFlo does not do is just as important: it does not give legal advice, calculate statutes of limitations, decide whether the stale-complaint rule applies, represent you to the FAA or NTSB, file or argue any motion, or guarantee any outcome. Those are your aviation attorney's job. FileFlo's job is narrower and concrete — make sure the dated evidence your attorney needs actually exists and can be produced. (And no, we are not SOC 2 certified; we will tell you exactly what our security posture is rather than imply a badge we do not hold.)
Frequently Asked Questions
Is there a statute of limitations on FAA enforcement?
There is no single FAA-specific statute of limitations that caps every kind of enforcement. Two distinct timeliness rules matter most. For certificate actions (suspension or revocation), the NTSB's rules of practice include a "stale complaint" rule at 49 CFR §821.33: if the FAA's complaint alleges offenses that occurred more than 6 months before the FAA advised you of the reasons for the proposed action, you can move to dismiss, and the FAA must then show good cause for the delay or that a sanction is warranted in the public interest. Separately, FAA civil penalty actions are generally subject to the five-year federal statute of limitations in 28 U.S.C. §2462. These are general frameworks, not legal advice — how either applies to your situation is fact-specific and a question for an aviation attorney.
What is the NTSB stale complaint rule?
The stale complaint rule lives in the NTSB's rules of practice at 49 CFR §821.33. It applies to certificate actions that are appealed to an NTSB administrative law judge. When the FAA's complaint states allegations of offenses that occurred more than 6 months before the FAA advised the respondent of the reasons for the proposed action, the respondent may move to dismiss those allegations as stale. The FAA then has the burden, within the time the rule allows, to show either that good cause existed for the delay in providing that advice, or that imposing a sanction is warranted in the public interest notwithstanding the delay. If the FAA cannot make that showing, the law judge dismisses the stale allegations and proceeds to adjudicate the rest of the complaint.
How far back can the FAA go in an enforcement case?
It depends on the type of action and on your records. The NTSB stale complaint rule (49 CFR §821.33) creates a 6-month trigger for certificate-action allegations: once the FAA has known the reasons long enough that the allegations are more than 6 months old when you are advised, you can force the FAA to justify the delay. For civil penalties, the general federal statute of limitations in 28 U.S.C. §2462 sets a five-year outer boundary, running from when the claim first accrued. But several things complicate "how far back": a continuing violation (such as an ongoing recordkeeping gap) can be treated as a separate offense for each day it persists, which can extend the practical exposure window. Falsification and certain serious matters are also treated differently. This is why the answer is genuinely fact-specific — confirm any timeliness question with an aviation attorney.
Does the 6-month stale complaint clock start when the violation happened?
No — and this is the most common misunderstanding. The 6-month period in 49 CFR §821.33 does not run from the date of the alleged offense. It is measured against the gap between when the offense occurred and when the FAA advised the respondent of the reasons for the proposed action. The rule is about how long the FAA sat on allegations after it had reason to act, not simply about how old the conduct is. So a complaint can describe older events and still survive a stale-complaint motion if the FAA advised the respondent promptly once it had the basis to do so, or if it shows good cause or a public-interest justification for the delay.
Does the stale complaint rule apply to civil penalties or just certificate actions?
The 49 CFR §821.33 stale complaint rule is part of the NTSB's rules of practice, which govern certificate actions (suspensions and revocations) that are appealed to an NTSB administrative law judge. It is not the rule that governs FAA civil penalty (money) cases, which proceed under the FAA's own rules of practice and, as a general matter, are subject to the five-year federal statute of limitations in 28 U.S.C. §2462. In short: think of §821.33 as the timeliness rule on the certificate-action side and the §2462 five-year period as the outer limit on the civil-penalty side. Because the two tracks have different rules and different forums, the timeliness analysis is genuinely fact-specific and belongs with an aviation attorney.
What is 28 U.S.C. 2462 and how does it apply to FAA fines?
28 U.S.C. §2462 is the general federal statute of limitations for civil fines and penalties. It provides that an action, suit, or proceeding for the enforcement of any civil fine, penalty, or forfeiture shall not be entertained unless commenced within five years from the date when the claim first accrued. As a general framework, FAA civil penalty actions are subject to this five-year period, which functions as the outer boundary for the government to commence an action on a given violation. The wrinkle is that a continuing violation can accrue separately each day it persists, so an ongoing documentation gap can keep generating fresh exposure. Whether and how §2462 bars a specific claim is a legal question — not something to assume — and should be confirmed with an aviation attorney.
Can the FAA still act on an old complaint if it is stale?
Possibly. Calling allegations "stale" under 49 CFR §821.33 does not automatically end the case. When a respondent moves to dismiss stale allegations, the FAA gets an opportunity to show either that good cause existed for the delay in advising the respondent, or that imposing a sanction is warranted in the public interest despite the delay. If the FAA makes that showing, the allegations proceed. There is also a separate path in the rule for qualification cases: where lack of qualification is alleged, the law judge first decides whether a disqualification issue would exist if all the allegations — stale and timely together — were assumed true. The takeaway is that timeliness is a defense to be raised and argued, not an automatic bar, which is exactly why counsel matters.
How do dated records help with a statute-of-limitations or stale-complaint defense?
Timeliness arguments turn on dates and timelines — when conduct occurred, when a record was created or corrected, when a deficiency was opened and closed, and when the FAA knew what it knew. Complete, contemporaneously dated records are what let you (and your attorney) establish that chronology with evidence rather than memory. If a record shows a corrective action was completed on a specific date, or that a check was current as of a given day, that documentation can be decisive in framing how old an allegation really is and whether an issue was continuing or resolved. FileFlo is the compliance proof layer that keeps those records current, complete, time-stamped, and instantly retrievable. It does not give legal advice, represent you to the FAA or NTSB, calculate limitations periods, or argue timeliness for you — that is your aviation attorney's role. What it does is make sure the dated evidence those arguments depend on actually exists and can be produced.
You can't control the clock. You can control the evidence.
Timeliness defenses are won by attorneys, on the facts — and the facts come from your records. FileFlo keeps every required document current, surfaces what's about to lapse, time-stamps the chronology, and produces an inspector-ready binder in seconds, so the dated proof is there long before any question of “how far back” ever comes up. Starter at $89/month, Professional at $299/month (unlimited pilots + aircraft). Five-day free trial, no credit card.
5-day free trial · No credit card required · Cancel anytime · A compliance document proof layer — not a law firm, not legal counsel, and not a substitute for your SMS, dispatch, or maintenance tracking system.