Safety Management Software for UK Airlines and the CAA
01The UK regulatory frame
When the United Kingdom left the European Union it kept the aviation safety rules it already applied, as UK law. That is why a UK operator still reads regulation numbers that look European. The texts are published on legislation.gov.uk, and they name the Civil Aviation Authority (CAA) where the European originals name a member state or its competent authority.
Two of those texts decide what your safety software has to do. The first is the management system rule for air operators, ORO.GEN.200, in the UK version of Regulation (EU) No 965/2012 (Part-ORO). It asks an operator for:
- Clearly defined lines of responsibility and accountability, including the direct safety accountability of the accountable manager.
- A safety policy.
- The identification of aviation safety hazards, their evaluation, and the management of the associated risks, including checking that mitigating actions work.
- Personnel who are trained and competent for their tasks.
- Documentation of the key management system processes.
- A function that monitors compliance and feeds findings back to the accountable manager.
The same rule says the management system must correspond to the size of the operator and the nature and complexity of its activities. A six-aircraft charter operator and a long-haul airline are held to the same list, not to the same volume of paper.
The second text is UK Regulation (EU) No 376/2014 on occurrence reporting, covered in the next section. Around both sits the CAA's own guidance. Its safety management systems page lists CAP 795, the safety management systems guidance material, and CAP 1059, the guidance for small, non-complex organisations. It also offers the CAA SMS evaluation tool, which the CAA describes as designed to be used as a gap analysis tool for organisations.
02What reporting to the CAA involves
The UK text of Regulation 376/2014 keeps the structure of the European one, which our guide to occurrence reporting under 376/2014 walks through. For a software decision, six points matter.
- Two clocks of 72 hours. An individual reports within 72 hours of becoming aware of the occurrence, unless exceptional circumstances prevent it (Article 4(7)). An organisation established in the United Kingdom then reports to the CAA as soon as possible, and in any event no later than 72 hours after becoming aware of the occurrence (Article 4(8)).
- A voluntary stream. Organisations set up a voluntary system for occurrences the mandatory list may miss and for other safety information a reporter sees as a hazard (Article 5). The CAA says voluntary occurrence reports are made in the same format as a mandatory occurrence report.
- A compatible database. The databases use formats that are standardised and compatible with the ECCAIRS software and the ADREP taxonomy, the coded vocabulary ICAO publishes for describing occurrences (Article 7(4)).
- The portal, or a file. The CAA directs reporters to the ECCAIRS 2 reporting portal. An organisation with a high volume may use an ECCAIRS-compatible E5X file or a reporting software solution, and the CAA states that its approval must be granted before an E5X file can be submitted. The mechanics of the file are in our note on ECCAIRS 2, ADREP and E5X.
- Analysis, with dates. Where the analysis identifies an actual or potential safety risk, the organisation sends the CAA its preliminary results within 30 days of the reporter's notification, and the final results no later than three months from that date (Article 13(4)).
- Written just culture rules. Each organisation, after consulting its staff representatives, adopts internal rules describing how just culture principles are applied, and the CAA may ask to review them (Article 16(11)). The protection of the reporter does not cover wilful misconduct or a manifest, severe and serious disregard of an obvious risk (Article 16(10)). Our note on just culture in five questions helps draw that line in practice.
Read those six points as a specification. A product that only collects reports covers the first two and leaves the rest to a spreadsheet.
03Where UK practice differs from EASA
Most safety software sold in Europe was built around the EASA system, and most of it works for a UK operator, because the two sets of rules share an origin and, for the articles cited here, the same numbering. The differences are in who you answer to and whose text you read.
| Topic | UK operator | Operator in an EASA member state |
|---|---|---|
| Occurrence reporting law | UK Regulation (EU) No 376/2014, the UK text on legislation.gov.uk | Regulation (EU) No 376/2014 |
| Who receives the report | The Civil Aviation Authority | The national competent authority of the member state |
| Management system rule for air operators | ORO.GEN.200 in the UK version of Regulation (EU) No 965/2012 | ORO.GEN.200 in the EU version of the same regulation |
| Acceptable means of compliance and guidance material | Published by the CAA | Published by EASA |
| Safety management guidance | CAP 795, CAP 1059 and the CAA SMS evaluation tool | EASA and national authority guidance |
| Sending an E5X file | CAA approval is needed before an organisation submits one | Ask the authority you report to |
Two practical consequences follow. First, the two texts are now amended separately, so a compliance register built on the European wording is not a UK register: check each requirement against the UK version before you rely on it. Second, a vendor saying “we are ECCAIRS compatible” has answered only half of the UK question. The other half is whether your organisation is approved by the CAA to submit the file, and what the product does for you on the days you use the portal form instead.
If you operate under both systems, for example with a second certificate in a member state, you need the two rule sets side by side, each with its own status, not one merged list.
04Requirements, and what to ask a vendor
Turn the two regulations into a table and take it to every demonstration. The left column is what you need. The right column is a question that cannot be answered with a slide.
| Need | What to ask a vendor |
|---|---|
| Mandatory and voluntary reports in one place | Show me both kinds of report arriving. Are they the same record, with the same follow-up? |
| A confidential channel | File a confidential report in front of me. Who can see the name of the reporter, and on which screens? |
| The 72-hour clock | Where does the record show when the report to the CAA is due, and who is told before it lapses? |
| Coding compatible with ECCAIRS and the ADREP taxonomy | When is the occurrence coded, by whom, and what happens when a mandatory attribute is missing? |
| The return to the CAA | Do you produce an E5X file? Until the CAA approves us to submit one, how does the record help us complete the portal form? |
| Analysis results at 30 days and three months | Where do the preliminary and final results of the analysis live, and are they dated on the occurrence? |
| Hazard identification and risk management | Which risk matrix do you use, can we use our own, and is a written rationale required for each score? |
| Actions that are verified | Can an action close before someone has checked that it worked? Show me one that was refused. |
| Compliance monitoring against UK Part-ORO | Does the UK rule set ship with the product, or do we load and maintain it ourselves? |
| Just culture rules | Where do our internal just culture rules live, and can a reporter read them from the reporting form? |
| Data location and assurance | Where is our data stored and processed, and which certifications do you hold today, not next year? |
Score each row as shown, promised or absent. A row that is promised is absent until you see it. For a wider method of comparing products, the guide to aviation safety management software sets out the questions that apply in any jurisdiction.
05Run one occurrence from report to return
The fastest way to test a product against the table is to walk one occurrence through it, using an event your own operation would recognise. A sample to use, and it is only a sample: a ground handler reports, confidentially, that a baggage loader touched the fuselage of an aircraft on stand during a night turnaround.
Ask the vendor to do the following while you watch:
- File the report from a phone, as the handler would, and show what the safety office sees of the reporter.
- Classify the occurrence and show the codes that will travel to ECCAIRS.
- Show the date and time by which the report to the CAA is due.
- Score the risk, and show the reason written for that score.
- Raise an action, verify it, then try to close it before anyone has checked that it worked.
- Produce the return: the E5X file, or the summary you would copy into the portal.
- Open the record a month later and show what has been sent to the CAA since, and when.
You are watching for seams. Each time the presenter leaves the record to open another tool, a document or a mailbox, write it down: that is where your 72 hours, or your three months, will be lost on a busy week.
06Where eAviora fits, and where it does not
eAviora covers the trace above on one record. In the Occurrences module a report arrives from the web, the eAviora app or a public reporting page, as identified, confidential or anonymous, and moves through eleven stages from triage to closure. It exports as an E5X file coded from its classification, and the export says when a mandatory attribute is still missing. Actions stay linked to the occurrence and, by default, a verified action closes only after its effectiveness review.
The Compliance module ships the UK CAA Air Operations rules in the regulator's own text, beside the IOSA Standards Manual and the EASA catalogues. A rule that is not in the library is registered as a standard of your own.
The limits, stated plainly for a UK buyer:
- No UK data residency. Data is stored in Canada, in the Montréal region, and the application runs in the United States. SOC 2 Type I is in preparation and no certification is claimed today. The detail is on the trust page.
- No CAA approval, and none claimed. eAviora produces the E5X file. The approval to submit one is between your organisation and the CAA, and until you hold it you report through the portal.
- One risk matrix. Risk is scored on the ICAO 5 by 5 matrix, the same for every operator. If your manual defines a different matrix, raise it before you commit.
- No jurisdiction named for the United Kingdom. Reporting deadlines are set by jurisdiction, and a UK operator uses the European one, whose 72-hour clock follows the same article as the UK text. Ask us to show it on your own event.
Questions
Two sets of rules do most of the work. The first is the management system requirement for air operators, ORO.GEN.200 in the UK version of Regulation (EU) No 965/2012, which asks for defined accountability, a safety policy, hazard identification and risk management, trained people, documented processes and a compliance monitoring function. The second is UK Regulation (EU) No 376/2014 on occurrence reporting, which sets the reporting streams, the 72-hour clocks, the database format and the protection of the reporter. Software does not make an operator compliant, but it should make each of those duties a record you can show.
The Civil Aviation Authority (CAA) directs reporters to the ECCAIRS 2 reporting portal for a mandatory occurrence report, and voluntary occurrence reports are made in the same format. An organisation that submits a high volume may use an ECCAIRS-compatible E5X file or a reporting software solution, but the CAA states that its approval must be granted before an E5X file can be submitted. So ask a vendor two things: whether the product produces the file, and how it helps you while that approval is not yet in place.
Yes, in the UK text as published on legislation.gov.uk. Article 4(7) asks an individual to report within 72 hours of becoming aware of the occurrence, unless exceptional circumstances prevent it. Article 4(8) asks an organisation established in the United Kingdom to report to the CAA as soon as possible, and in any event no later than 72 hours after becoming aware of the occurrence. The article numbers match the European regulation; the body that receives the report is the CAA.
The CAA lists two guidance documents on its safety management systems page: CAP 795, its safety management systems guidance material, and CAP 1059, the guidance for small, non-complex organisations. The same page offers the CAA SMS evaluation tool, which the CAA describes as designed to be used as a gap analysis tool for organisations. Run the gap analysis first, then score vendors against the gaps you actually have.
No. eAviora stores customer data in Canada, in the Montréal region, with backups in the same region, and the application runs in the United States. SOC 2 Type I is in preparation and no certification is claimed today. eAviora holds no approval from the CAA, and a safety management product does not need one to be used by an operator. If your policy requires data to stay in the United Kingdom, eAviora is not a fit today.