SMS software for business aviation,
right-sized for a flight department.

See the highlighted block above the contents list. The rest of this article covers why a flight department adopts an SMS, how the IS-BAO staged model works, how to right-size the system without a safety office, what to look for in the software, and when the Part 5 mandate is also in scope.

Corporate and business aviation carries a specific risk profile. The flying is demand-driven, so trips appear at short notice into airports the crew may not know well. The principals set the schedule, which puts quiet pressure on go or no-go calls. The department is small, so one departure, one maintenance deferral or one fatigued crew is a large share of the week's exposure. A safety management system is how a department makes those pressures visible and manages them on purpose rather than by instinct.

Two forces bring most departments to a real SMS. The first is IS-BAO, the International Standard for Business Aircraft Operations, which many operators adopt as a mark of a well-run flight department and which insurers and charter customers increasingly look for. The second is a Part 135 connection: the moment any of the flying is operated under a charter certificate, the FAA Part 5 mandate applies to that operation. Either way, the department needs a system that is used, not a manual on a shelf.

IS-BAO, published by the International Business Aviation Council (IBAC), is built around a scalable SMS and is assessed in three progressive stages:

• Stage 1, the SMS is established, the structure, policy and processes exist.
• Stage 2, the SMS is functioning, safety management activities are integrated into daily operations and data is being acted on.
• Stage 3, the SMS is embedded, safety management is part of the department's culture and is sustained over time.

The standard is deliberately scalable, from a single aircraft on domestic trips to a fleet flying intercontinentally. What moves a department from one stage to the next is not more paperwork, it is evidence of use: reports arriving, risk assessments recorded against real trips, actions raised and closed, and a management review that happens on a cadence and leaves a record. Software that keeps that evidence in one place turns each assessment from a scramble into an export.

A 2 to 5 aircraft department rarely has a full-time safety manager. The role is usually carried by the director of aviation, the chief pilot or a line captain alongside another job. That reality should shape the SMS, not be hidden by it. The four components still have to exist, policy, safety risk management, safety assurance and safety promotion, but they run at a depth that matches a small operation.

The common trap is to copy an airline's SMS manual and inherit a system no small department can feed. A 200-page manual describing committees the department does not have is worse than a short one that describes what the department actually does. Right-sizing means the software carries the routine, routing a new report to the right person, reminding an action owner before a due date, and assembling the record for review, so the one person wearing the safety hat spends their time on judgment, not administration.

Judge a platform against the jobs a small department does every week, not a feature list:

• Reporting anyone will use. A pilot, scheduler or mechanic should file a hazard or occurrence from a phone in under a minute, with the option to stay confidential. Reporting volume is the leading sign of a healthy SMS; friction kills it.
• A flight risk assessment tool. A FRAT that scores a trip before it launches and escalates a high score to a second set of eyes is the daily habit that most changes behaviour. Its value multiplies when the scores land in the same system as occurrences and become trend data.
• Risk assessment that is recorded, not remembered. Hazards and their assessments live as records with an owner and a review date, defensible to an assessor.
• Action tracking with closure. Mitigations have an owner, a due date and evidence they worked, so nothing is quietly dropped.
• One connected operation. Reports, hazards, risk, actions and documents share one graph, so an occurrence updates the hazard it relates to rather than sitting in a silo.

This is where a connected aviation platform separates from a generic incident app. In eAviora an occurrence updates the related hazard, moves the affected bow-tie barrier, ticks the indicator that tracks the category, and shifts the computed risk picture, with AI agents assisting classification under human-in-the-loop approval and every change audit-logged. The department also starts from a pre-built aviation risk model, 101 bow-tie models, 804 named barriers, 210 scenarios and a 610-indicator SPI library, rather than an empty canvas it has no time to fill.

For the parts of the buyer question that are common to any operator, the buyer's guide and the Part 135 software criteria cover the same ground in more depth.

A department flying purely under Part 91 for its own company is not directly inside the 2024 FAA Part 5 mandate. But a large share of business aviation is flown under Part 135 by a management company, and every Part 135 certificate holder must have a fully implemented SMS and a filed declaration of compliance by 2027-05-28, regardless of fleet size, including single-aircraft operations. If your aircraft is ever operated on a charter certificate, the rule reaches that operation, and the management company will need the evidence to back its declaration.

The practical takeaway: a department chasing IS-BAO and a department preparing for Part 5 need the same working system. Adopting one SMS that produces real records serves both the voluntary standard and the binding mandate, without running two parallel efforts. For the mandate specifics, see the Part 5 final rule explained and right-sizing an SMS for small operators.