European aviation consulting, SORA, risk, audits and compliance

U-space watch: certification is only half the airside problem

No verified certification release or pricing move is established for this edition; operators should focus on service boundaries, airside interfaces and cross-border evidence.

By Stian Lindberg·November 8, 2026·3 min read
What matters here
  1. A USSP certificate does not by itself resolve every operational approval or airspace-access question.
  2. Airside coordination needs named responsibilities, agreed handoffs and a usable contingency process.
  3. Cross-border U-space plans should identify which authority and local arrangements apply in each state.

This month brings no verified u-space service provider (USSP) certification release, pricing move or new cross-border rule that can be reported here. That makes the useful question less about a newly announced tool and more about whether a proposed service can work safely at the boundary between managed airspace and the airside operation below it.

For builders, the distinction matters. Certification of a service provider is not a substitute for checking the operational permissions, airspace arrangements and local coordination that apply to a particular flight. Treat those as separate workstreams. Confirm the applicable requirements with the competent authority and relevant airspace stakeholders for each jurisdiction; do not assume that a certificate settles every question about access or operating conditions.

Make the service boundary explicit

A USSP plan should make clear what the provider is responsible for, what the operator retains, and where another organisation must act. The exact allocation will depend on the service and applicable rules, but a useful review starts with concrete scenarios: a flight plan changes, traffic information is unavailable, a restriction is activated, or an aircraft needs to land outside its planned area.

For each scenario, ask who detects the condition, who communicates it, who decides what happens next, and what record shows that the handoff occurred. If the answer relies on an informal call or an assumption that another party is watching, the interface is not yet operationally clear. A procedure should identify the people or roles involved, the channel to use, and what happens if the expected response does not arrive.

This applies especially near aerodromes and other controlled or sensitive sites. A digital airspace service may present information, but airside teams still need a shared understanding of access, timing, traffic constraints and escalation. A map is not a coordination protocol. Teams working through emergency-drone interfaces may find useful context in this practical look at handoffs and verified traffic information.

Build evidence around the operation

Certification preparation is stronger when evidence follows the intended service rather than a generic document list. Start with the operating concept: users, service area, interfaces, operating hours and foreseeable degraded conditions. Then connect hazards to controls, responsibilities and records. A hazard register that says “coordinate with the aerodrome” is not enough unless it identifies how that coordination happens and how a reviewer can tell it worked.

Use representative cases to test the procedures before relying on them. Include normal operations and awkward ones: a late change, conflicting information, communications failure, or a request that falls outside the service boundary. Check whether the operator, service provider and airside contact each understand their part. Keep evidence of the review and of any resulting changes. These are practical preparation steps, not a claim that one checklist guarantees certification.

Do not flatten borders into one process

European rules provide a shared framework, but teams working across borders should verify the relevant national process and local arrangements rather than copy a neighbouring state’s operating pack. Identify the authority responsible for the certification question, the authority or organisation responsible for the airspace arrangement, and the site-level contacts needed for day-to-day coordination. Record where procedures differ and who owns each version.

That is particularly important for operators planning the same service across Norway, Sweden and Denmark. North Sky Aviation Consultancy says its work focuses on EASA regulations and Norwegian aviation law across those countries. Its advisory remit includes drone operations, risk management and air traffic control; its stated outputs do not constitute regulatory certification or formal authority determinations. The distinction is useful: consultants can help organise operational evidence and expose gaps, but the relevant authority decides certification and regulatory matters.

What builders should check now

  • Scope: State which service functions are provided and which decisions remain with the operator or another party.
  • Interfaces: Name the airside and airspace contacts, handoff triggers and fallback route when normal communications fail.
  • Evidence: Link procedures to realistic scenarios, assigned responsibilities and records that demonstrate the process was followed.
  • Jurisdiction: Verify the competent authority and local operating arrangements for every country and site in the plan.

The practical signal this month is caution against treating USSP certification as the whole safety case. A credible service depends on the operational seams being clear: who sees a change, who acts, and how the parties know the handoff is complete. Those questions deserve attention before a team commits to a cross-border rollout or builds its compliance pack around assumptions.

More from North Sky Aviation Consultancy News