By May 28, 2027, roughly 1,848 U.S. Part 135 operators and several hundred Part 91.147 commercial air tour operators must do something most of them have never done: design, implement, and declare compliance with a formal safety management system (SMS) under Title 14 of the Code of Federal Regulations (CFR) Part 5. For many, the date has already become a fixed point on the calendar, a milestone to be reached, documented, and reported to the U.S. Federal Aviation Administration (FAA).
But the date on the calendar is the wrong finish line.
The hard question is not whether an operator can produce the required documents by 2027 but whether the SMS will still be alive, used, and trusted in 2028, 2029, and the years after. An SMS is not a binder, a manual, or a software subscription, and it is not a project that ends when the deadline arrives. The FAA describes it as a formal, top-down, organization-wide approach to managing safety risk and assuring the effectiveness of risk controls. Two ideas sit inside that definition, managing risk and assuring controls, and both demand continuous attention. Seen that way, May 2027 is not the end of the work; it is the point at which the real work begins.
Beyond the Paper SMS
A documented SMS can look impressive. It may hold policy statements, reporting procedures, risk matrices, hazard forms, investigation templates, committee minutes, and corrective-action logs. Those elements are necessary. They are not sufficient. The real test comes after the document is approved and the auditor goes home.
What separates a living SMS from a paper one is not the quality of its templates but the behavior around them. In a living system, the accountable executive actually uses safety information to make decisions. Pilots and mechanics trust the reporting system enough to use it. Hazard reports are analyzed with discipline. Corrective actions are closed because they worked, not because a due date has passed. Trends are reviewed before they become incidents, and lessons return to the people who operate the aircraft. Strip those behaviors away, and the binder is just a binder.
This gap is widest at smaller operators, which the rule will now reach. Most Part 135 certificate holders operate just one or two aircraft. They rarely have a dedicated safety department, a data analyst, or a full-time internal auditor, and their people often perform several jobs at once. In that environment, the temptation is understandable: Build the documentation, meet the deadline, and move on. But safety does not improve because a form exists. It improves when information flows from the operation to management, from management to action, and from action back into the operation.
Assurance is Where SMS Becomes Real
The hardest part of an SMS is usually not safety policy, and not even hazard reporting. It is safety assurance, the component that asks an uncomfortable question: Are the controls we selected actually working?
Consider a common case. An operator identifies unstable approaches as a hazard and issues a reminder to crews. That may be a reasonable first step, but assurance requires more than a memo. Are stabilized-approach criteria clearly defined in the standard operating procedures (SOPs)? Are exceedances captured and reviewed? Do crews see that a go-around is supported by leadership rather than quietly held against them? Is training addressing the situations crews actually face on the line? When flight data, pilot reports, and line observations are laid side by side, do they tell the same story, or three different ones? Without that feedback loop, an organization can believe it has managed a risk when it has only documented it.
This is where quality-management thinking strengthens an SMS. Safety professionals speak of hazards, risk controls, and safety promotion; quality professionals speak of process control, root-cause analysis, corrective action, verification, and continuous improvement. These are not competing languages but the same discipline approached from two directions. A mature SMS borrows the auditor’s mindset, not the blame-and-checklist version, but the evidence-based version that keeps asking four plain questions: What did we say we would do? Are we doing it? Is it working? How do we know? Those questions move an SMS from intention toward performance.
Corrective Action Is Not Correction
One of the most common weaknesses in both safety and quality systems is the confusion between correction and corrective action. A correction fixes the immediate problem. A corrective action addresses the cause.
If a crew misses a checklist item, the correction might be a conversation, a reminder, or added supervision. The corrective action asks why it happened. Was the checklist design confusing? Was the crew interrupted? Was there time pressure, an unusual configuration, an SOP that reads well in the office but fights the crew during a rushed departure? Had something similar happened before? An organization that only corrects the visible error leaves the underlying condition in place, and the SMS becomes reactive even while its paperwork uses proactive language.
Disciplined cause analysis does not have to be elaborate, but it does have to be honest. The purpose is not to find someone to blame; it is to understand why the system allowed the hazard to surface and what can be changed to make recurrence less likely. This matters especially in business and on-demand aviation, where operations are dynamic and customer-driven: Short-notice trips, unfamiliar airports, international procedures, and small crews create subtle pressures. A useful SMS must be capable of detecting them.
Leadership Sets the Price of Safety
Because an SMS has a top-down structure, leadership cannot delegate safety culture to a manual. The accountable executive does not need to investigate every report personally, but leadership must demonstrate, repeatedly, that safety information changes what the organization does. When reports are ignored, people stop reporting. When corrective actions are superficial, people stop believing in them. And when production consistently wins over risk controls, the organization has taught its employees which priority is real, whatever the safety policy says.
The reverse is also true. When a pilot who reports a fatigue concern, a technician who flags a recurring defect, or a dispatcher who raises an operational risk sees the system listen and act, the SMS earns credibility. Not every report demands a major intervention, but every report deserves a process that is fair, structured, and visible. The same logic extends to safety promotion: Lessons learned should not stay trapped in committee minutes. They belong in briefings, training scenarios, SOP revisions, and the daily conversation of the operation. A closed-loop SMS communicates not only what went wrong, but also what the organization learned and what it changed.
A Question Worth Asking
A deadline is useful because it creates urgency, and for operators that have not yet built a Part 5 SMS, urgency is exactly what is needed. But deadline thinking carries a risk: it narrows the goal to passing a regulatory milestone, and in doing so it misses the larger opportunity.
The expansion of Part 5 to Part 135 and 91.147 operations is part of a broader movement, reflected in the U.S. National Transportation Safety Board’s longstanding placement of Part 135 safety on its Most Wanted List, to bring structured risk management into segments of aviation that were never previously required to maintain a formal SMS. The rule is not about producing a manual; it is about building organizational accountability into operations that have historically managed safety informally. Operators that treat the SMS as paperwork can achieve compliance and gain little resilience. Operators who treat it as a business process gain something more durable: clearer visibility of risk, more consistent decisions, stronger operational discipline, and earlier detection of weak signals.
Once the implementation surge passes, the useful question shifts from “Do we have an SMS?” to “How mature is ours?” A mature system can answer questions an immature one cannot. Which hazards are trending upward? Which corrective actions are overdue or ineffective? Which risks keep reappearing across reports, audits, and training events? Where are procedures drifting from actual practice? Which controls exist only on paper? And what decisions has management actually changed because of SMS data? Those are the questions that make an SMS worth the effort of building it.
The Measure of Success
The most effective operators will be the ones that fold the SMS into daily management instead of running it as a separate safety program. An SMS should connect with training, standardization, maintenance coordination, crew resource management, emergency-response planning, internal audit, and management review, because aviation operations change. Fleets, people, routes, customers, airports, technology, and regulatory expectations all move. A control that worked two years ago can quietly become insufficient; a procedure that looked clear in a conference room can fail during a weather diversion; a training topic that seemed minor can become important after several similar reports. The value of an SMS is that it gives an organization the structure to notice those shifts and respond before they produce consequences.
That structure does not need to be bureaucratic, and an overbuilt SMS may actually discourage its use. The best systems are practical, proportional, and operationally credible. They make reporting easy, analyze risk consistently, assign responsibility clearly, verify whether actions worked, and communicate what was learned.
By May 2027, many operators will be able to say they have implemented an SMS, and that statement will matter. But the better measure of success comes later, and it sounds less like a declaration than a set of honest questions. Did the SMS identify hazards that were previously invisible? Did it improve communication among pilots, maintenance, dispatch, and management? Did it produce corrective actions that changed behavior? Did it make audits more meaningful? Did it help leadership understand operational risk before an accident or incident forced the issue? Compliance has never been aviation’s highest ambition; safety performance is. The 2027 deadline is best understood as an invitation to build systems that outlast it, systems that are trusted, used, audited, improved, and embedded in how the organization actually operates. In that sense, May 28, 2027, is not the end of the SMS journey. It is the day the real work begins.
Image: © Rathke | iStockphoto
Raul Bonadia Rodrigues, MRAeS, is an FAA airline transport pilot, and an ASQ certified quality auditor. His work focuses on integrating quality- and safety-management systems in aviation, pairing active transport-category flight operations with formal quality-auditing expertise.
