C-DRONE GUIDE · 8 JULY 2026
Prior notification for flights over populated areas: the procedure step by step
No professional flight over a populated area can take place in France without the préfet being informed beforehand. This notification, inherited from national rules and kept alongside the European scenarios, is the formality that sets the rhythm of operators' weeks — and the one whose deadline, extended to 10 working days since 1 January 2026, most surprises clients in a hurry. A complete how-to.
Who must notify, and for which flights
The prior notification concerns professional operators planning a flight over a populated area — whether the flight is conducted in the specific category (STS-01) or, since 1 January 2026, in the open category over urban public space: built-up areas within the meaning of the highway code, but also any place where uninvolved third parties are close to the operation. In practice it accompanies almost every professional urban mission — façade inspection, real-estate photography, urban construction monitoring, event coverage. It is provided for by article L.6221-3 of the French transport code and its implementing order: the préfet of the département where the operation takes place must be informed before any populated-area flight of an unmanned aircraft for purposes other than leisure.
Not concerned: leisure open-category flights (which by construction cannot take place over urban public space), specific-category flights over unpopulated areas, and indoor flights, which fall outside aviation regulation altogether. Borderline cases to weigh carefully: a hamlet of a few houses, a busy business park, a campus — when in doubt, operators notify, since the procedure is free and quick.
The 10-working-day deadline and the validity window
The notification (cerfa form 15476*04) must reach the préfet no later than 10 working days before the flight — a deadline extended from 5 to 10 days by the order of 23 December 2025, in force since 1 January 2026. The count excludes Saturdays (for the services concerned), Sundays and public holidays: a mission planned for a Monday must be notified by the Monday two weeks before at the latest. It is this deadline — not the pilot's availability — that sets the real minimum notice for an urban job: always announce two to three weeks between order and flight in town to your clients.
Good news for recurring operations: a single notification can cover several flights over a given period, up to a few months, for the same location and the same type of operation — handy for monthly construction monitoring or a heritage inspection campaign. Any substantial change (location, dates outside the window, change of operator) requires a new notification. A simple weather postponement within the declared period, however, needs no step at all: that is exactly why experienced operators declare a multi-day window rather than a single date.
Filing the notification on AlphaTango: what goes in the file
The procedure is completed online from the operator's AlphaTango account, in the populated-area flight notification section; the portal automatically forwards the notification to the territorially competent préfecture and issues a time-stamped acknowledgement — the document to keep and show at any check. The form asks for: the operator's identity and number, the remote pilot(s), the aircraft used (class, mass), the operating scenario (most often STS-01), the precise flight location (municipality, address, coordinates or footprint on a map), the dates or period, the time slots and the maximum planned height.
Do not expect a positive reply: this is a notification regime, not an authorisation — the administration's silence counts as acknowledgement. The préfet may however oppose the flight or impose restrictions (time slots, perimeter) on public-order or safety grounds, particularly during events; the objection is notified to the operator before the planned date. Do not confuse this notification with the other possible steps: a protocol with civil aviation inside a CTR, a préfecture de police authorisation in Paris, a municipal order to take off from public land — they stack, they do not substitute.
The mistakes that sink urban missions
The most common failures, seen among operators and their clients alike:
- Counting calendar days instead of working days — with 10 working days, a flight on Monday the 20th must be notified by Monday the 6th, and every public holiday pushes the deadline back further.
- Declaring a single date with no fallback window: the first gust of wind cancels the flight and the whole procedure must be redone.
- Forgetting the related steps: the préfecture notification waives neither the CTR protocol near an airport nor the landowner's consent for the take-off point.
- Describing too vague a footprint ("city centre"), prompting a request for detail, or an objection, three days before the flight.
- Not carrying the acknowledgement on the day — the first document requested at a check.
Client side, a single verification suffices: ask for a copy of the AlphaTango acknowledgement before flight day. A provider who will "sort the notification later" or claims it is unnecessary for your urban façade inspection is implicitly announcing an illegal flight whose consequences you would share.
Planning an urban job: the standard countdown
To schedule a populated-area mission without stress, operators' proven countdown has four milestones. D-21: regulatory scouting — Géoportail, spotting any CTR (the protocol with the airport operator can take two weeks), checking that no major event will create a temporary no-fly zone. D-18: written consent from the take-off site's owner, informing the town hall or municipal police if the footprint touches public land. D-15: filing the prior notification on AlphaTango (10 working days minimum) with a multi-day window and wide time slots. D-1: NOTAM and weather check, document folder preparation.
This countdown explains the structure of urban quotes: the administrative share commonly represents two to four hours of work per mission, incompressible even for ten minutes of actual flying. It is also why bundling several needs into one notification — façade + roof + adjacent parcel for the same client — mechanically lowers the unit price of the deliverables. A good provider will suggest it unprompted; it is the sign that they master their regulations as well as their camera.