Skip to content
FRSign inBook a walkthrough
Regulation guideFAA Part 5

Part 5 SMS: What FAA Inspectors Check Before 2027

The FAA does not approve your SMS when it receives your declaration of compliance. Its own inspector guidance says validation happens afterwards, during routine surveillance. This guide goes through 14 CFR Part 5 subpart by subpart: the requirement, what it lets an inspector ask to see, and the artefact that answers it, with a month-by-month countdown to 2027-05-28.
Mounir OuafiFounder and CEO of eAvioraPublished 10 min read

01What the FAA does with your declaration

Start with what is written down, because there is a lot of hearsay about Part 5 inspections. The rule is 14 CFR Part 5. Section 5.9 gives every Part 135 operator, and every commercial air tour operator holding a Letter of Authorization under 91.147, until 2027-05-28 to develop and implement an SMS that meets the part and to submit a declaration of compliance. The final rule explainer covers who is in scope. This article is about what happens next.

The FAA's instructions to its own inspectors were first issued as interim notices (N 8900.700 in 2024, reissued as N 8900.737 in 2025). Both are now cancelled, and the guidance sits in FAA Order 8900.1, Volume 17, Chapter 2. It says four things an operator should know before signing.

  • The declaration is short. It contains the organization's name and certificate number, its physical address, a statement that it has developed and implemented an SMS that meets Part 5, and the signature of the accountable executive or another senior member of management. The order calls it a legal document. The declaration checklist covers the evidence behind that signature.
  • An acknowledgment is not an approval. The inspector records the declaration and the accountable executive's name in the Safety Assurance System, the tool the FAA uses to plan and record oversight. The order states that this does not constitute FAA approval or acceptance of the SMS.
  • No manual is required with it. If you send one, the inspector is not required to evaluate the design at that point.
  • The checking comes afterwards. In the order's words, validation of SMS performance will occur as part of routine surveillance activities.

So the declaration is a signed statement the FAA can test at any later visit, and 5.9(d) obliges you to make available, upon request, all necessary information and data that demonstrates you have an SMS that meets the part. What an individual inspector chooses to sample is not published, so the rest of this article works from what the rule requires you to be able to show.

02The evidence, subpart by subpart

Part 5 has six subparts: General (A), Safety Policy (B), Safety Risk Management (C), Safety Assurance (D), Safety Promotion (E), and SMS Documentation and Recordkeeping (F). The FAA's own oversight tools follow the same split: the order lists the safety management questions for a new Part 135 applicant under four elements, Safety Policy, Safety Risk Management, Safety Assurance and Safety Promotion. The table takes each requirement, states what it allows an inspector to ask to see, and names an artefact that answers it. The artefacts are examples, not FAA forms.

14 CFR Part 5 by subpart: the requirement, what an inspector can ask to see, and the artefact that answers it
SubpartRequirementWhat an inspector can ask to seeThe artefact that answers it
A5.5 and 5.9(d): an SMS fitted to your size, with the data that demonstrates it available on requestHow the four components work in your operation, and where the records liveOne index that names, for each section of Part 5, the process and the record that answers it
B5.21: a safety policy signed by the accountable executiveThe policy itself: objectives, reporting policy, unacceptable behaviour, code of ethicsThe signed, dated policy, its last review by the accountable executive, and proof it reached employees
B5.23 and 5.25: accountabilities, the accountable executive, who may accept riskWho the accountable executive is, and which level of management accepts which riskA named accountable executive, written accountabilities, and a risk acceptance table by management level
B5.27: an emergency response plan where one is necessaryWho holds emergency authority, who does what, how the plan lines up with other organizationsThe plan approved by the accountable executive, with its contact list and the date it was last exercised or reviewed
C5.51 and 5.53: system analysis and hazard identificationA new system, a revised system or a new procedure, and the hazards identified from itA hazard register whose entries point to the change or the report they came from
C5.55: risk analysis, assessment and controlHow you decide a risk is acceptable, and whether the control was evaluated before it went inA risk assessment per hazard: risk before the control, risk with the control, who accepted it and when
C5.57: notice of a hazard to an interfacing personA hazard you found in the operating environment and who you toldThe notice sent (to an airport, a fuel provider, a maintenance provider) with its date
D5.71(a): monitoring, audits, evaluations, investigations, confidential employee reportingEach data source in use: audits done, events investigated, reports receivedAudit reports with findings, investigation files, and the report log with what happened to each report
D5.71(b) and 5.73: analysis and safety performance assessmentAn assessment against your safety objectives, including a review by the accountable executiveIndicators with their history, and the dated record of each review with its decisions
D5.75: continuous improvementA deficiency found in an assessment and how it was correctedA corrective action with an owner, a due date, a closure date and a check that it worked
E5.91: competencies and trainingTraining for each person given a safety accountability under 5.23A training record per individual, with dates and content
E5.93: safety communicationHow employees learn of hazards and of why actions and procedures changedBulletins and briefings with the date sent and who received them
F5.95 and 5.97: documentation and recordsThe documented policy and processes, and records inside their retention periodsA controlled document set with revision history, and records that can be pulled by date

Two rows deserve a second look. The confidential employee reporting system sits in Safety Assurance, at 5.71(a)(7), and the rule describes it as a system in which employees can report hazards, issues, concerns, occurrences and incidents, and propose solutions, without concern of reprisal. A form nobody has used is hard to present as a system; the confidential reporting guide covers how to build one people trust. And 5.57 is the row most often missing: when you identify a hazard in the operating environment, you must notify any interfacing person who could address it, and 5.97(d) makes you keep that notice.

03One trace beats thirteen folders

The table reads as thirteen separate rows, but Part 5 is written as a loop, and the loop is what a records review exposes. Section 5.51(d) says safety risk management must be applied when safety assurance identifies a hazard or an ineffective risk control. Section 5.73(b) says the same from the other side: when an assessment finds an ineffective control or a new hazard, you must use the safety risk management process. Section 5.75 then requires a process to correct the deficiency.

So the most useful rehearsal is a single trace. Take one report from the last six months and follow it: the report, the hazard it was filed against, the risk assessment, the control, the person who accepted the remaining risk, the corrective action, and the check that the action worked. If any step lives in someone's memory or in an inbox, that is the gap. The same method is described for third-party audits in what SMS auditors ask for, and a Part 5 gap analysis finds the broken links across the whole system rather than in one record.

Run the trace three times before you sign: once from an employee report, once from an internal audit finding, and once from a change (a new aircraft type, a new base, a revised procedure). Those are three of the entry points the rule names in 5.51 and 5.71.

04The records clock in 5.97

Subpart F is two short sections, and it is where a declaration is easiest to test, because it sets how long each kind of record must exist.

  • Safety risk management outputs: kept for as long as the control remains relevant to the operation.
  • Safety assurance outputs: kept for a minimum of 5 years.
  • Training records: one per individual, kept for as long as the individual is employed.
  • Safety communications and hazard notices to interfacing persons: kept for a minimum of 24 consecutive calendar months.

Two practical consequences follow. A risk assessment for a control that is still in use cannot be archived out of reach, however old it is. And a record has to be retrievable by date and by subject, which is a different thing from existing somewhere on a shared drive. If your audit reports, your training sign-offs and your bulletins live in three tools with three naming habits, test now how long it takes to produce one of each from a given month.

05Countdown: December 2026 to May 2027

This is a sample plan for an operator that already has its processes written and needs to prove they run. The only date fixed by the rule is 2027-05-28; the monthly split is a suggestion to adapt.

  • December 2026: index. Build the one-page index from the table above: each section of Part 5, the process that meets it, where its records are. Mark every row with no record yet.
  • January 2027: policy and people. Have the accountable executive review and sign the safety policy (5.21). Confirm the written accountabilities and who may accept which risk (5.23). Start or refresh training for everyone named there (5.91).
  • February 2027: risk. Bring the hazard register up to date. Every open hazard gets a risk assessment, a control and a named acceptance (5.55). Send any hazard notice you owe to an interfacing person (5.57).
  • March 2027: assurance. Complete one internal audit and one evaluation of the SMS itself (5.71(a)(3) and (4)). Hold a safety performance assessment with the accountable executive and keep the dated record (5.73).
  • April 2027: close and rehearse. Close the corrective actions from March, or record why they remain open (5.75). Run the three traces. Test the retrieval of one record of each type in 5.97.
  • May 2027: declare. The accountable executive reviews the index one last time. Ask your responsible Flight Standards office how it wants the declaration delivered, then submit it with the four required items, before 2027-05-28, and keep the acknowledgment.

If December's index shows whole subparts with no records, the plan above is too optimistic for you, and the honest move is to start the slowest evidence first: reporting and assurance, which only exist once time has passed.

06Single-pilot operators and SMSVP letters

Two groups read the table differently. The first is the organization with a single pilot who is the sole individual performing every function related to the safe operation of the aircraft. Section 5.9(e) removes a specific list of requirements for that case, including the employee reporting policy, the designation of management personnel, the confidential employee reporting system (5.71(a)(7)), safety communication (5.93) and its records (5.97(d)). Everything else stays, and the FAA guidance has the inspector flag the operator as a sole individual when recording the declaration. The guide for small and single-pilot operators goes through what a proportionate system looks like.

The second group holds an acknowledgment letter from the Safety Management System Voluntary Program (SMSVP). The order states that an existing SMSVP acknowledgment remains valid until 2027-05-28, or until the organization revises its SMS and submits a declaration of compliance, whichever comes first. The letter does not replace the declaration. The SMSVP to Part 5 transition maps the differences.

One limit to state plainly: software does not file the declaration and does not stand in for the conversation with your Flight Standards office. eAviora holds the records and the links between them; the statement to the FAA is the accountable executive's.

Questions

No. FAA Order 8900.1, Volume 17, Chapter 2 says the FAA acknowledges that a declaration was submitted by updating the operator's record in its Safety Assurance System, and that this acknowledgment does not constitute FAA approval or acceptance of the organization's SMS. The same guidance says validation of SMS performance will occur as part of routine surveillance activities. So the declaration is the start of the looking, not the end of it.

Mounir OuafiFounder and CEO of eAviora, the aviation safety intelligence platform.

Related reading

Walk through your Part 5 evidence on your own records.

Book a walkthrough on your own operation, or keep reading in all the insights.