Resources

A call comes in. Before a vehicle has left the station, a drone lifts from a dock on a rooftop a few streets away, flies to the address on its own, and starts sending video to the control room. By the time the first unit is on the road, a dispatcher can see how many people are involved, whether anyone is hurt, and which way to send the officers who are coming.

That is Drone as a First Responder, usually shortened to DFR. It has moved from demonstrations to daily use in several parts of the world, and European public safety organisations are now working out what it takes to run one here. This post sets out what a DFR programme actually involves, what the European regulatory path looks like, and which parts decide whether the thing holds up once it is live.

What DFR is, and what it is not

A DFR programme sends a drone to an incident automatically, as part of the standard response, without anyone driving to the location first. The aircraft usually lives in a dock, launches on a trigger from the control room, flies a route it calculates itself, and streams what it sees to the people who need it.

Plenty of public safety organisations already fly drones without any of that. A team gets called out, drives to the scene, unpacks, briefs, and flies. That model is valuable and it is a different thing. The distinction is who moves first. In a drone team model, the drone arrives after people do. In a DFR model, it arrives instead of waiting for them.

The second distinction is who is in the loop. Automated launch does not mean an unattended aircraft. A remote pilot stays in command of every flight, and being able to take manual control at any moment is part of the design rather than an add-on.

Why European organisations are arriving at this now

The regulatory picture has settled enough to plan against. DFR flights go beyond the pilot's visual line of sight, which puts them in the specific category, and that means an operational authorisation from your national aviation authority based on a risk assessment. Since September 2025 that assessment runs on SORA 2.5, which we covered in our piece on SORA 2.5 in the June 2026 Easy Access Rules.

Three things about the European route are worth knowing early, because they differ from how DFR is discussed in other markets.

There is no European certification for a control room. In the United States a proposed rule would put beyond visual line of sight operations under the oversight of a certified operations centre, and that has become a standard reference point in the American conversation. No equivalent exists under EASA rules. The responsible party in Europe remains the drone operator and the remote pilot-in-command, whatever room they happen to be sitting in.

Authorisation is national, and the detail varies. The framework is European, and the interpretation, the processing time and the evidence expectations sit with each national authority. An organisation operating across borders will find the same operation assessed differently in two member states.

Data residency arrives early in the conversation. Where the video and mission data lives, and who can reach it, tends to be part of the authorisation discussion and almost always part of procurement. For a police force this is rarely a technical footnote.

The part that decides whether it works

Here is what the organisations furthest along with DFR tend to say once the novelty wears off. The aircraft is the easy part. What separates a programme that scales from one that stalls is the operation around it.

Three things carry most of that weight.

Coverage and the launch decision. A dock covers a radius, and the radius is set by flight time, airspace and the rules under which you are authorised. So the first design question is not which drone to buy. It is which parts of your area you can reach inside a useful number of minutes, and which calls justify a launch. Programmes that start by mapping coverage against call types tend to make better hardware decisions later.

Keeping a person in command. Automation earns trust by being interruptible. A remote pilot needs live telemetry, a clear picture of where the aircraft is and what it sees, and the ability to take over immediately. That requirement is regulatory and it is also operational: the moment a dispatcher stops believing they can intervene, the drone stops getting launched.

The record. Every automated flight produces an obligation. Who authorised it, who was in command, over which area, at what height, with what result, and can you produce that when an authority, a court or a journalist asks. At one flight a week a spreadsheet copes. At forty flights a day across several docks it does not.

What it looks like when it runs

Dubai Police operates one of the largest DFR networks in service, using AirHub across a city-wide set of docks, with dock-to-scene response inside 90 seconds. The interesting part is that the number holds across a network rather than at a single site, which is a coordination result more than an aviation one. There is more in the Dubai Police case study.

Closer to home, Belgian Police zones use drones for real-time situational awareness during live incidents, including running two aircraft at once so one can hold a wide view of the scene while the other zooms in and relays coordinates to the teams on the ground. Their case study is a good picture of what shared awareness changes about a response, which is the same benefit DFR delivers earlier in the timeline.

Curious to learn more about our DFR capabilities? Watch the video below:

Where AirHub fits

From 1 September, AirHub's upgraded DFR capabilities go live. They sit on the parts described above rather than alongside them: automated dispatch with a remote pilot in command, automated route calculation, live telemetry with takeover, and a Drone Operations Centre built for a control room running several aircraft and several pilots at once. Live operations and the shared operational picture underneath it are the same tooling that public safety teams already use for incident response, which is the point: DFR is a way of starting the response earlier rather than a separate system to run in parallel.

The platform is hardware agnostic and European hosting and deployment options are part of the architecture, which matters for the data residency question above.

Where to start

If your organisation is considering DFR, the useful first steps are unglamorous. Map which parts of your area a dock could reach inside a target response time. Decide which call types would justify an automatic launch, and which would not. Talk to your national authority early about the authorisation route, because that conversation sets your timeline more than procurement does. Work out who sits in the control room, what they see, and how they take over. And decide where your data will live before anyone asks you.

Our public safety page sets out how the platform supports each of those, and we are happy to walk through what a programme in your area would involve.

Today we are releasing a significant upgrade to our Drone-as-First-Responder capabilities. Dispatch, route calculation, situational awareness and reporting now run as one workflow, starting the moment a call reaches your control room.

For teams already working this way, this removes the steps that used to sit between an incoming call and a drone in the air. For teams considering it, this is the version we would want you to evaluate.

What changed in our Drone-as-First-Responder workflow

The short version: the workflow now begins in the systems your control room already uses, and it ends with the reporting your organisation needs afterwards. Everything in between happens without someone opening a second application.

Six things are different.

The call is the trigger. The alert passes from your computer-aided dispatch (CAD) system straight into AirHub. No operator has to switch systems, and no one has to phone a pilot to get a drone airborne.

The route is calculated automatically. Weather, airspace and no-fly zones are factored in, and the route is planned around them before the drone leaves the dock.

The best placed dock launches. Across a network of docks, the software selects the drone and dock that can reach the incident fastest. This is where fleet management does the work in the background.

Overhead within 90 seconds. That is the target the whole workflow is designed around.

Immediate situational awareness. The moment the drone arrives, your control room sees the scene. Units still on their way know what they are heading into, and an operator can take control at any point during the flight.

Every flight is logged. Coverage, dispatch rate, response times and a complete flight record, ready for reporting and review.

Why the control room integration matters most

Most conversations about Drone-as-First-Responder start with the drone. In practice, the deciding factor is what happens in the seconds before it launches.

If an operator has to leave the dispatch system, open a flight application and set up a mission, the time advantage disappears. That is why the integration with computer-aided dispatch sits at the front of this release. The alert flows in, and the workflow starts.

The same principle applies to what your operators watch. Through our live streaming capabilities, the drone feed can be brought into the video management system (VMS) your control room already works with, so the picture appears where people are already looking. Combined with the Drone Operations Centre, the aerial feed becomes part of the existing operational picture rather than a separate screen in the corner.

Built for flights beyond visual line of sight

Automated dispatch only works at scale if the flights themselves are permitted. Operations beyond visual line of sight (BVLOS) are part of how this workflow is designed, including the planning and documentation those flights require.

Regulation across Europe is still moving, and the route to approval is rarely quick. We wrote about that in more detail in our piece on SORA 2.5 and what it means for operators. What matters here is that the logging and evidence your authority asks for is generated by the workflow itself.

Drone-as-First-Responder in practice at Dubai Police

Dubai Police have been running a city-wide network on AirHub around the clock. Their operational target is the same 90 seconds. The value shows up in what happens next. The control room has a picture of the incident before units arrive, so commanders decide what to send based on what is actually there.

Read the full story in our case study: how Dubai Police use AirHub for DFR.

What this means if you are earlier in the process

Not every organisation is ready to dispatch drones automatically, and that is a reasonable place to be. Most teams we speak to start with live operations and a single operational picture, then add automated dispatch once coverage, docks and approvals are in place.

If you are building towards that, the sequence usually looks like this. Get the aerial feed into your control room. Prove the operational value on the incidents you already attend. Establish the airspace approvals. Then automate the launch.

What comes next

Over the coming weeks we will publish a closer look at each part of the workflow, from the control room integration through to logging and compliance. Our DFR pages cover how teams are working today, and the AirHub platform sits behind all of it.

Want to see the workflow running on your own operating area? Book a demo and we will walk through it with you.

Two months in which several of the headline items were individual permissions rather than new frameworks. Sweden cleared its first police operation beyond visual line of sight, Spain issued its first SAIL III cargo authorisation, and enforcement action arrived alongside both.

EMEA

Sweden clears its first police BVLOS operation. On 10 August the Swedish Transport Agency established a temporary danger area and a geographic UAS zone over parts of Norrköping, enabling the Swedish Police Authority to fly beyond visual line of sight there. It is the first decision of its kind in the country, and three details are worth noting. It works through airspace design, distributing responsibilities between air traffic control, the police, crewed aviation and other operators rather than giving anyone priority. It lets the police fly around the clock instead of depending on the control tower's opening hours. And the Police Authority intends to introduce the same capability in Stockholm, Göteborg and Södertälje during the year, so more decisions are coming.

Spain issues its first SAIL III cargo authorisation. AESA granted the country's first SAIL III operational authorisation for drone cargo transport, the level at which the evidence burden rises sharply.

EASA publishes the June 2026 Easy Access Rules. The revision consolidates current guidance for operators, authorities and manufacturers. We went through what it means in our piece on SORA 2.5 in the June 2026 Easy Access Rules.

Denmark requires electronic conspicuity. New rules oblige certain operations to be electronically visible, supporting safer integration between crewed and uncrewed aviation.

Poland consults on Drone Strategy 2.0. The civil aviation authority opened a consultation feeding the European Commission's review of the strategy's implementation, which is where the sector's next priorities are set.

Qatar enacts new drone legislation. A comprehensive framework covering registration, operations, enforcement and penalties.

UAE advances its aviation innovation programme. The GCAA announced further initiatives for the country's advanced aviation ecosystem.

Americas

FAA proposes a 289,215 dollar penalty. The agency proposed the civil penalty against one operator for multiple alleged violations.

Counter-UAS operations at the FIFA World Cup. The FAA reported coordinated detection and mitigation through the tournament, the largest recent test of counter-drone work at a major event. European readers will know the theme from Europe's counter-drone action plan.

Transport Canada repeats its wildfire warning. Flying near wildfire operations is illegal and dangerous, because it grounds firefighting aircraft.

Brazil and the FAA publish joint eVTOL safety objectives. ANAC and the FAA released the objectives together, and ANAC also ran a webinar on proposed Brazilian rule changes.

Chile launches online registration. The DGAC introduced a digital platform for registering remotely piloted aircraft.

Colombia sets conditions for earthquake response flying. Aerocivil established operational safety conditions for drone use in affected areas.

Asia-Pacific

Australia consults on flying above 400 feet. CASA opened consultation on operations above 400 feet in defined environments, published more flexible airworthiness pathways for large RPAs, and released the outcomes of its consultation on flying over people.

Japan issues further policy updates. MLIT published updates supporting continued commercial expansion.

Singapore trials dedicated flying areas. CAAS and SAFRA began trials of designated areas for recreational users.

Malaysia consults on a Low Altitude Economy framework. CAAM opened public consultation on its proposed framework.

Standardisation bodies

No major publications or consultations were released during this period.

What to take from it

Precedent is becoming useful. A national police force flying beyond visual line of sight in a defined urban zone, and a first SAIL III cargo authorisation, are reference points you can bring to your own authority. Neither guarantees anything about your case.

Conditions are shifting from how you fly to how you are seen. Electronic conspicuity and deconfliction routines are appearing as the price of complex operations, which belongs in procurement rather than at application stage.

Your authority sets your timeline. Sweden's decision followed a coordination meeting at Norrköping airport in spring and a full consultation. Every permission above took months that never make the announcement.

We track this every month. If you want help working out what an authorisation route looks like for your operation, our regulatory consultancy team does this with operators across Europe. And if there is a development we should be covering, tell us.