The SMS declaration of compliance is the statement a Part 135 operator submits to the FAA under 14 CFR §5.9 affirming that it has developed and implemented a Safety Management System meeting Part 5 and that the supporting documentation is available for FAA review. It is the culmination of SMS implementation, not the start of it — you sign it after the system is built and running, not to begin the process. For existing Part 135 operators the deadline is May 28, 2027 (a single date, no aircraft-count threshold). The declaration is only as strong as the §5.95 documentation and §5.97 records standing behind it.
New to the 2027 mandate itself? Start with the FAA Part 135 SMS 2027 deadline explainer for the four-component overview, then come back here for the declaration and the records it rests on. For the full Part 135 records picture beyond SMS, see what records a Part 135 operator must keep.
Why the Declaration Is the Finish Line, Not the Start
The single most expensive misread of the 2024 SMS rule is treating the declaration of compliance as a task you start with — a form you file to “get into the program.” It is the opposite. The FAA's Part 5 industry guidance is explicit that the declaration is the culmination of SMS implementation, not its initiation. You do not declare in order to begin; you declare because you have already finished building and you are now operating the system.
The wrong mental model
“We'll file the declaration by May 28, 2027, then build out the SMS over the following months.” This treats the declaration as a starting gun and the records as a follow-up project.
Result: a signed attestation with no records behind it — the exact gap an FAA surveillance evaluation is built to find.
The correct mental model
“We develop and implement the SMS, run it long enough to generate real §5.97 records, then declare — on or before May 28, 2027 — that it is built and the records are available.”
Result: the declaration is the visible top of an iceberg of documentation that already exists on the day you sign.
The deadline is the declaration date — the work has to precede it
§5.9 requires existing Part 135 operators to both “develop and implement” the SMS and submit the declaration no later than May 28, 2027. Because the declaration affirms the SMS is already operating and the records are already available, the practical build deadline is earlier than May 28, 2027 — you need enough runway before that date to stand up the system and accumulate genuine safety risk management and safety assurance outputs. An SMS that goes live the week before you declare has almost no §5.97 record history to show.
This reframing changes what “readiness” means. Readiness for the declaration is not “did we file the paperwork” — it is “can we produce, on demand, the documentation the declaration says is available.” That is a records-control question, and it is where most operators are quietly behind. If you have not mapped the gap yet, our Part 135 SMS gap analysis and SMS implementation timeline to 2027 show how to work backward from the declaration date.
What the Declaration Actually Attests — and What It Does Not
§5.9 requires the declaration to be submitted “in a form and manner acceptable to the Administrator.” There is no single universal paper form you download — your assigned FSDO or certificate-holding district office confirms the current submission channel. But across formats, the substance of what you are attesting is consistent.
What it does say
- Identifies the operator and the certificate or authorization
- Attests that a Part 5-compliant SMS has been developed and implemented
- Affirms the supporting documentation and records are maintained and available for FAA review
- Is signed by the appropriate accountable person for the organization
What it does not mean
- It is not an FAA approval or acceptance of your SMS
- It is not a request to begin building an SMS
- It does not end FAA oversight — surveillance continues afterward
- It does not substitute for the underlying §5.95 and §5.97 records
“Available for FAA review” is the operative phrase
The declaration's power — and its risk — lives in the affirmation that your supporting documents are available for FAA review. That is a promise the FAA can test at any time after you submit. A principal inspector does not need to accept the declaration to act on it; they can simply ask to see the §5.95 SMS documentation and a specific §5.97 record. The day you sign, “available” has to be true in practice, not in principle.
Because the FAA sets both the wording and the channel, treat any third-party “declaration of compliance template” you find online as a draft to validate with your FSDO — not as the official form. What you should be perfecting is not the attestation language; it is the evidence the attestation points at. For where the named SMS roles fit (the accountable executive who owns the policy, the person who signs), see the Part 135 Director of Safety and the SMS requirement and Part 135 required management personnel qualifications.
The Records the Declaration Rests On: §5.95 + §5.97
When you sign the declaration, you are affirming that two bodies of evidence are maintained and available. The first is the §5.95 documentation that describes the system. The other three are the §5.97 outputs the system generates as it runs — each with its own retention clock. This is the working checklist behind the signature.
The §5.95 SMS documentation
14 CFR §5.95The descriptive layer the declaration assumes exists. §5.95 requires you to develop and maintain SMS documentation consisting of (a) the safety policy and (b) the SMS processes and procedures — your SMS manual describing how all four components operate.
Be current, version-controlled, reviewed by the accountable executive, and retrievable on request
Records in this category
- Safety policy statement signed by the accountable executive (§5.95(a))
- SMS manual describing processes and procedures for all four components (§5.95(b))
- Organizational structure and SMS responsibilities by role
- Revision history showing which version was in effect on any date
Safety risk management outputs
14 CFR §5.97(a)The outputs of the safety risk management processes in Subpart C — the hazard analyses and risk decisions the SMS produces whenever operations change or a hazard surfaces. The declaration affirms these are available; an inspector will ask for a specific one.
Be retained for as long as the risk control remains relevant to the operation
Records in this category
- Hazard identification worksheets for operational changes and reported hazards
- Risk assessment matrices with likelihood and severity ratings
- Risk-control decisions and the basis for accepting residual risk
- Change-management documentation for operations affecting safety
Safety assurance outputs
14 CFR §5.97(b)The outputs of the safety assurance processes in Subpart D — the monitoring, auditing, and performance layer that proves the SMS is working over time. This is the longest fixed-retention category and the one operators most often under-keep.
Be retained for a minimum of 5 years
Records in this category
- Internal safety audit and evaluation reports with findings
- Continuous monitoring and safety-event investigation outputs
- Safety performance indicator and target data (trend tracking)
- Corrective and preventive action records with closure dates
- Management review minutes and outcomes
Training & communication records
14 CFR §5.97(c)–(d)The safety-promotion records. §5.97(c) requires a per-individual training record retained for as long as the person is employed; §5.97(d) requires safety-communication records retained for at least 24 months. (Single-pilot operators are exempt from the §5.97(d) piece under §5.9(e).)
Training: as long as the individual is employed · Communications: minimum 24 consecutive calendar months
Records in this category
- SMS training completion record for each individual under §5.91 (§5.97(c))
- Competency assessment documentation per person
- Safety communication logs — bulletins, newsletters, meeting minutes (§5.97(d))
- Distribution / acknowledgment records for safety communications
For the full breakdown of each retention clock — the event-driven §5.97(a) clock, the 5-year §5.97(b) clock, the employment-tied §5.97(c) clock, and the 24-month §5.97(d) clock — see our dedicated Part 135 SMS recordkeeping requirements guide, and lay them next to the rest of your stack with the aviation records retention schedule. The SMS manual structure itself is covered in Part 135 SMS manual: required sections.
Could you produce these records today if an inspector asked?
That is the real test behind the declaration. The free FAA readiness score surfaces the SMS and Part 135 records most likely to be missing, scattered, or expired — in about 3 minutes, no signup.
The Deadline, the Timeline, and the Single-Pilot Question
There is exactly one declaration deadline for existing Part 135 operators, and it is not phased by fleet size. Here is the §5.9 timeline, stated plainly.
| Who | Obligation under §5.9 | Date |
|---|---|---|
| Existing Part 135 operators (authorized before May 28, 2024) | Develop and implement a Part 5 SMS and submit the declaration of compliance | No later than May 28, 2027 |
| Existing §91.147 air-tour LOA holders | Same: develop, implement, and declare | No later than May 28, 2027 |
| New Part 135 applicants (on or after May 28, 2024) | SMS developed and implemented as part of obtaining authorization | At certification |
| After declaring | Maintain the SMS for as long as you are authorized to operate | Ongoing |
There is no “November 2027” date
A persistent myth holds that smaller or single-pilot operators get a later deadline. They do not. §5.9 sets one compliance date — May 28, 2027 — for all affected existing Part 135 operators. §5.9(e) exempts an operator with a single pilot who is the sole individual performing all necessary functions from certain specific sections (such as §5.93 and the §5.97(d) communication-record requirement) — but it does not grant a later declaration date. Single-pilot operators still declare by May 28, 2027.
Single-pilot operators therefore carry a lighter — but not empty — version of the obligation behind the declaration: the §5.95 documentation, the §5.97(a) risk management outputs, and the §5.97(c) training record still apply, on the same date. Our single-pilot Part 135 records guide and the broader single-pilot Part 135 SMS overview walk through the scaled set. If you are budgeting the build, the Part 135 SMS cost breakdown and how to implement an SMS under Part 135 cover the work that has to finish before you can honestly sign.
Make “available for FAA review” true on the day you declare
FileFlo classifies each SMS record against the correct Part 5 section, tracks every §5.97 retention clock, and produces an inspector-format evidence binder in seconds — so the documents your declaration points at are actually there. Check your readiness free, or start a trial and load your first documents today.
5-day free trial · No credit card required · Cancel anytime
Where FileFlo Fits: We Make the Declaration True, We Do Not Sign It
FileFlo holds and proves the records — it does not run your SMS or file your declaration
FileFlo is a compliance document intelligence platform: a proof layer that stores, classifies, version-controls, and expiration-tracks your §5.95 documentation and §5.97 records, and generates inspector-format binders on demand. It does not author your SMS manual, perform your hazard analyses or audits, replace your safety manager, run your SMS, file your declaration of compliance, or provide a safety program or legal advice. It sits alongside your SMS and makes the “available for FAA review” affirmation true.
The declaration is a promise about your records. The problem is not usually that operators cannot build a manual or run an audit — it is that the records those activities generate end up scattered across shared drives, inboxes, and a safety manager's laptop, with no version control and no retention tracking. When a Principal Operations Inspector asks for a specific record after you have declared, that scatter becomes a live failure of the very thing you attested to. FileFlo closes that gap.
Classification against 14 CFR Part 5
Upload an SMS record and FileFlo classifies it against the specific Part 5 section it satisfies — a risk assessment to §5.97(a), an audit report to §5.97(b), a training certificate to §5.97(c) and the individual. The documentation your declaration points at is filed where an inspector expects it.
Every §5.97 retention clock, tracked automatically
FileFlo tracks the event-driven risk management clock, the 5-year safety-assurance clock, the employment-tied training clock, and the 24-month communication clock — and surfaces gaps and expirations 90, 60, and 30 days out, so the record set behind your declaration never quietly lapses.
A live readiness view before you sign
Because FileFlo knows what each Part 5 section requires, it shows you what is present, what is missing, and what is expiring before you declare — turning "are we ready to attest?" from a guess into a checklist.
One-click SMS evidence binder
When the FAA asks to review the documentation your declaration affirms is available, FileFlo generates a complete, Part 5-organized evidence binder — §5.95 documentation plus the §5.97 record categories, indexed by section — in seconds rather than days. The same binder supports ACSF, IS-BAO, and ARGUS audit prep.
The records behind the declaration also cross-reference the rest of your compliance stack. An SMS training record sits next to the pilot training records under Part 135 training-program recordkeeping; a safety-event investigation can intersect NTSB Part 830 accident/incident reporting and service difficulty reports; and an inspector arriving for a Part 135 FAA surveillance audit will expect the SMS records to be produced as cleanly as everything else. FileFlo classifies the full Part 135 footprint, so the records behind your declaration do not become a parallel filing universe.
Starter Plan
$89/mo
Up to 100 documents/month · 3 users
For solo owner-operators and small teams getting the records behind their declaration in order.
Professional Plan
$299/mo
Unlimited documents + users · audit trail · employee auto-detection
For Part 135 operators managing the full §5.97 record load behind a declaration across all four categories.
Frequently Asked Questions
What is a declaration of compliance (FAA SMS)?
Under 14 CFR §5.9, a declaration of compliance is the formal statement a Part 135 operator (or a §91.147 air-tour Letter of Authorization holder, or certain Part 21 certificate holders) submits to the FAA, in a form and manner acceptable to the Administrator, affirming that it has developed and implemented a Safety Management System meeting the requirements of Part 5. It is not an application to start an SMS and it is not a request for FAA approval — it is an attestation that the system already exists and is running, and that the supporting documentation is available for FAA review. The FAA's Part 5 industry guidance describes it as the culmination of the implementation effort, not its initiation. For existing Part 135 operators, the declaration is due no later than May 28, 2027.
What is the FAA SMS declaration of compliance deadline?
May 28, 2027. Under §5.9, any person authorized to conduct operations under Part 135 before May 28, 2024 must both develop and implement a compliant SMS and submit the declaration of compliance no later than May 28, 2027. This is a single, hard date for all affected Part 135 operators — there is no aircraft-count threshold and no phased, per-fleet-size schedule. New applicants for Part 135 authorization on or after May 28, 2024 must have the SMS developed and implemented as part of certification. Note the date applies to the declaration itself; the supporting records the declaration rests on must already exist on the day you sign it.
Is there a declaration of compliance form or example?
The FAA accepts the declaration in a form and manner acceptable to the Administrator under §5.9 — operators submit it through the FAA's designated channel rather than on a single universal paper form, and your assigned FSDO or certificate-holding district office confirms the current submission method. Whatever the format, the substance is consistent: it identifies the operator and certificate, attests that a Part 5-compliant SMS has been developed and implemented, and affirms that the supporting documentation — the §5.95 SMS documentation and the §5.97 records — is maintained and available for FAA review. We do not reproduce a sample attestation here because the wording and channel are set by the FAA and confirmed by your principal inspector; treat any third-party 'template' as a starting point to validate with your FSDO, not as the official form.
Does submitting the declaration of compliance mean the FAA approved my SMS?
No. The declaration is your attestation, not an FAA approval or acceptance of the SMS. Submitting it affirms that you have done the work — developed and implemented the system and that the supporting documents are available for review. The FAA then exercises oversight through surveillance: a principal inspector can ask, at any point after the declaration, to see the §5.95 documentation and the §5.97 records that prove the SMS is actually operating. So the declaration is better understood as the moment your records become discoverable on demand, not the moment your obligations end. This is exactly why the records behind the declaration matter more than the signature on it.
What documents does the FAA SMS declaration require you to have available?
The declaration affirms that your supporting SMS documentation and records are maintained and available for FAA review, so on the day you submit it you need two things complete. First, the §5.95 SMS documentation: the safety policy and the SMS processes and procedures — in practice, your SMS manual describing all four components (safety policy, safety risk management, safety assurance, safety promotion). Second, the §5.97 records the system generates: safety risk management outputs (retained as long as the control stays relevant), safety assurance outputs (minimum 5 years), a training record for each individual (as long as employed), and safety communication records (minimum 24 consecutive calendar months). A declaration backed by an empty record set is the gap an FAA surveillance evaluation is designed to find.
Does a single-pilot Part 135 operator have to submit a declaration of compliance?
Yes. Single-pilot Part 135 operators are subject to Part 5 and face the same May 28, 2027 declaration deadline — §5.9 does not give them a later date. What §5.9(e) does is exempt an operator with a single pilot who is the sole individual performing all necessary functions from certain specific sections (for example §5.93 on safety communication and the §5.97(d) communication-record requirement), because there is no separate workforce to communicate to. But the core obligations remain: develop and implement a scaled SMS, maintain the §5.95 documentation and applicable §5.97 records, and submit the declaration on time. Our single-pilot Part 135 records guide walks through the scaled set the declaration must rest on.
What happens if you miss the FAA SMS declaration deadline?
Operating under Part 135 after May 28, 2027 without a developed and implemented SMS — and without having submitted the declaration of compliance §5.9 requires — puts you in non-compliance with a regulation that applies to your certificate. The realistic exposure is FAA enforcement action and findings during surveillance, which can affect your operating authority; the FAA, not FileFlo, determines the specific consequence in any given case. Practically, the bigger risk is treating May 28, 2027 as a paperwork date and discovering during a later surveillance evaluation that the records behind the declaration were never built. Confirm your exact obligations and any deadline questions with your assigned FSDO principal inspector and your aviation counsel — do not rely on a blog post for an enforcement determination.
Does FileFlo file my declaration of compliance or run my SMS?
No. FileFlo does not file your declaration, author your SMS manual, perform your hazard analyses or audits, replace your safety manager, run your SMS, or provide a safety program or legal advice. FileFlo is a compliance document intelligence platform — a proof layer. It stores, classifies, version-controls, and expiration-tracks the §5.95 documentation and §5.97 records that your declaration affirms are available for FAA review, files each against the correct Part 5 section, tracks the different retention clocks, and generates an inspector-format evidence binder on demand. In short: you and your safety team build and run the SMS and submit the declaration; FileFlo makes the 'available for FAA review' part true on day one. FileFlo also does not claim any SOC 2 certification.
Be ready to back your declaration before May 28, 2027
The declaration of compliance is the finish line — and it is only as strong as the §5.95 documentation and §5.97 records behind it. FileFlo classifies every SMS record against the correct Part 5 section, tracks every retention clock, and generates a complete FAA-organized evidence binder on demand. It makes “available for FAA review” true — it does not run your SMS or file your declaration. Starter at $89/mo · Professional at $299/mo · No credit card required.
5-day free trial · No credit card required · Cancel anytime