HADR foundationsApplied foundation · HADR coordinatorsPublic review edition

Drones in HADR

Choose missions from actual needs, interpret imagery and delivery limits, protect data and revise a plan through a fictional CPX producing KSEC evidence.

AI-generated illustration of HADR learning and exercise, not an actual event
AI-generated learning illustration, not a record of an actual event.
A learning synthesis based on the listed sources, not yet endorsed by an expert reviewer. Activities and rubrics are proposed by this project.

What will you be able to do?

From outcomes to observable evidence

drones-hadr · v0.1.0

Intended outcomes

Knowledge

Explain a drone mission’s potential, limits and unresolved information.

Skills

Draft a mission request and handover separating observation from interpretation.

Ethics

Justify data necessity, recipients and consequences for affected people.

Character

Take responsibility for correcting conclusions and handing over unknowns.

Practise through an activity

Original three-round CPX: release Cards A–C in order and rotate the liaison after C. Submit the mission draft, evidence table, internal/public text and reasoned change log. Assess one rubric criterion per KSEC domain using examples from two rounds. Have a handover recipient restate pending work, then revise the final version. This is tabletop learning: no flying, real permission requests or remote-pilot certification.

Collect evidence for assessment

Knowledge

A sourced question–data–limitations table and reasoned quiz responses.

DRONE-K
Skills

Mission draft, evidence checks and GIS/SITREP text before and after an inject.

DRONE-S
Ethics

A privacy decision record and a response to the fictional community concern.

DRONE-E
Character

Two revision rounds and assessor observations of listening/accountability; not proof of a lasting personal trait.

DRONE-C

Project learning synthesis showing proposed outcomes, activity and evidence. This is not a university-endorsed assessment framework.

Module references:[aviation-wfp-drones][aviation-wfp-mozambique-2020][aviation-unicef-supply][aviation-icrc-drones-2024][aviation-wfp-data-2025][aviation-caat-nan-2026][aviation-icao-utm-overview][aviation-caat-no16-2026][aviation-nbtc-registration]

Suggested preparation: HADR foundations and people-centred assistance Assessing needs and writing a situation note

Start with the assistance question

Scope as of 15 October 2026: a public-review lesson without documented aviation-expert endorsement. It is neither flight clearance nor an operational briefing. Recheck restrictions for the date, time, area and mission type before real use. All CPX data are fictional.

WFP describes drones supporting assessment, search, communications and preparedness, alongside aviation safety, privacy, law and public trust. This lesson develops coordination and information use; it does not teach aircraft handling or certify operators.

Project synthesis: first name the decision maker, decision, deadline and useful product. A coordinator choosing where to send a route assessment team needs a map of areas needing further checks, not simply attractive footage. Compare existing records, community reports, satellite imagery and ground assessment. If available information already answers the question, record why an additional flight adds little.

Imagery is one part of the evidence

WFP’s account of Mozambique in 2019, published on 31 January 2020, describes drone imagery feeding maps after Idai and Kenneth and notes that image analysis still took days. It distinguishes capture time from decision-ready information; it does not establish accuracy for every system.

Original project evidence check: record capture time, visible/unseen area, file provenance, analyst and outstanding verification. Separate ‘image set A shows no vehicles on the bridge’ from ‘the bridge is safe for vehicles’. The latter lacks evidence in this exercise. Refer the question to an appropriate assessor and carry the limitation into GIS/SITREP products. Do not turn an imagery gap into proof that nobody needs assistance.

Match limitations to the mission

UNICEF §§2–3 connect supply-chain needs with distance, payload weight/volume, connectivity, weather, energy, maintenance and local capacity. Platforms differ in weather tolerance and carriage capability; one platform’s capability does not establish suitability for every mission. Health-product transport also requires attention to product condition.

Project application: request capability evidence and procedures from the responsible operator; do not invent altitude, separation, wind, battery or temperature limits. If an exercise adds medicine delivery, create a separate request covering the receiver, handover, destination readiness and questions for specialists/authorities. Having a mapping drone present is not evidence of medical-delivery readiness.

Original sources: [aviation-unicef-supply]

Protect people when framing the task

ICRC Chapter 7 cautions that data without immediately identifiable individuals may still affect groups, and consulting community leaders is not everyone’s individual consent. Assess the processing basis in context; an emergency does not erase data-protection responsibilities. WFP guidance supports collecting only necessary data and limiting access.

Original exercise: prepare an understandable mission explanation and a contact for concerns. Separate internal and public products, justifying what each recipient needs. Assign publication review and a retention-review date in the fictional plan. Face masking is not an automatic solution if text, location or context still exposes the community’s concern.

Thai case: search support in Nan

CAAT’s 22 August 2026 article reports drones supporting a 21 August missing-person search on the Nan River in Wiang Sa, alongside police drone personnel and local rescuers. It describes facilitated permission requests through UAS Portal subject to safety conditions. The account supports surveying and coordination roles; it does not establish a successful search outcome or permission-free flying.

Learning synthesis: distinguish humanitarian need, operator readiness, relevant registrations and mission authorization. Registration is not permission to fly everywhere; emergency purpose is not a blanket exemption. Continue with the airspace coordination lesson to practise checking date-, time- and location-specific restrictions. This lesson does not replace an actual operational check.

Fictional CPX: actionable stimulus cards

Entirely original exercise: fictional ‘Khlong Ruam Chai’ has no real coordinates. Use a tabletop and text cards only. Assign an information requester, fictional drone operator, GIS analyst, community representative and aviation liaison. The educator controls play. T+ denotes exercise minutes, not notice validity or a response standard. Use no real personal imagery and submit no real flight request.

Card A — T+0 / requester: ‘The exercise centre must choose where to send route assessors for clinic C this round. Fictional 08:00 image A shows parts of the west road and a bridge, with no view beneath it. A fictional 08:20 community report describes water on the east road, unverified. Registration records exist, but this mission’s authorization is absent.’ Task: draft the mission question, desired product and unresolved checks. Do not label the route safe or the aircraft cleared.

Card B — T+10 / community and operator: ‘An image caption names household X as an aid recipient; a member objects to publication. The operator has not confirmed weather and capability for a new request. The clinic asks whether the same aircraft can deliver medicine.’ Task: produce a minimized sharing version with recipient rationale, separate the medicine request and identify information alternatives without adding a flight this round.

Card C — T+20 / aviation liaison: ‘A helicopter support request for the clinic concerns the same exercise area; timing is unconfirmed. Exercise control requires the drone request to remain on hold pending the aviation role’s response. The analyst discovers image A’s filename indicates the previous day, conflicting with its label.’ Task: record the hold, query imagery time and shared operations, revise GIS/SITREP and hand over to a replacement colleague. Invent no separation distance or authorization.

Submit traceable learning evidence

Original deliverables: (1) a one-page mission draft naming the information user, question, fictional area, product, alternatives and authorization status; (2) an observation–interpretation–verification table; (3) internal GIS/SITREP text and a minimized public message; (4) an inject change log recording new information, previous conclusion, revised conclusion, rationale, owner and recipients notified. Retain earlier versions for comparison.

Facilitator interpretation: after A, neither route safety nor flight clearance is established. After B, separate mapping from carriage and reduce disclosure. After C, retract conclusions dependent on the old timestamp and retain the card’s hold. Ask the receiver to restate outstanding checks and owners. Observe at least two rounds and ask learners for their reasoning. The quiz samples understanding; S/E/C require products and observed behaviour. Five answers cannot certify flying competence or lasting character.

See the process at a glance

A synthesized learning diagram. Read it alongside the lesson and original sources.

  1. Frame the question

    Name the decision, information recipient and available alternatives.

  2. Check conditions

    Separate capability, evidence, protection and authorization status.

  3. Analyse and hand over

    Relay observations with time, coverage, limitations and ownership.

  4. Revise and explain

    Use injects to revise with reasons and check receiver understanding.

Fictional learning scenario

Explore a decision

Fictional scenario: the team has partial road imagery and drone registration, but mission authorization is absent. The liaison reports a helicopter request for the same area. What should the tabletop team propose?

From knowledge to evidence

Original three-round CPX: release Cards A–C in order and rotate the liaison after C. Submit the mission draft, evidence table, internal/public text and reasoned change log. Assess one rubric criterion per KSEC domain using examples from two rounds. Have a handover recipient restate pending work, then revise the final version. This is tabletop learning: no flying, real permission requests or remote-pilot certification.

CriterionProficientDeveloping
K · Evidence boundariesExplains benefits and limits with sources and invents no authorization.Treats imagery or registration as proof of safety/unrestricted permission.
S · Handover productDraft and SITREP separate observations, conclusions and checks with owners.Mixes information with conclusions or omits outstanding checks.
E · Necessity and affected peopleJustifies minimization, recipients and concern handling without assumed proxy consent.Discloses beyond the task or substitutes leader consent for everyone.
C · Accountable revisionTwo rounds show listening, correction and receiver understanding of pending work.Conceals revisions or leaves questions without a successor.

A proposed rubric for educators to adapt, not a university accreditation standard.

Check your understanding

Answer all 5 questions, then review the explanations. This score is for self-study.

1Which request starts from the information user’s decision?
2Image A cannot show beneath the bridge. Which fictional SITREP statement fits?
3A community leader welcomes imagery. What follows for personal data?
4When Card C makes the image timestamp uncertain, which evidence shows accountability in the exercise?
5What does CAAT’s Nan search account support?

Continue with connected learning

Lessons that build on this topic. Choose according to your interests.

  • Airspace coordination in HADRDistinguish roles and authority, check sources of flight restrictions and coordinate drone, helicopter, medical and logistics requests through three fictional CPX updates.

References & further verification

Cite this module

PK-Research. (2026). Drones in HADR (drones-hadr, v0.1.0). HADR–CPX Knowledge Commons. https://hadr-cpx.pk-research.work/en/modules/drones-hadr/