EASA Part-ADR or ICAO Annex 14: build one auditable checklist
Regional airfield teams can cut duplicate paperwork with a clause-level crosswalk, while keeping distinct obligations and evidence visible.
Build the GRC from the aircraft, route and people exposed, then justify each M1 or M2 credit against the applicable SORA method.
A ground risk class calculation is only as sound as the operation it describes. For a BVLOS route, do not begin by looking for a single number to put in the application. First define where the aircraft can fly, where it could depart from that planned path, and who may be on the ground in the affected area.
Under EASA SORA, the assessment starts with an intrinsic ground risk class (GRC). Strategic mitigations under M1 may then reduce exposure, and M2 may reduce the effects of an impact. Each credit needs evidence. Treating a mitigation as a general safety statement, rather than a specific change to risk, is a common way to produce a GRC that will not stand up to review.
Break the route into segments where the operating conditions or ground exposure change. Include launch and recovery locations, planned holding or turn points, and credible route deviations or contingency areas. A route drawn as a thin line is not the full operation.
Set out the operational volume and the ground risk buffer using the applicable SORA guidance. Record the assumptions that determine their extent. The buffer is part of the ground-risk assessment, not an informal extra margin to be added after the calculation. If a segment crosses a settlement, industrial site or open land, the change in exposure should be visible in the assessment rather than averaged away across the whole route.
Use the current applicable SORA method and its tables to determine the starting class. The relevant inputs include the aircraft's characteristics, such as its size and maximum speed, and the ground exposure in the operational area and buffer. Use the aircraft and configuration intended for the operation, not a lighter or slower variant unless that is the one actually being assessed.
Assess the people who could be exposed, not just the land-use label on a map. Population data can help, but it may not capture workers, visitors, road users or temporary gatherings. Check likely use of the area at the time of flight and document the source, date and limits of the data. Where information is uncertain, state that uncertainty and take a conservative approach rather than implying precision that the evidence does not support.
Apply the SORA table as written. Do not substitute a locally invented score, or assume that a low average population density cancels out a concentrated group along one part of the route. Keep the segment-level evidence so another reviewer can follow how the intrinsic GRC was reached.
M1 covers strategic mitigations that reduce the likelihood of people being exposed to the aircraft's impact area. Depending on the operation and applicable SORA guidance, that may involve restricting when or where the flight takes place, or relying on substantiated sheltering. The key question is practical: what measure changes who can be present, or how exposed they are, during this flight?
Describe the measure, who is responsible for applying it, and how the operator will verify it before and during the operation. A proposed time window is not a mitigation if the route is still flown when the relevant area is occupied. A claim that people will be indoors needs a basis, too. Apply only the reduction allowed by the relevant SORA table and supported by the evidence. Record the resulting GRC and retain the intrinsic value for traceability.
M2 concerns reducing the effects of an impact. It does not make an exposed person disappear from the ground-risk picture. Assess the claimed measure against the aircraft and the conditions in which it will operate. Show what evidence supports the claim and whether the measure will be available and effective throughout the route.
Use the applicable SORA method to determine whether, and by how much, M2 can reduce the GRC. Do not stack reductions by assumption. If the safety case depends on a technical measure, explain its limitations and what happens if it fails. A mitigation that exists only in a design description, but is not assured in the operating configuration, is not a sound basis for credit.
Review the ground risk buffer against the route, aircraft performance and the assumptions used in the assessment. Check whether the buffer reaches roads, buildings or other occupied areas, and whether the exposure changes at particular times. Tie its dimensions and any operational restrictions to evidence. If the assessment relies on a restricted area, explain how the restriction is established and maintained.
Finish with a clear record: route and segment boundaries, aircraft configuration, exposure sources, intrinsic GRC, each M1 or M2 measure, evidence for its use, and the resulting class. Note the SORA version and applicable national requirements. EASA guidance does not remove the need to check the authority's expectations in the state where the operation will take place.
For work on a route where local population data, operating limits or mitigation credit is uncertain, a second review can expose weak assumptions before submission. North Sky Aviation Consultancy offers consultations on drone operations and regulatory compliance, including SORA-related work. Its advisory is not regulatory certification or a formal authority determination. For broader route-planning context, see how ground-risk calculations connect with landing options and local airspace coordination. North Sky can be contacted at roe.nerem@northsky.no.
Regional airfield teams can cut duplicate paperwork with a clause-level crosswalk, while keeping distinct obligations and evidence visible.
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.