Drone Regulations
A drone shot is an aviation operation first and a camera angle second.
What this is about
Drone work in Europe runs under the EU drone framework, which sorts flights into risk categories and attaches duties to each: operator registration, proof of remote pilot competence, marking of the aircraft, and respect for geo-zones around airports, hospitals or protected areas. On top of that sit the non-aviation permissions — landowner consent, municipal film permits, privacy considerations when residential windows appear in frame. Producers rarely handle this themselves. They book an operator who can show registration, competence certificates and liability cover for the intended flight, and they build approval lead times into the schedule.
A term only helps when everyone on set means the same thing by it — so what follows is how it is used, not a dictionary definition.
What runs differently here
Where this differs from the general case:
- Flight permission and film permission are different approvals from different authorities
- Ask the operator for registration, competence proof and liability cover before booking
- Geo-zones and site restrictions decide feasibility long before the weather does
- Approvals need lead time — a drone day scheduled late is a drone day at risk
With TillyGen
TillyGen marks aerial setups in the shot plan, so approval lead times land in the schedule instead of in the shoot week.
Change one constraint and the consequences travel through the whole plan: affected shots are flagged, the call sheet is regenerated, and nobody keeps working from yesterday's version.
Frequently asked
Can we just send up a drone for a few shots?
Not casually. The flight falls under aviation rules and usually needs the landowner and the city to agree as well. Book a registered operator and verify the requirements with the competent authority.
How long does it take to get started with TillyGen?
A first project takes under an hour to set up. There is no configuration phase in which templates and fields have to be defined before the tool produces anything.
Can the results be exported?
Yes — as PDF for the crew, CSV for downstream systems and through the API for anything automated. The plan stays the source; the exports are views of it.