Drone Safety and Regulations: Agriculture, Facility Cleaning, Logistics, and Emergency Services

Regulatory evolution and global models

International standard‑setting has moved from permissive guidance to structured model regulations designed to be adopted or adapted by States; ICAO publishes model UAS regulatory Parts (101, 102 and 149), a UAS Toolkit and U-AID guidance that regulators use as a template for national rules and aviation‑safety harmonisation [1][2][3].

Two concrete numeric anchors in ICAO model material commonly used for national thresholds are: registration/inspection triggers at ~15 kg and higher‑risk operation thresholds around 25 kg — these model cutoffs frequently inform national categorisations and are useful comparative markers when assessing national divergence [1].

ICAO also curates operational toolkits (UTM guidance, SORA/JARUS references and humanitarian U-AID materials) that explicitly encourage States to adopt risk‑based safety management and to provide pre‑packaged templates for CONOPS, ORA/SORA and expedited humanitarian approvals [2][3].

Why risk‑based approaches dominate modern regulation

Modern regimes emphasise structured risk assessment (concepts such as SORA/JARUS or ICAO ORA) rather than strictly prescriptive rules; regulators require operators to present an evidence‑based CONOPS and mitigations (ground‑risk and air‑risk reasoning) so that approvals match the actual operational exposure rather than arbitrary ceilings [5][3].

ICAO’s U-AID and JARUS/SORA origin documents define numeric likelihood/severity matrices and tolerability thresholds that regulators use to classify risks as INTOLERABLE, TOLERABLE or ACCEPTABLE — making risk-proportional mitigation and monitoring central to approval decisions for BVLOS, dangerous‑goods carriage and operations in populated areas [3][5].

Patterns of national implementation: convergences and divergences

Comparative practice shows a shared template: (a) baseline VLOS micro‑rules and remote pilot basics; (b) a risk‑assessment path for higher‑risk/BVLOS operations (often SORA‑based); (c) operator certification (ROC/ReOC/ROC equivalents); and (d) airspace integration work (UTM/remote ID pilots). However, weight/altitude thresholds and administrative process design vary materially between States, producing important operational effects in seasonal sectors such as agriculture and time‑critical work like emergency medical logistics [4][16][11][22][9].

The remainder of this report maps these common elements into sectoral safety protocols, certification and enforcement realities, then walks through jurisdictional case studies and practical recommendations for regulators and operators.

Sector safety protocols: tailored rules and practical controls

Agriculture (pesticide application and crop management)

Agricultural use is the dominant commercial drone application in many markets; industry guidance provides detailed SOPs for spray operations covering flight envelopes, environmental limits, nozzle calibration and operator hygiene [10][22].

Practical operational parameters recommended by CropLife Asia (Asia-focused, evidence‑based industry guidance) include flight heights of ~1.5–2.5 m above target, speeds of 4–6 m/s, wind limits <3 m/s, ambient temperature limits <35°C and relative humidity recommendations (>50%) to reduce drift — these are concrete mitigations regulators can incorporate into approvals and inspector checklists [10].

CropLife Asia also recommends machine‑specific certification, accredited training facilities, and limits on tank mixes and approach procedures (e.g., stay ~5 m from drones during spraying) — useful controls that reduce operator error, chemical exposure and environmental harm when paired with aviation approvals and pesticide registration requirements [10].

Facility cleaning and indoor operations

Indoor cleaning drones (window‑washing, façade maintenance) present atypical safety trade‑offs: they reduce work‑at‑height risks, but create proximate human‑interaction hazards, confined‑space contingency needs and equipment‑airworthiness concerns (electrical hazards, chemical cleaning agents) [15].

Regulatory treatments are emerging: some jurisdictions are creating dedicated instruments for indoor or near‑people operations (Australia’s Part‑101 work — see instrument listings including an ‘Indoor Operation’ item) to recognise the different risk profile of indoor BVLOS/near‑people training and to enable tailored safety controls such as occupancy exclusion, PPE and indoor‑specific maintenance checks [4][26].

Logistics (parcel and medical supply delivery)

Logistics uses (especially BVLOS medical corridors) combine higher technical assurance demands (detect‑and‑avoid, robust C2, remote‑ID and QoS guarantees) with pressing public‑health benefits; ICAO’s U‑AID guidance explicitly lists documentation and ORA elements required for humanitarian and medical delivery operations and supports expedited authorisations for urgent events where ‘known operators’ are pre‑recognised [3].

Dangerous‑goods carriage (e.g., medical samples, controlled therapeutics, or battery hazards) is addressed in ICAO U-AID: CAAs may accept operator ORAs with proportional mitigations instead of full Technical Instructions in some humanitarian contexts, but operators must maintain DG SOPs, packaging and incident reporting arrangements [3].

Emergency services and humanitarian response

Emergency operations benefit from pre‑authorisations, ‘expedited’ approval lanes and inter‑agency coordination; ICAO U‑AID recommends conditional pre‑recognition of ‘known UA operators’ and expedited authorisations in catastrophic events to ensure rapid deployment while keeping a documented ORA and emergency procedures on file [3].

Practical hazard guidance for emergency flights includes explicit emergency‑response planning, defined handover points for automation, and a clear chain of custody for dangerous goods and biological samples — all elements ICAO identifies as mandatory parts of a CAA decision dossier for routine humanitarian flights [3].

Compliance frameworks, certification pathways and training

Mature frameworks combine operator accreditation (ReOC/ROC), pilot licensing (RePL/RPL), and a safety‑management approach (SMM/SORA) that lets regulators scale oversight while focusing resources where risk is greatest [6][16][5].

Australia’s MoS/Part‑101 codifies RePL training requirements, BVLOS protocols, remote ID and record‑keeping expectations and explicitly links online training & examination options to credentialing — an example of a whole‑of‑operator approach that places training, procedures and SMS at the heart of compliance [4][6].

Kenya’s legislative instrument requires Remote Aircraft Operators Certificates (ROC) and Remote Pilot Licences with medical certification and background vetting, demonstrating how mid‑income States combine licensing, security vetting and ROC‑level organisational requirements to regulate commercial UAS activities [16].

The ICAO U‑AID and other guidance expect competency‑based training and ATO/approved training oversight for medical/humanitarian carriage, and advise CAAs to demand training records, maintenance evidence and operational manuals as part of approvals for higher‑risk operations [3].

Where governments lack rapid state‑run training capacity, private providers supply sector‑specific courses (e.g., Indonesian private providers offering pesticide‑spraying pilot certification). These market solutions are valuable but require regulatory recognition or oversight to ensure certificates translate into accepted credentials for permits and insurance [14][10].

Risk management strategies and SORA‑style implementation

SORA/SMM-style workflows require operators to: produce a CONOPS; identify ground‑risk (GRC) and air‑risk (ARC); propose mitigations; and demonstrate assurance commensurate with a SAIL level (I–VI) — CASA and other regulators have operationalised these steps in application checklists and TMIs [5].

CASA’s SORA guidance explicitly lists common application failure modes (mis‑estimated fGRC/ARC, weak mitigation evidence, poor CONOPS descriptions) and requires census‑based population grids for GRC calculations, tying risk scoring to reproducible datasets rather than ad hoc judgements [5].

ICAO U‑AID uses numeric likelihood (1–5) and severity (A–E) scales and a matrix define intolerable combinations (e.g., 5A, 4A) that must be mitigated before operations proceed — a transparent tolerability rubric useful for regulators and operators designing SOPs for agriculture, logistics and emergency response [3].

Airspace integration, UTM/U‑Space and remote ID

UTM/U‑Space pilots (InterUSS examples) use a Discovery & Synchronisation Service (DSS) to share Remote ID, flight authorisations and strategic conflict detection across multiple UAS Service Suppliers and authorities; standards used include ASTM F3411 (Remote ID) and ASTM F3548 (UTM) — these technical layers are increasingly treated as prerequisites for scaled BVLOS logistics and emergency networks [9].

Interoperability pilots demonstrate the value of multi‑host DSS pooling and automated conformity testing to support continuous regulator surveillance and automated onboarding of service providers — a strong signal that regulators should plan for testbeds and automated conformity tools rather than only manual approvals [9].

Enforcement, incident investigation and forensics

Operational incidents require a clear law‑enforcement / aviation coordination model. INTERPOL’s Framework for Responding to a Drone Incident provides a multi‑agency model for triage, scene containment, evidence preservation and drone forensics (items to seize: flight controllers, SD cards, FPV goggles, logs) that regulators and police can adopt into MOUs for aviation incidents [23].

Airport disruption guidance (EASA/ICAO) focuses on aerodrome roles, communications and contingency SOPs to reduce diversion and delay risks from unauthorised drones — a complementary operational playbook to INTERPOL’s forensic emphasis [24].

Practical enforcement constraints in many States include limited forensic laboratory capacity, civil–military coordination needs at airports, and the cost of detection/mitigation equipment — these limit how often full forensic investigations can be performed and shape regulator priorities toward prevention, archival reporting, and selective prosecution [24][23].

Cross‑sector regulatory variations and real‑world implications

Different sectors stress different parts of the regulatory stack: agriculture stresses quick area approvals and operator training (seasonality critical); facility cleaning stresses indoor‑operation exemptions and human‑factor controls; logistics stresses BVLOS assurance, remote ID and QoS; emergency services stress expedited lanes and pre‑authorised operators with interagency coordination [10][3][15].

These sector differences mean a one‑size regulatory approach is inefficient: regulators need modular approval paths (area approvals, known‑operator lists, expedited humanitarian lanes) and a data‑collection/retention strategy to evaluate operational safety over time [8][3].

Case studies: Indonesia, China, Australia and Africa (Kenya, Rwanda, Ghana)

Indonesia — multi‑instrument fragmentation and access friction

Indonesia’s DGCA framework is dispersed across ministerial regulations, directorate orders, circulars and regional rules; analyses of publicly listed ministry instruments show a corpus of many instruments (DGCA repository listing indicating over 100 entries) and multiple sectoral ministerial rules governing agriculture, health and spectrum allocation for drone C2 links [12].

PM 37/2020 is Indonesia’s primary ministerial regulation on UAS operations: default VLOS operations allowed to 120 m / 400 ft AGL; operations above 120 m require Director‑General approval; a small‑UAS weight band is defined around ~25 kg (≤55 lb) with additional scrutiny for commercial use; BVLOS requires DAA and tracking; administrators require permit dossiers at least 14 working days before flight with a 14‑day validation window and 7‑day notice for routine changes — timeliness constraints that interact poorly with seasonal agriculture and urgent emergency needs [11].

Practical access problems surfaced during research: Indonesia’s consolidated legal portals and DGCA publication indexes were intermittently inaccessible to automated searches and some public indices did not return expected documents (a real‑world transparency and discoverability problem that operators encounter) [13].

Market responses include private training providers offering pesticide‑spray pilot certification that cover both agronomy/pesticide stewardship and operational drone skills; these help fill capacity gaps but underline the need for regulatory oversight or recognition so operator certificates are accepted in permit processes [14][10].

Operational implication: Indonesia’s multi‑agency permit requirements (aviation + sectoral ministries), strict time windows for dossier submission and some opaque publication practices increase friction for time‑sensitive agricultural spraying and for rapid humanitarian flights unless pre‑authorised corridor/sandbox mechanisms are adopted [11][12][13].

China — massive scale, integrated telemetry and data‑driven oversight

China combines high operator volumes, centralized telemetry exchange and regulator test programs: CAAC statistics report over 1.26 million registered unmanned aircraft and ~194,400 licensed UAS pilots at end‑2023, with very large flight‑hour volumes — data assets that support data‑driven oversight and UTM deployment [22].

Operational telemetry in China’s vendor cloud‑exchange system reported ~2.97 billion exchanged records and ~4.12 million flight‑hours in 2023, with almost all flight‑hours at low altitude (≈99% ≤120 m and ~79% ≤5 m), and agriculture management class accounting for the dominant share of flight‑hours — a profile that supports tailored low‑altitude agricultural SOPs and proportional oversight models .

CAAC conducted low‑altitude connected drone safety tests and published test reports to build technical evidence informing policy — an example of regulator‑led trials that generate the technical basis for rule‑making and operational thresholds [20][21].

Practical implication: China shows how integrated telemetry, cloud exchanges and large‑scale training exam networks can underpin real‑time monitoring and high‑volume operation support, but that capacity is resource‑intensive (data analytics, telecom QoS agreements and vendor interoperability) [20].

Australia — structured MoS, SORA operationalisation and BVLOS scaling pilots

Australia’s regulatory architecture centres on CASR Part‑101 and an associated Manual of Standards that codify RePL/ReOC pathways, BVLOS standards and remote‑ID/record‑keeping obligations; CASA publishes user‑facing hubs and clear application checklists [4][6][7].

CASA has operationalised SORA (with local TMIs and checklists), published common application failure modes and is actively trialling ‘broad‑area BVLOS’ pathways (TMI 2025‑03) that aim to convert repeated SORA casework into standardised, area‑based approvals for ReOC holders — a practical scaling approach [5][8].

CASA’s stakeholder BVLOS survey (443 respondents) highlights operator burdens that regulators must prioritise: 64.6% cited ‘complex regulations’ as the top barrier, long approval lead times and costs were frequently reported, and respondents urged area approvals and low‑risk BVLOS criteria to reduce operational friction [27]. The ranked barriers are illustrated below as Figure 1.

Figure 1: Operator‑reported barriers to BVLOS adoption (CASA BVLOS stakeholder survey, Mar 2024) – Ranked bar chart of the top barriers reported by 443 Australian stakeholders responding to CASA’s BVLOS survey. Useful to show which practical/administrative frictions most inhibit sector scaling [27].

Australia demonstrates an explicit policy path: codify SORA workflows; publish checklists; run pilots that reduce per‑flight casework for qualifying operators; and mandate data reporting so regulators can evaluate trials before permanent rule changes [5][8].

Africa — regulatory diversity with pragmatic digital portals (Kenya, Rwanda, Ghana)

Kenya’s Civil Aviation (UAS) Regulations 2020 enact a risk‑based categorisation (Category A low risk VLOS with MTOW ≤25 kg and 400 ft AGL default altitude; Category B medium risk; Category C high risk/BVLOS) and require Remote Aircraft Operators Certificates (ROC) with safety management systems and security vetting — a comprehensive architecture with explicit enforcement penalties [16].

Rwanda implemented a practical digital Drone Portal and RCAR Part 27-based advisory circulars to operationalise permit processing (UAS Activity Permit, CONOPS forms) and requires 24‑hour incident reporting — a useful example of a small State implementing an efficient digital gateway for operations and incident transparency [17][18][19].

Ghana’s AC 28‑003 provides a mandatory, structured CONOPS template and evidence checklist for higher‑risk RPAS operations (triggers include MTOW >7 kg, BVLOS, populous areas, goods‑dropping) — an example of a regulator reducing review variation by insisting on a sealed, evidence‑centred submission format [25].

Practical implication across Africa: smaller States can achieve operational clarity by publishing standardised CONOPS templates, digital portals for permits and incident reporting, and explicit training provider authorisation criteria — a pragmatic route to safe, scalable applications without the heavy analytics program of larger States [25][17][18].

Enforcement challenges, capacity gaps and practical mitigations

Common enforcement constraints include limited inspector/headcount capacity, data‑analysis tools to handle telemetry, forensic lab capacity, and civil–military coordination for airport incidents — these realities shape the pragmatic mix of preventive controls, technology procurement and selective prosecution that most regulators adopt [23][24].

Case evidence: Indonesia has reported multiple aerodrome incursions and relies on military assets for counter‑UAS at some airports, highlighting gaps in civil detection/response capacity and the need for coordinated civil–military SOPs at airports .

Recommended mitigations for constrained regulators (based on sources and international best practice) include: (a) publish standard CONOPS templates to shorten review times (Ghana model); (b) provide area/seasonal approvals or ‘broad‑area’ pathways for repeatable low‑risk operations (CASA TMI model); (c) implement digital portals for permit and incident reporting (Rwanda model); and (d) invest in targeted forensic training and MOUs with police and airport authorities (INTERPOL / EASA guidance) [25][8][17][23][24].

Emerging policy trends and innovation signals

Five observable trends across the sourced material: (1) regulators shifting from single‑flight SORA cases to area‑based approvals for repeatable low‑risk BVLOS operations (CASA TMI); (2) growing emphasis on data‑driven oversight via telemetry/remote‑ID exchanges (China and InterUSS pilots); (3) sector‑tailored SOPs for pesticide spraying and indoor cleaning that merge aviation safety with occupational health rules (CropLife Asia & Safe Work Australia); (4) humanitarian expedited lanes for known operators (ICAO U‑AID); and (5) mandatory structured CONOPS templates to reduce application variability (Ghana AC) [8][9][10][3][25].

These trends suggest regulators will increasingly rely on: automated conformity testing, continuous performance surveillance of USS/UTM providers, standardised evidence checklists and pre‑authorised operator lists to manage the tension between safety assurance and operational timeliness [9][8][25].

Practical recommendations for regulators and operators

1. Publish a single, discoverable permit & guidance hub. Consolidate CONOPS templates, application checklists, incident‑report forms and sectoral SOPs in a single portal to reduce friction and support automation (CASA and Rwanda examples) [6][17].
2. Create pre‑authorised area approvals for routine seasonal operations. Use a broad‑area pathway for repeatable low‑risk agricultural corridors to align approvals with crop seasons (CASA TMI model) [8].
3. Standardise CONOPS templates and evidence checklists. Adopt sealed templates similar to Ghana’s AC to reduce reviewer variability and speed decisions [25].
4. Define expedited humanitarian lanes and ‘known operator’ lists. Align national practice with ICAO U‑AID to permit rapid medical and disaster flights with documented ORA and pre‑recognised credentials [3].
5. Integrate occupational health guidance for facility cleaning and pesticide operations. Merge aviation SOPs with workplace safety tools (PPE, re‑entry intervals) — CropLife Asia and Safe Work Australia provide sector guidance to adapt [10][15].
6. Invest in telemetry ingestion & automated testing capability. Plan for DSS/UTM interoperability pilots and conformance testbeds to verify remote‑ID and USS performance (InterUSS pilots, CAAC telemetry lessons) [9].
7. Mandate operator incident data retention and reporting. Require standardised records for seven years (CASA TMI approach) and 24‑hour reporting for serious incidents (Rwanda example) to enable trend analysis and enforcement prioritisation [8][17].
8. Authorise and oversee training providers. Require regulator recognition of private courses and align curricula with ICAO/CAA expectations for BVLOS and dangerous‑goods handling [3][10][14].
9. Use pilots and sandboxes with built evaluation metrics. Run time‑bound trials with mandatory data feeds and pre‑defined evaluation metrics before scaling (Australia/InterUSS examples) [8][9].
10. Strengthen multi‑agency incident MOUs and forensic capacity. Implement INTERPOL checklists and aerodrome SOPs, and prioritise forensic lab training where incidents occur (INTERPOL & EASA guidance) [23][24].

Comparative thresholds and triggers (ICAO vs selected States)

Methodology, research limitations and transparency notes

This report strictly uses sources provided in the research packet. During collection, access to some national consolidated legal portals (notably Indonesian JDIH/peraturan.go.id and some DJPU indices) was blocked or returned no‑match results in automated queries, creating retrieval friction for certain ministerial instruments and historic incident reports — a real‑world transparency challenge noted below and factored into recommendations [13].

Where primary legal PDFs were available (PM 37/2020; Kenya 2020 Regulations; CAAC statistical reports; Rwanda RCAR Part 27; Ghana AC 28‑003; CASA TMIs), the report quotes numeric thresholds and procedural timeframes directly from those documents and the ICAO toolkit materials cited earlier [11][16][22][18][25][8][2].

Conclusion — balancing safety, seasonality and scalability

Regulators must reconcile three practical imperatives: ensure aviation and public‑safety levels are maintained; enable rapid, repeatable approvals for time‑sensitive sectors (agriculture, emergency services); and build data‑driven oversight capacity (UTM/remote‑ID and automated testing). The sources reviewed show feasible policy mixes: standardised CONOPS, area/season approvals, telemetry ingestion, recognised training provider systems and incident‑data retention policies — all supported by practical examples from Australia, Ghana, Rwanda, Kenya, China and Indonesia [8][25][17][16][11].

Adopting these measures preserves safety while unlocking the real benefits drones can bring to worker safety (reducing falls and vehicle‑incident exposure), operational efficiency and rapid humanitarian response — provided regulators publish clear guidance, enable pre‑authorisation for trusted actors, and demand verifiable training and technical evidence from operators [15][27][3][10].

Frequently Asked Questions

1. What is SORA and why do regulators use it?
   SORA (Specific Operations Risk Assessment) is a structured, JARUS‑originated risk methodology used by regulators (CASA example) to assess higher‑risk operations (BVLOS, high altitude). It structures CONOPS → GRC/ARC → SAIL → mitigations → emergency planning and helps regulators standardise decisions [5].
2. How do humanitarian or emergency flights get expedited?
   ICAO U‑AID endorses expedited authorisations for urgent events and recommends pre‑recognition of ‘known operators’ so CAAs can grant conditional airspace approvals quickly while relying on a retained ORA and minimal documentation for urgent deployments [3].
3. What operational limits matter most for safe pesticide spraying?
   CropLife Asia recommends key parameters: flight height 1.5–2.5 m above target, speed 4–6 m/s, wind <3 m/s, temperature <35°C and RH >50%, plus nozzle/atomisation calibration and operator PPE — these reduce drift and operator exposure [10].
4. Are there examples of streamlined BVLOS approvals?
   Yes — CASA’s TMI 2025‑03 trials four broad‑area BVLOS pathways allowing ReOC holders to obtain 12‑month area approvals under defined RPA/ population/mitigation criteria, reducing per‑flight SORA workloads [8].
5. How do countries handle dangerous goods on drones?
   ICAO U‑AID sets DG guidance: CAAs may accept operator ORAs with proportional mitigations instead of full Technical Instructions in some humanitarian cases; operators must still have DG‑SOPs, training, emergency response plans and packaging/containment measures [3].
6. What is the role of telemetry/cloud exchanges in oversight?
   Telemetry and vendor cloud‑exchanges (China’s model) and DSS/USS architectures (InterUSS pilots) let regulators monitor flight volumes, perform strategic conflict detection, and run automated testing — critical for scaled operations and data‑driven oversight [9].
7. What are typical application timelines operators should expect?
   Timelines vary: CASA notes BVLOS approvals may take ‘several months’ and ReOC processing may run up to 70 business days in complex cases; Indonesia’s PM 37 sets 14‑working‑day validation windows after dossier submission but requires 14 working days’ pre‑application submission — both illustrate non‑trivial lead times that must be planned for [6][5][11].
8. How should regulators treat private training providers?
   Regulators should authorise and audit training providers, align curricula with national/ICAO expectations, and publish an approved‑provider list so private certificates can count towards regulatory approvals (CropLife Asia and ICAO training expectations support this) [10][3].
9. What incident reporting and evidence retention is recommended?
   CASA TMI trials require operators to retain operational data for seven years and report exits/collisions; Rwanda mandates 24‑hour incident reporting. INTERPOL provides a forensic evidence checklist for seizure and custody — regulators should harmonise retention/reporting windows and incident schemas for cross‑agency interoperability [8][17][23].
10. How can small States scale oversight without massive analytics budgets?
    Practical options include publishing standardised CONOPS templates (reduce review variance), running limited sandboxes with mandatory data feeds, requiring operator data retention, and prioritising targeted detection/forensic investments at high‑value nodes (airports, medical corridors) — Rwanda and Ghana provide models for templates and portals [17][25][19].

References

1. ICAO – Unmanned Aviation and Advanced Air Mobility (homepage) (https://www.icao.int)
2. ICAO UAS Toolkit (https://www.icao.int/safety/UA/UASToolkit/)
3. Unmanned Aircraft Systems (UAS) for Humanitarian Aid and Emergency Response Guidance (U-AID) (https://www.icao.int/sites/default/files/safety/UA/Documents/ICAO-U-AID-Guidance-Material.pdf)
4. Part 101 (Unmanned Aircraft and Rockets) Manual of Standards 2019 (Australia) (https://www.legislation.gov.au/F2019L00593/latest/text)
5. Specific operations risk assessment (CASA SORA guidance) (https://www.casa.gov.au/drones/flight-authorisations/beyond-visual-line-sight-operations/specific-operations-risk-assessment)
6. Get your ReOC | Civil Aviation Safety Authority (https://www.casa.gov.au/drones/remotely-piloted-aircraft-operators-certificate/get-your-reoc)
7. Drone safety rules | Civil Aviation Safety Authority (https://www.casa.gov.au/drones/drone-rules/drone-safety-rules)
8. Temporary Management Instruction (TMI 2025‑03) — Broad Area BVLOS Operations (CASA) (https://www.casa.gov.au/sites/default/files/2025-09/temporary-management-instruction-tmi-2025-03-broad-area-bvlos-operations.pdf)
9. UTM/U‑Space Deployments – InterUSS (https://interussplatform.org/utm-u-space-deployments/)
10. Recommendations for building a Standard Operating Procedure (SOP) for pesticide application by drone (CropLife Asia, Apr 2023) (https://croplife.org/wp-content/uploads/2023/04/SOP-Drones-Guidance-Asia.pdf)
11. Peraturan Menteri Perhubungan Republik Indonesia Nomor PM 37 Tahun 2020 — Pengoperasian Pesawat Udara Tanpa Awak (https://imsis-djpu.kemenhub.go.id/SidopiGO/Web/PM372020.pdf)
12. Juklak Internal (Direktorat Jenderal Perhubungan Udara) – Regulasi (Indonesia DGCA repository) (https://hubud.kemenhub.go.id/hubud/website/regulasi/rule/5)
13. JDIH Kemenhub — Peraturan (access rejected recorded) (https://jdih.kemenhub.go.id/peraturan/index?… (access note))
14. Sertifikasi Pilot Drone Spraying – JSP Jakarta (private training example) (https://jsp.co.id/sertifikasi-pilot-drone-spraying-drone-pertanian/)
15. Safe Work Australia — News Update Issue 9, November 2024 (https://www.safeworkaustralia.gov.au/media-centre/enews/news-update-issue-9-november-2024-plain-text)
16. LEGAL Notice No 42 — Civil Aviation (Unmanned Aerial Systems) Regulations, Kenya, 19 March 2020 (https://www.kcaa.or.ke/sites/default/files/regulation/Civil%20Aviation%20(Unmanned%20Aircraft%20Systems)%20Regulations%202020.pdf)
17. Rwanda Civil Aviation Authority — UAS / Drone permit & Drone Portal page (https://www.caa.gov.rw/drones)
18. RCAR Part 27 / ANNEX XXVII — Unmanned Aircraft System (Rwanda UAS Regulations PDF) (https://aaidportal.mininfra.gov.rw/…/ANNEX_XXVII__PART_27__-_Unmanned_Aircraft_System.PDF)
19. Drones in Rwanda — World Economic Forum Case Study (C4IR), 2020 (https://www3.weforum.org/docs/WEF_C4IR_Case_Study_Drones_In_Rwanda_2020.pdf)
20. CAAC — Research / Reports index (English) (https://www.caac.gov.cn/English/Research/Reports/Other/)
21. Low‑Altitude Connected Drone Flight Safety Test Report (CAAC reference listing) (CAAC low‑altitude test report (referenced))
22. China Civil Aviation Annual Report 2023 (CAAC) (http://www.caac.gov.cn/English/…/P020241211602850378121.pdf)
23. EASA — Drone Incident Management at Aerodromes (hosted on ICAO site) (https://www.icao.int/…/EASA Drone Incident Management at Aerodromes – Part I.pdf)
24. AC 28‑003 — Guidelines on Presentation of an RPAS CONOPS (Ghana GCAA, Aug 2024) (https://www.gcaa.com.gh/…/AC 28-003.pdf)
25. IMSIS/DJPU Publikasi and DJPU site navigation (search access notes) (https://hubud.kemenhub.go.id/hubud/website/publikasi-djpu)
26. Drones (drones.gov.au) — Australian policy hub & initiatives (https://www.drones.gov.au/drone-rules/safety)
27. Summary of Survey: BVLOS drone operations in regional Australia (CASA, Mar 2024) (https://consultation.casa.gov.au/…/summaryofsurvey-bvlosrpasopsregionalaus.pdf)