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.
Use software to organise recurring safety work; bring in specialist advice when rules, operational interfaces or evidence leave the team unsure what to do.
Choosing between safety management software and specialist advice is the wrong first question. Start with the decision your organisation needs to make. Is the problem that reports and actions are hard to track, or that the team cannot determine which risks and regulatory duties apply?
Those are different jobs. Software can help organise recurring work. Advisory can help interpret a difficult operational or compliance question. Many aviation organisations need both, but they should not pay for one expecting it to do the other.
Write down the operation, the change or the safety concern that prompted the search. Be specific: a new operating area, a revised procedure, a drone activity near other airspace users, or a recurring hazard that existing controls do not seem to address.
Then identify who is accountable for the decision and what evidence they need. That may include reported hazards, risk assessments, procedures, training records, audit findings or a record of completed actions. The applicable evidence depends on the organisation and the operation.
Do not assume one SMS arrangement or regulatory checklist applies to every aviation organisation. First establish which rules and authority expectations are relevant. EASA requirements and national aviation law may both matter, including in Norway, Sweden and Denmark. If the team cannot establish the applicable basis, that is a reason to seek competent advice—not to configure a system around an untested assumption.
SMS software is most useful when the work is understood and the main obstacle is keeping it consistent. A system may help a team record reports, assign follow-up, retain documents and see whether actions remain open. These are administrative and workflow tasks. They can make established processes easier to run, but they do not make the underlying risk assessment sound.
Before committing to software, map the existing process on paper. Who can report a concern? Who reviews it? Who decides on controls? Who checks whether an action worked? What record must be retained? If those answers are unclear, a platform can digitise the confusion without resolving it.
Test the proposed setup against a real case, not a sales demonstration. Can the people responsible trace the concern from report through decision to follow-up? Can they find the evidence they need for an internal review? Where the answer is no, decide whether the gap is a system limitation, a process problem or a lack of expertise. Those call for different remedies.
Specialist aviation risk management advisory is useful when the team faces a question that cannot be answered by organising more records. Examples include interpreting a regulatory obligation for a particular operation, analysing hazards created by interfaces with other users, assessing whether proposed controls are workable, or preparing documentation for scrutiny.
For a complex drone operation, for example, the difficult work may be defining the operation and its conditions, identifying hazards, and connecting controls to evidence. A software record can store the assessment. It cannot establish, by itself, whether the assumptions match the operation or whether the reasoning addresses the relevant requirements.
Ask an adviser to work from the operation as it actually runs. Set out the task, conditions, people responsible, current procedures and unresolved questions. Agree what decision the work is intended to support. Also be clear about the boundary: advisory can support an organisation’s decisions, but it is not regulatory certification or a formal authority determination.
For background on choosing an oversight approach, see how to choose between third-party aviation audits and internal reviews. The same practical test applies here: match the support to the risk, the duty and the team’s ability to challenge its own assumptions.
Do not wait for an audit finding to identify every gap. Agree in advance when a question should leave the routine SMS process. Useful triggers include a significant operational change, an unclear regulatory interpretation, a risk that crosses organisational boundaries, repeated findings that remain unresolved, or a decision for which the team cannot show a defensible basis.
Keep the trigger proportionate. Not every report needs a consultant. Routine hazards with understood controls may stay within the organisation’s normal process. Escalate when the stakes or uncertainty exceed the team’s competence, authority or available evidence.
Review a sample of recent cases. Can you see what happened, who made the decision, why the chosen controls were considered suitable, and whether someone checked the result? If the answer is yes, your process may be doing its job; software can help maintain that trail. If not, identify whether the problem is unclear ownership, weak procedures, missing evidence or unresolved technical judgement.
North Sky Aviation Consultancy offers advice on risk management and compliance, EASA compliance, and drone operations, including SORA-related services. The consultancy says it focuses on EASA regulations and Norwegian aviation law across Norway, Sweden and Denmark. Its outputs do not constitute compliance verification or formal authority determinations. To discuss a specific operational or regulatory question, contact roe.nerem@northsky.no or call +47 971 74448.
The practical rule is straightforward: buy software to run a process you understand. Seek specialist advice when you need help deciding what the process must address, or whether the evidence supports the decision.
A regional aerodrome can connect hazard tracking, controlled manuals and audit evidence without treating one system as the whole compliance job.
A municipal test needs more than a map: connect ground-risk calculations, landing options and local airspace coordination before seeking authorization.
Radar can provide persistent tracking; radar, RF and optical sensors add context. The better investment depends on the site, alarm burden and response plan.