Europe’s U-space framework was created to support safe, efficient and highly digitalised drone operations at scale. It introduced a structured environment in which unmanned aircraft operators, U-space service providers, common information service providers, air traffic services and national authorities exchange operational information.
The framework is ambitious, but the first years of implementation have also shown how demanding a complete U-space deployment can be. Designating the airspace, performing the airspace risk assessment, establishing information services, certifying providers and building interfaces between organisations require time, expertise and investment.
EASA is now preparing a regular update of the U-space framework. This creates an important policy question: should Europe introduce a more proportionate entry model, sometimes described informally as “U-space Light”, for operations and locations that need digital coordination but may not require the full complexity of a large U-space deployment?
What the current U-space framework requires
U-space is not simply an application used to display drones on a map. It is a regulated airspace environment established by a Member State following an airspace risk assessment.
Within designated U-space airspace, operators are required to use services delivered by certified U-space service providers. The current framework includes four mandatory services:
- UAS flight authorisation;
- geo-awareness;
- network identification; and
- traffic information.
These services are intended to create a shared operational picture, reduce conflicting flight intentions, inform operators about airspace restrictions and provide information about relevant manned and unmanned traffic.
Member States may also require additional services, including weather information and conformance monitoring, where these are needed for the safety and efficiency of a particular U-space airspace.
Why implementation is complex
The regulatory logic is understandable. Dense or complex drone traffic requires dependable services, clear responsibilities and consistent oversight. However, the same architecture may be difficult to justify for every location and every type of operation.
A full deployment may require:
- a detailed airspace risk assessment;
- formal designation of the U-space airspace;
- certified U-space service providers;
- a common information service architecture;
- interfaces with air traffic service providers;
- electronic conspicuity information from relevant manned aviation;
- cybersecurity and information-security controls;
- continuous service monitoring;
- contingency and incident-management arrangements; and
- regulatory oversight across several organisations.
This can be appropriate for a large urban region, airport environment or high-density drone network. It may be harder to support economically in a rural inspection corridor, temporary emergency area or location with only a small number of recurring BVLOS flights.
What EASA has officially planned
EASA’s Rulemaking Task RMT.0748 is intended to update the acceptable means of compliance and guidance material associated with the U-space regulatory framework. The task is based on lessons learned from implementation and feedback from national authorities, service providers, operators and other stakeholders.
The work is expected to consider industry experience, international and open standards, certification practices and recommendations developed through EASA’s implementation-support activities.
The current plan also allows EASA to collect proposals and justifications for broader improvements to the U-space framework. According to the European Plan for Aviation Safety 2026, consultation and the related EASA decision are planned for 2027.
This distinction is important. The confirmed task is currently an update of AMC and GM. It is not yet a published legislative proposal introducing a new legal category called U-space Light.
What could “U-space Light” mean?
A U-space Light model could provide a proportionate digital traffic-management layer for locations where operational complexity and traffic density are lower than those assumed for a full U-space deployment.
The word “light” should not mean weak safety requirements. It should mean requirements scaled to the real risk and complexity of the operation.
A possible model could preserve essential safety functions while simplifying the organisational and certification architecture. Depending on future policy decisions, this might involve a standardised service profile, simpler designation processes, reliance on nationally provided common information or recognition of qualified services without requiring the complete architecture used in high-density environments.
These are policy options, not current EASA requirements. Any implementation would need a formal legal basis and a clear demonstration that safety outcomes remain equivalent to the risk being managed.
Where a lighter model could be useful
Several operational environments may benefit from a proportionate digital coordination layer.
Rural BVLOS corridors
Linear inspections of power lines, pipelines, railways, roads and waterways may involve repeated operations over long routes with relatively low population and traffic density. Operators still need airspace awareness and coordination, but the business case may not support a full urban-style U-space ecosystem.
Temporary emergency deployments
Wildfires, floods, missing-person searches and infrastructure failures may create an urgent need to coordinate drones from several organisations. A rapidly deployable digital service profile could be more useful than a permanent, complex airspace structure.
Industrial and port areas
Ports, energy facilities, mines and large industrial sites may host recurring drone operations within defined areas. These locations could benefit from flight-intent sharing, authorisation and local traffic information without necessarily requiring the same architecture as a metropolitan U-space.
Early regional markets
Some Member States and regions may want to begin with limited U-space functions before traffic density justifies full deployment. A transitional model could allow operational experience to develop while preserving interoperability with future services.
Which functions should remain essential?
A proportionate model would still need to answer several safety-critical questions.
Operators need reliable information about geographical restrictions and temporary airspace changes. Relevant operations need a mechanism for sharing flight intent or obtaining authorisation. The system must provide an appropriate picture of nearby traffic and must identify responsibility for managing conflicts.
Authorities also need access to information for oversight, incident investigation and emergency intervention. Cybersecurity, identity management, service continuity and data quality cannot be removed simply because the deployment is described as light.
The design challenge is therefore to reduce unnecessary organisational burden without removing the functions that make digital airspace coordination trustworthy.
U-space Light should not become another isolated system
Interoperability would be essential. A lighter profile should not create a separate national or regional technology island that cannot exchange information with certified U-space service providers, air navigation services or operators using the full framework.
The data models, identities, interfaces and operational concepts should support transition. An area may begin with a lower-density service profile and later move to full U-space as the number and complexity of operations increase.
Operators should also be able to cross boundaries without changing equipment, identity systems or flight-planning formats every few kilometres.
Relationship with Electronic Conspicuity and DAA
A lighter U-space profile would still need to manage encounters with manned aviation. Electronic Conspicuity could provide information about equipped aircraft, while U-space traffic information could distribute that data to drone operators.
However, neither service guarantees that every aircraft will be visible. Non-cooperative or unequipped traffic may remain outside the digital picture. Depending on the air risk, operators may still require Detect and Avoid systems, observers, airspace coordination or other tactical mitigations.
U-space Light should therefore be seen as one part of a layered safety architecture, not as a universal replacement for DAA or conventional airspace procedures.
Certification and oversight
One of the most difficult questions is whether a lighter model would also require a lighter form of service-provider approval.
Full USSP certification establishes organisational, technical, operational and information-security requirements. These controls create trust, but they also require significant investment.
A proportionate framework could potentially distinguish between service profiles based on their safety role. A provider supporting low-density geo-awareness and flight-intent exchange may not create the same risk as a provider responsible for tactical deconfliction in complex airspace.
Any differentiated approach would still need clear accountability, minimum performance requirements, occurrence reporting, continuity arrangements and competent-authority oversight.
The economic argument
U-space needs a sustainable business model. If the cost of designation, certification and service provision is higher than the value of the drone operations it supports, deployment will remain limited.
A proportionate entry layer could help smaller regions, infrastructure operators and public authorities begin using digital airspace services without immediately building the most complex architecture.
It could also allow service providers to test demand, develop operational experience and expand gradually. At the same time, lighter requirements must not create unfair competition with fully certified providers carrying wider responsibilities.
What should EASA consider?
The update should focus on the practical lessons from the first implementations. Important questions include:
- which requirements have created genuine safety value;
- which requirements are interpreted differently by national authorities;
- where certification and designation processes can be standardised;
- how industry standards can be recognised more efficiently;
- how information-security obligations can remain proportionate;
- whether service requirements should vary with traffic density and operational complexity;
- how temporary or local deployments can be supported; and
- how a lighter profile could transition to full U-space.
A chance to make U-space easier to deploy
The first phase of U-space regulation created the legal and institutional foundation. The next phase should focus on implementation, proportionality and scale.
A U-space Light concept could become useful if it is designed as a genuine risk-based profile rather than a marketing label. It would need clearly defined use cases, performance requirements, governance and boundaries.
For complex and dense environments, full U-space will remain necessary. For simpler operations, Europe may benefit from an entry layer that delivers the right services without requiring every region to begin with the most demanding architecture.
Conclusion
EASA’s planned update is an opportunity to turn implementation experience into clearer and more efficient rules. The confirmed work currently focuses on revising AMC and GM, supporting harmonisation and collecting proposals for broader improvements.
Whether a formal U-space Light category emerges remains to be seen. The need behind the idea is nevertheless real: Europe needs digital airspace services that are safe, interoperable and proportionate to local risk.
For PANKA readers, the key takeaway is that the future of U-space may not be one identical architecture everywhere. A scalable system may require several implementation profiles connected by common standards — from limited rural coordination to fully automated high-density urban traffic management.