C-DRONE GUIDE · 22 AUGUST 2026
MANEX, flight file, maintenance log: the mandatory paperwork of a professional drone pilot
A professional drone pilot is not defined only by the aircraft or the insurance policy: it shows in the paperwork. An up-to-date MANEX, a complete flight file on every job, a maintenance log kept current day after day — these three documents form the backbone of any compliant operation in France, open to a DGAC inspection at any time and increasingly demanded by insurers and by clients themselves. Here is what each one must contain, who is actually concerned, and how a client company can use them to tell a serious provider from a hobbyist with a good camera.
Published on 22 August 2026, reviewed on 22 August 2026 — regulations in force as of August 2026.
The MANEX: the operations manual that describes the whole activity
The MANEX (operations manual, formerly called MAP — manual of particular activities, under the old national rules) is the central document for any operator flying in the specific category: since 1 January 2024, any operator working under the European standard scenario STS-01 or STS-02, or under a specific authorisation issued by the DGAC, must hold an up-to-date MANEX. Its content is set out in the acceptable means of compliance (AMC) of Regulation (EU) 2019/947: the operator's organisation, normal and emergency operational procedures, aircraft maintenance procedures, and the remote pilots' training and continued-competence programme. One practical requirement often surprises new operators: if they fly in France, their MANEX must be written in French, even if the company is based abroad.
The MANEX is not just a filing formality: the DGAC can inspect it at any time, on paper or on site, and it must reflect the operation as it actually runs — a MANEX describing an organisation or procedures the operator does not actually follow is a bigger liability than simply having no document at all. It is also the foundation for every mission's risk analysis. A landmark review by Reece Clothier and Rodney Walker, published in the Handbook of Unmanned Aerial Vehicles (Springer), describes this safety risk management process — hazard identification, assessment, treatment, monitoring — as the core of any safety case needed to obtain a drone operating authorisation, and notes that it directly shapes the organisation's operations manual (see the study on Google Scholar) — exactly the logic behind the SORA method underpinning the French STS scenarios, covered in our guide to BVLOS flights and STS/SORA scenarios.
In the open category (most everyday missions — roof inspection, real-estate photography, construction monitoring in a clear area), a MANEX is not required by the rules. Nothing stops a serious operator from keeping equivalent internal procedures in substance — and many do, not least because that is often exactly what professional insurers and public buyers ask for before signing a contract.
The flight file: what to have on site for every mission
The flight file is the set of documents the pilot must be able to produce on site to prove the flight is legal and that the mission was prepared in line with the operator's MANEX. This obligation stems from Regulation (EU) 2019/947, from the order of 23 December 2025 amending the French "Espace" order (in force since 1 January 2026) and, for specific-category operators, from their own MANEX. In its full form, it gathers: identity documents for the operator and the pilot, the acknowledgement of the activity declaration, an extract from the AlphaTango registry proving the drone is registered, a valid professional third-party liability insurance certificate, the pilot's (or pilots') qualifications matching the scenario flown (CATS, practical training, an aptitude certificate), and a pre-flight checklist covering the overflown zone, any NOTAMs and the prior declaration filed where required.
That pre-flight checklist is not a mere administrative ritual: it is the tool that turns a body of rules into a reliable routine, run minutes before every take-off. A landmark review by Brigette Hales and Peter Pronovost, published in 2006 in the Journal of Critical Care, shows that aviation pioneered the checklist as a tool for error management and performance improvement, breaking complex tasks down into verifiable steps — a logic that advanced medicine later borrowed from aviation, not the other way round (see the study on Google Scholar). The professional drone pilot's flight file applies exactly that principle to an activity where missing a single check — an unnoticed restricted zone, an insurance policy that has lapsed, a missing qualification — carries immediate regulatory and sometimes criminal consequences.
For a company booking a mission in a constrained zone (a built-up area, near an aerodrome, inside a Natura 2000 site), the flight file is also what lets the provider prove after the fact, in case of an inspection or an incident, that the mission was properly covered. Building it in advance directly drives the lead times quoted to the client, a point covered in our guide to hiring a professional drone pilot.
The maintenance log: the drone's technical memory
The maintenance log records each aircraft's technical history: maintenance work and its nature, part replacements (propellers, batteries, sensors), firmware updates with their date and version, and the results of the pre-flight checks run before every mission. Keeping it up to date has become, as DGAC inspections have stepped up and public tenders have tightened their specifications, an almost systematic part of any serious professional operation — alongside tracking pilots' qualifications and archiving flight reports, all elements that give the DGAC the complete traceability of the activity it is aiming for.
The maintenance log's value reaches well beyond an administrative audit. In the event of an incident or accident, it is the first document examined to determine whether a technical failure — an ageing battery, an undetected cracked propeller, outdated firmware known for a stabilisation bug — may have contributed to the event; its absence complicates an insurance assessment and, depending on the policy's terms, can affect whether the claim is covered. For a fleet of several aircraft shared across multiple sites, as described in our guide to the annual multi-site drone contract, the maintenance log also lets an operator decide objectively between repairing and retiring an aircraft, based on its actual history rather than a guess.
On the liability side, an up-to-date maintenance log is also what lets an operator demonstrate due diligence if an accident happens during a mission — a factor that weighs directly on how liability is split between client, operator and pilot, covered in our guide to liability in a professional drone accident.
What a company should check before booking a mission
For a buyer who is not a pilot, these three documents are not read — they are checked through their visible consequences. Before signing, four simple questions are enough to gauge how serious a provider is: can they produce their AlphaTango registration certificate and a valid professional insurance certificate? Does the planned flight scenario (a populated area, beyond visual line of sight, near an aerodrome) require a MANEX, and if so, can they confirm it exists without handing it over in full — an internal document, but one whose existence and last update date are easy to state? Do the pilots assigned to the mission hold the right qualification, a point our guide to the CATS theory exam helps verify precisely? And for an operator based outside France, is the recognition of their authorisation from another member state properly established, as covered in our guide to a foreign drone provider working in France?
These checks are not excessive distrust: they protect the client company itself. If a DGAC inspection happens during a mission on its premises, or an incident involves third parties, the client can see its own liability engaged if it knowingly hired a provider that was clearly non-compliant. They also shape the quality of the final deliverable and the ownership of the data produced, a contractual point in its own right covered in our guide to drone data ownership and security. For a one-off mission as much as a recurring contract, the simplest step is to request a quote stating the site and the objective: a serious provider answers questions about their regulatory framework spontaneously, with no need to pry it out of them.