Skip to main content
CitadelAero

AI for airline safety and compliance teams

Chuck works through occurrences with your safety team and reads your operations manual against the regulation, citing its source every time.

Sample data. Wexmoor Air is a fictional operator. The app’s own workflow: “Work a single occurrence through triage”.

An occurrence, worked through.

A report arrives one case at a time. Describe it, and Chuck proposes the coding and whether it is reportable and to whom, with the provisions cited, for you to confirm.

An airline’s safety and compliance teams code and assess every occurrence, keep the manuals in line with the regulations and put together the monthly safety pack. Chuck helps with all three.

The occurrence and the manual.

Chuck reads your operations manual against the regulations your AOC sits under and proposes where it has drifted. If you hold more than one approval, it keeps the frameworks apart and compares them.

  • Reportability under EU 376/2014 proposed, and the report drafted for you to check and submit
  • EU 965/2012 Part-ORO and Part-CAT, FAA 14 CFR Parts 121 and 135, and the UK equivalents
  • Operations Manual sections and SOPs drafted, with the requirement cited beside each clause

What airlines can put in place.

  • An occurrence worked through with you, its coding and reportability proposed
  • A year of your occurrence reports read as a set, with themes, counts and direction
  • Your own manuals read beside the regulations
  • Your wording set against a requirement row by row, exported to Excel
  • Documents drafted to Word or PDF
  • Answers from the regulation text, cited to the provision and, where the source publishes one, the amendment
  • A shared project for each audit or investigation, holding its documents and chats

Common questions

Can Chuck code an occurrence report for us?

Yes, one case at a time. Describe the occurrence and it proposes the event type, flight phase, severity against your own risk matrix, hazard and contributory factors, showing where each came from. You confirm the record and enter it in your own system.

Will it tell us whether an occurrence is reportable?

It proposes whether it’s reportable, under which regime, to whom and by when, with the provision cited. If it is, it drafts the report in the authority’s format for you to check and submit. Your internal record and any notification to the investigation authority are kept separate.

Can it check our operations manual against the regulations?

Yes. It reads your OM-A and SOPs beside the regulation and proposes where the wording has drifted, in a spreadsheet your team can work through. It cites each rule’s amendment where the source publishes one, and redrafts a section when you ask.

Can it prepare the monthly safety pack?

Yes, when you ask. It drafts the pack and the meeting slides, with actions carried forward, performance against your own indicators and what changed since last time. It never marks an action closed, and it doesn’t schedule or send anything.

Which regulations does it answer from?

FAA, EASA and UK CAA. If you hold more than one approval, it names the governing framework on every line. If the regulations don’t cover your question, it says so.

Tell us how you operate.

Bring a manual section you think has drifted, or a year of reports nobody has read as a set, and we’ll run it through Chuck in front of you. We’ll tell you straight if we’re not the right people for it.