C-DRONE GUIDE · 1 SEPTEMBER 2026

Drone Incident or Accident on a Job: Occurrence Reporting, What the Operator Owes the Authority

The drone came down. Nobody was hurt, the client got the footage, the aircraft goes back to the repair shop : for many operators the matter ends there — a warranty ticket and a line in the flight log. That reading is wrong. A flight that goes badly is not merely damage to be repaired : it is a safety occurrence, within the meaning of the European regulation governing occurrence reporting across civil aviation, drones included. That obligation is settled neither with the insurer nor with the client : it is settled with the authority, it has its own deadlines — 72 hours, then 30 days, then 3 months —, it legally protects whoever reports, and it survives any amicable settlement reached with the client. Here is who is concerned, what is mandatory and what is voluntary, how the civil aviation authority and the investigation bureau fit together, and what an industrial client should require from a contractor after an incident on its site.

Published on 1 September 2026, reviewed on 1 September 2026 — regulations in force as of September 2026.

A flight gone wrong is a safety occurrence, not just damage

An operator's reflex after a flight incident is almost always contractual and insurance-driven : who pays for the repair, did the client suffer a loss, should the insurer be told. Those questions are real, and our guide to liability after a drone accident on a professional job covers them in detail. But they do not cover a third obligation, which depends neither on the contract nor on the damage suffered : reporting the occurrence to the civil aviation authority.

That obligation comes from Regulation (EU) No 376/2014 of 3 April 2014 on the reporting, analysis and follow-up of occurrences in civil aviation. The text does not target airlines alone : it applies to anyone active in civil aviation, recreational flying included, and it explicitly extends to operators of unmanned aircraft. Implementing Regulation (EU) 2019/947, the one governing drone operations across Europe, restates it plainly in Article 19(2) : every UAS operator shall report to the competent authority any safety-related occurrence and exchange information about its UAS in accordance with Regulation 376/2014.

The logic has nothing to do with liability. Article 15 of Regulation 376/2014 requires that information drawn from occurrence reports be used only for the purposes for which it was collected ; the stated aim is accident prevention, not the attribution of blame. An occurrence report is therefore not an admission, and no more does it replace an insurance claim : these are two parallel tracks, with two recipients, two deadlines and two distinct purposes.

What actually gets reported bears little resemblance to the popular image of a « crash ». The guide published by the French authority for drone operators sorts occurrences into a few very concrete families : loss of control in flight, proximity to or collision with an aircraft, loss of the command link, unplanned transition to BVLOS — that is, losing visual contact with the aircraft when it was not planned. The examples given are ones any operator will recognise : departure from the operational volume, unintended entry into the prohibited perimeter around an aerodrome, destruction on landing following unexpected aircraft behaviour, ground impact without the required failsafe device triggering, or a crewed aircraft entering the airspace reserved for the operation.

That breakdown matches what the literature shows. A study by G. Wild, J. Murray and G. Baxter, published in 2016 in Aerospace, analysed 152 occurrences involving civil remotely piloted aircraft over 2006-2015 and compared them with the distribution of commercial air transport occurrences (see the study on Google Scholar). The result : the distributions differ significantly, with a clear overrepresentation of loss of control in flight and equipment problems — and, unlike in crewed aviation, technical failures rather than human factors are the leading contributor to drone occurrences. In other words : the typical occurrence for a professional operator is not a piloting error, it is a failure — exactly the kind of information that experience sharing lets circulate before it repeats itself elsewhere.

Mandatory or voluntary: where the line sits, and why it moves in the specific category

Regulation 376/2014 sets out two regimes. Mandatory reporting (Article 4) covers occurrences that may represent a significant risk to aviation safety, listed in detail in Implementing Regulation (EU) 2015/1018. Voluntary reporting (Article 5) covers everything else : every organisation must set up a system to collect occurrences that fall outside the obligation but still carry a safety lesson.

For drones, the French authority is explicit : mandatory occurrences are rare. The regulatory baseline retains three families — occurrences causing serious or fatal injuries, occurrences involving a certified drone, and occurrences involving a crewed aircraft. That last family is the most common in professional practice : a near miss with an air ambulance helicopter, an aircraft on approach or a crop-spraying aeroplane is a reportable occurrence, even without damage, even if the other pilot noticed nothing. The same applies the other way round when a crewed aircraft enters a temporary reserved area obtained for your operation.

The line shifts markedly as soon as you leave the open category. In the specific category under an operational authorisation, the authority's guide states that the authorisation itself carries a list of occurrences — its section 4.8 — that must be reported, a list that is added to the baseline requirements and set by the authority in light of the risk of the authorised operation. In other words : an operator holding an authorisation cannot simply know the European baseline, they must reread their own authorisation. The distinction between the two frameworks is developed in our guide to the open versus specific drone category, and the most exposed operations — beyond visual line of sight, standard scenarios, SORA analysis — in the one on BVLOS flight and STS scenarios. Operators holding a LUC certificate are, from the outset, in safety-management-system territory, where internal handling of occurrences is the heart of the arrangement rather than a side formality.

The real risk for the profession is not over-reporting : it is the opposite. A. Konert and P. Kasprzyk, in a paper published in 2021 in the Journal of Intelligent & Robotic Systems, examined European and national procedures for reporting UAS incidents and documented chronic under-reporting, driven by two practical difficulties : identifying the operators concerned, and the lack of a precise definition of what counts as an « incident » for an unmanned aircraft (see the study on Google Scholar). Their recommendations are blunt : clarify the definitions and actively raise operator awareness of the need to report. That is exactly the position taken by the French authority, which treats reporting any occurrence deemed significant as good practice : such a report is then handled as voluntary, but analysed and classified with the same care as a mandatory one.

72 hours, then 72 hours: the reporting chain from remote pilot to the European database

The timeline in Regulation 376/2014 is twofold, and that is where most operators get it wrong. Article 4(7) requires the individuals concerned to report the occurrence within 72 hours of becoming aware of it. Article 4(8) then requires the organisation to report to the competent authority as soon as possible and, in any event, within no more than 72 hours. The French authority sums the rule up in a memorable shorthand : « 72h+72h ». No more than 72 hours may pass between the occurrence (or its discovery) and the moment the operator is informed by the remote pilot ; the operator then has 72 hours to forward the report, together with details of any immediate corrective measures taken.

The deadline is not the only milestone. A first analysis must be sent within 30 days of the operator becoming aware of the occurrence, setting out the corrective or preventive measures adopted ; the final analysis is expected within 3 months, with longer periods acceptable for occurrences that warrant them. The report must also carry a risk classification : the method is left free, but the field is mandatory, and Delegated Regulation (EU) 2020/2034 of 6 October 2020 introduced the common European risk classification scheme, ERCS, which an operator may adopt if it wishes.

On the receiving end, in France the word « Authority » means the DSAC (or OSAC depending on the field). For drone operators the DSAC provides a dedicated form, CRESUS — a safety occurrence report for unmanned aircraft systems —, published under the heading « exploitation drone » and accompanied by a completion guide. Responsibility for sending it lies with the UAS operator, not the remote pilot : an employed remote pilot fills the form in and passes it to their employer, with whom they complete the Analysis section — which is also what allows the employer to act across the whole operation. A copy goes to the interregional DSAC office, shown on the operator's AlphaTango account for operators declared under the national scenarios. Organisations now submit through the European ECCAIRS 2 platform (« E2 »), either by electronic form or in the standard E5X format exported from their own safety management software — Article 7 of the regulation requires a format compatible with ECCAIRS and the ADREP taxonomy. An often-overlooked point : reports must be de-identified, carrying nothing that would allow the people involved to be identified.

None of this holds up without internal traceability. The exact take-off time, the firmware version, the battery state, the observed weather, the name of the designated remote pilot, the maintenance status : the form asks for all of it, and a properly run operation will find it in the documents described in our guide to the operations manual, flight file and maintenance log. An operator who discovers after the fact that they cannot reconstruct their flying day does not have a reporting problem : they have a documentation problem.

The safety investigation bureau: an inquiry apart from everything else

The occurrence report goes to the civil aviation authority. Above it sits a second tier reserved for the heaviest cases : the safety investigation, run by an independent body — in France the BEA, the civil aviation safety investigation bureau. It falls under Regulation (EU) No 996/2010 on the investigation and prevention of accidents and incidents in civil aviation, whose first article states unambiguously that an investigation has the sole objective of preventing accidents and incidents, without apportioning blame or liability. It is neither a criminal inquiry nor a compliance audit : the bureau looks for causes, not culprits, and its conclusions are not meant to found legal proceedings.

The notification duty here is separate from the one in Regulation 376/2014. Article 9(1) of Regulation 996/2010 provides that any person involved who becomes aware that an accident or serious incident has occurred shall notify the safety investigation authority without delay. In practice, the French authority states that where the reported occurrence is an accident or a serious incident, a copy of the report must also be sent to the BEA, at its duty address. So two submissions for a single event : one to the civil aviation authority for experience feedback, one to the bureau for the safety investigation.

Should an investigation be expected after every drone incident? No, and the text says so. Article 5 of Regulation 996/2010, as amended by Regulation (EU) 2018/1139, allows the investigation authority to decide not to open a safety investigation in a range of cases — including that of an unmanned aircraft for which no certificate or declaration is required under Article 56 of Regulation 2018/1139 — provided nobody has been killed or seriously injured. In other words : for the vast majority of professional drones under 25 kg operated in the open or specific category, opening an investigation remains a judgement call for the bureau, based on the safety lessons expected — not an automatic step. Which does not mean « never » : the bureau's notified-occurrence database does list drone investigations, including one opened after an event on 14 July 2019 at Le Barcarès involving a DJI Inspire 2 — collision with an obstacle, uncontrolled descent, impact with people on the ground.

One useful point for operators working near airports : an unintended incursion into controlled airspace or into an aerodrome perimeter is a matter for occurrence reporting, not for a safety investigation, so long as it has not escalated into an accident or serious incident. It is best prevented by protocol : our guide to flying a drone mission inside an airport CTR sets out who authorises what and within what lead times, which remains the best way never to have to report that kind of event at all.

Just culture: what the operator must guarantee its remote pilot in writing

A reporting system only works if reporting costs the reporter nothing. That is the whole point of just culture, defined by Regulation 376/2014 as « a culture in which front-line operators or other persons are not punished for actions, omissions or decisions taken by them that are commensurate with their experience and training, but in which gross negligence, wilful violations and destructive acts are not tolerated ».

The protection is legal, not merely moral. Article 16 of the regulation protects the source of the information and prohibits an employee from being prejudiced on account of a report, save for wilful misconduct or a manifest, severe and serious disregard of an obvious risk. French law follows suit with Article L. 6223-2 of the transport code : no administrative, disciplinary or professional sanction may be imposed on a person who has reported an occurrence, whether or not they were involved in it, unless they were themselves guilty of a deliberate or repeated breach of safety rules. The regulation goes further still : Article 16(11) requires every organisation to adopt written internal rules describing how these principles are guaranteed. For a drone operator employing one or several remote pilots, this is no boilerplate : it is a document to draft, circulate and maintain. The French authority has also set up a just culture observatory, which anyone who believes they have been harmed by a breach of these principles may refer a case to.

The hard question remains, and the regulation does not fully settle it : where exactly does the line run between excusable error and punishable fault? S. W. A. Dekker, in a much-cited 2009 paper in Cognition, Technology & Work titled « Just culture: who gets to draw the line? », argues that the line is never given in advance : it is drawn by someone, so the real governance question is who draws it, through what procedure, and with what legitimacy in the eyes of those expected to report (see the study on Google Scholar). The practical lesson for a small drone outfit is simple : if the owner alone decides after the fact, case by case, what counts as a fault, no remote pilot will volunteer the flight where they nearly hit a power line. Writing the rule before the incident beats improvising it afterwards.

This aviation duty also meets employment law, with which it should not be confused : protecting the reporter does not relieve the employer of its prevention and occupational risk assessment duties, which we cover in our guide to the workplace safety obligations of an employed drone pilot. One and the same event can therefore feed both a report to the authority and an update to the workplace risk assessment.

The insurer: a second track, with its own deadline and its own sanction

Notifying the insurer follows the opposite logic to the occurrence report : it is contractual, names names, and its purpose is precisely compensation. Its deadline is set by the policy, but Article L. 113-2 of the French insurance code imposes a floor : at least five working days from the moment the insured becomes aware of the loss (two working days for theft). Many professional policies simply adopt that floor, which in practice makes it a shorter deadline than the safety report — hence the value of handling the two in parallel, the same day, rather than one after the other.

The penalty for lateness is not automatic. The same article specifies that forfeiture for late notification, where a policy clause provides for it, can only be raised against the insured if the insurer establishes that the delay caused it prejudice. That is genuine protection, but it is better not to have to rely on it : a claim filed out of time starts any negotiation at a disadvantage. The covers themselves, the insurance obligation and typical premium levels are set out in our guide to professional drone liability insurance.

Beware the opposite temptation : settling amicably with the client to avoid opening a claim does not remove the occurrence reporting duty. The two obligations share neither their legal basis, nor their recipient, nor their purpose — one repairs a private loss, the other feeds collective safety. Conversely, an operator who reports properly to the authority but neglects its insurer risks bearing the cost of the damage alone ; and where the disagreement is about the service itself — lost deliverables, a job to redo, delay —, the route is different again, the one described in our guide to disputes with a drone contractor.

On an industrial site: stopping the job, co-activity, and what the client should receive

For a sole operator, an incident ends with an aircraft to repair and a form to fill in. On a live industrial site, it triggers something far wider. A drone coming down in an ATEX zone, onto a manned workstation, into a retention basin or across a vehicle route is no longer an operator's problem : it is a site event, touching co-activity, the prevention plan and sometimes the user company's own workplace accident analysis.

Good practice on such sites is to have decided before the job what triggers an immediate stop to flying and who calls that stop — the site manager or the operator. A properly built prevention plan already covers this, alongside third-party exclusion zones and alerting arrangements ; our guide to hosting a drone mission on an industrial site sets out that preparation, co-activity included. An incident that happens without that framework always leaves the same scene : two companies arguing at the foot of the drone while production carries on around them.

What the client should then receive comes down to four items : proof of reporting (de-identified copy and date), the analysis and its risk classification, the written corrective measures, and the conditions for resuming the job. These exist in any case, since the regulation requires them of the operator within 30 days and then 3 months : the only question is whether your contract provides for them to be passed on to you. For a public buyer, the natural place for that requirement is the tender specification — our guide to buying drone services through public procurement shows where to slot it among the other technical documents.

One final, more strategic point : how a contractor talks about its past incidents is one of the best indicators of its maturity. An operator who has « never had the slightest problem » across several hundred flight hours is mostly telling you they keep no records — the sector's loss data does not make that claim credible. Conversely, an operator who describes an incident, the corrective measure adopted and what changed in their procedure is showing you their safety system at work. That is a selection criterion in its own right, to be added to those listed in our guide to choosing a professional drone pilot.

Method and price: putting a reporting scheme in place that holds up

The method comes down to five moves, best prepared once and for all rather than improvised in shock. One : make people and the site safe, then freeze the evidence — photographs of the final position, flight logs from the aircraft and the controller, weather records, written witness accounts the same day. Two : qualify the occurrence — injury, certified drone, crewed aircraft involved? Any occurrence list attached to the operational authorisation? When in doubt, the French authority is explicit : do not hesitate to submit, since failing to pass on an occurrence whose seriousness went unnoticed is worse than the reverse. Three : trigger both tracks the same day — the occurrence report to the civil aviation authority (with a copy to the investigation bureau for an accident or serious incident), and the claim to the insurer. Four : analyse and classify by risk, with the first version within 30 days. Five : write the corrective measure and carry it into the operations manual, the procedure or the training programme — an occurrence that changes nothing has produced no lesson at all.

Typical 2026 figures, excluding VAT, for an operator who structures this rather than discovering it under pressure : drafting the internal just culture rules and the reporting procedure, aligned with the existing operations manual, runs €600 to €1,500 excl. VAT depending on team size and whether a safety management system already exists. An audit of an operator's documentation (operations manual, flight files, maintenance logs, the traceability reporting depends on) runs €800 to €2,000 excl. VAT. Support in handling an actual occurrence — qualification, drafting the report, analysis and corrective measures, exchanges with the authority — sits rather at €900 to €1,800 excl. VAT, including the final three-month analysis. Finally, resuming an interrupted job after an incident, with the flight plan, exclusion zones and prevention plan revised, generally means €400 to €900 excl. VAT of preparation on top of the cost of the flying day itself.

Set against the cost of a halted site, a disputed insurance claim or an operational authorisation renewed with conditions, these amounts are marginal. The real cost of having no scheme is not financial : it is the time lost reconstructing, at speed and under client pressure, a flying day nobody kept a record of. For a mission on a sensitive site, a resumption after an incident, or an upgrade to your operational documentation, request a quote stating your operating category, the type of site and your target date.

Frequently asked questions

Request a free quote

Also worth reading

• Flying a Drone Indoors on a Professional Site: Legal Framework, Uses, Price
• Drone Inspection and Thermography of a Battery Energy Storage Site (BESS): Method, French ICPE Framework, Price
• Detecting Downy and Powdery Mildew in Vineyards with a Multispectral Drone: What the Imagery Really Shows