Resources

Most public safety organisations looking at Drone as First Responder have stopped asking whether it works. Enough forces are flying to settle that. The question that decides whether a programme happens is narrower and less exciting: can you get it funded, and can you get it funded before the budget year closes.

This is a guide to building that case. It covers what you are actually buying, which costs get missed, what to measure when cost per flight tells you nothing useful, and how the authorisation timeline shapes the calendar you are working to.

What you are actually buying

A DFR programme has three cost blocks, and organisations tend to budget the first one well and the other two badly.

Aircraft and docks. The visible part. Docks are the item that turns a drone team into a DFR programme, because they remove the drive to the scene. The number you need follows from your coverage target rather than from your fleet size, which is a point most business cases get the wrong way round.

Software, integration and connectivity. The layer that turns a dock and a drone into a response capability: the launch decision, the route, the live picture in the control room, the link into computer-aided dispatch (CAD) and into your video management system (VMS), and the record afterwards. This is also where the recurring cost sits, so it belongs in the operating budget rather than the capital one.

People and authorisation. Remote pilots, their training and currency, the person in the control room, and the work of getting an operational authorisation. The last of these is consistently underestimated and it is often the item that sets your start date.

The costs that get missed

Five things turn up late in almost every DFR business case.

1. The authorisation work itself. Flights to an incident go beyond the pilot's visual line of sight, which puts them in the specific category and means a risk assessment and an operational authorisation from your national aviation authority. That is preparation time, sometimes external support, and a queue at the authority.

2. Currency and training. Pilots need recurrent training, and a control room operator running several aircraft is a distinct role from a field pilot. Budget the hours.

3. Connectivity at the dock. A dock on a rooftop needs power and a reliable connection. Site surveys and civil works have a habit of appearing after the drone quote is signed.

4. Depreciation and replacement. An aircraft launching several times a day reaches its service life faster than a standard write-off schedule assumes, so set the depreciation period on expected flight hours. Batteries are rated in charge cycles, which makes them a consumable in the operating budget rather than part of the capital purchase.

5. Insurance and legal review. Both are straightforward and both take longer than expected when it is the first time.

What to measure

Cost per flight is the wrong metric and it will sink your case, because a DFR flight is cheap and the number says nothing about value. Four measures tend to hold up better with a finance committee.

Time to first visual. The interval between a call coming in and someone seeing the scene. This is the number a DFR programme moves, and it is measurable from day one.

Calls resolved without a unit. Where the drone arrives first, some incidents need no ground response at all. US forces report this as a share of the calls their drone attended, and Police Chief Magazine puts it at around a quarter across established programmes, with individual forces reporting both less and considerably more. Measure your own once you are running, and check first whether your dispatch policy allows a call to be closed on a drone observation.

Better-informed arrival. Harder to quantify and often the strongest argument in the room. Officers who know what they are walking into make different decisions, and so do commanders deciding what to send.

Evidence and accountability. Automated flights produce a complete record: who authorised, who was in command, what was seen. That has value in court and in oversight, and it is worth naming in the case because it offsets a risk that your legal colleagues will otherwise raise as an objection.

What this looks like in a European force

Belgian Police zones use drones for real-time situational awareness during live incidents, and their experience is a useful reference for anyone building a case, because it speaks to outcomes rather than to technology.

Chief Inspector Bram Schoors puts the outcome plainly: “We have already been able to find two missing persons alive and well thanks to the deployment of the drone via the platform”

First inspector Kristof van den Broeck describes why running more than one aircraft changes the picture available to commanders: “The deployment of multiple drones is a major advantage. It allows us to use one drone to zoom in on the situation and relay coordinates, while the other provides a broad overview of the scene”

There is more in their case study, which is worth attaching to a business case as an annex.

Procurement criteria worth writing in early

Two things belong in your requirements rather than in a later discussion.

Where the data lives. For a police force, the location of video and mission data and the question of who can reach it is rarely a technical footnote. AirHub is a European company, is ISO 27001 and ISO 9001 certified, operates in line with GDPR and European data protection requirements, and can be deployed on-premise or in a private cloud where an organisation needs full control over sensitive operational data. Writing that into the requirement early saves a procurement round later.

Hardware independence. A platform tied to one manufacturer ties your fleet decisions to that manufacturer for the life of the programme. Specifying hardware agnosticism keeps the choice yours.

The calendar problem

Here is the practical constraint on a year-end business case. Your national authority sets your start date, and processing times in several member states are long. An organisation that secures budget in December and opens the authorisation conversation in January is not flying in the first quarter.

So the sequence that works is to start the authority conversation while the budget case is still being written. It costs nothing, it produces a realistic timeline to put in the case, and it turns an optimistic slide into a defensible one.

Our public safety page sets out how the platform supports each stage, and our regulatory consultancy team works with operators on the authorisation route itself.

An emergency call comes in. The location is clear. What is happening there is still uncertain.

Responding officers need to know what they are approaching. Fire crews need to understand access and hazards. The control room needs to decide which resources to send. Each team has questions, and the answers are changing by the second.

AirHub Drone as First Responder (DFR) software closes that information gap. It connects drone deployment, live video and operational coordination, so responders work from a shared view of an unfolding incident. The Drone Operations Centre is where that comes together: a live environment in which teams see, interpret and share operational information. That is a common operating picture, usually shortened to COP.

How the DFR workflow starts, from emergency call to eyes on scene

The workflow starts with Computer Aided Dispatch (CAD). With the integration configured, an incoming incident triggers AirHub's DFR workflow directly from the dispatch system.

AirHub selects the best-positioned drone dock and calculates a route around weather, airspace and no-fly zones. The drone travels to the incident under operator supervision and brings an aerial perspective into the control room while responding units are still on their way.

That early view gives commanders time to assess the situation and adjust the response before teams arrive, and AirHub records the flight information for later reporting and review.

How DFR software builds the common operating picture

A useful COP connects what teams are seeing with where it is happening.

AirHub's Custom Sessions combine multiple live feeds, maps and data sources in a persistent, shared dashboard. Connected devices appear with their video and their real-time location, so operators can see the relationship between a camera view and the wider incident.

The picture reaches people beyond the control room as well. Sessions can be shared with internal teams and external stakeholders, with controls including link expiry, IP restrictions and map visibility.

Consider a developing incident with several agencies involved. Commanders reference the same live scene, identify which entrance they mean, point colleagues towards the relevant view and follow developments together. The COP becomes the practical basis for coordination, a shared reference that holds as the situation changes.

Connecting the Real Time Crime Center (RTCC)

For a Real Time Crime Center, the room where an agency pulls its camera and data feeds together, aerial video adds a mobile perspective to fixed coverage.

AirHub brings drone footage into a Video Management System (VMS) through streaming protocols including RTSP and RTMP, so a compatible control-room environment displays aerial footage alongside its other video sources.

Imagine a fixed camera showing the front of a building while the drone covers the surrounding streets. Together those perspectives show movement, access and the broader scene, and operators can pass what matters to responding units.

Making aerial footage available inside the systems operators already use is what connects drone operations to everyday incident management.

Including awareness of the airspace

The operational picture also has to account for activity above the incident.

Counter-UAS sensors integrate directly into AirHub, bringing detected drone activity into the same COP as the organisation's own operations. Operators assess what is happening on the ground alongside what is in the surrounding airspace. Detection coverage depends on which sensors are deployed.

For police, fire, search and rescue and security teams, that context supports airspace coordination and informed decisions as an incident develops.

One shared picture, different operational needs

The value of a shared view runs across public safety and security.

Police: Live aerial video supports scene assessment and helps officers understand their surroundings before arrival.

Fire: With thermal equipment fitted, aerial feeds help commanders assess fire activity and coordinate resources.

Search and rescue: Teams combine perspectives from drones, vessels and personnel to support searches on land or water.

Security: Aerial coverage helps teams investigate activity beyond the view of fixed cameras.

AirHub brings video from drones, bodycams, mobile phones and compatible streaming devices into a single overview, which is what makes the shared picture useful across different teams and environments.

During a waterfront emergency, for example, police might coordinate access while fire and rescue crews respond on the water. A drone provides the overhead view, and feeds from personnel or vessels add detail from the scene. Sharing those perspectives lets each team see how its actions fit into the wider response.

The decisive moment comes when someone uses the information: a commander adjusts the response, an officer arrives better prepared, a rescue team gets a clearer direction.

That is the value of AirHub DFR as a COP. It connects the first alert to a shared understanding of the scene, and it helps the people responding make informed decisions while those decisions still matter.

What any given deployment can automate depends on its infrastructure, configuration and operational approvals. Our public safety and security pages set out what that looks like in practice.

Critical infrastructure drone operations are quietly becoming one of the busiest corners of the drone industry, and ports are leading the way. Every crane, quay and pipeline is now a candidate for drone inspection, and every drone flying nearby has to fit into a coastline that is already thick with air traffic. That is the environment AirHub is stepping into, with a new partnership with DronePort Rotterdam, which orchestrates the route from strategic challenge to scalable practice for autonomous and uncrewed systems. Using Rotterdam as a development and validation environment, DronePort Rotterdam connects public and private partners across technology, policy, operations and knowledge. 

Critical infrastructure drone operations are getting harder to ignore

DronePort Rotterdam works at the point where port, airport, city and region meet. That is where the connection with AirHub becomes relevant. DronePort Rotterdam is working on the wider conditions required to bring autonomous systems into real port operations: from governance and validation to digital infrastructure, safety, security and operational integration.

AirHub adds a specific capability to that environment. Its platform connects mission planning, live operations, compliance and operational data, helping operators manage increasingly complex autonomous operations through a single operational layer.

For AirHub, the fit is straightforward. Ports fall under the same critical infrastructure category as the energy, transport and industrial sites AirHub already supports, and the operational pressure is the same: more drones in the air, more data to bring into a single operational picture, and less room for a security gap.

"Ports are becoming one of the most demanding environments we work in. More drones, more regulation, and more at stake if something goes wrong. That is exactly the kind of complexity AirHub was built to handle."

Stephan van Vuren, co-CEO, AirHub. 

For DronePort Rotterdam, the partnership strengthens an important part of the operational architecture around autonomy. The challenge is not simply getting more drones into the air, but creating an environment in which autonomous missions can be planned, authorised, monitored and integrated into normal operations while maintaining safety, security and control. 

Why critical infrastructure drone operations need a European platform

For ports and other critical infrastructure operators, data sovereignty, deployment control and compliance are no longer secondary IT considerations. As operations become more digital and autonomous, they increasingly become part of operational resilience itself.  That is the standard AirHub was built to meet. AirHub is ISO 27001 and ISO 9001 certified, operates in line with GDPR and European data protection requirements, and can run on-premise or in a private cloud for organisations that cannot accept sensitive operational data leaving their own infrastructure.

That matters more in a port than in most places. A quay, a refinery or a power grid is also a target, and the operators responsible for it are increasingly expected to show exactly where their data lives and who can reach it.  We wrote about what that means for European drone software in more detail earlier this year.

AirHub and DronePort Rotterdam at DroneHorizon 2026

The partnership is being marked at DroneHorizon, part of a multi-year collaboration between Port of Rotterdam, Port of Antwerp-Bruges, Hamburg Port Authority, DronePort Rotterdam and The Beacon, to accelerate the transition from individual pilots and deployments towards scalable autonomous and uncrewed operations across European ports. The 2026 edition takes place on 15 September in Antwerp, opening a three day Port of the Future Week focused on autonomous and sustainable technology in ports.

It is a fitting place to formalise the collaboration. DroneHorizon draws exactly the mix of port operators, regulators and technology providers that critical infrastructure drone operations depend on, and it gives AirHub a direct line into the drone traffic integration work that Rotterdam is already leading on.

AirHub's live operations tools already bring drone, video and sensor feeds together into one view for teams managing complex sites. Within the partnership, that capability contributes to a wider operational architecture in which autonomous missions, situational awareness, compliance, security and operational decision-making increasingly need to work together.

"Scaling autonomous operations means building an operational environment in which technology, data, infrastructure, procedures, safety, security and governance work together. AirHub strengthens an important part of that architecture by connecting mission planning, live operations, compliance and situational awareness. Together, we can explore how these capabilities become part of normal operations in ports and other critical infrastructure.”

Chicane Visser, Partnership Lead, DronePort Rotterdam.

If you are at DroneHorizon on 15 September, come and find the AirHub and DronePort team!