European aviation consulting, SORA, risk, audits and compliance

A practical airfield safety stack for inspection readiness

A regional aerodrome can connect hazard tracking, controlled manuals and audit evidence without treating one system as the whole compliance job.

By Anke Weber·November 11, 2026·4 min read
What matters here
  1. A live hazard log needs an owner, review date and link to the evidence behind each action.
  2. Manual changes should be traceable from the relevant obligation through approval to the current version.
  3. North Sky offers advisory support and an audit preparation kit, but neither replaces an aerodrome’s own records.

A regional aerodrome manager preparing for a scheduled annual inspection has a familiar problem: the evidence exists, but it is split between a spreadsheet, the current manual, old emails and people’s memories. The answer is not necessarily a larger software system. It is a clear route from hazard to action, from requirement to procedure, and from each claim to the record that supports it.

The example here is a practical scenario, not a report of a North Sky client engagement. The stack combines ordinary document and task tools with North Sky Aviation Consultancy’s advisory services and its listed Aviation Third-Party Audit Preparation Kit. The exact scope of that kit should be confirmed with North Sky; its public description identifies it for maintenance and audits, but does not specify its contents.

1. Set one source of truth for hazards

Start with a live hazard log in a tool the airfield team can maintain. A spreadsheet may be enough for a small operation; the important part is the discipline around it. Give every entry a unique reference, a plain-language description, a responsible owner, a status, a review date and a link or reference to supporting evidence. Record the decision and rationale when an item is accepted, mitigated or closed.

Keep the log operational, not just presentable. A new hazard should be recorded when it is identified, not reconstructed before inspection. Review open actions on a fixed cadence and after relevant operational changes. A shared task tracker can help owners see due dates, but it does not replace the hazard record: the log should preserve the risk decision and its history.

The trade-off is straightforward. A spreadsheet is flexible and familiar, but can become fragile when several copies circulate or ownership is unclear. A dedicated system may impose more structure, but adds administration and still needs reliable inputs. Choose the simplest arrangement that gives the team a dependable current record.

2. Connect hazards to the aerodrome manual

Do not let the manual become a separate annual editing exercise. When a hazard, operational change or review identifies a procedural gap, record whether the manual needs to change. Track the proposed change, its reason, reviewer, approval and effective version. Keep superseded versions and approval evidence according to the organisation’s document-control arrangements.

For each relevant obligation, map the requirement to the procedure that addresses it and the evidence that shows the procedure is in use. A clause-level crosswalk can expose gaps without merging distinct obligations. The distinction matters when teams compare Part-ADR with ICAO material; a crosswalk that keeps each obligation visible is more useful than a single checklist that obscures where requirements differ.

Use a controlled document repository if one is already available. Otherwise, establish a consistent naming and approval convention in the tools the organisation has. A folder full of files is not document control unless staff can identify which version is current and how it was authorised.

3. Build an evidence index, not a last-minute bundle

Keep an evidence index beside the audit plan. For each inspection topic, list the relevant manual section, record or meeting decision, its owner, the storage location and the date it was last checked. Link to the record where possible rather than copying it into multiple folders. That reduces the risk of presenting an obsolete version.

Use a task list to chase missing evidence, with a named owner and due date. Separate “document exists” from “practice is working”: a procedure may be current while staff need a refresher, or a completed action may lack a record of verification. Before the inspection, sample the links and ask someone other than the record owner to retrieve selected evidence. A neat index is useful only if it leads to the underlying record.

4. Bring in advice where the decision is uncertain

North Sky provides aviation advisory, risk management and compliance support, including risk assessment, hazard analysis, safety management systems, audit support and EASA documentation review. For an aerodrome team, consultation can be useful when the team is unsure how an operational change affects its risk assessment, what documentation needs review, or how to interpret an evidence gap. North Sky also lists an Aviation Third-Party Audit Preparation Kit for maintenance and audits.

Those are options for support, not substitutes for the aerodrome’s accountable decisions and records. North Sky says its outputs do not constitute regulatory certification, licensing, compliance verification or formal authority determinations. Keep that boundary explicit when assigning work: advisers can help examine the operation and documentation, while the organisation remains responsible for its own processes and submissions.

5. Run a short readiness review

  1. Pick a sample of open and recently closed hazards. Check that each has an owner, a current decision and traceable evidence.

  2. Select manual changes from the review period. Confirm the reason, approval and current version can be found.

  3. Follow several evidence-index entries to their source records. Note broken links, stale documents and unclear ownership.

  4. Assign corrections and dates, then repeat the sample before the inspection.

This airfield safety stack is deliberately modest: a maintained hazard log, controlled manuals, an evidence index and a way to assign follow-up. Its weakness is that it relies on people keeping the links and decisions current. Its strength is that the working record can remain proportionate to a regional aerodrome rather than becoming a parallel paperwork exercise. The test is not how much material the team can assemble. It is whether it can explain a decision and retrieve the evidence behind it.

More from North Sky Aviation Consultancy News