Risk assessment sounds like paperwork. In practice it is sitting down for fifteen minutes and thinking about what could go wrong — and that alone prevents most incidents.
Identifying hazards
Harm to people below. An aircraft falling on someone. The most serious in consequence.
Conflict with crewed aircraft. Catastrophic if it occurs.
Property damage. Buildings, vehicles, crops, livestock.
Loss of the aircraft. Water landing, flyaway, unrecoverable position.
Harm to the crew. Terrain, weather, chemicals where spraying is involved.
Regulatory exposure. Unpermitted flight, restricted airspace, privacy intrusion.
Data loss or disclosure.
Schedule risk. Extended bad weather, equipment failure, permission not granted in time.
Reputational risk. An incident that reaches the public affects future work well beyond its direct cost, and it is rarely counted in an assessment that only looks at physical harm.
How to identify them. Walk mentally through each phase of the operation and ask what could go wrong at this step.
Assessing severity
Two dimensions. Likelihood and consequence, combined into a risk level.
Likelihood. Judged from experience and the specific situation. Flying above a busy area makes the presence of people in the fall zone near certain.
Consequence. From minor damage through to serious injury.
Priority. High-consequence risks demand treatment even at low likelihood. Collision with a crewed aircraft is the obvious example.
Acceptable risk. There is a level below which you proceed. Define it in advance rather than deciding in the moment.
Accumulation. Several modest risks together — strong wind, an inexperienced pilot, unfamiliar terrain, time pressure — combine into a large one.
That accumulation is what gets overlooked. Each factor is individually tolerable; the combination is not.
Write it down. Writing forces clear thinking and creates evidence that the assessment happened.
Mitigation
Order of preference. Eliminate, then reduce, then control by procedure, then prepare a response.
Eliminate. Do not overfly the housing if an alternative route exists. Simplest and most effective.
Reduce. Lower altitude, slower flight, timing when fewer people are present.
Separate. Cordon the area beneath the flight path, post a spotter.
Procedure. Pre-flight checklist, stop criteria, clear role allocation.
Equipment. Parachute systems on larger aircraft, conspicuity lighting, redundancy.
Crew competence. Experienced pilot for complex tasking.
Insurance. Does not reduce risk but limits financial consequence.
Rehearse the response. A plan nobody has walked through is a plan that will be improvised badly under pressure. Talking it aloud once costs five minutes.
Response plan. If it happens, what do we do. Prepared in advance means a correct reaction rather than an improvised one.
Deciding whether to fly
Set criteria beforehand. Which conditions mean no flight. Decided before travelling to site.
Why that timing matters. On site there is pressure — distance travelled, client waiting, cost already incurred. Pressure lowers standards.
Who can stop. Anyone on the crew. An observer who sees a hazard must be able to say so and be listened to.
No blame culture. Someone who stops a flight out of concern is not criticised. If they are, they stay silent next time.
Reassess when conditions change. Wind rising, cloud arriving, people entering the area. A plan is not a commitment.
Stopping mid-task is legitimate. Land and reassess.
Explain honestly to the client. Professional clients respect a safety decision.
Cover it contractually. A clause on postponement for weather or unsafe conditions removes the choice between safety and revenue.
Learning from occurrences
Report everything. Including near misses. A near miss is a free warning.
Do not look for someone to blame. Look for the systemic cause. Blame ends reporting.
Ask why repeatedly. The pilot did not see the wire — because the site was not surveyed — because time was short — because the schedule was unrealistic.
Fix at the system level. Add a step, change the planning method, improve training.
Share within the team. Everyone learns from one person's experience.
Share with the wider community. Where the lesson is general. This field is young and shared experience is valuable.
Review periodically. Aggregate occurrences by quarter. Recurring categories point to where the system needs attention.
Close the loop with whoever reported. Telling them what changed as a result is what convinces the rest of the team that reporting is worth doing.
Recognise good decisions. The person who stopped a flight at the right moment, or spotted a problem before launch. Recognition reinforces safe behaviour far more effectively than punishing unsafe behaviour.
Frequently asked questions
Which factor is most often overlooked in risk assessment?
Accumulation. Strong wind, an inexperienced pilot, unfamiliar terrain and time pressure are each individually tolerable, but combined they are not.
Why set stop criteria before arriving on site?
Because at the site there is pressure from distance travelled, a waiting client and costs already incurred — and pressure lowers standards.
What is the correct order of mitigation?
Eliminate the hazard first, then reduce it, then control by procedure, then prepare a response. Measures relying on human compliance are the weakest.
Why avoid assigning blame after an incident?
Because blame ends reporting, and the organisation loses its most valuable source of information about how to prevent the next one.
More in Search and rescue and Sensors and payloads.
