Direct Answer — Compliance Action vs Enforcement
A compliance action and a legal enforcement action are two different ways the FAA can respond to the same apparent deviation. A compliance action is a non-enforcement tool under the FAA Compliance Program (FAA Order 8000.373, currently 8000.373C) — the FAA fixes an unintentional, non-reckless mistake with you through education, on-the-spot correction, counseling, or remedial training. A legal enforcement action is the formal track under 14 CFR Part 13: administrative action under §13.11 (Warning Notice or Letter of Correction), a civil penalty under §13.16, or a certificate suspension or revocation under §13.19. The pivotal question is whether you were willing and able to return to compliance — and the most objective evidence of that is your records. Complete, current, immutable, retrievable records, plus documented corrective action, support the compliance-action side; gaps, contradictions, or altered entries point the other way.
The Compliance Program is FAA policy — not a regulation
The compliance-action vs enforcement decision lives in FAA Order 8000.373 and supporting FAA guidance, so there is no “compliance action” CFR section to cite. The enforcement procedures, by contrast, are codified in 14 CFR Part 13. Keep the two straight: a program (policy) decides which track; a regulation (Part 13) governs how the enforcement track runs.
One Deviation, Two Possible Tracks
Picture a finding from a ramp inspection or a surveillance audit — a missing maintenance entry, an out-of-date training record, an airworthiness item that slipped. The same facts can travel down one of two very different roads. Which road depends less on the deviation itself and more on what the deviation says about you: was it a one-off mistake by an operator with a sound system, or a symptom of an operation that is unwilling or unable to comply?
A non-enforcement response under the FAA Compliance Program. The FAA works with you to correct an unintentional deviation and fix its root cause.
- On-the-spot correction of a simple issue
- Counseling that clarifies the requirement
- Additional or remedial training, with a documented syllabus
- Suggested improvements to organizational processes
Source: FAA Compliance Program, FAA Order 8000.373.
The formal track under 14 CFR Part 13 — a sanction, with process and (potentially) appeal rights.
- Warning Notice or Letter of Correction (§13.11)
- Civil penalty — a monetary sanction (§13.16)
- Certificate suspension, amendment, or revocation (§13.19)
- NTSB appeal rights for certificate actions
Source: 14 CFR Part 13 (FAA enforcement procedures).
A quick note on terminology: a Warning Notice and Letter of Correction (§13.11) are sometimes called “administrative actions,” and they sit between the two tracks — they are part of the FAA’s enforcement framework in Part 13, but they are the lightest end of it. A compliance action under the Compliance Program is something different again: it is not an enforcement action at all. Because the labels overlap in everyday conversation, this is one of the most common points to clarify with aviation counsel before responding.
The FAA Compliance Program — What It Is (and Isn’t)
The FAA Compliance Program is FAA policy — guidance set out in FAA Order 8000.373 (the current version is 8000.373C, issued June 2022). It is not a federal regulation, and there is no CFR section that creates a “compliance action.” Its stated philosophy is straightforward: when a deviation can be corrected without an enforcement action, the FAA should use educational, counseling, and corrective measures first.
The program is built around the idea that most deviations in a healthy operation are unintentional — the result of a simple mistake, a flawed process, a lack of understanding, or diminished skills — and that the fastest route to a safer system is to find the root cause and fix it. A compliance action is the tool for exactly that situation.
What a compliance action can look like
On-the-spot correction
A simple fix the FAA and the operator resolve in the moment, with no formal follow-up required.
Counseling
A formal discussion that clarifies the regulatory requirement and how to meet it going forward.
Additional / remedial training
A structured syllabus with documented objectives — the training and its completion become records.
Process improvement
Suggested changes to organizational procedures so the same deviation does not recur.
A compliance action is not a free pass — and it is not legal advice from us to you
A compliance action is a non-enforcement tool, but the conduct is still evaluated, the action can be documented by the FAA, and AOPA cautions that the potential for a subsequent enforcement action remains if agreed corrective measures are not completed. Whether any particular response is a compliance action or enforcement — and what it means for you — is fact-specific. Treat any FAA contact seriously and consult aviation counsel.
The Compliance Program is closely related to the FAA’s voluntary safety programs, which are also policy rather than CFR. If you are weighing whether to self-disclose, compare ASAP vs VDRP vs ASRS — which to file and the operator-focused VDRP voluntary disclosure for Part 135. Those programs and the Compliance Program share the same underlying philosophy: surface the issue, fix the root cause, and document it.
The Deciding Question: Willing and Able to Comply
Under the Compliance Program, the core question the FAA asks is whether the certificate holder is both willing and able to return to compliance. Both words carry weight, and an operator can fail the test on either one.
“Willing”
Generally shown by:
- Acknowledging the issue rather than minimizing or hiding it
- Sharing information openly with the FAA
- Taking — and committing to — corrective action
“Able”
Generally shown by having:
- The resources to actually fix the underlying cause
- The personnel and competence to follow through
- A process that makes recurrence unlikely
What takes a case out of the compliance-action lane
FAA guidance treats several categories as pointing toward enforcement rather than a compliance action. These are legal determinations — the list below is a plain-English summary, not a substitute for counsel:
Intentional conduct
A deliberate decision to deviate, rather than an honest mistake.
Reckless conduct
Conduct showing gross disregard for, or deliberate indifference to, safety.
Failure to complete agreed corrective action
Committing to a fix and then not following through.
Unacceptable safety risk
Conduct that presents a risk the FAA cannot allow to continue.
Enforcement mandated by statute or regulation
Some matters require enforcement regardless of intent.
A repeated history of similar deviations
A pattern suggests the operation is not actually returning to compliance.
Falsification is its own category
Knowingly making a false record can itself be a basis for enforcement under the FAA’s falsification rules — now consolidated in 14 CFR Part 3, Subpart D (§§3.403–3.405) after former §43.12 was reserved effective November 3, 2025 — separate from whatever the underlying deviation was. This is the sharpest reason never to “clean up” a record after the fact. See FAA falsification of maintenance records (§43.12) and the correct way to fix an error in how to correct a maintenance logbook entry.
Are your records ready to tell the willing-and-able story?
See where your aviation document set stands before the FAA ever asks — then keep it audit-ready.
Related Aviation Compliance Guides
The Enforcement Track — 14 CFR Part 13
When a matter moves to legal enforcement, the procedures are codified in 14 CFR Part 13. Three sections cover the responses an operator is most likely to encounter. (The exact text and procedures matter — verify against the regulation and consult counsel for any real matter.)
Administrative disposition of certain violations
When the FAA determines that an apparent violation does not warrant legal enforcement, it may use a Warning Notice — which recites the available facts and indicates that the conduct may have been a violation — or a Letter of Correction, which states the corrective action the apparent violator has taken or agreed to take. The rule notes that if the violator does not complete the agreed corrective action, the FAA may pursue formal legal enforcement.
Civil penalties (administrative assessment)
This section sets out the FAA’s procedures for administratively assessing civil penalties against businesses (and, for hazardous materials, against all persons), exercising the FAA’s authority under 49 U.S.C. It covers the notice process, the right to a hearing, payment, and the option to compromise. Penalty amounts are adjusted over time and are proposed before they are final — a proposed civil penalty is the start of a process, not the end of one.
Certificate actions appealable to the National Transportation Safety Board
This is the suspension, amendment, or revocation of a certificate (airman, airworthiness, operating, and others). For non-emergency actions, the certificate holder generally receives advance notice and an opportunity to respond, may request an informal conference, and may appeal to the NTSB. Emergency orders take effect immediately, with a limited path to ask the Board to review whether an emergency in fact exists.
A statute sits on top of all of this: the Pilot’s Bill of Rights
The Pilot’s Bill of Rights (Public Law 112-153, signed August 3, 2012) is a federal statute — not an FAA program or a CFR section. It requires the FAA to give an airman timely written notice of an investigation that could lead to enforcement against an airman certificate, to identify the nature of the investigation, and to advise the airman of certain rights, including the ability to request relevant air traffic data. It governs process, not the compliance-vs-enforcement choice. If you receive a written notice of investigation, that is the moment to call aviation counsel — see FAA ramp check pilot rights.
Two related reads round out the enforcement picture for paperwork-driven cases: FAA fines for Part 135 paperwork violations walks through how recordkeeping gaps become penalties, and the FAA crackdown on illegal “grey” charter shows the high end of the enforcement spectrum, where intent and operational-control evidence drive the outcome.
How Your Records Decide Which Track You Get
Here is the through-line of this whole article. The FAA’s choice between a compliance action and enforcement turns on two judgments — was this an isolated, unintentional deviation? and is this operator willing and able to return to compliance? — and the most objective evidence for both is your records. Records are not paperwork for its own sake; in a compliance inquiry they are the story you can prove.
| What the FAA is weighing | Records that support a compliance action | Records that point toward enforcement |
|---|---|---|
| Was this isolated, or a pattern? | A clean, complete history showing the deviation is a one-off | Repeated gaps or the same finding recurring over time |
| Was it unintentional? | Contemporaneous entries consistent with an honest mistake | Late-created or back-dated entries; signs of clean-up |
| Are you willing to fix it? | A documented root-cause analysis and a corrective-action record | No evidence of any corrective action taken or committed |
| Are you able to fix it? | Completed training records, updated procedures, verified entries | Committed corrective steps with no proof of completion |
| Did you preserve integrity? | Immutable, version-tracked records with a clear audit trail | Altered, missing, or contradictory records (a falsification risk) |
| Can you produce it on demand? | An indexed record set retrievable in minutes for an inspector | A scramble across email, shop systems, and file cabinets |
None of this is about gaming the system. It is the opposite: an operator with current, complete, immutable records and a documented corrective-action habit usually is the willing-and-able operator the Compliance Program is designed for — and the records simply let them prove it quickly. The operator who cannot find a training record, or whose maintenance entries do not match the work, has a harder story to tell even when the underlying mistake was innocent. For the specific records that come up most, see what records a Part 135 operator must keep, §43.9 maintenance entry requirements, and the aviation records retention schedule.
FileFlo as the Proof Layer Behind a Compliance Action
FileFlo is a compliance document intelligence platform — the proof layer for your records. It does not represent you to the FAA, file a disclosure on your behalf, give legal advice, run your safety program, or guarantee any outcome. Those belong to you and to qualified counsel. What FileFlo does is keep the document set the FAA weighs — current, complete, immutable, and instantly retrievable — and help you document corrective action when something needs fixing.
- Classifies and indexes your aircraft, crew, training, and maintenance records so a deviation looks like the one-off it is, not a pattern
- Tracks currency and expirations so fewer deviations happen in the first place
- Preserves an immutable, version-tracked history — the integrity that keeps a record set defensible and away from any falsification question
- Captures corrective-action documentation (root cause, completed training, verified re-entry) that evidences willing and able
- Generates an inspector-ready records index on demand, so "produce the records" is a button, not a scramble
FileFlo classifies 600+ document types and manages records across Part 91, Part 135, and Part 145 operators. Pricing: Starter $89/mo, Professional $299/mo. 5-day free trial, no credit card required. FileFlo keeps the documents that prove compliance audit-ready — it is not an SMS, a dispatch/flight-operations system, an attorney, or a guarantee of any FAA outcome.
Frequently Asked Questions
What is the difference between an FAA compliance action and an enforcement action?
A compliance action and a legal enforcement action are two different responses the FAA can take to the same apparent deviation. A compliance action is a non-enforcement tool under the FAA Compliance Program (FAA Order 8000.373): the FAA uses education, on-the-spot correction, counseling, or remedial training to fix an unintentional, non-reckless mistake — it is not a sanction. A legal enforcement action is the formal track under 14 CFR Part 13: administrative action (a Warning Notice or Letter of Correction under §13.11), a civil penalty (§13.16), or a certificate suspension or revocation (§13.19). Which one you get is largely decided by whether you were willing and able to return to compliance — and whether you can produce records that show it.
Is a compliance action an enforcement action that goes on my record?
No. The FAA Compliance Program describes a compliance action as a non-enforcement method to correct unintentional deviations — it is not a legal enforcement action and is not the same as a certificate suspension or civil penalty. That said, this is exactly the kind of fact-specific point you should confirm with aviation counsel for your situation: a compliance action can be documented by the FAA, the conduct can still be evaluated, and AOPA cautions that the potential for a subsequent enforcement action remains if agreed corrective measures are not completed. The takeaway for an operator is to treat a compliance action seriously, complete every committed corrective step, and keep the documentation proving you did.
What is the FAA Compliance Program (Order 8000.373)?
The FAA Compliance Program is FAA policy — guidance set out in FAA Order 8000.373 (the current version is 8000.373C, issued in June 2022) — not a federal regulation. Its philosophy is that when a deviation can be corrected without an enforcement action, the FAA should use educational, counseling, and corrective measures first. The program reserves enforcement for conduct that is intentional or reckless, for repeated deviations, for an unacceptable safety risk, for failure to complete agreed corrective action, and for cases where enforcement is required by statute or regulation. Because it is a program and not a CFR section, you will not find a 'compliance action' rule number in the regulations — it is found in the Order and supporting FAA guidance.
What decides whether the FAA chooses a compliance action or enforcement?
The core question under the Compliance Program is whether the certificate holder is both willing and able to return to compliance. 'Willing' generally means acknowledging the issue, sharing information openly, and taking corrective action. 'Able' generally means having the resources, personnel, and competence to actually fix the underlying cause. When both are present and the deviation was an unintentional mistake, a compliance action is appropriate. When conduct is intentional or reckless, when deviations repeat, when there is an unacceptable safety risk, or when an operator will not or cannot correct the root cause, the case moves toward enforcement. Records are central to this judgment because they are the most objective evidence of whether you were both willing and able.
What kinds of conduct push a case from compliance action to enforcement?
FAA guidance treats several categories as taking a matter out of the compliance-action lane: intentional conduct; reckless conduct showing gross disregard for or deliberate indifference to safety; failure to complete agreed-upon corrective action; conduct presenting an unacceptable risk to safety; and situations where enforcement is mandated by statute or regulation. A repeated history of similar deviations can also push a case toward enforcement. Falsification of records is a notable example — knowingly making a false record can itself be a basis for enforcement, separate from the underlying issue. (Note: the FAA consolidated its falsification rules effective November 3, 2025 — former 14 CFR §43.12 is now reserved, and falsification is addressed under 14 CFR Part 3, Subpart D, §§3.403–3.405.) These are legal determinations; consult aviation counsel about how they apply to a specific situation.
What are the types of FAA legal enforcement actions under 14 CFR Part 13?
Part 13 sets out the FAA's enforcement procedures. Administrative action under §13.11 ('Administrative disposition of certain violations') uses a Warning Notice (which recites the facts and indicates a possible violation) or a Letter of Correction (which states the corrective action taken or agreed to) when a matter does not warrant legal enforcement. Civil penalties are handled under §13.16, which assesses monetary penalties against businesses and, for hazardous materials, against all persons, under the FAA's 49 U.S.C. authority. Certificate action under §13.19 ('Certificate actions appealable to the National Transportation Safety Board') is the suspension, amendment, or revocation of a certificate, with notice-and-response rights, the option of an informal conference, and an appeal to the NTSB; emergency orders take effect immediately.
How do my records decide which response I get?
Records are the evidence of the two things the FAA is weighing: whether the deviation was an unintentional, isolated mistake, and whether you are both willing and able to return to compliance. Complete, current, immutable, and instantly retrievable records support the compliance-action narrative — they show a sound process, a documented root-cause fix, completed training, and a corrected entry. Missing, contradictory, late-created, or altered records do the opposite: they can suggest a pattern, an inability to control the operation, or — at worst — falsification, all of which point toward enforcement. FileFlo keeps that record set audit-ready and documents corrective action, but it does not represent you to the FAA, give legal advice, or guarantee an outcome.
What is the Pilot’s Bill of Rights and how does it relate to FAA enforcement?
The Pilot's Bill of Rights is a federal statute (Public Law 112-153, signed August 3, 2012), not an FAA program or a CFR section. Among other things, it requires the FAA to provide timely written notice to an airman when it opens an investigation that could lead to enforcement action against an airman certificate, to identify the nature of the investigation, and to inform the airman of certain rights — including the ability to request relevant air traffic data. It is distinct from the Compliance Program: the Compliance Program is FAA policy about whether to use a compliance action or enforcement, while the Pilot's Bill of Rights is a statute about the process and notice the FAA must follow once an enforcement investigation is under way. Anyone who receives a written notice of investigation should consult aviation counsel promptly.
Be the operator the Compliance Program is built for — and be able to prove it.
FileFlo keeps your aviation records current, complete, immutable, and instantly retrievable, and documents the corrective action that shows you are willing and able to comply. It does not represent you to the FAA, give legal advice, or guarantee an outcome — it produces and proves your records. Starter plan $89/mo. Professional $299/mo. 5-day free trial — no credit card required.
5-day free trial · No credit card required · Cancel anytime
Also related: Aviation Compliance Hub · Part 135 Records List · VDRP Voluntary Disclosure · FAA Paperwork Fines
Written by Chad Griffith, Founder, FileFlo — compliance document intelligence. Reviewed June 15, 2026. This article is general compliance document information, not legal advice. The FAA Compliance Program (FAA Order 8000.373) is policy/guidance, not a regulation; 14 CFR Part 13 is the enforcement regulation; the Pilot’s Bill of Rights (Public Law 112-153) is a statute. Whether the FAA pursues a compliance action or enforcement is fact-specific — if you are the subject of an FAA inquiry, investigation, or enforcement action, consult a qualified aviation attorney, and verify every regulation and program reference against the current source.