Resources

Resources

Browse our guides, industry news, and success stories to optimize your drone operations.

Browse our guides, industry news, and success stories to optimize your drone operations.

Latest helpcenter

Latest helpcenter

How to: Create a Pilot Mission

Plan safe and compliant manual drone flights.

How to: Add Drones to Your Workspace

Adding drones to your library is helpful for multiple reasons. It’ll give you a clear overview of which drones are present within the organization, provide clarity on drones due for maintenance, and enable you to track where each drone has flown, among other benefits. On this page, you will learn how to add new drones and how to edit existing ones.

How to: Report a Drone Incident in AirHub

Reporting incidents, accidents, and hazards is a cornerstone of a strong Safety Management System (SMS). It allows your organization to learn from events, identify trends, and implement corrective actions to prevent future occurrences. Consistent and thorough reporting helps improve operational procedures, enhances safety for your team and the public, and ensures regulatory compliance. AirHub provides two convenient ways to report an incident.

How to: Set Up and Manage a Maintenance Program

Proactive maintenance is critical for ensuring the safety, reliability, and longevity of your drone fleet. The AirHub Maintenance feature provides a comprehensive system to create scheduled maintenance programs, track asset usage against set intervals, and maintain a detailed service history for every asset. This helps you move from reactive repairs to a proactive maintenance culture, reducing downtime and ensuring regulatory compliance.

How to: Edit Maintenance Program

Over time, you may need to update your maintenance programs to reflect changes in your fleet or procedures. Editing a program allows you to modify its details, change the trigger conditions, or, most commonly, add new assets to an existing maintenance schedule. This ensures your maintenance tracking remains accurate as your fleet grows and evolves.

How to: Archiving Maintenance

If a maintenance program is no longer relevant to your operations, for example, if you have retired all assets the program applies to, you can archive it. Archiving removes the program from your active list, keeping your maintenance dashboard clean and focused on current requirements. All historical data associated with the program is preserved.

How to: Read the Weather Advisories

Weather is one of the most important factors influencing the safety and success of any drone operation. A thorough pre-flight weather check is essential to ensure your drone can perform within its operational limits, maintain stability, and comply with aviation regulations. The AirHub weather tool provides detailed, location-specific forecasts to help you make informed go/no-go decisions.

How to: Flyzones

Learn how to create and manage flyzones in AirHub to define safe and compliant flight areas for your drone operations.

How to: Manage Your Drones

Adding drones to your library is helpful for multiple reasons. It’ll give you a clear overview of which drones are present within the organization, provide clarity on drones due for maintenance, and enable you to track where each drone has flown, among other benefits. On this page, you will learn how to add new drones and how to edit existing ones.

News

News

Police officers in a control room running public safety drone operations on live screens

Content

One continuous workflow: how modern public safety drone operations run from CAD to dock fleet

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.

A vast empty desert valley of dry hills and bare mountains, a visual for the Valley of Death

Content

Bridging the Valley of Death: public-private partnership in security technology

Promising technology that never reaches the operation. Innovative solutions that stay stuck in pilots for years. Public-private partnerships that stall on bureaucracy, competing interests or a lack of mutual understanding.

In the security sector this phenomenon has a name: the Valley of Death. It is the gap between technological innovation and real operational deployment. It is also one of the most stubborn challenges that governments and technology companies both face.

Two worlds, one goal

Public safety organisations and private technology companies share the same goal at heart: keeping people safer. The way they operate, make decisions and weigh risk differs considerably.

The public sector works from compliance, risk management and long decision-making processes. Tenders, budget cycles and political interests all play a part. Change is slow, and often for good reason, because mistakes in the security sector can have serious consequences.

The private sector runs on a very different dynamic. Speed, innovation and decisiveness are the drivers. Products keep developing, markets shift quickly and the pressure to show results is high.

Joost Tuinman, strategic advisor at Gardener Consultancy and a former officer with the Netherlands Commando Corps and SOCOM, knows both worlds from the inside. "Public-private collaboration is essential, and in practice it is often complex, slow and bureaucratic. The public sector operates from compliance and risk management, while the private sector brings speed, innovation and drive. Those two worlds have to find each other, and that rarely happens on its own."

What causes the Valley of Death

The gap rarely comes from bad intentions. It usually grows from a combination of structural factors that make collaboration harder:

  • Different time horizons. A technology company works in quarters. A government organisation works in budget years and policy periods. That mismatch makes it hard to build momentum.

  • Limited mutual understanding. Technology companies do not always grasp how government organisations work, which regulations apply or how decisions get made. The other way round, government organisations sometimes find it hard to translate technical possibilities into operational needs.

  • Unclear goals. Collaborations that start from enthusiasm without clear goals, governance and agreements run aground sooner or later.

  • Risk aversion. In the public sector the pressure to avoid mistakes is high. That can lead to caution about adopting new technology, even when the potential value is clear.

A visual representation of how you reach the "Valley of Death", created by Kevin Landtroop

How to make a public-private partnership work

There is no single fix for the Valley of Death. Several approaches do have a proven track record.

  • Start with concrete pilots and clear goals. A collaboration that begins with a defined use case, measurable objectives and a clear timeline stands a far better chance than a broad letter of intent.

  • Invest in mutual understanding. Technology companies that take the time to understand the operational context of their public partners build trust. That trust is the basis for lasting collaboration.

  • Get the right people round the table. Collaboration often succeeds or fails on the people who lead it. People who know and understand both worlds are invaluable as bridge-builders.

  • Make governance explicit. Who decides what? How are disputes resolved? What does each side expect? Agreements like these sound formal, and they prevent a lot of misunderstanding in practice.

Tuinman sums it up neatly: "It comes down to making collaboration concrete, with clear goals, governance and mutual understanding. That is what lets you bring technology to the operation far faster and more effectively."

AirHub's role in public-private partnership

For AirHub, public-private partnership is the daily reality of working with security organisations, governments and defence at home and abroad.

Stephan van Vuren, CEO of AirHub: "We build a platform that genuinely helps operational teams. To land that in the right environments, you need people who know those environments from the inside. That is exactly why the collaboration with Joost is so valuable to us."

The collaboration with Gardener Consultancy puts that conviction into practice. By bringing strategic insight and operational knowledge together with technological innovation, AirHub closes the distance between what is possible and what actually gets deployed.

Looking ahead

The pressure on security organisations is rising. Geopolitical tension, climate-related crises and the rapid spread of new technology make the operational environment more complex. At the same time, the availability of effective technology that can help organisations keeps growing.

The organisations that manage to bridge the Valley of Death are the ones that invest early in the right partnerships, the right people and the right platforms. They build that as a foundation for what comes next, well before any crisis demands it.

Curious how AirHub works with security and defence organisations? Book a demo with one of our experts.

Regulatory updates and Industry news

Content

Global drone regulatory update: May 2026

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.

Police officers in a control room running public safety drone operations on live screens

Content

One continuous workflow: how modern public safety drone operations run from CAD to dock fleet

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.

A vast empty desert valley of dry hills and bare mountains, a visual for the Valley of Death

Content

Bridging the Valley of Death: public-private partnership in security technology

Promising technology that never reaches the operation. Innovative solutions that stay stuck in pilots for years. Public-private partnerships that stall on bureaucracy, competing interests or a lack of mutual understanding.

In the security sector this phenomenon has a name: the Valley of Death. It is the gap between technological innovation and real operational deployment. It is also one of the most stubborn challenges that governments and technology companies both face.

Two worlds, one goal

Public safety organisations and private technology companies share the same goal at heart: keeping people safer. The way they operate, make decisions and weigh risk differs considerably.

The public sector works from compliance, risk management and long decision-making processes. Tenders, budget cycles and political interests all play a part. Change is slow, and often for good reason, because mistakes in the security sector can have serious consequences.

The private sector runs on a very different dynamic. Speed, innovation and decisiveness are the drivers. Products keep developing, markets shift quickly and the pressure to show results is high.

Joost Tuinman, strategic advisor at Gardener Consultancy and a former officer with the Netherlands Commando Corps and SOCOM, knows both worlds from the inside. "Public-private collaboration is essential, and in practice it is often complex, slow and bureaucratic. The public sector operates from compliance and risk management, while the private sector brings speed, innovation and drive. Those two worlds have to find each other, and that rarely happens on its own."

What causes the Valley of Death

The gap rarely comes from bad intentions. It usually grows from a combination of structural factors that make collaboration harder:

  • Different time horizons. A technology company works in quarters. A government organisation works in budget years and policy periods. That mismatch makes it hard to build momentum.

  • Limited mutual understanding. Technology companies do not always grasp how government organisations work, which regulations apply or how decisions get made. The other way round, government organisations sometimes find it hard to translate technical possibilities into operational needs.

  • Unclear goals. Collaborations that start from enthusiasm without clear goals, governance and agreements run aground sooner or later.

  • Risk aversion. In the public sector the pressure to avoid mistakes is high. That can lead to caution about adopting new technology, even when the potential value is clear.

A visual representation of how you reach the "Valley of Death", created by Kevin Landtroop

How to make a public-private partnership work

There is no single fix for the Valley of Death. Several approaches do have a proven track record.

  • Start with concrete pilots and clear goals. A collaboration that begins with a defined use case, measurable objectives and a clear timeline stands a far better chance than a broad letter of intent.

  • Invest in mutual understanding. Technology companies that take the time to understand the operational context of their public partners build trust. That trust is the basis for lasting collaboration.

  • Get the right people round the table. Collaboration often succeeds or fails on the people who lead it. People who know and understand both worlds are invaluable as bridge-builders.

  • Make governance explicit. Who decides what? How are disputes resolved? What does each side expect? Agreements like these sound formal, and they prevent a lot of misunderstanding in practice.

Tuinman sums it up neatly: "It comes down to making collaboration concrete, with clear goals, governance and mutual understanding. That is what lets you bring technology to the operation far faster and more effectively."

AirHub's role in public-private partnership

For AirHub, public-private partnership is the daily reality of working with security organisations, governments and defence at home and abroad.

Stephan van Vuren, CEO of AirHub: "We build a platform that genuinely helps operational teams. To land that in the right environments, you need people who know those environments from the inside. That is exactly why the collaboration with Joost is so valuable to us."

The collaboration with Gardener Consultancy puts that conviction into practice. By bringing strategic insight and operational knowledge together with technological innovation, AirHub closes the distance between what is possible and what actually gets deployed.

Looking ahead

The pressure on security organisations is rising. Geopolitical tension, climate-related crises and the rapid spread of new technology make the operational environment more complex. At the same time, the availability of effective technology that can help organisations keeps growing.

The organisations that manage to bridge the Valley of Death are the ones that invest early in the right partnerships, the right people and the right platforms. They build that as a foundation for what comes next, well before any crisis demands it.

Curious how AirHub works with security and defence organisations? Book a demo with one of our experts.

Police officers in a control room running public safety drone operations on live screens

Content

One continuous workflow: how modern public safety drone operations run from CAD to dock fleet

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.

What's new

What's new

AirHub's Cockpit view from their Drone Operations Center

Content

Cockpit & Mission Editor Improvements

We have overhauled the Ground Station experience to give you better situational awareness during flight and more precision during planning.

Mission Editor: POI Heading

Focus on what matters. You can now set the Heading Mode to POI (Point of Interest) within the Mission Editor. simply select a specific coordinate, and the drone will automatically rotate to face that target while flying its waypoints, perfect for inspections and cinematic shots.

Cockpit Improvements
  • New Status Widgets: Instantly monitor DroneMode and Control State with our cleaner, data-rich widgets.

  • Sound Cues: You no longer need to stare at the screen to know what’s happening. We’ve added audio alerts to confirm critical events, allowing you to keep your eyes on the aircraft.

  • Refined Actions: Critical inputs are faster and more reliable. We have improved the Take Picture, Video Recording, Obtain Control, and Pause Mission buttons.

  • Thermal Zoom: Detail meets data. Thermal view is now fully available while in Zoom mode. This allows you to inspect heat signatures with precision without sacrificing the optical advantage of the zoom lens.

  • Better Messaging: We’ve updated aircraft messages to be clear and actionable, removing ambiguity.

AirHub's Thermal Pallette functionality from their Drone Operations Center

Content

Thermal Palette Control on the DJI Dock

In public safety operations, every second counts and clear information can be the difference between success and failure. We are rolling out a software update for the DJI Dock that improves its thermal imaging capabilities, providing you with a more powerful tool for search and rescue, firefighting, and incident command.

This update gives you direct control over how the thermal camera visualises heat, allowing your team to adapt to rapidly changing tactical situations.

What is the New Feature?

With the latest update, operators can now switch between different thermal color palettes in real-time. Instead of a single, default thermal view, your team can instantly select the visualisation that best suits the mission environment and objective.

Why This Matters for First Responder Missions

This enhanced control provides tangible advantages when deploying the DJI Dock for emergency operations:

  • Faster Subject Detection in Search & Rescue (SAR): Finding a missing person is a race against time. The ability to switch palettes allows an operator to find the best color contrast to make a human heat signature stand out against challenging backgrounds, whether it's dense foliage at night, a rubble field, or open water. This can significantly reduce search times.

  • Pinpointing Hotspots and Dangers in Fires: For fire departments, this feature is invaluable. One palette might be ideal for cutting through smoke to identify the seat of a fire, while another can be used during overhaul to find hidden hotspots in walls and ceilings, preventing re-ignition. It also helps in identifying hazardous material tanks that may be overheating.

  • Improved Situational Awareness for Incident Command: Clear intelligence is key to command decisions. By adjusting the thermal view, you can provide commanders with the most actionable imagery, whether it's tracking a suspect's heat trail, monitoring team locations, or identifying areas that are unsafe for personnel to enter.

  • Reduced Operator Strain in High-Stress Events: During a prolonged or intense incident, staring at a single thermal display can cause fatigue. Allowing the operator to select a palette that is clearer or more intuitive to them reduces cognitive load, helping them stay focused and effective for longer.

AirHub's Live Operations view with the newly added resizeable panels

Content

Take Control of Your Live Operation: Introducing Resizable Panels in LiveOps

During a live operation, your informational needs can change in an instant. One moment, the primary video feed is your main focus; the next, you're deep in the chat log coordinating ground teams. To support this dynamic workflow, we’re excited to introduce a simple but powerful update to the LiveOps interface: horizontally resizable panels.

What is the New Feature?

You now have the ability to drag and slide the dividers between the main panels in your LiveOps view. This allows you to dynamically change the horizontal size of the:

  • Map Panel

  • Livestream Panel

  • Chat Panel

  • Shareable Links Panel

The Purpose: A Live Operations View That Adapts to Your Mission

This feature is all about giving you control and allowing you to prioritise your focus based on the task at hand. Here’s why this matters:

  • Focus on What's Critical: If you are actively piloting a drone or monitoring a critical video feed, you can now expand the Livestream panel to get a larger, more detailed view. You can shrink the chat or links panels to minimise distractions and dedicate more screen real-estate to the live video.

  • Enhance Situational Awareness: During a wide-area search or when tracking multiple assets, the Map panel is your most important tool. You can now enlarge it to see more of the operational area, track assets more clearly, and review map layers without excessive zooming or panning.

  • Improve Team Coordination: When an incident requires heavy communication and coordination, a narrow chat window can be frustrating. You can now widen the Chat panel to see more of the conversation history at a glance, reducing the need to scroll and helping you stay on top of rapid-fire messages and updates.

  • Streamline Information Sharing: If your primary role is managing information for external stakeholders, you can expand the Shareable Links panel to get a clear, organised view of all active links, manage their settings, and share them more efficiently.

This user interface improvement is designed to make the LiveOps platform more flexible and responsive. Your workspace should work for you, not the other way around. With resizable panels, you can instantly configure your view to match the exact needs of your operation.


AirHub's Cockpit view from their Drone Operations Center

Content

Cockpit & Mission Editor Improvements

We have overhauled the Ground Station experience to give you better situational awareness during flight and more precision during planning.

Mission Editor: POI Heading

Focus on what matters. You can now set the Heading Mode to POI (Point of Interest) within the Mission Editor. simply select a specific coordinate, and the drone will automatically rotate to face that target while flying its waypoints, perfect for inspections and cinematic shots.

Cockpit Improvements
  • New Status Widgets: Instantly monitor DroneMode and Control State with our cleaner, data-rich widgets.

  • Sound Cues: You no longer need to stare at the screen to know what’s happening. We’ve added audio alerts to confirm critical events, allowing you to keep your eyes on the aircraft.

  • Refined Actions: Critical inputs are faster and more reliable. We have improved the Take Picture, Video Recording, Obtain Control, and Pause Mission buttons.

  • Thermal Zoom: Detail meets data. Thermal view is now fully available while in Zoom mode. This allows you to inspect heat signatures with precision without sacrificing the optical advantage of the zoom lens.

  • Better Messaging: We’ve updated aircraft messages to be clear and actionable, removing ambiguity.

AirHub's Thermal Pallette functionality from their Drone Operations Center

Content

Thermal Palette Control on the DJI Dock

In public safety operations, every second counts and clear information can be the difference between success and failure. We are rolling out a software update for the DJI Dock that improves its thermal imaging capabilities, providing you with a more powerful tool for search and rescue, firefighting, and incident command.

This update gives you direct control over how the thermal camera visualises heat, allowing your team to adapt to rapidly changing tactical situations.

What is the New Feature?

With the latest update, operators can now switch between different thermal color palettes in real-time. Instead of a single, default thermal view, your team can instantly select the visualisation that best suits the mission environment and objective.

Why This Matters for First Responder Missions

This enhanced control provides tangible advantages when deploying the DJI Dock for emergency operations:

  • Faster Subject Detection in Search & Rescue (SAR): Finding a missing person is a race against time. The ability to switch palettes allows an operator to find the best color contrast to make a human heat signature stand out against challenging backgrounds, whether it's dense foliage at night, a rubble field, or open water. This can significantly reduce search times.

  • Pinpointing Hotspots and Dangers in Fires: For fire departments, this feature is invaluable. One palette might be ideal for cutting through smoke to identify the seat of a fire, while another can be used during overhaul to find hidden hotspots in walls and ceilings, preventing re-ignition. It also helps in identifying hazardous material tanks that may be overheating.

  • Improved Situational Awareness for Incident Command: Clear intelligence is key to command decisions. By adjusting the thermal view, you can provide commanders with the most actionable imagery, whether it's tracking a suspect's heat trail, monitoring team locations, or identifying areas that are unsafe for personnel to enter.

  • Reduced Operator Strain in High-Stress Events: During a prolonged or intense incident, staring at a single thermal display can cause fatigue. Allowing the operator to select a palette that is clearer or more intuitive to them reduces cognitive load, helping them stay focused and effective for longer.

Success stories

Success stories