Flying a drone in Italy is mostly a matter of category, location, and paperwork. Italy drone laws sit inside the EU framework, but the real difference between a legal flight and a problem flight is usually one missed check on insurance, registration, or a geo-zone map. I would treat the whole thing as a three-part decision: what you are flying, where you are flying, and whether you can prove you are allowed to do it.
The parts that matter most before you fly
- Italy follows the EU open, specific, and certified structure, so most simple flights stay in the open category.
- Insurance is required for almost every operator, and the local system expects third-party liability cover.
- Most operators must register on d-flight and display the QR code on the drone.
- The default open-category ceiling is 120 metres above ground level, with VLOS and people-distance limits.
- UK or other non-EASA certificates are not automatically accepted, so check your status before travelling.
How the Italian rulebook is structured
The basic architecture is simple: open for low-risk flying, specific for higher-risk missions, and certified for the most demanding operations. For most travellers, hobby pilots, and a lot of low-risk commercial work, the open category is the one that matters. Once you move beyond it, the paperwork and the approval process become much heavier.
In practice, the local layer matters just as much as the European one. ENAC adds rules around registration, insurance, and airspace checking, and it expects you to use the right geo-zone information before every flight. That is why I would not treat this as a simple "bring a drone and go" destination. The category tells you what kind of flight you are doing; the map tells you whether you can do it in that spot at all. Once that structure is clear, the next step is figuring out which drone bucket you actually fall into.
Which category your drone falls into
The class label on the drone matters, but it is not the only thing that matters. EASA's current open-category framework is built around class-marked drones, legacy drones, and privately built aircraft, with the exact subcategory determined by weight and risk. If you own an older drone, do not assume it is automatically excluded; transitional rules can still apply, but they do not remove the need to check the weight, date of market placement, and operational limits.
| Drone type | Typical subcategory | What it usually means in practice | What you normally need |
|---|---|---|---|
| C0, under 250 g | A1 | No flight over assemblies of people; short, low-risk use close to everyday spaces | User manual, and registration only if the drone has a camera or other personal-data sensor and is not a toy |
| C1, under 900 g | A1 | Can fly over uninvolved people only in a limited sense, but overflight should be minimised | d-flight registration, A1/A3 online training and exam |
| C2, under 4 kg | A2 | Closer work around people, but not over them; 30 m separation normally, 5 m with low-speed mode | A1/A3 proof plus the A2 competency exam |
| C3 and C4, under 25 kg | A3 | Far from uninvolved people and urban areas, with a wider buffer | d-flight registration and A1/A3 online training and exam |
| Legacy drone without a class mark, placed on the market before 31 December 2023 | Depends on weight and use | Can still operate under transitional open-category rules if it fits the weight and subcategory limits | Check the specific weight band before you plan the flight |
The two numbers that matter most here are 250 g and 120 m. Under 250 g, the paperwork can be lighter, but a camera often brings registration back into the picture. Above that, the open-category training requirements start to matter quickly. If your drone has a camera and you are the operator, I would assume registration is part of the job unless you have confirmed an exception. That is the point where the paperwork starts to matter as much as the hardware.
Registration, insurance, and pilot proof
The biggest mistake I see is people assuming that pilot qualification, operator registration, and insurance are all the same thing. They are not. One is about who is flying, one is about who is legally responsible for the drone, and one is about the financial protection around third-party damage.
For most operators, the practical checklist is straightforward:
- Register on d-flight and obtain the QR code for the drone.
- Keep third-party liability insurance in place for the operation.
- Carry the right remote-pilot proof for the subcategory you intend to use.
- Check whether your specific drone needs remote identification support.
The UK point deserves extra care. If your drone certificate was issued outside EASA/EU systems, do not assume it transfers automatically. In plain terms, a UK paper trail may be useful as background, but it is not a free pass in Italy. For many visitors, that is the surprise that turns a planned flight into a cancelled one. The safest assumption is simple: if you cannot show the right open-category competence in the EASA system, get that sorted before you travel. Once the paperwork is in place, the real issue becomes where you are allowed to take off.
Why the map matters more than the drone box
The exact take-off point can change the answer even when the drone itself is perfectly legal. The d-flight maps show UAS geo-zones, including safety zones around airports, heliports, and airfields, plus security and environmental zones. In safety zones, open-category flight is prohibited. In some other restricted zones, extra permission can reopen the door, but I would never assume that without checking the note attached to the zone.
If you are visiting Italy, the spots that most often need attention are:
- Airports, heliports, and other aerodrome surroundings.
- Historic centres and major landmarks.
- National parks and protected landscapes.
- Dense urban areas where people are constantly moving through the frame.
- Coastal promenades, beaches, and event areas that look open but are often busy.
I would not plan by generic map apps alone. Use the exact coordinates, not the nearest town name, because a flight that looks harmless on paper can sit inside a restricted zone in reality. Once you go beyond those map checks, you are no longer asking a simple "can I fly?" question; you are asking whether the operation belongs in the specific category.
When the open category is not enough
Not every paid shoot becomes a specific-category mission. But if you want to fly beyond visual line of sight, over people, or in a more complex environment, the law stops being simple very quickly. This is where SORA comes in: it is the structured risk assessment used to justify operations that sit outside the open-category comfort zone.
A practical way to think about it is this:
| Operation | Likely treatment | Why it matters |
|---|---|---|
| Quiet rural inspection far from people | Often open category, usually A3 | Low-density airspace and simple separation can keep the flight compliant |
| Roof or facade work in a built-up area | Can move toward A2 or specific | Distance from uninvolved people becomes the deciding factor |
| Wedding footage over guests | Not open | Overflight of assemblies of people is not allowed in the open category |
| Pipeline or corridor inspection beyond visual line of sight | Specific category | BVLOS usually needs authorisation and a formal risk case |
| City-centre mapping or work near traffic | Often specific | Higher density, more obstacles, and more airspace constraints |
The useful distinction is not "commercial versus hobby". The useful distinction is "low risk versus elevated risk". A simple paid job can still fit the open category, while a personal flight over a crowd can be illegal. That is why the category question matters more than the money question. Even a professional pilot can get caught out by the same rules that trip up a tourist. The final layer is avoiding the mistakes that seem small until they cost you the flight.
The mistakes I would avoid in Italy
I would not treat a small drone as a free pass. Small drones still crash, still capture personal data, and still trigger the same airspace and insurance logic. Most problems I see come from pilots who understand the drone but underestimate the surrounding rules.
- Using the wrong map or skipping the geo-zone check altogether.
- Assuming a UK certificate works automatically inside Italy.
- Forgetting that a camera can trigger registration even on a sub-250 g drone.
- Flying past 120 m because the drone still has signal and battery.
- Overflying a crowd for a "brief shot" and hoping nobody notices.
- Leaving insurance proof at home and hoping an officer never asks for it.
Most of these errors are not technical failures. They are planning failures. The good news is that they are easy to prevent if you use a short routine before every flight.
The 10-minute routine that keeps a simple flight simple
- Open d-flight and check the exact launch point, not just the general area.
- Confirm the drone class, the subcategory, and whether registration or training applies.
- Keep your insurance proof and remote-pilot documentation available.
- Set your ceiling, return-to-home altitude, and visual line-of-sight boundaries before you arm the drone.
- Look again for people flow, events, emergency activity, and any last-minute geo-zone changes.
- If anything pushes the flight outside open-category limits, stop and get the right authorisation first.
