Skip to content
FRSign inBook a walkthrough
Buyer’s guideFAA Part 5

SMS Software for Part 135 Operators: What You Need for the 2027 Declaration

The FAA SMS final rule brings every Part 135 certificate holder under 14 CFR Part 5, with a declaration of compliance due to the FAA no later than May 28, 2027. A two-aircraft charter needs the same four safety-management components as an airline, at a fraction of the depth. This is what to look for in SMS software, and what you can safely ignore.
Mounir OuafiFounder and CEO of eAvioraPublished Updated 12 min read

01The 2027 deadline and Part 5

The FAA SMS final rule was published on April 26, 2024 and took effect on May 28, 2024. It revised 14 CFR Part 5 and extended Safety Management System requirements beyond the Part 121 airlines to a much broader set of operators: all Part 135 certificate holders, commercial air tour operators flying under a 91.147 letter of authorization, and certain Part 21 certificate holders. If you hold a Part 135 certificate, you are in scope, and the revised Part 5 rule is now your baseline.

The timeline has two dates that matter for a charter operator. The rule took effect on May 28, 2024, with no implementation plan owed by Part 135 operators. The SMS must be fully implemented, with a declaration of compliance submitted to the FAA, no later than May 28, 2027. There is one line that changes how a small operator should read all of this: the requirement applies regardless of operator size, explicitly including single-aircraft and single-pilot certificate holders. There is no small-operator exemption. A two-plane charter faces the same deadline as a regional carrier.

What Part 5 asks for is structured into four components: Safety Policy, Safety Risk Management, Safety Assurance and Safety Promotion. The 2024 revisions also require a confidential employee reporting system and the declaration of compliance itself. Those four components are the same words an airline uses, and that similarity is exactly where small operators get into trouble: they assume the four components mean the same volume of paperwork. They do not. The components are mandatory; the depth scales to your operation.

02What the software must do

Strip the buzzwords away and a Part 135 SMS asks its software to do four connected jobs. Miss any one and the declaration gets shaky, because each maps to a Part 5 component you have to evidence.

  • Confidential reporting intake. Any pilot, dispatcher or mechanic must be able to report a hazard or occurrence without fear of it landing on them. That means a de-identified channel, not an email to the chief pilot. A proper confidential reporting system is a named requirement of the revised rule, not a nice-to-have.
  • Risk assessment. Every report needs a structured severity-and-likelihood assessment so you triage the two things that actually matter this week instead of treating a bird strike and a coffee spill the same. This is the Safety Risk Management component in practice.
  • Corrective-action tracking. A hazard is not closed when someone nods in a meeting. It is closed when the fix is assigned, done, and proven effective. The software has to carry each action to closure and refuse to let the record pretend otherwise.
  • Evidence trail. When an FAA reviewer or your principal inspector asks, you have to show the chain: report, risk assessment, action, closure, all linked, all timestamped, without a weekend of screenshotting. That trail is the difference between an accepted declaration and an open finding.

Sitting across all four is the flight risk assessment tool (FRAT). A FRAT is pre-flight numeric risk scoring, widely used across Part 135, business aviation and helicopter operations, and the FAA and industry associations publish reference models. The point of putting the FRAT inside the same system is that a crew's daily go/no-go score is not a throwaway form: a pattern of high FRAT scores on a particular route or a particular tail is a leading indicator that belongs in the same risk picture as your reported occurrences.

03What you can skip

Just as important as the must-haves is permission to ignore the rest. A small charter buying for the 2027 declaration does not need, and should actively avoid, several things that enterprise catalogs push:

  • A blank library you have to populate. Many legacy tools ship an empty hazard catalog and an empty risk register and expect your team to build the content from scratch. For an operator without a safety department, that is months of unpaid data entry before any safety value appears.
  • An airline-scale configuration project. If the tool needs a paid implementation consultant and a three-month rollout to switch on, it is the wrong size. A two-to-twenty-aircraft operation should be running real reports within days, not quarters.
  • Modules you will not touch for years. Fleet reliability engineering suites, cabin-safety analytics, and heavyweight audit-planning tooling are real, but they are not what gets you to a Part 5 declaration. Pay for the loop that closes, not the catalog that impresses.
  • Disconnected point tools. A reporting app here, a spreadsheet risk register there, and a separate action tracker is three places for the evidence chain to break. The value of an SMS is the links between records, not the records themselves.

The instinct to over-buy usually comes from a fear of failing the audit. The cure is not more features. It is a system that makes the four jobs above impossible to skip, and stays out of your way on everything else.

04Evaluation criteria

Here is a plain checklist to run any candidate tool against. You are a charter operator, not a procurement department, so score each on whether it helps you produce evidence by May 28, 2027 with the staff you actually have.

  • Time to first real report. Can a pilot file a confidential report on day one, or does the system need weeks of setup first?
  • Does the risk model come in the box? Are hazards, scenarios and barriers pre-loaded and aviation-specific, or is the register blank?
  • Can a record close over open risk? A good tool refuses to close a hazard while its corrective action is still open. Ask the vendor to try to break that rule in a demo.
  • Is the evidence trail exportable? Can you hand a reviewer a linked chain from report to closure without re-keying it into a separate report?
  • Is confidential reporting truly de-identified? Does the reporter get feedback without ever being exposed?
  • Is the FRAT part of the same system? Does pre-flight scoring feed your risk picture, or live in a separate app?
  • What does AI cost and who is in control? Is AI consumption predictable and capped, and does a human accept or reject every AI proposal?
  • Where does your data live? Is tenant isolation enforced by the database, and is your reporting data kept out of any model training?

If a tool clears that list, it will get you to the declaration without a safety department. Our buyer's guide expands each of these into procurement questions you can send verbatim.

Questions

Yes. The FAA SMS final rule revised 14 CFR Part 5 and extended Safety Management System requirements beyond Part 121 to every Part 135 certificate holder, and the obligation applies regardless of fleet size, including single-aircraft and single-pilot certificate holders. The rule took effect on May 28, 2024, and the SMS must be fully implemented with a declaration of compliance submitted no later than May 28, 2027. A two-aircraft charter carries the same four Part 5 components as a major carrier; what changes is the depth and volume, not whether the system exists.

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

Related reading

Run your first confidential report and FRAT on day one.

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