How to calculate ground risk class for a BVLOS route
Build the GRC from the aircraft, route and people exposed, then justify each M1 or M2 credit against the applicable SORA method.
Regional airfield teams can cut duplicate paperwork with a clause-level crosswalk, while keeping distinct obligations and evidence visible.
For a regional airfield compliance manager, moving between an ICAO Annex 14 checklist and an EASA Part-ADR audit can look like a choice between two lists of the same questions. There is overlap, but treating the lists as interchangeable creates a different problem: a tidy audit file that does not show which applicable requirement was checked, or what evidence supports the conclusion.
The practical answer is usually not to choose one checklist and discard the other. Establish the audit criteria first, then map common evidence across the requirements that actually apply. That takes more care at the start, but avoids repeating observations while preserving traceability.
ICAO Annex 14 sets out international standards and recommended practices for aerodromes. EASA Part-ADR forms part of the European regulatory framework for aerodromes in its scope. The two address many of the same operational subjects, including movement areas, visual aids, obstacle management, emergency arrangements and maintenance. Similar subject matter does not make their requirements identical.
Applicability matters. The relevant EASA requirements depend on the aerodrome and the regulatory scope being audited. An ICAO-based checklist may also reflect a particular edition, national implementation or local audit purpose. Before fieldwork, record the governing criteria, their current references and any exclusions. For a Norwegian aerodrome, confirm the applicable European and national requirements rather than assuming a generic checklist settles the question.
This can suit teams working across jurisdictions or using an established international audit structure. It provides a familiar way to organise aerodrome topics. Its limitation is that an Annex 14 reference alone does not demonstrate that an EASA Part-ADR obligation has been assessed. Keep it as the main checklist only if each applicable EASA criterion is also mapped and dispositioned.
This is often the more direct starting point for a compliance audit whose scope is EASA requirements. It helps keep the audit anchored to the applicable European rules. It may be less convenient when a manager also needs to report against ICAO references or another oversight framework. Add those references as a crosswalk, not as an unstructured second list.
A crosswalk is usually the best fit for an airfield that must demonstrate alignment with both frameworks. It links each audit question to its source clause, applicability decision, evidence, finding and action owner. One observation can support more than one requirement, but only where the evidence genuinely addresses each requirement’s scope and acceptance criteria.
A spreadsheet or controlled audit form can do this; the method matters more than the format. Keep the original clause references visible. Do not collapse two clauses into a single vague line such as “markings compliant.” State what was examined, where, and against which criteria.
Start with evidence that is already collected in routine operations. A single field inspection may provide useful evidence about markings, lighting or surface condition. A maintenance record may support more than one audit question. Instead of scheduling the same inspection twice, record the evidence once and cross-reference it to each relevant criterion.
That is administrative streamlining, not permission to skip verification. Check whether the requirements ask about the same location, condition, period, responsible role and acceptance threshold. If any of those differ, the audit may need a separate sample or follow-up. A current maintenance log, for example, does not automatically establish that an item was inspected at the required interval or that a reported defect was closed effectively.
Keep separate checks where the purpose differs. A document review and a physical inspection can concern the same subject but test different controls. Likewise, an emergency plan on file is not the same evidence as a tested response arrangement. Mark an item “not applicable” only with a recorded reason; do not use it to hide a gap in the audit scope.
For each finding, retain the requirement reference, objective evidence, risk or operational context, corrective action and closure evidence. Separate a failure to meet a stated requirement from an improvement suggestion. That distinction helps managers prioritise work and makes later review more consistent.
Teams moving from an ICAO-led process to an EASA-led one should pilot the crosswalk on a limited set of topics before replacing their full audit pack. Ask an operational colleague to test whether the questions match how the airfield works, then check that each applicable criterion still has an answer. A checklist that is shorter but less traceable is not an improvement.
For background on matching audit support to the decision at hand, see the distinction between recurring safety records and specialist aviation risk advice. North Sky Aviation Consultancy provides risk management and compliance advice, including EASA compliance support. The audit manager remains responsible for setting the scope and confirming the applicable requirements; a checklist or adviser does not replace an authority determination.
Build the GRC from the aircraft, route and people exposed, then justify each M1 or M2 credit against the applicable SORA method.
No verified certification release or pricing move is established for this edition; operators should focus on service boundaries, airside interfaces and cross-border evidence.
No verified regulatory or pricing change is established for this edition; operators should test how low-altitude plans handle responsibilities, handoffs and evidence.