Safety & compliance: occurrences, findings and the audit plan.
Safety, compliance and training
From the FlyPack CAMO manual
Safety & compliance
Three things on one screen: occurrences, findings, and the audit plan.
Occurrences
Report occurrence records what happened, when it happened, and when it was detected. It refuses "An occurrence cannot be detected before it happened."
Mark reported records that it has gone to the authority. Reporting is an obligation with a clock on it, and the state is kept so the question "was this one reported" has an answer other than somebody's memory.
Close closes it.
Findings
Raise finding records something an audit — yours or the authority's — found. A finding carries what was found, against what, and what is being done about it.
Audit plan
The schedule of internal audits. Compliance monitoring is a continuing obligation, not an event, and this is where it is planned rather than remembered.
What an occurrence asks for
| Field | Notes |
|---|---|
| Aircraft | Which one it happened to |
| Classification | Accident · Serious incident · Incident · Observation · Other occurrence |
| Title | What happened, in one line — "Engine rough running on climb-out" |
| What happened | The account. This is the record; the title is the index |
| Occurred and Became aware | Two dates, because they are two facts. Reporting clocks run from the second |
| Authority reference | AACR/2026/0142, once the authority has given one |
What a finding asks for
| Field | Notes |
|---|---|
| Level | Level 1 — significant, immediate action · Level 2 — corrective action required · Observation |
| Finding | What was found |
| Regulatory reference | ML.A.302(c) — against what |
| Owner | Who is answerable for closing it |
| Corrective action due | The date it has to be closed by |
| Follow-up action taken | Filled in as it is worked |
A Level 1 is the level that grounds an approval if it is not answered. The distinction is the authority's, not this application's, which is why the level is chosen rather than derived.
Training & authorisations
Record training against a person: the requirement it satisfies, the course title, the provider, when it was completed, who assessed it, and any notes.
The requirements it knows about are the ones the regulation names: initial and continuation training, human factors, SMS, fuel tank safety, EWIS, type training, competence assessment and review training for airworthiness review staff.
Each record carries its own expiry, and the screen states each one as OK, due soon or expired. It refuses training recorded as completed in the future: "Training cannot be recorded as completed in the future."
Authorisations are the other half, and they are load-bearing elsewhere: a certificate of release to service is refused unless the signatory holds the matching authorisation, current and unsuspended.
"Stanislav Salat does not hold a current CRS_ML801 authorisation and cannot sign this release."
When that refusal appears on a release, the fix is here — check whether the right person's authorisation has lapsed. It is never to pick somebody else from the list because they happen to be available.
Authorisations are recorded on the person, in Organisation info, and the ones that matter for release are CRS_145, CRS_ML801 and PILOT_OWNER. Which one a given release needs depends on the aircraft's regime — see Release to service (CRS).