Resources

EASA has taken a major step in defining how Artificial Intelligence can be safely integrated into aviation, including unmanned systems. With the release of NPA 2025-07(B), the agency introduces its first regulatory framework for AI, offering guidance on how to demonstrate the safety and trustworthiness of AI components in aeronautical products — including drones.

A Shift Toward Risk-Based, Scalable AI Oversight

Instead of creating an entirely new category for AI systems, EASA proposes a performance- and risk-based framework that sits within existing regulatory pathways. This includes detailed specifications, Acceptable Means of Compliance (AMC), and Guidance Material (GM) tailored to how critical an AI component is within a drone’s architecture.

The focus is on enabling innovation while maintaining safety and public trust. The proposal addresses a wide range of AI use cases, from perception models for object detection to higher-level autonomy like navigation and flight control in drone-in-a-box systems. As AI becomes more embedded in operations such as inspections, security, and emergency response, the need for a harmonised framework becomes essential.

What Makes AI “Trustworthy”?

EASA outlines seven dimensions of AI trustworthiness:

• Robustness

• Explainability

• Transparency

• Human Oversight

• Data Quality

• Reliability

• Safety

These elements scale with the criticality of the AI system. A low-risk support tool (e.g. AI for pre-flight diagnostics) will be subject to lighter requirements than an autonomous mission controller used in beyond visual line-of-sight (BVLOS) operations.

The trustworthiness criteria will become an integral part of the compliance argument for Design Verification, Type Certification, and operational authorizations, especially when AI plays a safety-critical role.

Why This Matters for Drone Operators

Drone manufacturers and enterprise operators already rely on AI for advanced tasks - think of real-time object tracking, predictive maintenance, or autonomous flight planning. EASA’s proposed rules make it clear that such capabilities can no longer be treated as “black boxes.” Regulators will require visibility into how these systems are trained, tested, and monitored.

If you’re planning to deploy AI-driven functionality in a safety- or mission-critical setting, you’ll need:

• Documented design intent and model behaviour

• Evidence of robustness and explainability

• Human override mechanisms

• Traceability of input, output, and decisions

How AirHub Can Support

At AirHub, we support both the technical deployment and the regulatory integration of AI in drone operations.

With our software, you can:

• Integrate AI tools via API or SDK into the AirHub platform

• Log inference data and sensor inputs during flights

• Maintain a complete operational trace of decisions and performance

• Centralize documentation to support future audits or certification

With our consultancy services, we help you:

• Translate EASA’s trustworthiness principles into practical documentation

• Align your ConOps, SORA, and risk assessments with AI features

• Prepare for Design Verification or Certification submissions

Whether you’re developing an autonomous inspection workflow or deploying AI-driven situational awareness tools for security, we help bridge the gap between operational value and regulatory compliance.

What’s Next?

NPA 2025-07(B) is still in the consultation phase, and stakeholders can submit comments until June 2026. However, it’s already clear that AI will require a structured approach to risk, performance, and documentation, just like any other safety-critical system in aviation.

Drone operators that adopt these principles early will not only be better prepared for compliance but also gain a competitive edge by safely and confidently scaling autonomous operations.

Public safety agencies across the world increasingly rely on drones to improve situational awareness, protect responders, and accelerate decision-making. Fire departments use them to size up structure fires or map wildfires; police agencies deploy them to manage incidents, support search and rescue, or document crime scenes; emergency managers use them to survey damage and plan operations. Everywhere drones are deployed, they’re proving their worth.

But building a drone program that is safe, accountable, and built to last requires far more than buying hardware and putting pilots through training. It requires structure. It requires governance. And it requires documentation that brings consistency to every mission a drone team flies.

In November 2025, the U.S. Department of Homeland Security’s National Urban Security Technology Laboratory (NUSTL) released a comprehensive guide titled “Small Unmanned Aircraft System Program Documentation for Public Safety”, offering one of the most complete frameworks to date for agencies seeking to establish or mature an sUAS program. 

At AirHub , we see daily how the most successful drone programs, from small municipal departments to large metropolitan agencies, are those that invest early in building this kind of foundation. Below, we translate the most important guidance from the NUSTL document into a clear, readable narrative for public safety leaders.

Why Documentation Matters More Than Ever

Most drone programs begin with enthusiastic pilots and early success stories. A drone helps find a missing person, maps a wildfire, or provides overwatch during a tactical incident. But as usage grows, inconsistencies emerge: different flight procedures, different logging methods, unclear privacy boundaries, or uncertainty over who is allowed to deploy a drone and under what conditions.

This is where documentation becomes essential.

A well-structured operations manual is not “bureaucracy”, it is the mechanism that ensures:

• Safe flight operations, grounded in aviation standards

• Legal and regulatory compliance

• Consistency, even as personnel change

• Transparency and accountability to the public

• Scalability, especially as programs move toward DFR or 24/7 readiness

NUSTL’s framework is built around that philosophy: give agencies a blueprint they can adapt to their own environments, no matter their size or mission set. 

The Backbone: Policy and Governance

One of the strongest messages from the NUSTL guide is that a drone program must be rooted in clear governance. That starts with a policy that defines purpose, authority, and limitations.

The policy sets out why the program exists - whether to support firefighting, SAR, hazardous materials incidents, crime scene investigation, or emergency management - and makes explicit that drones are deployed only within defined legal and ethical constraints. It also affirms that pilots must be properly trained and certified, and that operations must respect privacy, data protection, and civil liberties. 

From there, governance becomes a matter of people: defining who is responsible for what.

The NUSTL document outlines a set of roles that together form the structure of a professional drone team: a program manager, remote pilots, visual observers, a training officer, an airspace coordinator, a records manager, and someone responsible for communications with the public. These roles may be combined in smaller agencies, but the responsibilities must be clearly described.

This clarity is what allows a program to function safely and predictably, even when the stakes are high and conditions are rapidly changing.

Training and Competency: Beyond the Certificate

Earning a Part 107 certificate is only the beginning. Public safety drone operations are often complex, high-risk, and time-sensitive. They require decision-making under pressure, coordination with air and ground units, and the ability to adapt to changing conditions.

NUSTL emphasizes the importance of recurrent training, scenario-based exercises, and continuous proficiency tracking. 

It also introduces aviation principles that are sometimes overlooked in the drone world: Aeronautical Decision-Making (ADM), Crew Resource Management (CRM), and structured situational awareness tools such as the PAVE and IMSAFE checklists.

These frameworks help pilots identify risks early, communicate effectively, and avoid the types of human-factor mistakes that remain the number one cause of aviation incidents.

In our work at AirHub, we see how transformative this mindset is. When a drone team adopts aviation-grade professionalism, everything improves - flight safety, mission outcomes, and community trust.

From Theory to Action: Building Operational Procedures

Policies describe what the program should do. Procedures describe how to do it.

The NUSTL document includes an extensive set of procedures covering every phase of flight, from 24 hours before takeoff to the final post-flight debrief. These include:

• Preflight inspections

• Equipment setup

• Mission planning

• In-flight conduct

• Landing protocols

• Post-flight data validation

• Emergency procedures

The value of these procedures is that they remove ambiguity. They ensure that every pilot follows the same sequence, the same communication protocols, the same standards before launching an aircraft over a fireground or urban area. 

This also enables after-action reviews. When procedures are clear and consistent, it becomes possible to understand what went well (or what went wrong) and to continuously improve.

Preparing for the Unexpected: Emergency Procedures

One of the strongest contributions of the DHS/NUSTL guide is its detailed emergency procedures. These address exactly the kinds of contingencies public safety pilots fear most:

• Losing connection to the aircraft

• GPS dropout

• RF interference in urban or airport environments

• Propulsion or flight-control failures

• Low-battery situations

• Airspace incursions

• Bird strikes

• Flyaways

Each procedure is written as a step-by-step checklist designed to snap pilots back into a structured response under pressure. 

These tools are invaluable, and we often help agencies translate them directly into their SOPs or into quick-reference cards for field operations.

Maintenance, Equipment, and Lifecycle Management

Public safety drone fleets are no longer small collections of off-the-shelf quadcopters. Increasingly, agencies operate a mix of:

• Multirotors

• Fixed-wing platforms

• Thermal and optical payloads

• LTE/5G-connected drones

• Remote charging stations

• Command-and-control platforms

• Docking systems for DFR

With this complexity comes the need for structured maintenance and asset management.

NUSTL emphasizes regular inspections, maintenance logs, controlled storage, battery-health management, and monthly operational audits. Even small issues - a worn propeller, outdated firmware, or poorly stored battery - can escalate into safety risks. 

A mature drone program maintains full traceability of every airframe, every battery, every payload, and every repair.

Data, Cybersecurity, and Privacy

As drones increasingly become flying cameras, sensors, and data collectors, agencies must treat them as part of a broader digital ecosystem. NUSTL dedicates an entire section to cybersecurity and data governance, emphasizing the importance of protecting:

• Command-and-control links

• Captured data

• Stored media

• Network connections

• Cloud-based or on-premise integrations

This includes encryption, access control, software updates, and alignment with agency-wide cybersecurity policies. 

Equally important is the protection of privacy and civil liberties. Public trust is essential, especially for police and municipal agencies. Progressive programs go beyond minimum compliance, actively educating the community about how drones are used, when they are deployed, and how data is managed or deleted.

Sustaining the Program: Budgeting and Collaboration

A drone program is not a one-time investment; it is an ongoing capability. NUSTL recommends building a multi-year budget that accounts for:

• Equipment replacement

• Battery lifecycle costs

• Software subscriptions

• Training and recurrency

• Maintenance and repairs

• Program audits

• New mission capabilities

Collaboration is also key. Drone programs increasingly support - and are supported by - neighboring agencies, state emergency management offices, and federal partners. Clear procedures help define when and how these collaborations occur. 

Conclusion: Documentation as a Foundation for Trust and Excellence

Public safety drone programs are rapidly evolving, moving toward continuous operations, DFR, automated dispatch, and deeper integration with command-and-control systems. This evolution brings extraordinary opportunity, but only for agencies that approach drones with the rigor of aviation.

The DHS/NUSTL framework provides an invaluable blueprint. It helps agencies build policy, structure teams, standardize procedures, ensure safety, manage equipment, protect data, and improve continuously. It is the kind of guidance that elevates a drone program from “good” to “professional”.

At AirHub, we help public safety agencies translate these principles into reality - building documentation, developing SOPs, training pilots, designing DFR concepts of operations, and deploying our AirHub Drone Operations Center that makes drone operations safe, compliant, and scalable.

If your agency is looking to create or mature an sUAS program, we would be glad to support you.

One of the key enhancements in SORA 2.5 is the more refined role of population density in the risk assessment process. Understanding who is on the ground, and how many, is essential when determining the Ground Risk Class (GRC) of a drone operation. This influences everything from operational constraints to the level of mitigation required. But until recently, finding reliable and consistent data across EASA Member States was a real challenge.

To address this, EASA has now released a harmonised dataset of statistical population density, which can directly support operators in conducting more precise and consistent SORA assessments. At AirHub, we’ve already integrated support for this dataset into our software, helping our users streamline their risk assessments and build compliant operations.

Why Is Population Density So Important in SORA?

In the SORA framework, one of the primary steps is the determination of the initial GRC, which is based on the area of operation and the expected presence of people on the ground. This step is crucial because it determines the baseline level of risk that must be mitigated before an operation can be approved.

Under SORA 2.5, population density is used to support the following:

• Characterisation of the operational area: rural, sparsely populated, populated, or densely populated

• Adjustments to the GRC based on shielding, strategic mitigations, or containment measures

• Justification of CONOPS and ground risk mitigations in more complex or populated environments

Accurate population data is therefore a cornerstone of any robust SORA package.

The New EASA Dataset: A Step Forward

To improve consistency across Member States, EASA has published a new, harmonised dataset of population density. It is designed specifically to support drone operations and is accessible via this portal:

EASA Statistical Population Density Portal: https://experience.arcgis.com/experience/b00a6ce43d1943959d21bc957de265f4

The underlying methodology and use of this dataset are explained in the EASA document:

Guidelines on Static Population Data: https://www.easa.europa.eu/en/domains/drones-air-mobility/operating-drone/statistical-population-density-easa-member-states

According to this guidance, the dataset classifies population density using a hexagonal grid with cells of 250 meters in width (approximately 5 hectares per hex). Each hexagon contains the population count and the population density per square kilometre, allowing operators to determine the applicable category for their area of operation.

The four categories of population density defined are:

• Very low: fewer than 100 people per square kilometre (typically rural or remote areas)

• Low: between 100 and 400 people per square kilometre (sparsely populated regions)

• Medium: between 400 and 1,000 people per square kilometre (suburban or semi-urban environments)

• High: more than 1,000 people per square kilometre (urban or city areas)

Using the Dataset in Your SORA

To use the EASA dataset in your SORA, follow these steps:

1. Identify your operational area by defining the full volume and ground buffer of your mission using GIS tools or the EASA population portal.

2. Extract the hexagonal density data and determine the density class of your flight area.

3. Use the assigned density level to justify your initial GRC, following the methodology defined in the SORA AMC/GM.

4. Include map visuals, numerical data, and your justification in your CONOPS and SORA documents.

At AirHub, we help automate this process.

How AirHub Software Supports This

Our Drone Operations Platform allows users to upload and overlay the EASA dataset directly in our mission planning environment. Users can:

• View the EASA population density map as an integrated layer

• Automatically assess density levels per operational zone

• Export relevant data for use in SORA and CONOPS documentation

• Combine the density layer with other planning data, such as airspace, weather, terrain, and infrastructure

This offers a complete and compliant planning environment, particularly important for BVLOS and urban operations.

How Our Consultancy Can Help

Navigating SORA 2.5 isn’t just about data, it’s about interpretation and application. Our Consultancy team can support you in:

• Choosing appropriate risk levels and mitigations based on your operation’s design

• Structuring your documentation in line with current authority expectations

• Generating SORA, CONOPS, and OM documents that incorporate real-world data, including population density overlays

• Advising on future-proofing your authorisation strategy as operations expand or regulations change

We combine deep regulatory knowledge with hands-on operational experience. With the right tools and support, compliance becomes an enabler, not a burden.