A practical risk stack for regional vertiport planning

A regional vertiport proposal can look straightforward on a map and still conflict with nearby flight activity, exposed populations, or obstacles that a desktop dataset misses. The useful response is not one all-purpose risk score. It is a repeatable assessment stack that preserves the evidence behind each finding and makes uncertainty plain.

Consider a planning team comparing two possible sites in a Nordic town. This is an illustrative workflow, not a description of a North Sky project. The team needs to screen ground risk, understand nearby air traffic, and identify obstacle hazards before it spends time on detailed design. North Sky Aviation Consultancy’s stated services include air traffic control consulting, risk management and compliance consulting, and drone operations and regulatory compliance assistance. An adviser in that role can help frame and review the assessment; the company does not describe a proprietary mapping platform or software integration.

1. Set the question before opening the map

Define the decision first: which sites merit deeper investigation, and what operating concept is being considered? Record the assumed aircraft, routes, operating hours, landing and departure paths, and any proposed altitude or separation constraints. These are working assumptions, not settled design parameters.

Set a common study boundary around each candidate site and agree on the data date, coordinate reference, units, and naming conventions. Keep a source register with the dataset owner, coverage, date, resolution, and limitations. If two analysts cannot reproduce the same map from the same inputs, the workflow is not yet repeatable.

2. Build the ground-risk layer

Use a geographic information system (GIS) to combine population and land-use information with the proposed site, route corridors, and plausible areas where an aircraft could come down. Separate residential areas, public spaces, roads, sensitive facilities, and less populated land where the available data supports those distinctions. Do not treat a population raster as a direct measure of risk: exposure depends on the operating concept and on the limits of the data.

Keep the underlying layers visible. A shaded map can help compare candidate areas, but it should not conceal data gaps or imply a level of precision the source does not provide. Where the result depends on a boundary or a population estimate, record the assumption and test a reasonable alternative. The output is a screening comparison, not a declaration that a location is safe.

3. Add air traffic and airspace context

Overlay the relevant airspace structure and available evidence of existing activity. Depending on the site, that review may include aerodromes, heliports, published routes or procedures, controlled airspace, and known local operations. Use current, authoritative information where available, and record its date. A static chart or a single traffic snapshot cannot establish how activity varies by time or season.

Ask an air traffic specialist to review the operational picture, not just the geometry. Identify who operates nearby, which interactions need coordination, and what information is missing. If a model or simulation is used to compare routing options, document its inputs and have the assumptions reviewed by people familiar with the airspace. North Sky’s earlier discussion of testing an air traffic scenario before trusting a simulation is relevant here: an attractive output is only as credible as its inputs and review.

4. Treat obstacles as an evidence problem

Bring terrain and available building or obstacle data into the same GIS project, but distinguish dataset-derived features from verified observations. Record the source and date for each obstacle layer. Buildings, cranes, masts, trees, and temporary works can change at different rates; a dataset that is adequate for early screening may not be adequate for a final operational assessment.

Flag features near proposed paths for targeted verification. That may mean checking records, requesting updated information, or arranging a suitable site survey. State what was checked, when, and by whom. Do not silently remove an apparent obstacle because it looks implausible on a basemap.

5. Compare, challenge, and preserve the record

Bring the three evidence groups together only after their limits are understood. Compare candidate sites against the same criteria and operating assumptions. A simple register can record each hazard, its evidence, uncertainty, proposed control, owner, and next action. Keep residual concerns visible instead of compressing them into one score.

Then run a sensitivity check. Change one important assumption at a time: for example, the route corridor, operating period, or population dataset. If the preferred site changes, that is a decision-relevant finding. If it does not, the team still learns which uncertainties matter less to the comparison.

For airspace planning and safety audits, retain dated source files, map exports, assumptions, review comments, and change history. A reviewer should be able to trace a conclusion back to its evidence. The assessment supports planning; it does not itself grant permission or replace applicable EASA requirements, Norwegian aviation law, or engagement with relevant authorities and operators.

Where advisory support fits

North Sky says it provides aviation advisory services across Norway, Sweden, Denmark, and the broader European region, including risk management and compliance consulting and air traffic control consulting. Its role in this kind of workflow would be advisory: helping an organization navigate aviation requirements and operational realities, rather than supplying a stated, bundled software stack. The trade-off is deliberate. Teams can choose tools suited to their data and internal processes, but they must own data quality, version control, and the links between evidence and decisions.

A credible vertiport airspace risk assessment is therefore less about buying a single map and more about joining separate evidence carefully. Start with a defined operating concept, preserve the ground, traffic, and obstacle layers, verify what matters on site, and document what remains uncertain. That produces a planning record that can be challenged and updated as the proposal develops.