The difference between a chaotic drone operation and a calm one isn’t the equipment. It’s the procedures. Standard Operating Procedures (SOPs) are detailed, step-by-step instructions for getting a mission done the same way every time — same way each time, regardless of weather, client pressure or fatigue. They’re what the CAA expects to see in an Operations Manual, and they’re what we run on every Recon mission.

The five decision pillars

Before any flight, the Remote Pilot in Command (RPIC) needs to be able to answer five things:

  1. Scope. I have a clear tasking. I know exactly what the client wants, where and when.
  2. Competence. I am qualified, current and competent to carry out this operation with this aircraft.
  3. Location knowledge. I understand the site: ground risk, air risk, access, emergency landing options, people, vehicles, public interface.
  4. Risk assessment. I can identify the hazards, apply the correct controls and justify that the residual risk is tolerable.
  5. Go / No-Go. Based on the above, it is safe and lawful to start. If not, the answer is No-Go.

If any pillar is missing or weak, the mission either gets delayed, re-scoped, or cancelled. The pilot has standing authority to say No — that’s baked into the Operations Manual.

Pre-flight planning

The bulk of the work is done before anyone leaves the office. We use a stack of planning tools:

  • Altitude Angel / SkyDemon Light / Drone Assist — airspace structure, controlled airspace, FRZs, active or planned NOTAMs.
  • 1:250,000 aviation chart — the authoritative reference for airspace classification, nearby aerodromes, ATZ/FRZ boundaries.
  • Google / Bing Maps (aerial and street view) — takeoff and landing areas, ground risk, public access routes, power lines, masts, vehicle flow.
  • Ordnance Survey mapping — terrain, footpaths, rights of way, water features, restricted access, elevation contours.
  • NATS airspace overlays — live restrictions data.

Out of this comes a job pack: client tasking, airspace classification, identified hazards (air and ground), the planned flight geography, initial hazard assessment with mitigations, and the explicit conditions attached to safe flight. Written down, in a controlled format. If it isn’t recorded, it doesn’t protect anyone.

The operational volume

UK rules require the operator to define the operational volume — the local area at risk — before flight. This is composed of:

  • Flight geography — where the flight is intended to take place.
  • Contingency volume — the buffer around the flight geography where the aircraft might end up if something goes wrong but is still recoverable.

If the aircraft leaves the operational volume, emergency procedures activate immediately. The volume is built with two buffers in mind:

  • Ground risk buffer — at minimum the 1:1 rule (a flight at 50 m altitude needs a 50 m horizontal buffer beyond the operational volume) to protect third parties below.
  • Air risk buffer — the operational volume must sit outside any airspace restrictions unless we hold appropriate permission, and the proximity to nearby crewed-aircraft activity must be assessed before flight.

Pre-notification

People who may need to know about the flight before it happens:

  • Neighbours and site occupants — to avoid alarm and prevent people walking into the operating area.
  • Local police force control room — to prevent a 999 call for "suspicious drone activity."
  • Local authority / council — if operating on or over council property, highways, parks or town centres.
  • Highway agency, port authority, rail operator, utility owner — if near critical infrastructure or live traffic.
  • Nearby airfields, heli routes, aero clubs — to coordinate on low-level activity.
  • ATC / NATS — where the flight is in or near controlled airspace.
  • NOTAM — for operations that warrant warning other airspace users.

And the one that catches operators out: landowner permission. Without it, your insurance may be void, any damage on site may be blamed on you, and your operator name gets attached to "drone cowboy" stories that don’t go away.

The on-site recce

Plans made in the office are tested against reality on site:

  • Walk the perimeter. Has anything changed since the satellite image?
  • Imminent weather check — wind speed, direction, gust, cloud, precipitation likelihood.
  • Meet the client and agree a brief toolbox talk — what we’re going to do, what they need to do (or not do).
  • Lay out the takeoff and landing area. Mark it. Cones and tape if needed.
  • Confirm the operational volume against the actual ground. Adjust if reality has moved.

If site reality contradicts the plan, the plan loses. Re-plan or No-Go.

The crew briefing

Even a single-pilot operation benefits from a verbal brief — either to a spotter, the client acting as a designated lookout, or as a focusing exercise alone. A good briefing covers:

  • Mission — what we’re doing and why.
  • Airspace — where we’re flying, what restrictions or NOTAMs apply.
  • Ground risk — who or what is on the ground that we’re managing.
  • Weather — current and any forecast changes.
  • Roles — RPIC, spotter, payload operator.
  • Communications — agreed callouts, closed-loop acknowledgements (e.g. "Battery 30%, recommend recover" — "Copy, returning to land now").
  • Triggers — low battery limit, loss of VLOS, ground incursion, unexpected crew illness.
  • Emergency actions — loss of link, flyaway, public incursion, pilot incapacitation. Where we land if we need to get down immediately.

In-flight discipline: the scan

The single most important in-flight habit. Divide attention systematically and repeatedly across:

  • The UAS itself — orientation, attitude, controllability.
  • The airspace — other aircraft, birds, weather changes.
  • The ground — people, vehicles, livestock approaching the area.
  • The telemetry — battery state of charge, link strength, GPS fix.
  • Your blind spot — whatever direction you haven’t checked recently.

Repeat continuously. The point is that the scan happens whether you feel sharp or not.

Emergencies

Every Operations Manual lists emergency procedures. The common ones:

  • Loss of control link — aircraft enters its programmed failsafe, usually return-to-home or hover-and-land. Crew clears the landing area.
  • Loss of GNSS — aircraft falls back to attitude-only mode. Pilot manually controls; if conditions don’t allow safe manual flight, land immediately.
  • Flyaway — the aircraft is in flight but not under pilot control and heading away. Attempt to regain control; note flight path, height, direction; estimate remaining flight time; contact nearest ATC immediately if it will enter controlled airspace.
  • Fire / structural failure — land immediately, clear personnel, fire extinguisher to hand.
  • Pilot incapacitation — the spotter or designated crew member activates Return-to-Home (rehearsed during the brief), waits for the aircraft to land and shut down, then administers first aid. The most common cause of pilot incapacitation, perhaps surprisingly, is food poisoning.
  • Air incursion — crewed aircraft enters the operational volume. Land immediately. Give way is the rule, always.
  • Ground incursion — an uninvolved person enters the operational area. Hover at safe altitude, redirect via the spotter, wait for the area to clear, or land if needed.

Post-flight

After the motors stop:

  1. Make the aircraft safe — disarm, disconnect battery for transport, cool batteries before charging or storage.
  2. Aircraft check — visual inspection for damage, propeller condition, sensor cleanliness.
  3. Record keeping — flight times for aircraft log and pilot log, battery cycles, any anomalies.
  4. Crew debrief — soon after flight, open and honest. What worked, what didn’t, what we’d change. Feed lessons into the Operations Manual.

The post-flight debrief is where SOPs evolve. Procedures that lived only in someone’s head get written down. Near-misses that didn’t become incidents get documented. The Operations Manual ages forward.

Why this matters

An Operational Authorisation is a privilege the CAA grants on the basis that the operator will follow a defined set of procedures. If we don’t follow our SOPs, we’re not operating under our OA — legally, we’re a different operator from the one the CAA authorised. The SOPs aren’t bureaucracy. They’re what makes the authorisation real.