Skip to main content
CitadelAero

No more typing up
every report by hand.

Describe an occurrence and Chuck proposes the coding, the severity on your own matrix and whether it looks reportable, to whom and by when. The record stays marked proposed, for you to confirm and enter.

Request a demo

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

Coding and severity, proposed.

From your own description, on your own matrix, with the words each field came from beside it.

  • Coding from your description

    Event type, flight phase, hazard and contributory factors, each marked proposed.

  • Severity on your matrix

    Rated against the matrix your SMS Manual sets, and left open where the facts aren’t in yet.

  • Room to confirm

    A line for whoever confirms the record, and the date, before it goes into your system.

Reportable or not, to whom and by when.

Chuck proposes whether it’s reportable, under which regime, to whom and by when, with the provision attached. It covers FAA, EASA and the UK.

  • Three duties kept apart

    The report to the authority, your internal record and any notification to the investigation body.

  • The notification, drafted

    In the authority’s own format, for the reporter to check and submit.

  • Has this happened before?

    Ask, and it shows similar cases, how each was classified and what was decided.

How teams use it.

  • Monday’s reports

    Work the weekend’s reports through triage one at a time, each record ready for you to confirm.

  • A reportable occurrence

    See who must be told and by when, then check the drafted notification and submit it yourself.

  • Like cases alike

    Ask whether it has happened before, so similar events are handled the same way.

More of Chuck

Chuck overview

See it on your own reports.

We set Chuck up with the frameworks you operate under, and walk you through it on your own material.

Request a demo