Aviation SMS software for OTAR operators
If you operate in the UK Overseas Territories, your framework is OTAR, not EASA and not the FARs. FlightAtom AURORA Ai links safety records to the clause numbers your inspector uses, with your OTAR clause library loaded during implementation.
Why OTAR operators end up fighting their safety software
Aviation SMS products commonly organize their clause libraries, audit templates, and reporting categories around EASA or FAA structures, because that is where most operators are. An OTAR operator that adopts one then has to map its own requirements onto that numbering.
Your clauses, not theirs
Records link to the OTAR and ICAO Annex 19 clauses loaded for your operation, so an audit finding attaches to the requirement it actually relates to.
Built for a small safety office
A small safety team often shares reporting, risk, audit, and follow-up between a few people. AURORA Ai's assurance inbox puts each person's assigned work and emerging concerns in one place.
One linked record for the audit
Reports, hazards, risk decisions, audits, findings, corrective actions and closure evidence sit in one linked record an inspector can walk end to end.
From AOC application to steady-state assurance
An applicant is building a safety management system and proving it works at the same time. An established operator is trying to keep one current with a small team. Both problems are about evidence.
- Safety policy and objectives Keep the safety policy and its supporting procedures as controlled documents, with revisions, distribution, and read acknowledgements.
- Safety risk management Run occurrence reporting, hazard identification, and 5×5 risk assessment with initial and residual scores, barriers, owners and review dates.
- Safety assurance Plan and run recurring internal audits, raise clause-linked findings with drafted corrective action plans, and close safety cases only after independently verified action and an effectiveness check.
- Safety promotion Track training requirements and read acknowledgements, and publish closure feedback to the people who reported.
- Change management Trace a regulatory or operational change to the records it affects and the approvals that cleared it.
OTAR SMS software FAQs
What is OTAR?
The Overseas Territories Aviation Requirements (OTARs) are the aviation requirements for the UK Overseas Territories, published by Air Safety Support International (ASSI), a wholly owned subsidiary of the UK Civil Aviation Authority. OTAR Part 119 covers air operator certification, Parts 121 and 135 cover commercial air transport operations, Part 125 covers complex general aviation including corporate operations, and Part 145 covers the approval of aircraft maintenance organizations. They apply in Territories such as Anguilla, Bermuda, the British Virgin Islands, the Cayman Islands, the Falkland Islands, Montserrat, St Helena, and the Turks and Caicos Islands. Oversight is carried out by each Territory's regulator, or by ASSI where it has been designated.
Why does OTAR matter when choosing SMS software?
SMS software often organizes its clause library and audit templates around EASA or FAA structures. An OTAR operator then has to map its own requirements onto that numbering, and the gap shows at audit when an inspector asks about a requirement the system does not list.
What OTAR content does AURORA Ai include?
AURORA Ai links records to regulation clauses and their supporting evidence. Its demonstration uses illustrative OTAR Part 125 and ICAO Annex 19 clause entries with paraphrased text, not a compliance library. The operator's clause library, at the edition and amendment it confirms from ASSI publications, is loaded as data during implementation, including Parts 119, 121, 135 or 145 where needed.
Does this certify OTAR compliance?
No. AURORA Ai runs your safety and quality workflows and holds the record, evidence and clause mapping. It does not certify compliance or determine which requirements apply to your operation. The operator remains responsible for its approved procedures, data completeness, accountable decisions, and demonstrating compliance to ASSI or the relevant authority.
Is this suitable for an AOC applicant rather than an established operator?
Yes. An applicant builds the reporting process, the risk register, the audit programme, and the evidence trail at the same time as everything else. AURORA Ai provides those workflows from the start, and clause references for the Parts that apply to the application, such as 119, 121, or 135, are scoped during implementation.
How does this relate to ICAO Annex 19?
Annex 19 sets the SMS framework that OTAR implements: safety policy and objectives, safety risk management, safety assurance, and safety promotion. AURORA Ai's document, risk, audit, and training records map onto those four components, and the OTAR clause references sit alongside the selected Annex 19 clauses.
What about maintenance under OTAR Part 145?
The quality management side of AURORA Ai (audits, clause-linked findings and corrective action plans) can be applied to maintenance organization workflows as well as flight operations. Part 145 clause references are loaded during implementation if you need them.
Official OTAR context
Use current authoritative material and your approved system when defining scope and acceptance tests. Start with Air Safety Support International, which publishes the OTARs, and ICAO Safety Management for the underlying Annex 19 framework. References provide context; they do not imply certification or complete coverage, and the applicable edition and amendment state are the operator’s to confirm.
Bring a clause you have to demonstrate
We will show you the record linked to it, and the evidence trail behind it.
Request a demo