Safety management systems (SMS) in crewed commercial aviation are a mature discipline. The structure is well documented, the regulatory expectations are clear, the assessment frameworks are settled, and the operator community has decades of accumulated experience with what good looks like. Almost every uncrewed operator with an aviation background brings some version of that playbook into their UAS operation and tries to apply it.
The result is usually a system that is recognisable as an SMS, satisfies many of the documentary requirements of one, and yet does not perform in the way the operator expected. The reason is not that the operator has implemented the crewed playbook badly. The reason is that the playbook itself only takes the operator part of the way, because the operating environment it was developed for is not the operating environment uncrewed aviation actually presents.
Four structural differences that define the gap
Four structural differences explain most of the gap. The first is scale and pace of change. A crewed commercial operator typically runs a stable fleet of well-characterised aircraft on well-defined routes with well-understood failure modes. The SMS sits inside that stability and is updated incrementally as new variants, new routes or new equipment come online. An uncrewed operator, by contrast, is often running a platform that has been in service for less than two years, against a regulatory framework that is being rewritten in real time, in airspace where the rules of engagement with other users are still being negotiated. The SMS in that environment has to be designed for continuous change rather than for incremental update. The risk register that was current six months ago is unlikely to be current today, and the management system has to know how to absorb that without falling out of date.
The second is the crew composition. The SMS in crewed aviation has a clear answer to the question of who the operator is, who the maintainer is and who the dispatcher is. In a BVLOS uncrewed operation, the operator is often a multi-role crew distributed across a Safety Pilot, a System Operator, an Observer, a Team Lead, a Datalink Specialist and a Payload Specialist. The competence management, the duty management, the fatigue management and the human performance dimensions of the SMS all have to be built around that crew composition rather than around the single-pilot or two-pilot model.
The third is the data picture. A crewed SMS can draw on a relatively well-understood data infrastructure, including flight data monitoring, line operations safety audits, mandatory occurrence reporting and a long history of comparable operations. An uncrewed SMS often has to work with much thinner data, drawn from systems that were not designed for safety reporting and from operations that are too novel to have meaningful comparators. The risk methodology has to be appropriate to that data picture, and the methods that work well in crewed contexts can produce misleading outputs when applied to uncrewed operations.
The fourth is the regulatory interface. A crewed operator is interfacing with a regulator that has decades of experience with the operation in question and a settled view of what good looks like. An uncrewed operator is interfacing with a regulator that is still developing its view, still publishing new guidance and still working through how the existing framework applies to novel operations. The SMS has to be designed to communicate with that regulator in a way that builds confidence rather than triggers concern, and the communication burden falls more heavily on the operator than it does in mature crewed contexts.
Designing an SMS for the uncrewed environment
The Baines Simmons approach to uncrewed SMS design is built around a methodology we call SMARRT MAP. The framework was developed across our crewed aviation consulting work and has been adapted specifically for the uncrewed context. The principle behind it is proportionate. A small uncrewed operator does not need the SMS infrastructure of a flag-carrier airline, and trying to force one on them produces compliance theatre rather than safety performance. A large defence-grade operator needs significantly more than the lightweight structures that work for a small commercial operator. SMARRT MAP scales to the size, complexity and risk profile of the actual operation, and addresses Safety Risk, Enterprise Risk and Fatigue Risk inside a single coherent framework.
For uncrewed operators specifically, the SMARRT MAP application is informed by five years of work alongside the regulatory drafting community, the defence aviation authorities and a growing book of commercial operators moving into BVLOS work. The framework aligns with UK CAA, EASA, FAA and military airworthiness requirements, which matters increasingly as operators take their operations across borders or move between civil and defence contracts.
The deeper point is that an SMS in the uncrewed context does not work as a standalone artefact. It works when it is integrated with the training that builds the competence, the safety culture that sustains the behaviour, and the software that holds the evidence base. The SMS is the connective tissue. The training, the culture and the software are the organs. The operator who tries to perfect the SMS in isolation from the rest of the structure is optimising the wrong thing, and the operator who tries to run the rest of the structure without the SMS in place is building a house without foundations.
This is why we treat uncrewed SMS work as the entry point to the broader Baines Simmons offer rather than as a standalone product. The consultancy work designs the SMS, the safety culture and the regulatory strategy. The training work builds the competence the SMS depends on. The Centrik 5 platform from TrustFlight sustains the evidence, the reporting and the continuous improvement loops that the SMS requires to function over time. The integration is what makes the operation perform.
Where operators should begin
For operators considering where to start, our recommendation is consistent. Begin with a structured assessment of where the SMS currently sits against the operational reality and the regulatory direction. Identify the gaps that matter most to the operation and the gaps that matter most to the regulator. Build the road map that addresses the gaps in the right order, and integrate the training, culture and software work into the road map from the start. The operators who follow this approach arrive at regulatory inspections, contract bids and operational scale-ups significantly better positioned than those who do not.
The crewed playbook is a starting point, not an answer. The work of adapting it to the uncrewed operating environment is what separates operators who are merely compliant from operators who are genuinely safe and demonstrably so.
Baines Simmons designs and assesses safety management systems for uncrewed operators across civil and defence sectors. Read more about the SMARRT MAP methodology and the wider UAS safety and compliance here.