At the end of June 2026, EASA released a new revision of the Easy Access Rules for Unmanned Aircraft Systems (the EAR for UAS). For anyone who works with the specific category on a daily basis, this is the edition worth reading, because it is the point at which SORA 2.5 finally sits inside the single, consolidated reference document alongside Regulation (EU) 2019/947 and its acceptable means of compliance (AMC) and guidance material (GM).

If you have been following the file, none of the underlying content is a surprise. The legal change happened in September 2025, when EASA published Executive Director Decision 2025/018/R and introduced SORA 2.5, the latest version of the Specific Operations Risk Assessment developed by JARUS, into the AMC and GM to Regulation (EU) 2019/947. We looked at that moment when SORA 2.5 first landed. What the June 2026 EAR does is bring that decision, catalogued as Issue 1, Amendment 4 to the AMC and GM, into the one document that most operators and competent authorities actually open when they need an answer. The Easy Access Rules are a consolidation, so no new legal obligation arrives with them. What arrives is readability: three separate publications you used to cross-reference now sit in one coherent, colour-coded, navigable whole.

This post is written for the operators we work with most closely, meaning those flying in and around critical infrastructure, those running security operations, and public safety teams who often sit under their own national regime. Below is what changed, and what it means for each of you.

What actually changed

SORA 2.5 keeps the same fundamental logic as SORA 2.0: you describe your operation, assess the ground risk and the air risk, mitigate what you can, and arrive at a Specific Assurance and Integrity Level (SAIL) that tells you how much evidence you have to produce. What SORA 2.5 adds is a tidier method, sharper definitions, and less friction than operators and authorities met over the first years of practical use.

The methodology is now expressed as ten systematic steps. In outline, you document the proposed operation, determine the intrinsic ground risk class, optionally reduce it to a final ground risk class through mitigations, determine the initial air risk class and then the residual air risk class after strategic mitigations, apply tactical mitigation performance requirements, determine the SAIL, determine the containment requirements, identify the operational safety objectives, and finally compile the comprehensive safety portfolio.

A few points stand out for professional operators:

• The intrinsic ground risk is now more quantitative. The intrinsic ground risk class is scaled from 1 to 10 and is driven by the unmanned aircraft characteristics, meaning maximum characteristic dimension and maximum speed, together with the population density at risk in the operational volume and the ground risk buffer. This is a more explicit, data-led starting point than many operators were used to.

• The SAIL still runs from I to VI, and it remains the pivot of the whole assessment. A final ground risk class above 7 falls outside SORA and belongs in the certified category. SAIL V and VI operations require a type certificate issued by EASA under Part 21.

• The operational safety objectives are consolidated to seventeen. For the assigned SAIL, you show compliance with each of the seventeen OSOs at the required level of robustness, low, medium or high. This is a leaner set than the previous version, and the robustness logic is clearer.

• Containment is treated as its own function. Step 8 sets containment requirements at one of three robustness levels, low, medium or high, calculated from the unmanned aircraft characteristics, the SAIL, the average population density in the defined adjacent ground area, and the presence of any outdoor assembly of people within one kilometre of the outer limit of the operational volume.

• The comprehensive safety portfolio replaces the older documentation set. SORA 2.5 also ships with official templates, which is a welcome step towards harmonisation across Member States.

One practical warning on timing. SORA 2.5 became applicable across the European Union on the date ED Decision 2025/018/R was published, 29 September 2025. Individual Member States were permitted to set their own transition windows during which applications prepared under SORA 2.0 would still be accepted, and to define the maximum validity of authorisations granted in that window. Those windows differ by country and several have already closed. If you operate across borders, do not assume a single deadline. Check the position of each national aviation authority you deal with.

What SORA 2.5 means for critical infrastructure operators

This is where the detail rewards close reading, because SORA treats critical infrastructure in a very specific way.

SORA is a safety methodology. Its categories of harm are the potential for fatal injuries to third parties on the ground and fatal injuries to third parties in the air. Damage to critical infrastructure is acknowledged as a genuine and more complex condition, and it is explicitly left out of the quantified part of SORA itself. The reasoning is that different countries have differing sensitivities to this harm, so it is treated as a national specificity and is expected to be assessed in cooperation with the organisation responsible for the infrastructure, which is the party that best understands the threat to its own assets.

There are two consequences for those of you protecting or inspecting energy assets, ports, airports, rail, water, and comparable sites.

First, if your operation could affect critical infrastructure, you complete the SORA risk picture with an additional assessment of the critical infrastructure risk, run in cooperation with the infrastructure owner and folded into your concept of operations. In practice this means an earlier and more structured conversation with the asset owner, and it means your emergency response plan must explicitly account for the possibility of harming critical infrastructure, which the AMC now lists among the emergency situations an operator should plan for. The definition to keep in mind is broad: critical infrastructure means systems and assets vital to national defence, national security, economic security, and public health or safety, at both regional and national level.

Second, when you fly close to sensitive sites, the containment and adjacent-area logic in Step 8 moves to the centre of your assessment. Beyond-visual-line-of-sight inspection routes over or beside a live facility, and drone-in-a-box deployments that hold a fixed operational volume against a fixed asset, are exactly the operations where average population density in the adjacent ground area and the presence of nearby assemblies of people drive the robustness level you have to demonstrate. SORA 2.5 makes those inputs more explicit, which helps, and it also means you need to work the assessment through properly.

What SORA 2.5 means for security operators

For security operations, the same specific-category machinery applies, and there are two things worth separating clearly.

The operation you fly, whether that is perimeter surveillance, a rapid-response deployment, or persistent overwatch of a site, is assessed through SORA in the ordinary way. The site you are protecting may itself meet the definition of critical infrastructure, which brings the cooperation and adjacent-area considerations above directly into your own planning.

It is worth being precise about scope, because it is a common source of confusion. Regulation (EU) 2019/947 and SORA govern how you operate your own unmanned aircraft safely. They do not, on their own, regulate the detection of, or defence against, third-party drones. Counter-UAS sits under a different set of legal instruments, and the security threat posed by an uncooperative third-party aircraft is outside what SORA is designed to quantify. SORA does note that competent authorities may, where appropriate, consider additional categories of harm such as cybersecurity and privacy under Article 12 of the Regulation, and these sit outside the core safety calculation. For those of us building integrated detection, assessment and response capability, the takeaway is that safety compliance for your own platforms and security assurance for the wider site are two distinct workstreams that must be run in parallel and joined up deliberately.

Public safety and the state-operator question

Public safety teams frequently ask whether any of this applies to them at all, and the honest answer is: it depends on how your country has organised itself.

Under the EASA Basic Regulation, Regulation (EU) 2018/1139, aircraft used in military, customs, police, search and rescue, firefighting, border control, coastguard and similar services are treated as state aircraft and fall outside the scope of the EASA framework. Many police and emergency services therefore do not operate under Regulation (EU) 2019/947 directly.

In practice, though, very few Member States have built their state-operator frameworks from a blank sheet. It is far more common for a national authority to construct a regime for state drone operations that borrows heavily from the civil rules, taking large parts of Regulation (EU) 2019/947 and, importantly, its AMC and GM, including the SORA methodology, and adapting them to the operational reality of a state service. Where that is the case, and it is the norm, SORA 2.5 becomes the de facto benchmark even for public safety operators who are formally outside EASA scope. If your national framework references SORA, it will over time reference the current version of SORA, and the ten-step method, the seventeen OSOs, and the containment logic described above will shape how your operations are assessed regardless of the state-aircraft carve-out.

The pragmatic conclusion for public safety operators is to look at how closely your national regime tracks the civil AMC and GM, and to assume that the SORA 2.5 vocabulary is the one your authority and your partners will increasingly speak. Prepare for that language now, whatever your formal status.

What operators should do now

If you take one action from this blog, make it a re-baselining exercise. Concretely:

• Re-map your existing concepts of operations against the ten SORA 2.5 steps, and identify where the more quantitative intrinsic ground risk and the revised containment inputs change your SAIL or your evidence burden.

• Confirm the transition position with each national aviation authority you work with. The SORA 2.0 acceptance windows were set nationally and are not uniform. Do not let a live authorisation lapse on an assumption.

• Adopt the official SORA 2.5 templates and update your internal operations manual, compliance matrix and comprehensive safety portfolio to match.

• For critical-infrastructure-proximate work, open the conversation with the asset owner early, and build the separate critical infrastructure risk assessment into your concept of operations and your emergency response plan from the start.

• For security operations, keep the safety case and the security case as distinct but coordinated workstreams, and be clear internally about where the specific-category rules stop and the counter-UAS and site-security regimes begin.

• For public safety teams, check how your national state-operator framework references the civil AMC and GM, and prepare for SORA 2.5 to become the working language even if you are formally outside EASA scope.

The June 2026 Easy Access Rules confirm the direction of travel and make it official and readable in one place. SORA 2.5 is a genuine step towards a more harmonised, predictable and practical framework for the specific category, and for those of us operating in and around critical infrastructure it brings the risk conversation closer to where it always should have been, which is a shared conversation between the operator and the owner of the asset at stake.

At AirHub we build the software that carries this compliance work through the whole operational lifecycle, from concept of operations and risk assessment to live mission coordination and evidence capture.

If you would like to talk through what SORA 2.5 means for your specific operations, we are always happy to have that conversation. Book a demo and we will walk you through it.

This article is a general overview and does not constitute legal advice. For binding requirements, always refer to the official EASA publications and to the guidance issued by your national aviation authority.

June was a busy month for drone regulation. Every region moved on something that affects how operators plan, register aircraft or prove compliance, from a Danish hearing on mandatory Remote ID to a groundbreaking at the FAA's new research range in Oklahoma. If you run a fleet, a control room or a compliance function, this drone regulation update pulls together what changed and why it matters.

Europe: identification, zoning and data access move forward

Norway's Luftfartstilsynet published its 2025 flight statistics for Specific-category operators on 5 June. Operators with an operational authorisation logged 23,469 flight hours, slightly down from 25,000 the year before. The regulator points to operators shifting into the Open category after C-marking rollout, plus a few large contracts ending. Of the total, 11,502 hours came from the Specific category itself, with a clear split towards VLOS over BVLOS.

Denmark's Trafikstyrelsen opened a hearing on 29 June for a draft amended drone order. The headline change is mandatory Remote ID, or another form of remote identification, for every drone above 250 g, and for lighter drones fitted with sensors when flying in safety- or security-critical zones. The draft also adds new distance requirements around commercial ports, airfields, prisons and two royal residences, and gives police direct access to operator logbooks. If adopted, the rules take effect on 1 January 2027. The consultation closes on 21 August 2026, so there is still time for operators to respond.

Germany's LBA released a filling aid for drone application forms this month, aimed at cutting the errors that slow down authorisation processing. It sits alongside the LBA's broader effort to modernise how it handles drone applications.

In Italy, ENAC opened consultation on 24 June on a draft regulation for UAS Geographic Zones. The draft sets out how Italy will define, manage and communicate the geographic zones required under EU 2019/947, a step that matters for any operator planning missions near restricted or regulated airspace.

Oman's Civil Aviation Authority published an update moving its Advanced Air Mobility programme from strategic vision into phased implementation, with the next set of milestones for integrating AAM and UAS into Omani airspace.

Americas: infrastructure and faster access for operators

On 25 June, the US Department of Transportation and the FAA broke ground on the Vertical Take-Off and Landing Procedures and Analysis Range, known as V-PAR, at the Mike Monroney Aeronautical Center in Oklahoma City. The roughly $8.3 million facility includes a vertiport, a covered hangar and a small control centre, and will support research into wake separation, downwash and outwash, radiofrequency interference and vertiport operations for electric and hybrid VTOL aircraft.

ANAC presented Brazil's new drone regulation at DroneShow Latin America, the region's largest drone fair, walking the industry through what changes for operators under the updated framework.

Peru's Ministry of Transport and Communications launched a virtual accreditation system that cuts drone pilot accreditation from days to minutes. It is a practical example of a regulator removing friction for the operators it oversees, rather than adding it.

Asia-Pacific: roadmaps and personnel governance

Japan's MLIT and METI published an updated roadmap and version 2 of the Operational Concept for flying cars, setting out the path for AAM services beyond the Osaka-Kansai Expo.

CASA Australia released new Key Personnel guides to help RPAS operator's certificate holders identify, appoint and manage the key roles their operations require, tightening up personnel governance across the sector.

Standards bodies: building the technical foundation

Standards work rarely makes headlines, but it decides what operators will be required to prove in a few years. ASTM's Digital Information in the Supply Chain Committee proposed a new guide (WK99450) on 25 June, setting out a framework for purchasing, authenticating and tracing the materials and components used in drones. The aim is to give public safety, infrastructure, agriculture, defence and commercial operators more confidence in the supply chain behind their aircraft, an area closely linked to the kind of data security and sovereignty guarantees we detail on our trust centre.

EUROCAE published ED-341 on 5 June, giving practical guidance for showing compliance with SAIL III and IV Operational Safety Objectives under SORA. EASA recognises the document as an Acceptable Means of Compliance for the non-design-related OSOs in SORA Annex E, which makes it directly relevant to any operator working through their own SORA 2.5 compliance process.

EUROCAE also opened consultation on two further standards in June. ED-347, out for consultation from 19 June, defines the interface between the UAS operator and the Network Identification Service required under EU U-space Regulation 2021/664. ED-355, out for consultation from 26 June, sets minimum performance standards for cooperative surveillance systems supporting detect-and-avoid operations. Both consultations run into August, giving operators and manufacturers a window to feed in comments.

The Global UTM Association marked its tenth anniversary on 27 June with a look back at how the UTM ecosystem has developed since 2016, from early concept work to live U-space services and certified providers.

What this means for your operations

Taken together, June's updates point in one direction: identification, zoning and traceability are becoming standard requirements rather than optional extras. Denmark's Remote ID hearing, Italy's geographic zoning consultation and EUROCAE's network identification standard all deal with the same underlying question, which is how regulators and operators know what is flying where. At the same time, several regulators spent June removing friction rather than adding it, whether that is Peru's faster accreditation, Germany's filling aid or the FAA's investment in AAM research infrastructure.

For teams running drone programmes across public safety, infrastructure or security operations, the practical takeaway is to keep an eye on the consultation deadlines that affect your market and build for identification and traceability now, rather than treating them as a future compliance project.

AirHub tracks these developments every month so operators do not have to. If you want a platform built with the same principles of transparency and accountability that regulators are pushing towards, book a demo.

In May 2026 the centre of regulatory gravity moved to the United States and to the standardisation bodies. The FAA issued two significant drone-focused decisions: a proposed rule allowing critical infrastructure operators to petition for site-specific drone restrictions, and a set of No-Drone Zones for FIFA World Cup 2026 backed by the new DETER enforcement initiative. Transport Canada published its monthly Drone Zone newsletter, ANAC Brazil put drones and advanced air mobility on the agenda of its multi-stakeholder workshop on the future of Brazilian civil aviation, and EUROCAE advanced three pieces of standards work relevant to UAS and emerging aviation technologies. Here are the developments shaping drone operations worldwide.

EMEA

ENAC advances hydrogen drone trials at the Padova Sandbox On 7 May, ENAC reported new milestones for the Padova Sandbox project, born from a cooperation agreement between ENAC, the Veneto Region and Gruppo SAVE. A test session at Milani's Osnago site demonstrated H2C's Key Energy Builder for green-hydrogen production, storage and delivery, plus a logistics vehicle refuel. For hydrogen-powered drones used to transfer medical goods, the demonstration confirmed 5-minute refuelling, 100 km range, 4 kg payload, 340 g hydrogen consumption per flight and 55 km/h maximum speed.

NCAA Nigeria launches digital drone regulation portal On 13 May, the Nigeria Civil Aviation Authority officially launched the Drone (UAS/RPAS) Portal at the 6th Africa International Drone Technology Conference and Exhibition (Dronetecx 2026) in Lagos. NCAA Director-General Capt. Chris Najomo framed the portal as a way to curb drone proliferation, manage the rapid growth of recreational Open-category drones, provide a roadmap for the industry, and complement Nigeria's existing Civil Aviation Regulations (Nig. CARs Part 21).

Americas

FAA proposes rule to restrict drones near critical infrastructure sites On 6 May, U.S. Transportation Secretary Sean P. Duffy and the FAA unveiled a proposed rule allowing operators of certain critical infrastructure to petition for FAA-approved restrictions on drone operations over their sites. Sixteen sectors would be eligible, including energy production, transportation systems, chemical facilities, water treatment and defence industrial complexes. Restrictions would be submitted and approved via a new FAA web portal based on safety or security criteria.

FAA establishes no-drone zones for FIFA World Cup 2026 stadiums On 28 May, the FAA established temporary flight restrictions over stadiums hosting FIFA World Cup 2026 matches and related fan events, prohibiting all aircraft, including drones, within a 3 nm radius up to 3,000 ft AGL on match days. Violators face fines of up to $100,000, drone confiscation and federal criminal charges. The FAA's Drone Expedited and Targeted Enforcement Response (DETER) initiative will support enforcement.

Transport Canada publishes Drone Zone issue 7 Transport Canada released Issue 7 of its Drone Zone newsletter on 1 May, covering right-of-way rules, recurrent training (recency) requirements, drone operating-weight rules, SFOC-RPAS service standards under high seasonal application volumes, updated Transport Canada fees from 1 April, the NAV CANADA RPAS/AAM market study, the medium-RPAS operations survey closing 31 May, the Drone Zone newsletter renaming consultation, the introduction of the Canadian Space Launch Act, and the latest registration and pilot certificate statistics.

ANAC Brazil convenes the aviation sector on future challenges On 20 May, ANAC concluded its workshop "Challenges of Civil Aviation for the next 5 years," bringing together sector representatives, experts, public and private institutions, academia and civil society. Drones, eVTOLs and advanced air mobility were explicitly on the agenda alongside the regulatory and operational challenges they pose for the Brazilian system.

Aerocivil Colombia strengthens measures and advances its national drone safety campaign Aerocivil announced reinforced enforcement measures and the next phase of its national "Vuela Legal, Vuela Seguro" ("Fly Legally, Fly Safely") campaign for legal, responsible and safe UAS operation across Colombia. The campaign rests on four pillars: registration and legality, operational safety aligned with RAC 100 and international standards, education, and enforcement. Penalties for restricted-area or non-compliant operation range from 4 to over 50 minimum monthly wages depending on severity.

Asia-Pacific

CASA publishes consultation summary on supporting uncrewed aircraft research and development CASA released the summary of consultation on Discussion Paper DP 2521US, which examined how the safety regulatory framework for uncrewed aircraft operations can better support research and development, including flexibility for research, regulatory burden, and the use of sandboxes and flight-testing. The output will feed into upcoming proposed amendments to broaden R&D pathways for the Australian industry.

CASA publishes RPAS news for May 2026 CASA's monthly RPAS newsletter for May covers the latest activity on BVLOS trial pathways, the assisted-visual-line-of-sight trial, progress on above-400 ft general approvals for low-risk operations, the three Operations Over or Near People (OONP) pathways for ReOC holders, the large-RPA commercial pathway, and category-based medium-drone approvals.

CAAC China sets out its 15th Five-Year vision for the low-altitude economy On 27 May, CAAC Administrator Song Zhiyong published a programmatic article on advancing the healthy and orderly development of the low-altitude economy, designated a national pillar industry in the 2026 Government Work Report. The article sets 15th Five-Year goals including 100% UAV real-name registration, more than 1 million certified operators, and over 80 million civil low-altitude flight hours per year. Current statistics show 3.8 million registered drones, more than 430,000 operators, 45.3 million flight hours in 2025 (up 70% year on year), 1,200 mid- to large-UAV manufacturers, over 40,000 operating companies, and 300,000 agricultural UAVs serving 460 million mu of farmland.

Japan MLIT hosts the first JARUS working group meeting on Japanese soil From 18 to 22 May, MLIT hosted the JARUS (Joint Authorities for Rulemaking on Unmanned Systems) Working Group meeting at X-NIHONBASHI in Tokyo, the first such meeting held in Japan since JARUS was founded in 2007, with record participation of around 60 delegates from 25 countries. Discussions focused on the revision of SORA, including quantitative methods for assessing and mitigating air risk. Japan presented its national UAS framework and SORA-derived risk-assessment case studies, reinforcing its active role in international UAS harmonisation.

Standardisation bodies

EUROCAE opens consultation on ED-286A for counter-UAS systems On 11 May, EUROCAE WG-115 opened public consultation on the draft ED-286A "OSED for Counter UAS Systems in Controlled Airspace," updating the 2021 ED-286 with current scenarios, use cases and risk-assessment guidelines for C-UAS deployment around airports and ANSPs. Comments are open until 25 June 2026.

EUROCAE opens call for experts on WG-135 On 12 May, EUROCAE published a call for experts for the newly launched Working Group 135 (CRL framework for emerging aviation technologies), alongside calls for WG-126, WG-67 and WG-28. WG-135 will advance the Common Reference List framework relevant to drone and AAM integration.

EUROCAE publishes its May 2026 NEWSblog On 28 May, EUROCAE released its monthly NEWSblog summarising May standards, working group activity, partnerships and event highlights, including the WG-135 launch, the digital standards initiative, virtual ATM work (WG-122), and EUROCAE's participation in Airspace World 2026 in Lisbon (26 to 28 May).

EUROCAE publishes ED-300A on AFHA and PASA guidance for VTOL On 29 May, EUROCAE published ED-300A "Guidance on conducting an AFHA and PASA for a VTOL using a generic example," supporting consistent functional hazard and preliminary aircraft safety assessments for VTOL aircraft, a key reference for eVTOL and advanced air mobility certification work.

ASTM releases a UAS special technical publication ASTM made available a UAS-related Special Technical Publication paper from its STP1633 series via its store, supporting ongoing technical-committee work on unmanned aircraft systems standards.

May's developments point to a clear shift towards enforcement, infrastructure protection and international coordination. From the FAA's proposed critical infrastructure drone restrictions and the FIFA World Cup No-Drone Zones backed by the new DETER initiative, to MLIT Japan's first hosting of the JARUS Working Group on SORA revision, regulators are at once hardening the operating envelope and harmonising the global rule set. In parallel, ENAC's hydrogen drone trials at the Padova Sandbox, CAAC China's 15th Five-Year low-altitude economy vision, and CASA's R&D consultation point to the next wave of scaled, sustainable operations.

The AirHub consultancy team will keep monitoring these developments as the industry moves towards broader integration and more advanced use cases. If there is a regulatory update we should include next month, let us know through our consultancy page.

Want to understand how these regulatory changes affect your operations? Book a demo with one of our experts.

A modern police force is buying a workflow. The drone is one part of it.

That distinction matters more than it sounds. A drone on its own is a sensor on a stick. A drone programme is a set of decisions stitched together. A call comes in, an aircraft launches, a feed reaches the operator, a unit on the ground acts on it, the airspace stays safe, the evidence is preserved, the fleet stays ready. The drone is one component of that chain. The platform that holds the chain together is the system the chief is actually procuring.

What follows is how public safety drone operations should run, end to end, in 2026. It is the model AirHub is built around. Dubai Police already runs it as a live, city-wide Drone as First Responder network, and it is the direction public safety teams across Europe and the Middle East are moving towards.

The scenario, in one paragraph

An emergency call reports an armed individual at a transit station. Computer-Aided Dispatch (CAD) creates the incident. AirHub receives the ticket, identifies the nearest rooftop dock, launches a docked aircraft autonomously, and streams the feed back to the duty operator within seconds. The AI layer flags a person matching the description. The counter-UAS layer confirms no hostile drones in the area. The feed appears in the control room alongside the station's CCTV, and is pushed to the responding units on their mobile devices. Every action, every frame, every command is logged. The aircraft returns to dock, recharges, and is ready before the next incident. A pilot supervises throughout, without driving to the scene.

That is the loop. Here is what happens underneath.

Stage 1: CAD brings the incident into the workflow

The trigger is always a dispatch system. Computer-Aided Dispatch, whether Hexagon, Frequentis or a regional platform, is where a 112 or 911 call becomes a structured incident: location, type, priority, units assigned.

For a drone programme to be operationally relevant, the dispatch system has to reach the drone platform automatically. A manual workflow, where a dispatcher sees a call, picks up a phone and asks for a drone, adds minutes the operation does not have. In Drone-as-First-Responder deployments, the target response time is measured in tens of seconds. Dubai Police operates against a sub-ninety-second target across the city, and that target collapses without CAD integration.

AirHub connects to dispatch systems through its open API, so an incident created in a CAD platform can task a drone automatically. The incident type and location determine which dock is nearest, what altitude profile to fly, what camera angle to default to, and which sensors to enable on the way.

The principle here is straightforward. The dispatcher keeps working as a dispatcher. The drone becomes another unit they can task.

Stage 2: the dock takes the call

The next stage is the launch. In a serious programme, this happens without anyone going to the rooftop.

A dock, whether a DJI Dock, a Skydio Dock or another drone-in-a-box system AirHub orchestrates, sits on a precinct roof, a tower or a perimeter mast. When the CAD-triggered tasking arrives, the dock opens, the aircraft takes off, climbs to the configured altitude and proceeds to the incident. The duty operator sees the launch confirmation, the live feed and the telemetry within seconds of the call being created.

The aircraft is not flying blind. AirHub has already checked the airspace, validated the geofence, applied the relevant operational area and contingency volume, and selected a flight path that respects the ground risk buffer. The pilot, formally the remote pilot in command, supervises the flight. That is what the regulatory framework intends, and it is what lets a programme scale beyond the limits of manual piloting.

For programmes that mix docked and field-deployed assets, the same workflow runs in parallel. A patrol unit with a controller in the car can be tasked through AirHub the same way a dock is. The dispatcher does not need to know which one is closer. The platform does.

Stage 3: AI image recognition makes the feed actionable

A live video feed is useful. A live feed that flags relevant objects automatically is decisive.

AI at the aircraft and platform layer can detect and classify objects such as people, vehicles and anomalies, with further mission-specific modules. The aircraft picks up the visual scene and the AI layer turns it into structured events. A person matching a description becomes an alert with a timestamp, a location and a frame, instead of staying buried in twenty minutes of orbiting footage.

For the operator, this turns passive watching into active searching. A duty officer can supervise several live feeds at once when the AI is doing the looking.

For investigators afterwards, the AI layer makes the footage searchable. A query like "show me every vehicle that passed the south entrance between 22:00 and 23:00" becomes a short task rather than a long manual review.

The important point is that AI is a support layer. The platform surfaces information and the human makes the decision. AirHub is designed around that boundary deliberately, and it is part of how we build programmes that hold up to scrutiny from prosecutors, ombudsmen and procurement auditors.

Stage 4: counter-UAS detect and avoid keeps the airspace safe

Once a public safety drone is airborne, a second question matters just as much. What else is in the airspace around it?

This is where the counter-UAS layer enters the workflow. Detection sensors, including radar, RF, acoustic, Remote ID receivers and visual systems, feed the same operational map the drone is flying on. Cooperative manned traffic appears via ADS-B, gliders and light aviation via FLARM, and non-cooperative drones via the counter-UAS sensors.

For the operator running the mission, this gives two things. The first is deconfliction. If a police helicopter is inbound, the drone descends or repositions before either pilot has to make a radio call. The second is threat awareness. An unidentified drone approaching the same incident becomes a track on the map, with a classification, a heading and a confidence score.

In the AirHub ecosystem this is the SecHub layer, a hardware-agnostic sensor-fusion and counter-UAS engine that brings detection, assessment and response into the same operational picture as the friendly drone. For public safety, that combination is increasingly essential. A programme that ignores the counter-UAS dimension will eventually fly into a problem it could not see coming.

Stage 5: VMS integration gets the feed to the people who need it

The control room running the incident is rarely a drone control room. It is a security or command-and-control room running on a Video Management System (VMS) such as Genetec Security Center, Milestone XProtect or Hexagon HxGN OnCall. The operator there has spent years learning that VMS, so asking them to leave it for a separate drone view is the wrong design.

The right architecture puts the drone feed inside the VMS as a native video source, alongside the fixed CCTV, the bodycams, the ANPR cameras and any other tile the operator already works with. AirHub streams over open protocols such as RTSP and RTMP, so a VMS can take the feed as a standard video source without a bespoke build for every site.

The effect on the operator is significant. The drone feed sits next to the perimeter CCTV. The counter-UAS detection sits as an alert layer. The bodycam from the responding officer sits in the next tile. One operator, one toolset, one operational picture.

This is also where SecHub closes the loop. The same VMS that shows the drone feed shows the counter-UAS detections, so the operator who sees the threat is the operator who can act on it.

Stage 6: video sharing makes the field part of the operation

Not everyone who needs the feed is in the control room. The patrol unit en route, the supervisor in the command vehicle, the tactical team on the perimeter, the prosecutor on call, the partner agency on a joint operation. All of them may need access, with different permission levels, for different durations.

A modern drone platform treats video sharing as a first-class function. A live link, a time-limited token, a permission set that determines who can see what, and a mobile-friendly interface that works on the device the field user already carries. AirHub lets the operator in the control room push the feed to the right people in seconds, without copying files, without sending screen recordings, and without losing track of who saw what.

The principle is the same as elsewhere in the workflow. The feed follows the operation, to the people who need it, for as long as they need it.

Stage 7: logging the evidence chain and audit trail

Everything that happens in the workflow is logged. It is captured as a structural property of the platform, built in from the start.

Flight logs, pilot identification, airspace clearances, geofence applications, contingency volume definitions, ground risk buffer parameters, AI events, counter-UAS detections, video segments, who watched which feed at what time, and which patrol unit had access for how long. All of it is captured, timestamped and retrievable.

This matters for three audiences. The first is the prosecutor, because footage from a drone is only as useful as the chain of custody around it. The second is the regulator, because every BVLOS approval, population overflight and special authorisation comes with the obligation to demonstrate that the operation ran as approved. The third is the chief, because an annual review of the programme should take a query rather than six people and a month of forensic effort.

AirHub treats logs as the institutional memory of the programme. They let an operation stand up to scrutiny.

Stage 8: fleet management keeps the docks ready for the next call

The last stage determines whether there is a next workflow.

A docked drone is only useful if it is ready when the next call comes in. That means batteries charged and within cycle limits, propellers within service life, sensors calibrated, firmware current, geofences valid, weather within the operating envelope, connectivity verified, pilots in the supervision roster and current on their requirements, and maintenance scheduled before it falls overdue.

Across a fleet of ten docks, this is manageable by hand. Across a fleet of a hundred, it decides whether the programme can scale.

AirHub treats fleet management as a first-class function. Every dock, aircraft, battery, controller and pilot has a state, visible to the programme manager in one place, with proactive flags before something becomes a problem. Maintenance windows are scheduled around expected demand. Pilot rosters are aligned with dock readiness. Battery cycles are tracked against manufacturer envelopes.

The workflow is the product

When people discuss public safety drone programmes, it is tempting to focus on the aircraft. The aircraft is the visible part. It is also the smallest part of the system the operator is actually buying.

What a serious public safety force is procuring is a platform that holds the whole chain together, from a citizen's call to a closed case file. CAD integration at the front. Autonomous launch in the middle. AI, counter-UAS, VMS integration, sharing, logging and fleet management woven through. That platform stays sovereign and on-premise where the operator requires it, and hardware-agnostic across DJI, Skydio, Parrot and the open protocol world.

That is what AirHub, SecHub and our partner ecosystem are built to deliver. The drone is part of the picture. The picture is the product.

Curious how AirHub runs this workflow end to end for public safety teams? Book a demo with one of our experts.