FAA SMS Mandate for Part 135: Your Implementation Timeline and Compliance Roadmap

The FAA finalized rules requiring all Part 135 certificate holders to implement a Safety Management System (SMS) under 14 CFR Part 5. The compliance deadline is May 28, 2027, but the preparation timeline starts now.

SMS is not a new concept — Part 121 carriers have operated under SMS since 2015. What is new is extending the requirement to Part 135 on-demand operators, many of whom have never implemented a formal safety management framework beyond basic regulatory compliance.

Pillar 1 — Safety Policy and Objectives: Your accountable executive must commit to SMS in writing, define safety objectives, and establish a non-punitive reporting culture. This pillar sets the tone.

Pillar 2 — Safety Risk Management (SRM): Systematically identify hazards, assess risk probability and severity, and implement mitigations before incidents occur. Document every risk assessment.

Pillar 3 — Safety Assurance (SA): Monitor your operation for compliance with risk controls, audit your own processes, and track corrective actions to completion. This is where data analysis matters.

Pillar 4 — Safety Promotion: Train your team on SMS concepts, communicate safety lessons, and build a culture where reporting hazards is expected, not feared.

Phase 1 (Now through Q3 2026): Draft your SMS manual, appoint a safety manager (can be part-time for small operations), and start voluntary hazard reporting. Review the ACSF consortium ASAP program for turnkey reporting.

Phase 2 (Q4 2026 through Q1 2027): Submit your SMS implementation plan to your FSDO, conduct initial safety risk assessments for your top operational hazards, and begin safety assurance auditing.

Phase 3 (Q2 2027): Final validation, staff training completion, and compliance documentation. Your SMS should be operational — not just documented — before the deadline.

You do not need a dedicated safety department. For operations with fewer than 10 aircraft, the safety manager role can be combined with another position. The key is documented authority and time allocation.

Leverage existing processes: your compliance task tracking, crew training records, and maintenance reporting already contain safety data. SMS formalizes the analysis, not the collection.

Use Navlyt Compliance to map SMS requirements to your existing compliance tasks and build the audit trail regulators expect.

Buying an off-the-shelf manual without customizing it to your operation. Inspectors will test whether your team understands the procedures — not whether the document looks professional.

Treating SMS as a compliance checkbox rather than an operational tool. If your safety reporting system generates data that nobody reviews, it provides zero safety value and will be flagged during surveillance.

Waiting until 2027 to start. The implementation plan submission itself requires months of groundwork. Operators who start in 2027 will not make the deadline.

Navlyt maps SMS requirements to compliance tasks, tracks corrective actions from safety reports, and provides the audit trail your FSDO expects. You can start building your SMS framework inside the same platform that manages your day-to-day compliance.

Start with a 14-day free trial and use the compliance task generator to create your SMS implementation checklist.