C-DRONE GUIDE · 26 JULY 2026
Can a foreign drone operator work in France? EU recognition and formalities
A Belgian civil-engineering firm wins a rail contract in northern France and wants to bring in its usual drone team. A French industrial group with a plant in Germany wants the same provider it uses in France to run the thermal survey over there. Either way, the same question keeps coming up: can a drone operator registered in one EU country work in another without starting from scratch? The short answer is: almost. European regulation has harmonised the essentials — registration, certificates, flight categories — but part of the framework stays firmly national, starting with the flight zones themselves. Here is what travels from one country to another, what does not, and the checklist for preparing a cross-border mission in 2026.
Published on 26 July 2026, reviewed on 22 August 2026 — regulations in force as of August 2026.
The harmonised core: one registration and certificates valid across 31 countries
Implementing regulation (EU) 2019/947 and delegated regulation (EU) 2019/945 apply identically across the 27 EU member states, plus Iceland, Liechtenstein, Norway and Switzerland — 31 territories sharing the same regulatory space overseen by EASA. In practice, an operator registers once, in the country where they reside or have their main place of business; the operator number obtained there — in France via AlphaTango, see our AlphaTango registration guide — is then valid across the other 30 territories, with no further registration step. It simply has to be affixed to every drone in the fleet deployed.
Remote pilot certificates follow the same logic: the A1/A3 theory certificate, the A2 certificate of competency and the specific-category certificate (CATS) obtained in one member state are recognised in the other 30, as long as they meet the common baseline set by the regulation — see our open vs specific category guide. That was precisely the goal: preventing a patchwork of national rules from capping the sector's economic potential. A study by Gerke published in 2021 in the journal Drones reviewed the new European rules and stressed that their harmonisation directly conditioned the effective use of UAS and their economic potential in scientific and commercial sectors (see the study on Google Scholar) — a stake practice confirms every time a job crosses a border.
What stays national: flight zones, notifications, language
Harmonisation stops where physical territory begins. Every member state defines and publishes its own UAS geographical zones — prohibited, restricted or condition-bound areas — on its own national register: in France, the Géoportail drone map, detailed in our Géoportail drone zone map guide; in Belgium, Germany or Spain, other portals, with different boundaries. An operator flying outside their country of registration must check the destination country's map before every mission — their own tells them nothing about local restrictions.
Some formalities also stay purely national, whatever country the operator is registered in. In France, any professional flight over public space in a built-up area requires a prior declaration to the préfecture (cerfa form 15476*04, ten working days' notice) — a Belgian or German provider is subject to it exactly like a French one. The paperwork is filed in French, and the counterpart remains the préfecture of the relevant département, not a centralised European authority.
Specific category: recognition that is not automatic
For the specific category — standard scenarios STS-01/STS-02, authorisations based on a SORA or PDRA risk assessment, LUC certification — mutual recognition exists in principle, but it is not automatic in practice. The regulation requires that before operating in another member state under an authorisation or declaration issued elsewhere, the operator notify the competent authority of the country where the mission will take place (the DGAC for France); that authority may judge that local risks — population density, airspace configuration, proximity to an aerodrome — call for additional mitigation measures specific to its territory. See our BVLOS, STS and SORA guide for the detail of these steps.
In practice, this cross-border notification needs to be built into the job's schedule just like a national declaration — it cannot be settled the day before the flight. It is also worth checking that the aerial third-party liability insurance certificate, mandatory for any commercial operation under Regulation (EC) No 785/2004, actually covers activity in the country of the mission: a policy taken out for strictly domestic use sometimes carries a territorial clause best lifted before the first flight, not after an incident — see our professional drone liability insurance guide.
Switzerland, the UK, the US: the third-country case
Switzerland, Norway, Iceland and Liechtenstein apply the same body of rules as the EU under bilateral agreements with EASA: a Swiss operator fits in exactly like a French one, with no special formality. The United Kingdom, by contrast, has been a third country since Brexit: its CAA runs its own framework, derived from the European text but managed independently — an operator registered in France is not automatically recognised there and must register separately with the British authority to operate, and vice versa.
For an operator based outside the EASA area — post-Brexit UK, the United States, Canada... — who wants to work in France or elsewhere in the Union, the regulation sets out a precise mechanism: they register in the first member state where they plan to operate, which makes them, from that registration onward, a fully-fledged "European operator", subject to the same rules as any EU operator for all subsequent operations within the EASA area. That is often the simplest route for a foreign company landing its first French contract, rather than setting up a local legal entity.
Checklist before a cross-border mission
Ahead of any mission that crosses a border, in either direction, a checklist narrows the risk of cancellation or an unpleasant surprise:
- A valid EU operator number, affixed to the drone deployed.
- Pilot certificates that actually cover the category and scenario planned for the mission.
- The UAS zone map of the destination country checked — never just the home country's.
- A préfecture declaration or local equivalent filed in time if the flight takes place in a built-up area.
- Notification to the competent authority of the mission country if the operation falls under the specific category using an authorisation issued elsewhere.
- An insurance certificate checked for territorial cover including the mission country.
- Documents and communications prepared in the language expected locally.
For a multi-site group weighing whether to build an in-house drone team able to operate anywhere or to rely on a local provider in each country, our in-house or outsource guide details the trade-offs. And to check case by case what a specific mission involves, request a quote stating the country, the site and the nature of the job.