Yes — a single-pilot Part 135 operator needs an SMS under 14 CFR Part 5, with the same May 28, 2027 compliance date as every other Part 135 operator. There is no fleet-size threshold and no later deadline. What is different is the scope: §5.9(e) exempts an operator with a single pilot who performs all SMS functions from thirteen specific sections — the multi-person management, employee-reporting, and internal-communication pieces. You still must develop the §5.95 SMS documentation and keep the §5.97(a) risk management, §5.97(b) safety assurance, and §5.97(c) training records. The system is scalable, not optional.
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 how it scales to one pilot. For the records detail behind every operator size, see Part 135 SMS recordkeeping requirements.
Does a Single-Pilot Operator Need an SMS? (Yes — and the Date Is the Same)
This is the question one-pilot operators search most, and the internet is full of wrong answers. Here is the regulation, plainly. Under 14 CFR §5.9(a), any person authorized to conduct Part 135 operations — or holding a §91.147 air-tour Letter of Authorization — before May 28, 2024 must (1) develop and implement a Part 5 SMS no later than May 28, 2027, and (2) submit a declaration of compliance to the FAA by that same date. Nothing in that paragraph turns on how many pilots or aircraft you have.
There is no “single-pilot deadline” later than May 28, 2027
You will sometimes see a later date floated for small or single-pilot operators. It is wrong. The 2024 SMS final rule set one compliance date for all affected Part 135 and §91.147 operators, with no phased schedule by fleet size. §5.9(e) reduces what a single-pilot operator must do — it does not move when it must be done. Plan to your May 28, 2027 date.
So the honest framing is not “am I exempt?” — it is “which parts am I exempt from?” The FAA built in relief for one-person operations because, in the preamble to the final rule, it agreed that several Part 5 requirements are impractical or illogical when one human performs every function. That relief lives in §5.9(e), and we walk the exact list below. But the SMS itself — the four components and the records that prove they run — applies to you. If you want to see where SMS records sit in the wider Part 135 picture, our guide to the records a Part 135 operator must keep maps the whole stack, and the dedicated single-pilot Part 135 records guide covers everything beyond SMS.
Is the SMS Scalable for a Small Operator? Yes — by Design
The reassuring part: the Part 5 framework is explicitly scalable to the size, scope, and complexity of the operation. The FAA says this directly in its guidance — the AC 120-92D advisory circular and the preamble to the 2024 SMS final rule. Scalable means your processes do not need to be extensive or complex to be compliant. A one-pilot SMS can be lean — but it must still exist and produce records.
What “scalable” gives you
- One person can be accountable executive, safety manager, and pilot at once
- Hazard ID and risk assessment can be a short, structured worksheet — not a committee
- Safety assurance can be a periodic self-evaluation you run alone
- No multi-person management designations, no employee reporting program
What scalable does NOT mean
- It does not mean the SMS is optional for you
- It does not move your deadline past May 28, 2027
- It does not waive the §5.95 manual or the §5.97 records
- It does not let you skip the declaration of compliance
The catch for a single-pilot operator is not building the system — it is proving it. With no safety manager and no admin staff, the records a scaled SMS generates land on the one person already flying the airplane, doing the maintenance coordination, and running the business. That is the precise problem FileFlo was built to absorb: it is the lightweight evidence keeper that holds your scaled-down records and produces them on demand, so the proof burden does not eat your flight time.
The §5.9(e) Carve-Outs: Exactly What a Single Pilot Skips
§5.9(e) names thirteen provisions that do not apply to “organizations with a single pilot who is the sole individual performing all necessary functions in the conduct and execution related to, or in direct support of, the safe operation of the aircraft.” Every one of them assumes a workforce you do not have. Here is the full list, in plain English, with why it falls away.
| CFR | What it requires of larger operators | Why a single pilot is exempt |
|---|---|---|
| §5.21(a)(4) | Safety reporting policy — requirements for employees to report hazards | No employees to report |
| §5.21(a)(5) | Policy defining unacceptable behavior and disciplinary action | No workforce to discipline |
| §5.21(c) | Communicating the safety policy throughout the organization | Organization of one |
| §5.23(a)(2) | Accountability of all members of management for SMS processes | No separate management |
| §5.23(a)(3) | Accountability of employees for safety performance | No employees |
| §5.23(b) | Identifying the levels of management that may accept risk | One decision-maker |
| §5.25(b)(3) | Communicating the safety policy throughout the organization | Organization of one |
| §5.25(c) | Designating sufficient additional management personnel | Pilot wears every hat |
| §5.27(a) | Delegation of emergency authority throughout the organization | No one to delegate to |
| §5.27(b) | Assignment of employee responsibilities during an emergency | No employees |
| §5.71(a)(7) | Confidential employee reporting system | No employees to protect |
| §5.93 | Safety communication (Subpart E) | No one to communicate to |
| §5.97(d) | Records of safety communications | Nothing to record |
Read together, the carve-outs strip out three things: the multi-person management structure (§5.23(a)(2), §5.23(a)(3), §5.23(b), §5.25(b)(3), §5.25(c)), the employee-facing safety culture machinery (§5.21(a)(4), §5.21(a)(5), §5.71(a)(7)), and the internal communication and its records (§5.21(c), §5.27(a), §5.27(b), §5.93, §5.97(d)). What you are left with is a single accountable human running a lean risk-management and safety-assurance loop — and documenting it.
The exemption hinges on “sole individual performing all necessary functions”
§5.9(e) applies to an operator where one pilot truly performs every function — flying, and the direct support of safe operation. The moment you add a second pilot, a dispatcher, or a maintenance employee, the operation is no longer single-pilot for this purpose and the carved-out sections come back into force. If you are scaling up before 2027, see Part 135 required management personnel qualifications and the Part 135 Director of Safety & SMS requirement for what the management layer adds back.
What a Small Part 135 SMS Still Requires You to Keep
After the carve-outs, four record obligations remain for a single-pilot operator. None of them needs a workforce. All of them need to be retrievable when a Principal Operations Inspector asks. This is the working checklist for your scaled SMS.
SMS Documentation (§5.95)
14 CFR §5.95The single pilot must still develop and maintain SMS documentation: (a) the safety policy and (b) the SMS processes and procedures. This is your SMS manual — scaled to a one-person flight department, but a real, current, version-controlled document.
Maintained current; superseded versions retained and marked
Records in this category
- Safety policy signed by the accountable executive — who is you (§5.95(a))
- A scaled SMS manual describing your SRM and SA processes (§5.95(b))
- Revision history showing which version was in effect on any date
Safety Risk Management Outputs (§5.97(a))
14 CFR §5.97The hazard analyses and risk-control decisions your SMS produces when operations change or a hazard surfaces. For a single pilot this is a lean but genuine record — one person can identify hazards and assess risk, and the outputs must be retained.
As long as the risk control remains relevant to the operation
Records in this category
- Hazard identification worksheets for new operations or routes
- Risk assessments with likelihood and severity ratings
- Risk-control decisions and the basis for accepting residual risk
Safety Assurance Outputs (§5.97(b))
14 CFR §5.97The monitoring and self-evaluation layer. Even a one-person operation must periodically check that its SMS is working and that its risk controls are effective — and retain that evidence. This is the longest fixed retention clock you carry.
Minimum 5 years
Records in this category
- Internal SMS self-audit or evaluation findings
- Safety event tracking and any investigation outputs
- Corrective-action records with closure dates
SMS Training Record (§5.97(c) / §5.91)
14 CFR §5.91§5.91 requires the operator to ensure each individual identified in §5.23 attains and maintains the competencies to perform their SMS duties. In a single-pilot operation that individual is you — so a training record proving your own SMS competency must be kept.
As long as the individual (the pilot) is employed by the operator
Records in this category
- SMS training completion record for the pilot/accountable executive (§5.97(c))
- Evidence of recurrent SMS competency under §5.91
- Sits alongside your Part 135 pilot training records
No safety manager to track all this? See what you are missing in 3 minutes.
The free FAA readiness score surfaces the SMS and Part 135 records most likely to be missing or expired before a surveillance evaluation — built for one-person operations, no signup required.
One pilot, every hat — let the records prove themselves
FileFlo classifies each SMS record against the correct Part 5 section, tracks the §5.97 retention clocks, and produces an inspector-format evidence binder in seconds — so a single-pilot operation can answer a surveillance request without a safety department. 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: The Evidence Keeper for a One-Person Flight Department
FileFlo holds and proves the records — it does not build or run your SMS
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 risk assessments, run your safety assurance reviews, act as your accountable executive or safety manager, or provide a safety program or legal advice. For a single-pilot operator with no safety staff, it is the lightweight evidence keeper that makes the records side survivable.
The single-pilot operator is the exact-fit case for a records proof layer. You have no safety manager to maintain a document-control system, no admin to track four retention clocks, and no slack in your week to assemble a binder when the FSDO calls. The §5.9(e) carve-outs lighten the doing of the SMS — but they barely touch the proving of it. The §5.95 manual still needs version control; the §5.97(a), (b), and (c) records still need to be filed, retained, and retrievable. That proof burden is what lands on you, and it is what FileFlo absorbs.
Classification against 14 CFR Part 5
Upload a record and FileFlo files it against the specific Part 5 section it satisfies — a risk assessment to §5.97(a), a self-evaluation to §5.97(b), your own SMS training certificate to §5.97(c) and §5.91. No manual sorting, no records lost in a generic safety folder.
Retention clocks tracked automatically
FileFlo tracks the event-driven §5.97(a) risk-management clock, the 5-year §5.97(b) safety-assurance clock, and the employment-tied §5.97(c) training clock — and surfaces gaps and expirations 90, 60, and 30 days out, before they become findings. No spreadsheet to keep alive.
Version control on the SMS manual and policy
Your §5.95 documentation carries revision history so the version in effect on any date is recoverable, and superseded versions are retained and marked rather than overwritten — the document-control discipline a one-person shop rarely has time to enforce by hand.
One-click SMS evidence binder
When the FAA requests your SMS records during a surveillance evaluation, FileFlo generates a complete, Part 5-organized evidence binder in seconds rather than evenings. The same binder supports ACSF, IS-BAO, and ARGUS prep if you pursue an audit standard.
Your SMS records do not live in isolation — they sit on top of the rest of your single-pilot compliance stack. An SMS training record sits next to the pilot training records under Part 135 training-program recordkeeping; a risk assessment for a new aircraft type touches your aviation records retention schedule; your drug-and-alcohol program still applies, per the Part 135 drug & alcohol records checklist; and an inspector preparing for a Part 135 FAA surveillance audit expects to see SMS records produced as cleanly as everything else. FileFlo classifies the full Part 135 footprint, so your scaled SMS does not become a parallel filing universe.
Starter Plan
$89/mo
Up to 100 documents/month · 3 users
Built for the single-pilot owner-operator — enough room for a scaled SMS plus your core Part 135 records.
Professional Plan
$299/mo
Unlimited documents + users · audit trail · employee auto-detection
For when you add pilots or aircraft and the §5.9(e) carve-outs fall away.
Frequently Asked Questions
Does a single pilot operator need an SMS?
Yes. A single-pilot Part 135 operator needs an SMS under 14 CFR Part 5, and the compliance date is the same May 28, 2027 that applies to every other Part 135 certificate holder. There is no aircraft-count threshold and no later deadline for one-person operations. What changes for a single pilot is the scope, not the obligation: under 14 CFR §5.9(e), an operator with a single pilot who is the sole individual performing all necessary SMS functions is exempt from a specific list of sections that only make sense when you have a workforce to manage. The four-component framework — safety policy, safety risk management, safety assurance, and safety promotion — still applies, scaled to a one-person flight department.
Does a single pilot Part 135 need SMS, or is it exempt?
A single-pilot Part 135 operation is not exempt from SMS — it is exempt from certain sections of the SMS rule. §5.9(a) requires every Part 135 operator (and §91.147 air-tour LOA holder) authorized before May 28, 2024 to develop and implement a Part 5 SMS and submit a declaration of compliance no later than May 28, 2027. §5.9(e) then carves out specific sections for an operator with a single pilot who performs all SMS functions: §§5.21(a)(4), 5.21(a)(5), 5.21(c), 5.23(a)(2), 5.23(a)(3), 5.23(b), 5.25(b)(3), 5.25(c), 5.27(a), 5.27(b), 5.71(a)(7), 5.93, and 5.97(d). Those carve-outs remove the multi-person management, employee-reporting, and internal-communication pieces — but the core SMS, and the same deadline, remain in force.
Is the SMS scalable for a small operator?
Yes — the FAA designed the Part 5 framework to be scalable to the size, scope, and complexity of the operation, and it says so directly in its guidance (the AC 120-92D advisory circular and the preamble to the 2024 final rule). For a single-pilot operator, scalable means your SMS processes do not need to be extensive or complex to be compliant: one person can be the accountable executive, run the hazard identification and risk assessment, and conduct the safety assurance review. The FAA added §5.9(e) to the rule precisely because it agreed certain Part 5 requirements were, in its words, impractical or illogical for many single-pilot organizations. Scalability is a feature of the rule, not a loophole — you still need the records that prove the scaled-down system is running.
What does a small Part 135 SMS actually require a single pilot to keep?
Even after the §5.9(e) carve-outs, a single-pilot operator must still develop and maintain the §5.95 SMS documentation (the safety policy and the SMS processes and procedures — your SMS manual), and must still retain the §5.97 records the system generates: §5.97(a) safety risk management outputs (hazard analyses and risk decisions, kept as long as the control stays relevant), §5.97(b) safety assurance outputs (audits, monitoring, and self-evaluation data, minimum 5 years), and §5.97(c) the training record showing the pilot attained and maintains SMS competencies under §5.91. What §5.9(e) removes is the §5.97(d) safety-communication record and the §5.93 communication process — because there is no separate workforce to communicate to. The records burden is lighter, but it is not zero.
Can one person be the accountable executive and the safety manager in a single-pilot SMS?
Yes. In a single-pilot operation the same person is typically the accountable executive, the safety manager, and the pilot — that is the entire point of the §5.9(e) carve-outs. §5.9(e) exempts a single-pilot operator from §5.25(c), which requires the accountable executive to designate sufficient additional management personnel, and from §5.23(a)(2) and §5.23(b), which deal with accountability across members of management and identifying which levels of management may accept risk. With one person wearing every hat, those designations are unnecessary. The accountable-executive role itself is not waived — the single pilot is the accountable executive, responsible for the SMS and for the resources to operate it. FileFlo does not fill any of these roles; it holds the records that prove the one-person system ran.
What is a single pilot Part 135 SMS exempt from under §5.9(e)?
§5.9(e) lists thirteen provisions that do not apply to an operator with a single pilot who is the sole individual performing all necessary SMS functions: §5.21(a)(4) the safety-reporting policy, §5.21(a)(5) the disciplinary-action policy, §5.21(c) communicating the safety policy throughout the organization, §5.23(a)(2) management accountability, §5.23(a)(3) employee accountability, §5.23(b) identifying management levels that may accept risk, §5.25(b)(3) communicating the safety policy, §5.25(c) designating management personnel, §5.27(a) and §5.27(b) the emergency-response delegation and employee-assignment elements, §5.71(a)(7) the confidential employee reporting system, §5.93 safety communication, and §5.97(d) the safety-communication record. Every one of these assumes a workforce. None of them changes the May 28, 2027 deadline.
When is the single-pilot Part 135 SMS deadline?
May 28, 2027 — the same date as every other Part 135 operator. This is the single most misreported fact about single-pilot SMS. §5.9(a)(1) sets one compliance date for all Part 135 certificate holders and §91.147 air-tour operators authorized before May 28, 2024, with no phased schedule by fleet size and no later date for single-pilot operations. §5.9(e) only exempts single-pilot operators from specific sections; it does not push the date back. You will sometimes see a later date floated online — it is wrong. By May 28, 2027 a single-pilot operator must have implemented its scaled SMS and submitted a declaration of compliance to the FAA under §5.9(a)(2). See our Part 135 SMS 2027 deadline guide for the full timeline.
Does FileFlo build or run my single-pilot SMS?
No. FileFlo is a compliance document intelligence platform — the proof layer for your records, not the SMS itself. For a single-pilot operator with no safety manager, that is exactly the gap it fills: FileFlo stores, classifies, version-controls, and expiration-tracks your §5.95 SMS documentation and §5.97 records, files each against the correct Part 5 section, tracks the different retention clocks, surfaces what is missing before a surveillance evaluation, and generates an FAA-ready evidence binder on demand. It does not author your SMS manual, perform your hazard analyses or risk assessments, run your safety assurance reviews, act as your accountable executive or safety manager, or provide legal or safety-program advice. It is the filing cabinet that proves your one-person SMS is real and audit-ready. FileFlo also makes no SOC 2 claim.
Chad Griffith
Founder, FileFlo — compliance document intelligence
FileFlo helps Part 135 operators — down to single-pilot flight departments — keep their compliance documents classified, version-controlled, and audit-ready. This article reflects a compliance-document and recordkeeping perspective on 14 CFR Part 5; it is not legal advice and not safety-program or SMS-implementation advice. Confirm your specific obligations, §5.9(e) exemptions, and deadline with your assigned FSDO principal inspector and your aviation counsel.
Keep your single-pilot SMS records audit-ready before May 28, 2027
FileFlo classifies every §5.95 and §5.97 record against the correct Part 5 section, tracks the retention clocks, and generates a complete FAA-organized evidence binder on demand. It holds the proof your scaled SMS is running — it does not run your SMS. Starter at $89/mo · Professional at $299/mo · No credit card required.
5-day free trial · No credit card required · Cancel anytime