What Happens If the Drone Comes Down on Your Site

Most drone jobs end with files. Occasionally one ends with an aircraft on the ground somewhere it was not meant to be: in a stockpile, on a pipe rack, against a fence, or in the bush half a kilometre from where it took off. It is uncommon, and every operator who flies enough has had something like it happen.

What follows is not a legal opinion and it is not a substitute for your own health and safety procedures. It is a description of how this plays out on an Alberta industrial or construction site, who has to tell whom, and the handful of decisions in the first hour that determine whether the rest of it is straightforward or expensive.

The first hour

The order matters, and it is not the order instinct suggests.

• Stop work and account for people. Treat it as you would any other dropped load or equipment failure. Nobody approaches until the area is controlled.
• Treat the battery as the hazard. This is the part site teams get wrong. A crushed or punctured lithium polymer pack can go into thermal runaway, and it does not always do so immediately. The approach distance, the extinguisher type and who is allowed near it are the pilot's call and should already be in the flight plan. If there is any sign of swelling, smoke or heat, it stays where it is and the area stays clear.
• Secure the area rather than clear it. Barricade and post somebody. The temptation is to pick the drone up and get the site moving again, and that is the single most common mistake because of the next point.
• Photograph before anything moves. Position, orientation, what it struck, the surrounding ground. From several angles and with something in frame for scale. This takes two minutes and it is the record that settles the argument later.
• Leave the wreckage in place. Beyond what safety requires, nothing gets moved or recovered until the operator has confirmed there is no obligation to preserve the scene. An aircraft occurrence can carry a preservation duty, and a well-meant cleanup can remove the evidence that would have exonerated everyone.
• Get the pilot's account while it is fresh. Written, same day, in their words, before anybody has had time to think about how it reads.

Who has to report, and to whom

This is where site owners tend to assume more exposure than they have. The aviation side of it is the operator's duty, not yours.

• Transport Canada and the aviation occurrence regime: the drone crew. Remotely piloted aircraft operations in Canada sit under the Canadian Aviation Regulations, which place the duty to report a defined occurrence on the pilot of the aircraft, while the separate Transportation Safety Board occurrence regime places its reporting duties on the owner or operator. The split matters when you are chasing the paperwork, but either way the duty is the contractor's rather than yours, and the thresholds and mechanics are set by the regulations and are theirs to know and discharge. As a buyer you are entitled to ask whether a report was required and whether it was filed, and a competent contractor will tell you without being pushed. Do not accept an assurance that no report was needed without a reason attached. The broader regulatory picture is summarised in the 2026 Alberta drone regulation update, and the compliance paperwork worth checking before a contractor arrives is covered in how to vet a commercial drone contractor.
• Your own incident system: you. A contractor incident on your site is a contractor incident. It goes into your reporting, your investigation process and your contractor management record on the same terms as any other. If a person was injured, or if the circumstances were such that a person could have been seriously injured, the provincial occupational health and safety reporting obligations that already apply to your operation apply here too. Those are set by Alberta's occupational health and safety legislation rather than by anything drone-specific, and your own advisor is the right person to apply them to the facts.
• Your client or the asset owner: usually you. If you are a contractor flying a drone contractor over somebody else's plant, the notification chain in your own contract is the one that governs, and it is typically faster than any regulatory clock.
• The utility, the road authority or the operator of whatever was struck. If the drone contacted third-party infrastructure, that party has to be told immediately and will have its own process. The reasons those parties set standoffs in the first place are covered in the companion piece on flying near a transmission line, wind farm or active rig.

The evidence, and how fast it disappears

A drone incident is unusually well documented compared with most equipment failures, because the aircraft was recording itself the whole time. The evidence exists, and it lives on devices that get reused.

Ask in writing, on the day, for the flight log for the flight in question, the controller telemetry, the imagery and video captured up to the event, and the maintenance record for that airframe and that battery. A professional operator has all of it and will share it. The flight log is the item that matters most, because it carries altitude, position, control inputs and any warnings the aircraft raised, and it answers the question that otherwise becomes a dispute: what was the aircraft doing at the moment it stopped flying.

Keep your own record alongside it. The photographs from before anything moved, the names of everyone in the area, the weather at the time, the work that was underway nearby, and the authorisation under which the flight was being conducted. If conditions were part of the cause, note them specifically; the thresholds that should have grounded the flight are set out in wind limits on a drone survey.

Where the money actually gets decided

The outcome of a drone incident is largely determined before the drone ever arrives, by the insurance position you either verified or did not. Three things do the work:

• Aviation liability, at a limit that matches what is under the flight path. General commercial liability frequently excludes aircraft operations, which is why an aviation-specific policy is the one that matters. A limit appropriate to a bare field is not appropriate above a process unit.
• Additional insured status, if your contract requires it. Named on the certificate, not promised in an email.
• Hull coverage on the aircraft. This one is not for your benefit. It is the reason a contractor who wrecks an expensive airframe over your pond stays solvent and stays reasonable about the rest of it.

How to read the certificate, and the specific entries worth checking, is covered in reading a drone contractor's certificate of insurance. The short version is that this is a five-minute check before a job and an unrecoverable omission afterwards.

What to settle before the flight

Everything above is easier if four things were agreed in advance, and all four belong in the pre-flight conversation described in how to prepare your site for a drone survey:

• The emergency plan, in the flight plan. Where the aircraft is intended to come down if something fails, what the pilot does, and who they call on your site. A professional operator brings this. Read it rather than filing it.
• Who the pilot calls, by name and number. Not the main switchboard. The person who can stop work in the affected area.
• What is underneath the flight path. Occupied buildings, live process equipment, public road, rail, water. This is the input to both the flight plan and the insurance limit, and it is the reason an operator may refuse to overfly part of a site.
• The reporting expectation, in writing. That the contractor will notify you of any occurrence, near miss included, within a stated period, and will provide the flight log and imagery on request.

Treat the near miss the same way

A link lost over a tank farm that recovered on its own, a return-to-home that clipped a handrail, a battery warning that forced a landing in the yard. None of these produce damage and all of them have the same causes as the event that does. Put them through the same debrief, and look for the pattern across jobs rather than at the single event. The useful question after an occurrence is not whose fault it was. It is whether the same flight, flown the same way next month, would end the same way.

Handled properly, a drone incident is a contained event with a clear owner, a documented cause and an insurer who pays. Handled by moving the wreckage, cleaning up the site and sorting it out later, it becomes an argument with no evidence in it. The difference is almost entirely the first hour.