Skip to content
STRIKE SMS

The Part 135 SMS deadline

May 28, 2027.

Part 135 operators authorized before May 28, 2024 must implement a Safety Management System meeting 14 CFR Part 5 and submit a declaration of compliance to the FAA by May 28, 2027. Read the FAA requirements (opens in a new tab)

Safety management for Part 135 operators

One connected
safety program.
Clear next steps.

Give your team a clear path from reporting a concern to investigating it, assigning action, and checking the result. Keep your operation moving forward.

A guided walkthrough, built around your operation.

The work of safety, connected

Your safety program.
A clearer way forward.

Start with reporting, investigation, and accountable follow-through. Explore the capabilities available in the current trial and what’s coming next.

In the current trialComing soonNot available in the current trial
01

Report & investigate

Give concerns a clear route from the person who sees them to the people who can act.

  • Confidential employee reporting
  • Assigned investigations and contributing factors
  • Independent investigation review
  • File attachmentsComing soon
02

Assess & control risk

Build a connected view of hazards, decisions, and the controls that matter.

  • Hazard register and change reviews
  • Initial and residual risk assessments
  • Risk acceptance authority
03

Verify & improve

Keep responsibility visible and check the outcome after an action is completed.

  • Corrective actions with owners and due dates
  • Independent effectiveness checks
  • Audits and findingsComing soon
04

Manage documents & training

Bring important guidance and learning into the same safety program.

  • Versioned manuals and policiesComing soon
  • Required-read acknowledgementsComing soon
  • Training assignments and renewalsComing soon
05

Lead & review

Give each role a useful view of the work and a record of decisions.

  • Employee, safety manager, and executive roles
  • Role-based dashboards
  • Readable review exports (HTML and JSON)
  • Safety meetings and executive reviewsComing soon
06

Prepare & respond

Keep emergency responsibilities, checklists, and communication together.

  • Emergency plans and response checklistsComing soon
  • Incident coordination and acknowledgementsComing soon
  • Emergency text alertsComing soon

From concern to follow-through

A report should lead to action.

See how one concern moves through the people, decisions, and checks that follow.

Step 01

Make it easier to speak up.

An employee reports ground equipment parked close to a taxi route. The concern reaches the safety team, with reporter identity protected by role-based access.

The handoffEmployee → Safety managerGround equipment near a taxi route

Follow-through you can explain

“Done” is a task status.
Effective is an outcome.

Completing an action does not automatically mean the concern is resolved. Keep the check, the result, and the next decision connected.

  1. Name the owner.

    Make responsibility and the expected result clear.

  2. Check independently.

    Separate completion from the review of whether the change worked.

  3. Keep the record.

    Follow the concern through its investigation, action, and effectiveness result.

Built around your people

A clear next step.
For every role.

Part 135 operators

Practical safety management.
Shared accountability.

Keep the work moving between the people who report concerns, investigate them, and oversee the safety program.

Employees
Report concerns and follow assigned work.
Safety managers
Coordinate investigations, actions, and checks.
Executives
See the work that needs leadership attention.
Talk through your operation
Part 141 flight schools

Make safety part of
the learning environment.

Bring student, instructor, and staff concerns into a shared process with clear responsibility and follow-through.

  • Encourage concerns to be raised.
  • Connect findings to practical actions.
  • Keep leadership involved in the result.

Explore how the current trial fits your school’s people and procedures.

Talk through your school’s workflow

Before we talk

Know what to expect.

Explore the interactive demo (opens in a new tab)
What will we cover in a demo?

We’ll walk through reporting, investigations, corrective actions, effectiveness checks, and role-based dashboards, then discuss how they fit your operation.

Can I explore before booking a call?

Yes. The public interactive demo lets you explore example workflows. It uses fictional data and may show capabilities beyond the current trial. The feature list above identifies what is available in the trial.

Are all listed capabilities available now?

No. Each capability marked “Coming soon” is outside the current trial. The trial includes confidential reporting, investigations with independent review, hazard register and change reviews, initial and residual risk assessments, risk acceptance by an independent authorized position holder, corrective actions and effectiveness checks, employee/safety manager/executive roles, dashboards, and readable HTML/JSON review exports.

Does software make an operator compliant?

No. Your organization is responsible for implementing and maintaining its SMS under the applicable requirements. Strike SMS supports the work and records within that program; it does not guarantee FAA compliance or approval.

Does Strike SMS replace dispatch or flight planning?

No. Strike SMS focuses on safety management. Dedicated flight risk assessment tools, flight following, offline mobile access, and external integrations are not included in the current trial.

Make the next step clear

See your safety program
working together.

Bring your current process. We’ll walk through the work, the people, and the follow-through.