SMS Compliance Timeline

The FAA’s SMS final rule established a clear, non-negotiable timeline for Part 135 compliance. For operators who have not yet begun implementation, the window is narrowing. For those already underway, understanding the phases ahead helps ensure nothing is missed. This page lays out the key dates, explains the recommended implementation approach, and identifies the common pitfalls that delay operators.

​

Key Regulatory Dates

​

Why Start Now

Three years may seem like ample time, but SMS implementation involves organizational change, not just software deployment. Several aspects of SMS require time that cannot be compressed: Building trust in reporting takes months. Employees need to see that reports are handled fairly and result in action before they will report consistently. A just culture does not emerge from a policy document — it emerges from repeated positive experiences with the reporting system. Developing meaningful risk assessments requires understanding your specific operational environment. Risk criteria calibrated to your routes, aircraft, and personnel come from experience with the process, not from copying another operator’s matrix. Training personnel takes time to schedule around operational demands. SMS training is not a single session — it includes initial training for all personnel, role-specific training for investigators and safety managers, and recurrent training to reinforce concepts. Demonstrating a functioning SMS requires a track record. The Declaration of Compliance is a legal affirmation that your SMS is operational, not just documented. The FAA will validate through surveillance, and they will look for evidence of real activity — reports, risk assessments, corrective actions, committee meetings — over a sustained period. Operators who begin early accumulate safety data that demonstrates their SMS is operational. They identify and resolve implementation challenges while there is still time to course-correct. And they enter the Declaration of Compliance process with confidence rather than anxiety.

​

The Seven-Phase Implementation Approach

The FAA does not prescribe a specific implementation methodology, but industry experience and AC 120-92D guidance suggest a phased approach. The following timeline assumes a 30-36 month implementation for a typical Part 135 operation. Smaller operators may compress some phases; larger or more complex operations may need additional time. For detailed task guidance on each phase, see Track Part 5 Compliance.

​

Phase 1: Gap Analysis (Months 1-2)

The implementation journey begins with understanding where you already stand. Most operators discover they do more than they think — existing safety meetings, maintenance tracking, training programs, and operational procedures often align with SMS concepts even if they are not formally labeled as such. The reason a gap analysis matters is that it separates what needs to be formalized from what needs to be built from scratch, preventing the common mistake of over-engineering an SMS that ignores existing strengths. The gap analysis maps current practices against Part 5 Subparts B through F, producing a clear picture of organizational readiness. PlaneConnection’s Compliance module supports this by letting you map your current state against every regulatory element at a granular level.

​

Phase 2: Planning (Months 3-4)

With gaps identified, the planning phase establishes the organizational infrastructure for SMS implementation. This is when the accountable executive is designated, safety personnel are identified, budgets are set, and a project timeline with milestones is created. The reason this phase is distinct from the gap analysis is that planning requires commitment decisions — who will lead the effort, how much will it cost, and what technology platform will support the SMS — that should be informed by the gap analysis findings rather than predetermined.

​

Phase 3: Documentation (Months 5-8)

Documentation produces the written foundation required by Part 5 Subpart F: the safety policy statement, SMS manual, non-punitive reporting policy, risk assessment criteria, investigation procedures, training curriculum, record retention policy, and emergency response plan. The critical insight for this phase is that documents must describe processes you will actually use, not aspirational processes that sound good on paper. PlaneConnection’s Documents module provides version-controlled storage for all SMS documentation, and the policy settings capture your safety policy statement and organizational commitments. The DOC generator can produce a draft Declaration of Compliance when you reach Phase 7.

​

Phase 4: Training (Months 9-12)

Training translates documentation into organizational capability. The reason this phase takes several months is that different roles need different training depth — the accountable executive needs to understand oversight responsibilities, safety managers need competence in risk assessment and investigation techniques, line personnel need to recognize hazards and submit reports, and investigators need root cause analysis skills. Training often reveals gaps in documentation when people ask questions your procedures do not answer. That feedback is valuable — it refines your documentation before you move to live implementation.

​

Phase 5: Implementation (Months 13-20)

Implementation is where the SMS transitions from documentation to operation — processes begin accepting safety reports, conducting risk assessments, holding safety committee meetings, tracking corrective actions, and monitoring safety performance indicators. An adjustment period is normal and expected. Reporting rates will be low initially as people build trust in the system. Risk assessments will be inconsistent until assessors calibrate their judgments. Safety committee meetings may feel stilted until participants find their rhythm. The important thing is that processes are running and producing real data that builds the operational record needed for the Declaration of Compliance.

​

Phase 6: Testing and Refinement (Months 21-28)

Internal auditing demonstrates Safety Assurance (Pillar 3) in action. This phase verifies that SMS processes are working as intended and produces evidence that the SMS is not just running but producing results. The reason testing takes several months is that meaningful trends require time to emerge — SPI data needs enough history to show patterns, and corrective actions need enough time to demonstrate whether they are effective. Audit findings feed directly into process refinement, closing the loop between monitoring and improvement that Part 5 Section 5.75 requires.

​

Phase 7: Validation and Declaration (Months 29-36)

The final phase confirms all Part 5 requirements are met through a comprehensive internal review covering Subparts B through F. The accountable executive reviews and signs the Declaration of Compliance, and it is submitted to your FAA Certificate Management Office. PlaneConnection’s Part 5 compliance report generates a comprehensive summary mapped to every regulatory requirement, and the evidence export feature packages supporting documentation for audit or inspection.

​

Essential Documents

By the time you submit your Declaration of Compliance, you need a complete set of SMS documentation. The reason these specific documents are required relates directly to Part 5’s structure — each one provides the evidence base for a specific regulatory requirement:

​

Common Implementation Pitfalls

​

After the Declaration

Submitting the Declaration of Compliance is not the finish line — it is the starting point of ongoing SMS maintenance. Part 5 requires continuous improvement, meaning your SMS must evolve as your operation changes, new hazards emerge, and lessons are learned. The FAA will validate your SMS through routine surveillance. They will look for evidence that your processes are functioning, not just documented. A healthy SMS shows a steady flow of reports, active risk management, timely corrective actions, regular safety committee engagement, and performance indicators trending in the right direction — exactly the kind of ongoing activity that PlaneConnection is designed to capture and demonstrate.

​

Related