A practical audit toolkit for regional charter fleets

A regional charter operator can pass an audit on paper and still struggle to show how its safety controls work across several aircraft, crews or bases. The problem is often not a lack of documents. It is that the documents do not join up: audit questions sit apart from evidence, risk records, findings and the operation’s actual differences.

Here is a worked example, not a report of a North Sky client engagement. Imagine a Norwegian charter operator adding aircraft and operating from more than one base. Its flight safety officer needs a repeatable flight department safety audit that can be used across the fleet without pretending every aircraft or station is identical.

Start with scope, not a stock checklist

First define which operation, certificates, locations and activities the audit covers. Map the audit criteria to the requirements that actually apply to that operator, including relevant EASA rules and Norwegian aviation law. The details depend on the operation and its approvals; a generic checklist cannot establish applicability on its own.

North Sky Aviation Consultancy offers risk management and compliance consulting and assists organizations with EASA regulations and Norwegian aviation law compliance. An operator may involve an adviser such as North Sky to help examine the regulatory scope and operational context. The operator still needs to own its manuals, records, decisions and corrective actions.

Set up a master audit register with one row per requirement or control. Record the source, the responsible owner, the evidence expected, the audit result, any finding reference and the next review date. This gives the safety officer one index instead of a stack of disconnected checklists.

Build the working files around evidence

A lean aviation audit toolkit can use existing document-control and safety-management arrangements. It does not require buying a new platform. The essential pieces are a controlled audit plan, a checklist tied to applicable criteria, an evidence index, a findings and corrective-action log, and a risk register. Use the operator’s established recordkeeping tools where they can preserve version history, access and traceability.

• Audit plan: state the scope, criteria, locations, sampling approach, assigned auditors and schedule. Note what is outside scope.
• Checklist: ask for evidence and test whether a control works in practice. A tick against a manual reference is not proof that crews follow the procedure.
• Evidence index: identify each record by title, date, version and location, with a link or reference in the operator’s controlled repository. Avoid copying sensitive records into unmanaged files.
• Findings log: capture the requirement, observed condition, supporting evidence, risk or consequence, accountable owner, due date, action and effectiveness check.
• Risk register: connect relevant hazards and controls to the audit finding or operational change, while retaining the operator’s defined assessment method.

The register should make it possible to trace a finding backwards to evidence and a criterion, and forwards to an owner and verified action. That trace is more useful than a high completion percentage. For a related discussion of when a spreadsheet remains workable, see the test for keeping a manual risk log current as activity grows.

Make fleet variation visible

A regional charter safety audit should test common controls once where appropriate, then sample their application across aircraft and bases. Create a simple variation matrix: rows for aircraft, bases or operating contexts; columns for differences that affect the audit, such as approved equipment, local procedures, contracted services or record ownership. Populate it from controlled operational documents, not memory.

This matrix prevents two opposite errors. The first is assuming a fleet-wide procedure applies identically everywhere. The second is repeating every audit question for every aircraft when a central control is genuinely shared. The auditor should record the sampling rationale and investigate exceptions rather than treating a sample as proof of universal compliance.

In the worked example, a finding about a recurring briefing record could affect several aircraft. The log should identify which crews and records were sampled, whether the issue is isolated or common, and how the operator will check the correction across the fleet. If the finding exposes a hazard, the risk register should show whether existing controls remain adequate while the action is open.

Close the loop, then standardize

At the closing meeting, separate a missing document from a control that exists but is not followed. Agree the factual basis, accountable owner and due date. Corrective action should address the cause, not just replace a missing record. Before closing a finding, the safety officer should record what evidence shows the action worked and whether the same weakness appears elsewhere.

Keep the process proportionate. A spreadsheet and controlled folders may be sufficient for a small, stable fleet, but manual tracking becomes fragile when owners, aircraft and open actions multiply. A dedicated system may improve reminders and traceability, but it cannot decide which requirements apply or make weak evidence persuasive. The operator must also manage access and sensitive operational records in either setup.

The practical result is a repeatable audit cycle: define scope, map criteria, sample operations, link evidence, track findings and verify actions. North Sky’s advisory work spans air traffic control, risk and compliance, drone operations and military liaison; for a charter flight department, the relevant service is its risk and compliance consulting. The useful outcome is not a polished template. It is a fleet-wide record that lets the safety team explain what it checked, what it found and what changed.