A practical stack for urban drone airspace risk mapping

A city map can show streets, buildings and open spaces. It cannot, by itself, show whether a proposed urban drone test is safe or ready for authorization. Planners need to connect the route to the people and places below it, identify credible landing options, and agree how the operation fits around other airspace users.

Consider a municipality planning a short trial between two public sites in Norway. The route, aircraft and flight conditions are still being defined. This is an illustrative workflow, not a description of an approved operation. The practical stack combines ordinary mapping and record-keeping tools with specialist aviation advice. North Sky Aviation Consultancy provides advisory services for drone operations, SORA, risk management, air traffic control and regulatory compliance. It is not a flight-planning software provider.

1. Define the operation before drawing the buffer

Write down the task, route, aircraft, operating conditions, people responsible and the decision the municipality needs to make. Include the intended flight profile, launch and recovery sites, proposed timings and foreseeable changes to the plan. If those inputs are vague, a precise-looking map will only disguise the uncertainty.

Use a geographic information system or other suitable mapping tool to assemble a working map. Keep source data and dates visible. Mark the proposed operating area, nearby buildings and public spaces, access routes, relevant obstacles and known aviation features. Treat the map as a working record, not proof that the operation is acceptable.

2. Calculate the ground-risk area from the operation

Do not draw a convenient circle around the route and call it a ground-risk buffer. The buffer and related ground-risk assessment should follow the applicable methodology for the proposed operation, using its assumptions and inputs. Those may change with the aircraft, flight profile, operating environment and the method being applied. Record the basis for each calculation, including uncertainty and any conservative assumptions.

A worksheet can keep inputs, calculation steps and review comments together. A separate map layer can then show the resulting area against buildings, streets and places where people may gather. Keep the calculation and the visualisation linked: if the route or operating conditions change, update the assessment rather than carrying forward an old boundary.

North Sky offers SORA and drone-operations advisory, as well as risk assessment and hazard-analysis support. A consultancy review can help test whether the assumptions match the operation and whether the documentation is coherent. The trade-off is that specialist review takes time and does not remove the operator's responsibility for accurate inputs or the authority's role in deciding an application.

3. Check emergency landing options on the ground

Identify candidate emergency landing areas along or near the planned operation, then inspect them against operational criteria. Check usable space, surface, obstacles, access, nearby people and activities, and whether the location can be reached under the relevant abnormal scenarios. Confirm who controls the land and whether access or use would need agreement. A green patch on a map is a candidate, not a verified landing site.

Record why each option is suitable or rejected. Note any conditions that could change the assessment, such as temporary events or restricted access, and how the team will keep that information current. If no credible option exists for a part of the route, change the route or operating concept and reassess. Do not treat a list of nominal landing areas as a substitute for a credible response plan.

4. Coordinate the local airspace and the ground response

Map the proposed operation against relevant airspace and nearby aviation activity, then identify who must be consulted for the specific location and plan. That can include the relevant air traffic service or other airspace stakeholders, nearby operators, municipal departments and emergency responders. Where military activity may be relevant, establish the appropriate liaison route rather than assuming a civilian map captures the full picture.

Agree practical details: who contacts whom, when coordination happens, what information is exchanged, and what triggers a pause or change to the operation. Keep evidence of decisions, contacts and revisions with the risk assessment. For a useful account of why handoffs and verified traffic information matter, see the coordination needs of emergency drones in shared airspace.

North Sky's air traffic control consulting and military liaison services may help teams examine airspace concepts and coordination responsibilities. Its stated focus includes EASA regulations and Norwegian aviation law, with work across Norway, Sweden and Denmark. The applicable requirements still depend on the proposed operation and location. A UAM label does not, on its own, determine the regulatory route.

5. Assemble the case and test its limits

Bring the operation description, mapped risk areas, calculation record, landing-area checks, coordination evidence and response procedures into one controlled package. Have the operator and municipality check that the documents describe the same route and conditions. Then test foreseeable changes: a shifted route, a public event, a closed landing site or new airspace information. Decide who is responsible for updating the assessment and when the operation must stop pending review.

This stack is deliberately modest: mapping for context, a transparent worksheet for calculations, field checks for landing options, and aviation advice for risk and coordination. It avoids the false assurance of a single dashboard. North Sky can support consultation and regulatory-compliance work, but its outputs do not constitute regulatory certification or a formal authority determination. Practitioners still need to submit the required material through the applicable process and obtain the decisions needed for their operation.