Detailed working notes on the ICAO RPAS framework for integrating remotely piloted aircraft systems into non-segregated controlled airspace alongside crewed traffic. This folder expands the summary in topics/rpas.md into per-aspect files so each can be read independently.

Files in this folder#

• overview.md — what RPAS is, where it sits in the ICAO framework, the scope distinction between controlled-airspace RPAS and lower-level UAS/U-Space, and the principal ICAO instruments.
• components.md — the physical and functional building blocks of an RPAS: RPA, remote pilot station (RPS), C2 link, DAA system, remote crew, ATC interface, and the ROC/TC regulatory instruments.
• blocks.md — the integration phases from accommodation through integration to evolution; the airspace-class access ladder; and how RPAS maps onto the ASBU modernization trajectory.
• threads.md — the six functional axes that together constitute RPAS integration: airworthiness/type certification, C2 link, detect-and-avoid, remote crew licensing, ATM procedures, and contingency/lost-C2-link.
• modules.md — anatomy of one worked strand: the lost-C2-link contingency procedure as a complete operational module, including the DAA-to-CA transition and transponder action.
• enablers.md — CNS infrastructure, frequency spectrum, procedures, training, regulation, certification, and institutional arrangements required for RPAS in controlled airspace.
• performance_objectives.md — KPA-keyed performance table and KPIs for RPAS integration at each phase.
• timeline.md — historical evolution: ICAO circulars, panel meetings, Annex amendments, Doc 10019 publication, and SARPs milestone dates.
• references.md — consolidated ICAO and authoritative external references for all content in this folder.

Reading order#

Start with overview.md for the concept and framework context, then components.md for physical architecture, then threads.md for the functional axes. blocks.md shows how access matures over time. modules.md gives a concrete worked example. enablers.md is a planning checklist. performance_objectives.md and timeline.md provide the metrics and dates. references.md is the citation master list.

Source basis#

Content is grounded in:

• ICAO Doc 10019 (Manual on Remotely Piloted Aircraft Systems), 1st edition 2015.
• ICAO Annex 2 (Rules of the Air), Appendix 4 — RPAS operating rules.
• ICAO Annex 1 (Personnel Licensing), Chapter 2, §§2.11-2.13 — remote pilot licence.
• ICAO Annex 8 (Airworthiness), Parts VIII and IX — RPA type certification.
• ICAO Annex 7 (Aircraft Nationality and Registration Marks), §2.3.
• ICAO Annex 6, Part IV (from 26 November 2026) — RPAS operator certificate.
• RTCA DO-365 (DAA MOPS) and DO-362 (C2 Link MOPS) — not in local library.
• EASA Reg (EU) 2019/947 and 2019/945 — certified category RPAS rules for Europe — not in local library.

What RPAS integration means in the ATM context#

Remotely Piloted Aircraft System integration is the process by which RPAS operating in international air navigation become routine participants in non-segregated airspace alongside crewed traffic. The ICAO definition of RPAS — from Annex 2 — is the complete system: the remotely piloted aircraft (RPA), the associated remote pilot station(s) (RPS), the required C2 Link(s), and any other components specified in the type design. All four elements form a unified safety-critical system for certification and operational purposes.

The topic scope is RPAS in controlled airspace under IFR, primarily airspace classes A, B, and C, engaged in international air navigation. This is different from:

• Autonomous UAS (no remote pilot in the loop; ICAO has not yet developed full SARPs for autonomous operation).
• Low-level drone delivery and U-Space (a separate UTM ecosystem below controlled airspace, addressed in the u_space topic).
• Model aircraft and recreational drones (not addressed by ICAO international SARPs for international navigation).

Where RPAS sits in the ICAO framework#

ICAO Doc 10019 is the primary guidance document. Its Foreword states the ICAO goal: "to provide an international regulatory framework through Standards and Recommended Practices (SARPs), with supporting Procedures for Air Navigation Services (PANS) and guidance material, to underpin routine operation of RPAS throughout the world in a safe, harmonized and seamless manner comparable to that of manned operations."

The RPAS Panel (RPASP) is the principal expert body. It has met through 18 sessions (RPASP/1 through RPASP/18 as of 2024) and produced amendment packages to Annexes 1, 2, 6, 7, 8, and 10 covering RPAS certification, ROC, remote pilot licensing, C2 Link, and DAA SARPs. The most significant package — RPASP/18 — brings international SARPs for RPAS operations in controlled airspace and aerodromes into force on 26 November 2026.

The global ATM Operational Concept (Doc 9854) is the conceptual anchor: the concept anticipates full RPAS participation in the ATM system, including eventual integration into trajectory-based operations (TBO).

The safety principle#

Doc 10019 makes the governing principle explicit: "introduction of remotely piloted aircraft into non-segregated airspace and at aerodromes should in no way increase safety risks to manned aircraft." Every element of the RPAS integration framework — DAA standards, C2 link performance requirements, lost-C2-link procedures, ATCO awareness training — flows from this principle. RPAS must be at least as safe as, or safer than, present manned operations.

The scope distinction: RPAS versus UAS#

ICAO deliberately uses RPAS rather than UAS (Unmanned Aircraft System) when referring to the category of unmanned aircraft that falls within civil aviation SARPs. UAS is a broader term used in some national regulations. RPAS specifically implies that a remote pilot is in the loop for flight management. The distinction matters operationally: an RPAS in ATC-controlled airspace has an identified, licensed remote pilot who is responsible for responding to ATC instructions, executing contingency procedures, and maintaining separation from other traffic via DAA, analogous to a crewed pilot.

The three-pillar integration model#

Doc 10019 structures RPAS integration around three interdependent pillars:

The certification pillar (Annex 8, Annex 6 Part IV) establishes what must be approved before an RPAS can enter controlled airspace: an RPA type certificate covering the complete RPAS system, an individual certificate of airworthiness, and an RPAS operator certificate (ROC).

The operations pillar (Annex 1, Annex 2, Doc 10019) establishes how the RPAS is operated: licensed remote pilot, RPAS operating manual, safety management system, ATM compliance procedures, and the filed lost-C2-link contingency.

The technical enabler pillar (Doc 10019, Chapters 10-13) specifies the technical capabilities that make safe operations possible: DAA systems, C2 link performance (RLP — required link performance), RPS displays, transponder/ADS-B, and spectrum protection.

Regional context#

All ICAO contracting states are expected to implement the RPAS SARPs under the applicable Annex amendment applicability dates. EASA has issued RPAS regulations for European airspace (Reg (EU) 2019/947 and 2019/945) covering the certified category of larger RPAS. The FAA has published RPAS integration policies through its UAS integration office and NextGen programme. APAC states are progressing RPAS frameworks through APANPIRG. The MID and AFI regions are at earlier stages of national regulation but are bound by the same ICAO SARPs applicability dates.

References#

• Doc 10019 (Manual on Remotely Piloted Aircraft Systems), Foreword — ICAO goal and governing safety principle.
• Doc 10019, Chapter 1, §1.1 — ICAO regulatory framework scope for RPAS.
• Doc 10019, Chapter 14, §14.2.1 — gradual integration process building on technology and procedure development.
• Annex 2 (Rules of the Air), Appendix 4 — fundamental RPAS operating rules in international air navigation.
• Annex 8 (Airworthiness), Part VIII, §1.4.3 — type certification of RPA to include RPS and C2 Link as of 26 November 2026.
• Doc 9854 (Global ATM Operational Concept) — conceptual anchor for full RPAS integration in future ATM (authoritative source — not in local library).

The RPAS system boundary#

Unlike a crewed aircraft, an RPAS is a distributed system. Annex 2 defines the RPAS as the RPA, its associated remote pilot station(s), the required C2 Link(s), and any other components specified in the type design. This system boundary has critical implications: the type certificate (TC) covers all four elements as an integrated whole, not the RPA alone.

Doc 10019 reinforces this: "the associated RPAS components specified in the type design shall be certificated and maintained in accordance with the provisions of related Annexes."

The building blocks of an RPAS operating in controlled airspace are:

• Remotely piloted aircraft (RPA)
• Remote pilot station (RPS)
• C2 link (command and control link)
• Detect-and-avoid (DAA) system
• Remote crew
• ATC interface (voice and data communications, transponder)
• Regulatory instruments (type certificate, CofA, ROC, remote pilot licence)

1. Remotely Piloted Aircraft (RPA)#

The RPA is the airborne element. It carries avionics, propulsion, structure, payload, and the onboard elements of the C2 link and DAA system. The RPA must meet:

• Type design requirements for the applicable Annex 8 category (Part VIII for remotely piloted aeroplanes, Part IX for remotely piloted helicopters).
• Certificate of airworthiness (CofA) issued in accordance with Annex 8; as of 26 November 2026, the CofA must convey airworthy status of the complete RPAS system.
• Equipment carriage requirements for the airspace class and route (transponder, ADS-B, communications equipment, DAA sensors).

Performance characteristics of the RPA — speed, climb/descent rate, turn radius, response latency — directly determine how the ATM system integrates it. HALE (high-altitude, long-endurance) RPA with slow climb/descent and low cruise speed require specific coordination with ATC for level changes through manned cruise altitudes.

2. Remote Pilot Station (RPS)#

The RPS is defined as "the component of the remotely piloted aircraft system containing the equipment used to pilot the remotely piloted aircraft." It is the functional equivalent of the cockpit or flight deck. The RPS must provide the remote pilot with equivalent capability to command and manage the flight as a crewed pilot in a conventional cockpit.

Key RPS functions include:

• Flight control interface (controls, instruments, FMS access).
• C2 link status monitoring — continuous display of link health and alerts on degradation toward Tsloss.
• DAA display — showing surrounding traffic, terrain, weather hazards, and DAA alerts (remain-well-clear and collision-avoidance advisories).
• ATC communications relay — voice and/or data link between the remote pilot and the ATC unit serving the flight.
• Traffic situational awareness — display of all traffic in the vicinity with audible and visual alerts.
• Emergency and contingency controls — access to flight termination, lost-C2-link procedure initiation, and emergency descent.

The RPS may be fixed on the ground or carried aboard another vehicle (ship, aircraft). Multiple remote pilots may occupy a single RPS for complex operations.

3. C2 Link (Command and Control Link)#

The C2 link is the datalink between the RPA and the RPS for managing the flight. It is a safety-critical system component, not an accessory. Two operational configurations exist:

RLOS (Radio Line of Sight) — direct radio frequency link, typically using the 5 030-5 091 MHz band allocated by the ITU for RPAS C2. RLOS provides low-latency, high-availability links for operations within radio coverage of the ground station.

BRLOS (Beyond Radio Line of Sight) — relay via satellite or airborne relay platform. BRLOS enables long-range and oceanic operations. Typical architectures include single-satellite relay and multiple satellite/airborne relay.

Key C2 link performance parameters (the "required link performance"):

• Transaction time — end-to-end latency for a control command.
• Availability — probability that a communication transaction can be initiated when needed.
• Continuity — probability the transaction completes once started.
• Integrity — probability of undetected errors in a completed transaction.

These parameters mirror the Required Communication Performance (RCP) concept in Doc 9869. The RLP for each RPAS is defined by the manufacturer/operator and agreed with the certifying authority. There is currently insufficient operational service history to prescribe universal minimum RLP standards; these will develop through experience.

The C2 link may also carry relayed ATC voice or data communications between the ATC unit and the RPS. If both C2 messages and ATC communications share the link, the combined performance must not degrade either function below its minimum requirements.

Tsloss is the maximum permitted duration of C2 link unavailability before the lost-C2-link condition is declared and the contingency procedure is initiated. It is agreed during the certification process.

4. Detect-and-Avoid (DAA) System#

The DAA system replaces the visual see-and-avoid obligation of a crewed pilot. DAA is defined in Annex 2 as "the capability to see, sense or detect conflicting traffic or other hazards and take the appropriate action."

Doc 10019, Chapter 10 identifies five hazard categories that a DAA system may need to address:

• Conflicting traffic (the primary concern for controlled airspace).
• Terrain and obstacles.
• Hazardous meteorological conditions.
• Ground operations hazards.
• Other airborne hazards (wake turbulence, birds, volcanic ash).

A single DAA system is not expected to address all five categories. The two functions most critical for controlled-airspace operations are:

Remain-Well-Clear (RWC) — detecting traffic that may approach the RWC volume boundary and alerting the remote pilot to manoeuvre, analogous to the traffic advisory (TA) in ACAS. The RWC function keeps the RPA outside the minimum separation zone before a conflict develops.

Collision Avoidance (CA) — last-resort action when a conflicting aircraft crosses the CA threshold, analogous to the resolution advisory (RA) in ACAS. The CA manoeuvre may be automated or pilot-executed depending on DAA system design.

The DAA system must be approved by the State of Registry. When ACAS is installed on the conflicting crewed aircraft, the RPA's DAA resolution advisory should be consistent with the rules of the air to avoid conflicting manoeuvres.

5. Remote Crew#

Annex 1, Chapter 2, §2.11 requires that a person acting as remote pilot- in-command or remote co-pilot of an RPA in international operations holds a remote pilot licence. The licence carries:

• Category rating (aeroplane, helicopter, rotorcraft, etc.).
• Medical certificate (class consistent with the rating).
• Instrument rating where IFR operations are to be conducted.
• Type or class rating for the specific RPA.
• Currency requirements (recency of experience).

Remote crew members must also be trained on RPAS-specific procedures: C2 link management, DAA system interpretation, lost-C2-link drill, ATC communications via relay, and contingency/emergency procedures.

6. ATC Interface#

The ATC interface covers two elements:

Communications. The RPA carries VHF/HF radio equipment per the minimum communications requirements for its airspace class and route. ATC voice communications are relayed between the remote pilot and the ATC unit via the C2 link. The relay introduces a performance dependency: the ATC communication round-trip time must account for C2 link latency. Doc 10019, §12.7.3 notes that regulators may allow alternative equipage arrangements (one radio onboard plus a secondary path from RPS to ATC) given the C2 link relay capability.

Transponder and surveillance. RPA must comply with transponder operating rules for the airspace class in the same way as crewed aircraft. The lost-C2-link transponder action is a RPAS-unique procedure: a new non-discrete code may eventually be standardized to indicate the state. Until then, Mode A code 7700 is used for general emergencies and 7600 for voice communication failure; the lost-C2-link state requires specific guidance.

7. Regulatory Instruments#

The complete set of regulatory instruments required for an RPAS in controlled airspace is:

• Type certificate (TC) for the RPAS system (RPA + RPS + C2 Link).
• Individual certificate of airworthiness (CofA).
• RPAS operator certificate (ROC) from the State of the Operator.
• Remote pilot licence from the State of the Operator.
• State authorizations for each flight (State of take-off, overflown States, ATS authority for high-seas operations).
• RPAS operating manual acceptable to the State of the Operator.

As of 26 November 2026, Annex 2 §2.1 and Annex 8 §1.4.3 make the full international SARPs for these instruments mandatory. Until that date, national regulations that are "consistent with the provisions of related Annexes" are accepted under Assembly Resolution A41-10.

References#

• Doc 10019 (Manual on Remotely Piloted Aircraft Systems), Chapter 4, §4.5 — C2 link as component of the type design.
• Doc 10019, Chapter 11, §11.3.21 — required C2 link performance parameters and RLP concept.
• Doc 10019, Chapter 10, §10.1.1-10.1.3 — DAA definition, hazard types, and multi-sensor interoperability requirement.
• Doc 10019, Chapter 13, §13.1.1 — RPS as the functional equivalent of the cockpit/flight deck.
• Doc 10019, Chapter 14, §14.2.9-14.2.10 — CNS and transponder requirements for RPA in controlled airspace.
• Annex 2, Appendix 4, §2.1 — certification framework for RPAS including RPA CofA and RPAS component certification.
• Annex 1 (Personnel Licensing), Chapter 2, §2.11.1 — remote pilot licence requirement for international RPAS operations.
• Annex 8 (Airworthiness), Part VIII, Chapter 11 — remotely piloted aeroplane unique considerations: C2 Link and detect-and-avoid.

How RPAS access to controlled airspace matures#

RPAS integration into controlled airspace does not occur in a single step. Doc 10019, Chapter 14 describes integration as "a gradual process that builds upon technological advances and development of associated procedures." Three phases characterize the progression:

Phase 0 — Segregated or Restricted Operations (Pre-integration)#

Character. The RPA operates in segregated airspace (restricted/danger areas reserved for its exclusive use) or in agreed corridors notified by NOTAM. No mixed operations with crewed traffic. This phase predates formal RPAS SARPs and describes the situation in most States through the early 2020s for large RPAS.

Access conditions. Requires coordination with the ATS authority, usually through restricted airspace activation or special-use airspace allocation. No requirement for full RPAS TC/ROC in most States. Applicable to military RPAS and experimental large UAS.

ATM impact. Minimal: ATC can sequence around the reserved airspace as a known constraint. No real-time integration.

Phase 1 — Accommodation (Limited Access, Special Procedures)#

Character. The RPA operates in non-segregated airspace under special procedures negotiated with the ATS authority. Standard ATM procedures apply as far as possible, but deviations are permitted where technology has not yet met the manned-equivalent standard.

Access conditions. The RPAS holds a certificate of airworthiness, an ROC (or national equivalent), and the remote pilot holds a licence (or national equivalent). The lost-C2-link contingency procedure is filed with ATC. The DAA system may be limited and/or a NOTAM is issued to warn other airspace users. Operations may be restricted to specific routes, times, or airspace volumes. State-by-State authorization under Annex 2, Appendix 4, §1.1 and §1.2 applies.

ATM impact. Moderate: ATCOs require familiarization with RPAS response latency and performance characteristics. Specific coordination at handoffs. Special transponder procedures for lost-C2-link state.

Enabling SARPs. Annex 2, Appendix 4, §2.1 (pre-26 November 2026 version) accepts national regulations consistent with ICAO Annexes. This phase corresponds to current operations (2020s) for most large civil RPAS.

Phase 2 — Integration (Routine Access, Standard Procedures)#

Character. RPAS operates routinely in controlled airspace using the same standard ATM procedures as crewed aircraft. Full ICAO RPAS SARPs apply. ATC issues clearances without awareness that the aircraft is remotely piloted (except where operational characteristics require attention).

Access conditions. Full RPAS TC under Annex 8 Parts VIII/IX covering RPA, RPS, and C2 Link. ROC under Annex 6, Part IV. Remote pilot licence under Annex 1, §2.11-2.13. Approved DAA system meeting State of Registry requirements. Filed lost-C2-link contingency accepted by ATS authority.

This phase corresponds to the intent of the 26 November 2026 RPASP/18 SARPs package. Routine IFR RPAS operations in controlled airspace become internationally standardized.

ATM impact. Low for controllers trained on RPAS characteristics. Standard flight plan formats, standard communications, standard transponder codes (except the eventual lost-C2-link code). Key remaining differentiators: response latency, HALE performance profile, DAA alert workflow.

Phase 3 — Evolution (Seamless Participation)#

Character. RPAS participates fully in trajectory-based operations. The agreed 4D trajectory is filed and managed through FF-ICE. DAA collision- avoidance actions may be automated. RPAS are participants in the SWIM ecosystem (Doc 10019, §12.8 anticipates this). The distinction between crewed and remotely piloted aircraft in the ATM picture is operational, not procedural.

Access conditions. Mature TBO enablers: FF-ICE, SWIM, ATN B2 data link, advanced DAA with automation-to-automation coordination for CA. Full CA automation approved by the State of Registry. Global C2 link performance standards established through accumulated operational experience.

ATM impact. RPAS become a managed element of trajectory-based network management. ATFM constraints are applied to the RPAS trajectory the same way as to crewed traffic. HALE operators submit desired trajectories; RTA constraints are applied at metering points. RPAS performance profiles (lower speed in climb/descent) are known to the trajectory management system and factored automatically into conflict detection.

This phase aligns with ASBU Block 3 (from 2031) in the GANP roadmap.

Airspace class access ladder#

Doc 10019, §14.2.4 states: "The operational and equipage requirements of RPA will be governed, as per manned aviation, by the class of airspace in which they will be operating."

Correspondence to Annex amendments and SARPs#

References#

• Doc 10019 (Manual on Remotely Piloted Aircraft Systems), Chapter 14, §14.2.1 — gradual integration process.
• Doc 10019, Chapter 14, §14.2.3-14.2.4 — airspace class requirements for RPA and the operational/equipage rules.
• Annex 2 (Rules of the Air), Appendix 4, §2.1 — certification requirements before and after 26 November 2026.
• Annex 8 (Airworthiness), Part VIII, §1.4.3 — type certification of RPA inclusive of RPS and C2 Link from 26 November 2026.
• Doc 9750 (GANP), ASBU Block 3 — long-term evolution context for full RPAS integration in TBO (authoritative source — not in local library; see https://ganpportal.icao.int/).

Six threads that together constitute RPAS integration#

RPAS integration into non-segregated controlled airspace requires simultaneous readiness across six functional axes. Unlike a single-technology problem, a gap in any thread blocks routine international operations. The threads are interdependent: DAA depends on C2 link continuity; ATM procedures depend on DAA approval; the lost-C2-link contingency ties threads 2 and 5 together.

The six threads are:

• Thread 1: Airworthiness and Type Certification
• Thread 2: C2 Link (command and control link)
• Thread 3: Detect-and-Avoid (DAA)
• Thread 4: Remote Crew Licensing
• Thread 5: ATM Procedures
• Thread 6: Contingency and Lost-C2-Link

Thread 1 — Airworthiness and Type Certification#

Governing instruments: Annex 8 Parts VIII/IX, Annex 6 Part IV, Annex 2 Appendix 4.

The airworthiness thread covers the lifecycle of design approval (type certificate) and operational approval (ROC) for the integrated RPAS system. The key departure from manned aviation is system-level certification: the TC must cover the RPA, the RPS, and the C2 link together, because their interdependencies are safety-critical.

Key aspects:

• TC application to the State of Design; TC covers RPA performance envelope, flight envelope protections, C2 link redundancy architecture, DAA equipment installation, and RPS design standards.
• Certificate of airworthiness from the State of Registry; as of 26 November 2026, the CofA must convey airworthy status of the complete RPAS system.
• RPAS operator certificate (ROC) from the State of the Operator under Annex 6, Part IV; covers operations specifications, crew training and currency, maintenance control, and SMS.
• Continuing airworthiness: the RPAS operator is responsible for maintaining all RPAS components, including the C2 link if provided by a contracted C2 service provider, in an airworthy condition.

Thread 2 — C2 Link#

Governing instruments: Doc 10019 Chapter 11, Annex 8 Part VIII Chapter 11.

The C2 link thread is often the most complex certification challenge. No single universal RLP standard exists yet; the performance requirements are defined per RPAS design and agreed during the certification process.

Key aspects:

• Architecture choices: RLOS (within radio line of sight, using the 5 030-5 091 MHz ITU allocation or other approved bands), or BRLOS (satellite relay, or multiple relay layers).
• Redundancy: dual simultaneous decorrelated links or active/standby configurations increase availability. A failure in one link of a dual system triggers a reversionary procedure, not the full lost-C2-link procedure.
• C2 service provider (C2CSP): where the link is provided by a third-party network (e.g. satellite operator), the C2CSP must either be under civil aviation safety oversight or have its safety performance managed under the RPAS operator's SMS. Service level specifications (SLS) and service level agreements (SLA) govern the QoS delivered to the operator.
• Spectrum protection: the 5 030-5 091 MHz band and applicable satellite bands must be protected from harmful interference; this is a regulatory matter under ITU coordination.
• ATC voice relay: if ATC communications are relayed over the C2 link, the combined availability must satisfy both the C2 RLP and the ATC communication RCP for the airspace.

Thread 3 — Detect-and-Avoid (DAA)#

Governing instruments: Doc 10019 Chapter 10, Annex 2 Appendix 4, RTCA DO-365 / DO-362 (not in local library).

The DAA thread provides the functional equivalent of a pilot's visual scan and right-of-way obligations. For controlled airspace, the primary function is remain-well-clear (RWC) with a secondary collision-avoidance (CA) function.

Key aspects:

• RWC function: detects traffic approaching the RWC boundary and alerts the remote pilot to manoeuvre well before separation minima are threatened. Requires quantitative definitions of the RWC volume agreed with the approving authority.
• CA function: last-resort automation (or remote pilot action) when the conflicting aircraft crosses the CA threshold. The CA manoeuvre must be consistent with the rules of the air. If CA is automated, the system may act during lost-C2-link conditions.
• ACAS interoperability: if the conflicting crewed aircraft is equipped with ACAS, the RPA's DAA advisory must be compatible with the ACAS RA to prevent conflicting manoeuvres.
• Sensor mix: different sensors (radar, ADS-B, optical, acoustic) address different environments and threat classes. A single sensor is unlikely to be sufficient for all conditions. Sensor fusion is required.
• Approval: the DAA system must be approved by the State of Registry. RTCA DO-365 (MOPS for DAA) and DO-362 (C2 link MOPS) are the industry standards supporting certification in the US; EUROCAE equivalents exist in Europe.

Thread 4 — Remote Crew Licensing#

Governing instruments: Annex 1, Chapter 2, §§2.11-2.14.

The remote pilot licence framework in Annex 1 mirrors the pilot licence structure for crewed aircraft but with RPAS-specific requirements.

Key aspects:

• Remote pilot licence categories: aeroplane, helicopter, rotorcraft, etc. The category rating reflects the RPA type.
• Medical fitness: holders of remote pilot licences are subject to the same medical periodicity rules as private pilot licence holders (48-month validity, reducing to 24 months after age 40, to 12 months after age 50 in a Recommendation).
• Instrument rating where IFR operations are planned.
• Practical test requirement: the applicant must demonstrate knowledge and skill competencies for the category and rating, using the RPAS appropriate to the privileges sought.
• RPAS instructor rating: required to provide instruction on RPAS operations (Annex 1, §2.14).
• Amendment 179 to Annex 1 (applicable 26 November 2026) aligns the remote pilot licence framework with RPASP/18 output for international operations.

Thread 5 — ATM Procedures#

Governing instruments: Doc 10019 Chapter 14, Annex 2, Doc 4444 (PANS-ATM).

The ATM procedures thread covers how the RPAS participates in the ATM system in the same way as crewed aircraft, plus the RPAS-unique procedures.

Standard ATM procedures (same as crewed): flight plan submission (including filed lost-C2-link contingency options), standard ATC clearance compliance, transponder squawk, SSR/ADS-B mode compliance, right-of-way rules under Annex 2, CNS equipage per airspace class (RVSM, PBN, 8.33 kHz), level change coordination, transition from VFR to IFR in IMC.

RPAS-unique ATM aspects:

• Response latency: ATCOs must understand that the round-trip latency (ATC instruction — C2 link to RPS — remote pilot response — C2 link to RPA — RPA manoeuvre) may make "expedite" or "immediate" instructions impractical. Specific RPA performance characteristics (speed, climb, turn rate) must be briefed to controllers.
• HALE separation: a HALE RPA transiting cruise levels at a fraction of manned aircraft cruise speed creates a dynamic separation challenge. Pre-coordination with ATC is required for level-change profiles.
• Transponder code for lost-C2-link: currently procedural (using existing codes pending a dedicated standard). Future SARPs may introduce a new non-discrete code.
• Controller training: ATCOs serving airspace where RPAS operate routinely need familiarity with RPAS performance characteristics, communication relay procedures, and the lost-C2-link procedure.

Thread 6 — Contingency and Lost-C2-Link#

Governing instruments: Doc 10019 Chapter 11, §§11.6-11.7.

The lost-C2-link (lost link) thread is unique to RPAS and the most safety-critical operational procedure. It is covered in detail in the modules.md file.

Key aspects:

• Tsloss: the maximum duration of C2 link unavailability before the lost- C2-link condition is declared. Agreed during certification. Long enough to avoid nuisance alerts, short enough to protect other airspace users.
• Lost-C2-link flight option: the pre-filed contingency procedure. Options may include continuing on a filed holding pattern, proceeding direct to the filed alternate aerodrome, or executing a descent to a specific altitude. The chosen option is known to ATC before the flight.
• ATC notification: the remote pilot notifies ATC of which lost-link option is being executed; the RPA's SSR code changes to alert ATC.
• Recovery: the remote pilot and the RPAS continuously attempt to recover the C2 link via reversionary architectures or frequency switching.
• CA during lost-link: if the DAA system supports automated CA, the RPA may execute a CA manoeuvre even during lost-link to avoid collision. If CA is not automated, the lost-link contingency procedure must protect against collision in the most probable traffic scenarios.

References#

• Doc 10019 (Manual on Remotely Piloted Aircraft Systems), Chapter 11 — C2 link architecture, performance, spectrum, and lost-link procedures.
• Doc 10019, Chapter 10 — DAA overview, hazard types, RWC, CA, and approval requirements.
• Doc 10019, Chapter 14, §14.3.3 — ATCO awareness of RPA performance characteristics and response latency.
• Annex 1 (Personnel Licensing), Chapter 2, §2.11-2.14 — remote pilot licence, categories, ratings, and instructor rating.
• Annex 8 (Airworthiness), Part VIII, Chapter 11 — C2 Link and DAA airworthiness provisions for remotely piloted aeroplanes.
• RTCA DO-365 (Minimum Operational Performance Standards for DAA) — industry standard for DAA certification (authoritative source — not in local library).
• RTCA DO-362 (MOPS for C2 Link Systems) — industry standard for C2 link certification (authoritative source — not in local library).

Why the lost-C2-link procedure is the key integrating module#

The lost-C2-link contingency procedure is the single most important RPAS- unique operational element. It determines whether an RPAS can be safely accommodated in controlled airspace: without a predictable, filed, and ATC- accepted lost-link procedure, no integration is possible. It integrates all six functional threads — airworthiness (procedures defined in TC application), C2 link (Tsloss parameter), DAA (CA during lost link), remote crew licensing (remote pilot trained on the drill), ATM procedures (filed procedure, transponder code), and contingency management (link recovery).

Doc 10019, Chapter 11, §§11.6-11.7 is the primary guidance. The procedure is worked through below as a complete operational module.

Pre-flight: planning the lost-C2-link procedure#

Before departure, the RPAS operator and remote pilot must establish and file the lost-C2-link procedure with the ATS authority. This involves:

Alternate aerodrome selection. For long-distance flights, multiple alternate aerodromes appropriate to the route are identified. Selection criteria include: proximity to likely C2 loss locations, meteorological conditions, aerodrome capability for the RPA, and the RPA's fuel state at the point of C2 loss. The remote pilot updates the active alternate in the FMS during the flight so the RPA's expected lost-link route is always current.

Lost-C2-link flight option. The operator chooses among the available contingency options (consistent with what the TC holder has defined) and files it with ATC as part of the flight plan. Options typically include:

• Proceed via a defined holding pattern at a specific waypoint and altitude.
• Proceed directly to the pre-filed alternate aerodrome via a specific route.
• Descend to a defined altitude on the current track and continue.
• Execute an immediate return to the departure aerodrome.

The filed option must be predictable to ATC — once the lost-link state is declared, the RPA's actions are known.

ATC coordination. The ATS authority reviews the filed procedure and confirms it is compatible with the ATC environment. In early operations, ATC may need to approve the lost-link option on a case-by-case basis "until ATC has confidence in the process" (Doc 10019, §11.6.22).

In-flight: C2 link monitoring#

During the flight, the RPS continuously monitors C2 link performance. The key indicators monitored are:

• End-to-end transaction time (latency of the most recent control transaction).
• Availability of the link (proportion of time the link is operational).
• Integrity of received messages.

If the C2 link degrades but remains above the minimum usable performance, the remote pilot must assess whether to continue. Repeated short dropouts even below Tsloss individually do not individually trigger the procedure, but their pattern may indicate underlying degradation warranting voluntary initiation of the lost-link procedure to maintain safe operations.

A C2 link interruption lasting less than Tsloss is a short degradation event. The remote pilot waits for recovery. If the interruption exceeds Tsloss, the lost-C2-link condition is declared.

The following are explicitly NOT lost-C2-link situations (Doc 10019, §11.6.12):

• Erroneous messages from undetected RPS or RPA faults.
• Failure of one link in a dual-redundant C2 link (triggers reversionary procedure instead).
• System failures causing the RPA to lose controlled flight (separate emergency category).
• Short planned interruptions during handovers.

Lost-C2-link condition declared: the drill#

Step 1 — Declare and notify. Once Tsloss is exceeded, the lost-C2-link condition is declared. The remote pilot notifies ATC on the communication channel available (voice radio direct or via an alternative path if the C2 link is also carrying ATC communications). The RPA's transponder is set to the appropriate code. If the C2 link carries the ATC voice relay and that relay is also lost, the RPA is effectively radio-silent to ATC from the ATC perspective.

Step 2 — Initiate filed contingency. The remote pilot notifies ATC which lost-C2-link flight option is being executed. The RPA's onboard systems execute the pre-programmed procedure automatically (since the remote pilot can no longer send commands to the RPA). The FMS proceeds to the filed holding point, alternate aerodrome, or defined route.

Step 3 — DAA during lost-link. If the DAA system supports automated collision avoidance, the RPA may execute CA manoeuvres during the lost- link period despite the absence of remote pilot input. Doc 10019, §10.4.3.4: "If the DAA system design allows automated CA, the RPA may perform the CA manoeuvre despite loss of the C2 link." If CA is not automated, the filed contingency procedure must be designed to keep the RPA away from other traffic throughout its duration.

Step 4 — Continuous recovery attempt. In parallel with executing the contingency procedure, the remote pilot and RPAS systems continuously attempt C2 link recovery. Recovery methods include:

• Frequency switching to a backup frequency allocation.
• Switching to a standby or alternative link architecture (e.g., switching from RLOS to BRLOS satellite path).
• RPS handover to a secondary remote pilot station with a different antenna.
• Waiting for the RPA to move into a better coverage area.

Step 5 — Link recovery or aerodrome arrival. If the C2 link recovers before the RPA reaches the alternate aerodrome, normal operations may resume. Recovery must be confirmed as stable before the lost-link procedure is cancelled and normal ATC clearances are resumed. The remote pilot notifies ATC of the recovery and obtains a new clearance.

If the link is not recovered, the RPA lands at the alternate aerodrome under its automated procedure. Arrival at the alternate must be coordinated with the ATC unit; the Mode S data link (if equipped) may provide position information to ATC in the absence of voice.

Worked example: oceanic HALE RPAS#

Scenario: a HALE RPAS is on an IFR trans-oceanic flight at FL400, using a single-satellite BRLOS C2 link with Tsloss set at 90 seconds. The pre-filed lost-link option is to proceed direct to an en-route alternate aerodrome at FL360 (descent profile pre-programmed to avoid impacted cruise altitudes) at a filed time.

Event sequence:

1. At 14:32Z, the C2 link fails (satellite beam pointing loss).
2. The RPS C2 link monitor records the outage start.
3. At 14:33:30Z (90 seconds), Tsloss is exceeded. The lost-C2-link condition is declared.
4. The remote pilot transmits on HF: "Ocean Control, RPAS [callsign], lost C2 link, executing Option Bravo, proceeding to [alternate], descending FL360."
5. The RPA's FMS executes the pre-programmed profile automatically.
6. The transponder squawks the agreed lost-C2-link code.
7. The remote pilot simultaneously initiates BRLOS link recovery via the backup satellite service.
8. At 14:41Z, the backup satellite link is established. Normal C2 is restored.
9. The remote pilot notifies ATC: "[callsign], C2 link recovered, request return to filed route."
10. ATC issues a new clearance. The remote pilot resumes manual control.

Design principles from this module#

The lost-C2-link procedure illustrates six design principles for RPAS integration that apply beyond the contingency scenario:

Predictability. ATC must always be able to predict what the RPA will do. Filed procedures, pre-computed routes, and the FMS executing exactly what was filed are the basis of integration in controlled airspace.

Autonomy within agreed boundaries. The RPA acts autonomously during lost-link only within the pre-agreed envelope. It does not improvise.

ATC as informed partner. The remote pilot's first obligation on declaring lost-link is to notify ATC. Integration requires ATC to be a participant in RPAS operations, not a passive observer.

Graceful degradation. The RPA system is designed so that degrading link quality triggers a hierarchy of responses: degradation warning, reversionary architecture, lost-link declaration, autonomous contingency execution — each step more conservative, each maintaining safety margins.

DAA as the final safety layer. Even without the remote pilot, the DAA system (if CA-capable) provides a last safety layer against mid-air collision during the lost-link period.

Recovery as design intent. The system is designed to recover the C2 link, not simply to survive without it. The lost-link procedure is a temporary state, not an end state.

References#

• Doc 10019 (Manual on Remotely Piloted Aircraft Systems), Chapter 11, §11.6.12 — events not constituting lost C2 link.
• Doc 10019, Chapter 11, §11.6.13 — criteria for identification of lost C2 link condition.
• Doc 10019, Chapter 11, §11.6.20-11.6.22 — intermittent degradation assessment; alternate aerodrome selection; ATC coordination of the lost-link option.
• Doc 10019, Chapter 11, §11.7 — C2 link recovery procedures.
• Doc 10019, Chapter 10, §10.4.3.4 — automated CA manoeuvres during lost-C2-link conditions.
• Doc 10019, Chapter 14, §14.2.11 — transponder procedure for lost-C2-link state; distinction from voice comm failure (7600) and emergency (7700).

What must be in place before routine RPAS operations in controlled airspace#

Enablers are the prerequisites that must exist before an RPAS can operate routinely in non-segregated controlled airspace. Unlike a single-system deployment, RPAS integration requires simultaneous readiness across regulatory, technical, procedural, human, and institutional dimensions.

1. Communications, Navigation, and Surveillance (CNS)#

1.1 Communications#

The RPA carries VHF (and HF for oceanic routes) radio equipment per the requirements for its airspace class and route, consistent with Annex 10. ATC communications are either transmitted by equipment on the RPA directly, or relayed via the C2 link to the remote pilot at the RPS. The relay adds a latency overhead to every ATC communication transaction.

Where dual communication paths are required, Doc 10019 §12.7.3 recognizes that one radio onboard plus a secondary path (e.g., SATCOM) from RPS to ATC may satisfy the requirement, subject to competent authority acceptance.

RPAS will eventually need SWIM compatibility when SWIM service requirements for RPAS are defined (Doc 10019, §12.8).

1.2 Navigation#

RPA must meet navigation performance requirements for the airspace class and route: RNP/RNAV specifications per the PANS-OPS procedure design, and RVSM equipment where operating at RVSM altitudes. The FMS must support the RTA/CTA function if the RPAS is to participate in initial 4D metering or TBO operations.

1.3 Surveillance#

RPA must carry Mode C/S transponder and ADS-B equipment consistent with the requirements for the airspace class. The lost-C2-link transponder code procedure requires a Mode A code change. ADS-B OUT provides surveillance to ATC regardless of voice communication status.

2. C2 Link Spectrum#

The ITU has allocated the 5 030-5 091 MHz frequency band for aeronautical mobile C2 links (RLOS operations). RPAS operators must comply with ITU spectrum regulations and national frequency assignments.

For BRLOS (satellite) operations, FSS bands (12/14 GHz and 20/30 GHz) have been studied by ITU in collaboration with ICAO for suitability. Ongoing ITU studies are expected to clarify the conditions under which these bands may support RPAS C2 (Doc 10019, §11.3.15).

Spectrum protection from harmful interference is a high priority. The C2 link availability and integrity depend on freedom from intentional jamming, unintentional interference, and physical obstruction.

3. Certification and Regulatory Framework#

3.1 Type certificate (TC)#

The RPAS type certificate must be issued by the State of Design covering the RPA, RPS, and C2 link as an integrated system. For operations from 26 November 2026, the TC must comply with Annex 8, Parts VIII/IX.

3.2 Certificate of airworthiness (CofA)#

Issued by the State of Registry. From 26 November 2026, the CofA must convey airworthy status of the complete RPAS system.

3.3 RPAS operator certificate (ROC)#

Issued by the State of the Operator under Annex 6, Part IV (from 26 November 2026). The ROC covers operations specifications, crew qualifications, maintenance arrangements, and SMS obligations.

3.4 State authorizations#

Under Annex 2, Appendix 4, the RPAS operator must obtain:

• Authorization from the State of take-off.
• Special authorization from each overflown State (not less than seven days before the flight unless otherwise agreed).
• Prior coordination with the ATS authority for operations over the high seas.

These authorization requirements are a significant operational overhead for international RPAS operations until bilateral or multilateral agreements streamline them.

4. ATM Procedures and Tools#

4.1 Controller training and tools#

ATCOs serving airspace where RPAS operate routinely must receive training on:

• RPAS performance characteristics (speed, climb/descent rates, turn radius).
• Communication relay procedures and expected latency.
• Lost-C2-link procedure recognition and response.
• DAA alert implications for ATC separation services.

The ATCO's flight data processing tool and radar/ADS-B display must be able to flag RPAS traffic with relevant RPAS-specific status information.

4.2 Filed lost-C2-link procedure acceptance#

The ATS authority must accept the filed lost-C2-link contingency as part of flight plan processing. This requires a procedure for reviewing and approving the filed option against the ATC environment along the route. Until ATC has confidence from operational experience, acceptance may be on a flight-by-flight basis.

4.3 Transponder code administration#

States must agree on the transponder code(s) to be used for the lost-C2-link state. Pending a standardized ICAO code, each State or region must publish a procedure for RPAS operators.

5. DAA System Approval#

The DAA system must be designed, tested, and approved by the State of Registry before the RPAS can operate in airspace where DAA is required. Approval requires:

• Defined quantitative standards for the RWC volume (distance and time thresholds agreed with the approving authority).
• Performance testing of the sensor suite (ADS-B, radar, EO/IR, acoustic) across the range of encounter geometries.
• Evaluation of CA manoeuvre compliance with Annex 2 right-of-way rules.
• ACAS compatibility verification where the RPAS will operate alongside ACAS-equipped aircraft.

Industry standards RTCA DO-365 (DAA MOPS) and DO-362 (C2 link MOPS) provide the certification baseline in the US and are referenced by EASA for Europe. No equivalent ICAO SARPS for DAA equipment performance currently exist in the ICAO Annexes beyond the general DAA definition.

6. Human Factors and Training#

Remote pilots must be trained and current on:

• Normal RPAS operating procedures.
• Abnormal and emergency procedures including lost-C2-link drill.
• RPAS instrument flight procedures.
• DAA system interpretation and response.
• ATC communications via relay (including voice relay lag).
• Fatigue risk management for long-duration remote operations.

Doc 10019, Chapter 8 provides detailed guidance on remote pilot training requirements, type rating training, and recurrency. The RPAS instructor rating (Annex 1, §2.14) ensures that training standards are maintained across operators.

Simulator training devices (FSTDs for RPAS) are recognized in Annex 1 as providing an accurate representation of the RPAS environment, including the RPS interface.

7. Safety Management#

The RPAS operator must maintain an SMS (Annex 6, Part IV; Doc 10019, Chapter 7) appropriate to the complexity and risk of operations. The SMS must account for:

• Interactions with other airspace users (the primary external risk).
• C2 link service provider performance (if an external C2CSP is used).
• Hazard identification specific to RPAS operations (see Doc 10019, §7.6).
• Integration with the State Safety Programme (SSP) of the State of the Operator.

8. Institutional and Coordination Arrangements#

International RPAS operations require bilateral or multilateral coordination frameworks to streamline the authorization requirements in Annex 2, Appendix 4. Without such frameworks, obtaining State-by-State authorization for routine routes is operationally impractical.

The ICAO RPAS Panel (RPASP) provides the normative framework; regional bodies (APANPIRG, MIDANPIRG, EANPG) are expected to develop regional RPAS coordination mechanisms. EASA in Europe has developed the certified category framework under Reg (EU) 2019/947, which provides a model for harmonized regional authorization.

References#

• Doc 10019 (Manual on Remotely Piloted Aircraft Systems), Chapter 11, §11.3.10 — C2 link spectrum protection priority.
• Doc 10019, Chapter 11, §11.3.14-11.3.15 — 5 030-5 091 MHz RLOS allocation; FSS band studies for BRLOS.
• Doc 10019, Chapter 12, §12.7.3 — alternative communications equipage arrangements for RPAS.
• Doc 10019, Chapter 12, §12.8 — future SWIM compatibility requirement for RPAS.
• Doc 10019, Chapter 14, §14.3.3-14.3.4 — ATCO training on RPAS performance characteristics; response time, speed, climb/descent characteristics.
• Doc 10019, Chapter 8 — remote pilot training requirements, FSTD for RPAS.
• Annex 1 (Personnel Licensing), Chapter 2, §2.14 — RPAS instructor rating requirements.
• Annex 2 (Rules of the Air), Appendix 4, §3 — request for authorization procedure for international RPAS flights.
• RTCA DO-365 and DO-362 — DAA and C2 link MOPS (authoritative source — not in local library).
• EASA Reg (EU) 2019/947 — certified category RPAS operations framework (authoritative source — not in local library).

The performance case for RPAS integration#

RPAS integration is justified on the overriding condition that it must not increase safety risk to manned aircraft and must deliver benefits equivalent to manned operations in terms of efficiency, predictability, and access. Doc 10019 frames this as: "introduction of remotely piloted aircraft into non-segregated airspace and at aerodromes should in no way increase safety risks to manned aircraft" and "RPAS will have to be at least as safe as, or safer than, present manned operations."

The performance objectives are mapped to the Key Performance Areas (KPAs) defined in Doc 9854 (Global ATM Operational Concept) and Doc 9883 (Manual on Global Performance of the Air Navigation System).

KPA performance table#

The table below maps each primary KPA to the RPAS integration performance objective, the primary KPI, and the maturity phase at which the improvement is principally delivered.

KPA contribution by integration phase#

The matrix below scores each KPA by its principal benefit horizon across RPAS integration phases (1 = some benefit/progress, 2 = clear benefit, 3 = primary driver / achieved). Safety is a baseline requirement at all phases.

Detailed KPI definitions#

Safety KPIs#

Near mid-air collision (NMAC) rate. The frequency of encounters within the defined NMAC threshold volume per RPAS flight hour. The RPAS DAA system target is to keep NMAC rate at or below the crewed aviation equivalent for the same airspace class and flight type.

DAA system activation-to-avoidance rate. The proportion of DAA RWC alerts that result in a successful manoeuvre keeping the RPA outside the CA threshold. A rate below an agreed threshold triggers a design review of the DAA system.

Lost-C2-link procedure conformance. The proportion of lost-C2-link events in which the RPA executes the pre-filed contingency procedure accurately (route, altitude, timing within agreed tolerances). Deviations indicate FMS programming errors or procedure design flaws.

Predictability KPIs#

Trajectory conformance rate. Proportion of RPAS flight segments where the actual flown track and altitude remain within the tolerance of the filed route and cleared altitudes. A lower conformance rate increases ATCO workload.

ATC instruction count per RPAS flight. The number of positive ATC interventions per flight attributable to RPAS performance characteristics (slow climb, response latency) compared to the crewed-aircraft average. A high count indicates accommodation procedures are adding workload.

Capacity KPIs#

ATFM delay attributable to RPAS. Delay minutes per flight caused specifically by RPAS accommodation procedures, lost-C2-link events, or RPAS performance characteristics restricting sector throughput. The target for Phase 2 integration is zero incremental ATFM delay attributable to RPAS.

Interoperability KPIs#

Annex 10 communication performance. Proportion of RPAS ATC communication transactions meeting the required communication performance (RCP) type for the airspace, accounting for C2 link relay latency.

CNS compliance rate. Proportion of RPAS flights carrying and activating all required CNS equipment (transponder mode, ADS-B, comm equipage) throughout the flight.

Performance measurement framework#

RPAS performance data is gathered through:

• State accident and incident reporting (ADREP): NMACs and incidents involving RPAS are reported to ICAO through the normal safety reporting channel.
• ANSPs: ATFM delay attributable to RPAS can be extracted from ATFM logs once RPAS traffic is identified in the data stream.
• RPAS operators: ROC holders maintain SMS records including C2 link performance data, DAA activation events, and lost-link procedure execution records.
• Regional bodies: APANPIRG, MIDANPIRG, and EANPG will eventually monitor RPAS integration metrics in their regional performance reports as RPAS operations grow.

No consolidated global RPAS performance reporting framework exists yet (as at 2026). The RPASP has recommended that performance data collection structures be developed in parallel with the SARPs package.

References#

• Doc 10019 (Manual on Remotely Piloted Aircraft Systems), Foreword — governing safety principle: no increased risk to manned aircraft; RPAS at least as safe as manned operations.
• Doc 10019, Chapter 10, §10.1.5 — RPAS will have to be at least as safe as, or safer than, present manned operations.
• Doc 9854 (Global ATM Operational Concept) — KPA definitions and global performance framework (authoritative source — not in local library).
• Doc 9883 (Manual on Global Performance of the Air Navigation System) — KPA definitions and global KPI methodology (authoritative source — not in local library).

Two timelines to keep distinct#

1. ICAO regulatory and standards development — when ICAO and RPASP produced circulars, Annex amendments, panels, and guidance.
2. SARPs applicability — the dates by which States must comply or national provisions must conform.

Regional and national implementation timelines (FAA, EASA) are a third axis, running in parallel.

RPAS regulatory development timeline#

SARPs applicability table#

Regional implementation context#

Europe (EASA). Reg (EU) 2019/947 and 2019/945 established the European UAS regulatory framework with the certified category applicable to larger RPAS from 2020 onwards. EASA is progressively developing Acceptable Means of Compliance and Guidance Material for the certified category operations in controlled airspace aligned with ICAO SARPs.

United States (FAA). The FAA has operated RPAS integration under BVLOS waiver/exemption processes and is developing a type certification pathway for larger RPAS under its UAS integration framework. DO-365 and DO-362 provide the certification basis. The FAA NextGen programme includes RPAS integration as a long-term element of the NAS modernization.

Asia-Pacific. APANPIRG monitors RPAS developments as part of its ASBU implementation tracking. Several APAC States (Australia, Japan, Singapore) have advanced national RPAS regulations and are moving toward ICAO SARP alignment for international IFR operations.

Middle East and Africa. MIDANPIRG and AFIRS are at earlier stages. The 26 November 2026 ICAO SARPs applicability date applies to all contracting states.

How to read a date in an RPAS document#

When an RPAS regulatory document uses a date, verify which kind it is:

• "Applicable 26 November 2026" — ICAO SARP applicability date; not a deadline for individual operators, but the date from which the international standard is binding on contracting states.
• "First edition 2015" — Doc 10019 publication date (guidance, not SARPs).
• "RPASP/18 (2024)" — ICAO expert panel meeting that produced the SARPs.
• "EASA Reg (EU) 2019/947" — European regulation in force from 2020.

References#

• ICAO Circular 328 (UAS, 2011) — first ICAO conceptual framework for UAS/RPAS integration (authoritative source — not in local library).
• Doc 10019 (Manual on Remotely Piloted Aircraft Systems), 1st edition 2015 — primary RPAS guidance document; first edition publication.
• Annex 2 (Rules of the Air), Table of Amendments — Amendment 43 (2018), Amendment 47 (2021) RPAS provisions history.
• Annex 8 (Airworthiness), Table of Amendments — Amendment 108 (2021), Amendment 110 (2024/2026) RPAS airworthiness provisions.
• Annex 1 (Personnel Licensing), Table of Amendments — Amendment 175 (2018), Amendment 179 (2024/2026) remote pilot licence provisions.
• EASA Reg (EU) 2019/947 and 2019/945 — European UAS certified category framework (authoritative source — not in local library).
• RTCA DO-365 and DO-362 (2020) — US DAA and C2 link MOPS (authoritative source — not in local library).

Primary ICAO sources#

• Doc 10019 (Manual on Remotely Piloted Aircraft Systems, RPAS), 1st edition 2015 — comprehensive primary guidance on RPAS airworthiness, operations, C2 link, DAA, licensing, and ATM integration; primary source for this topic.
• Doc 10019, Foreword — ICAO goal: routine RPAS operations in a safe, harmonized, seamless manner comparable to manned operations; governing safety principle of no increase in risk to manned aircraft.
• Doc 10019, Chapter 2 — Introduction to RPAS; RPAS components and definitions; operational categories (VLOS, BVLOS, RLOS, BRLOS).
• Doc 10019, Chapter 4, §4.5 — C2 link as a component of the RPAS type design; contracted C2 link service provisions.
• Doc 10019, Chapter 10 — Detect and Avoid (DAA): overview, hazard identification, RWC function, CA function, DAA system design, DAA equipment for RPAS.
• Doc 10019, Chapter 11 — Command and Control (C2) link: architecture, spectrum, RCP/RLP requirements, C2 link management procedures, protection requirements, lost-C2-link characteristics and contingency procedures, C2 link recovery.
• Doc 10019, Chapter 12 — ATC communications for RPAS: relay over C2 link, RCP for ATC communications, minimum communications airborne equipment, future SWIM compatibility.
• Doc 10019, Chapter 13 — Remote Pilot Station (RPS): functional overview, design principles, display of information for DAA and situational awareness.
• Doc 10019, Chapter 14 — Integration of RPAS operations into ATM and ATM procedures: integration principles, airspace class requirements, C2 link latency, transponder procedures, right-of-way, RPAS performance considerations for ATC.

ICAO Annexes#

• Annex 2 (Rules of the Air), Chapter 3, §3.1.9 — RPA operated to minimize hazards; reference to Appendix 4.
• Annex 2, Appendix 4 — Remotely Piloted Aircraft Systems: general operating rules, certificates and licensing, request for authorization; provisions before and after 26 November 2026.
• Annex 1 (Personnel Licensing), Chapter 2, §2.11 — general rules concerning remote pilot licences and ratings for international RPAS operations.
• Annex 1, Chapter 2, §2.13 — remote pilot licence privileges, limitations, and conditions.
• Annex 1, Chapter 2, §2.14 — RPAS instructor rating.
• Annex 8 (Airworthiness of Aircraft), Part VIII — type certification requirements for remotely piloted aeroplanes: structural, systems, performance, C2 Link, and DAA requirements; applicable from 26 November 2026.
• Annex 8, Part IX — type certification requirements for remotely piloted helicopters.
• Annex 7 (Aircraft Nationality and Registration Marks), §2.3 — unmanned aircraft including RPA subject to registration and marking requirements.
• Annex 6, Part IV (from 26 November 2026) — RPAS operator certificate (ROC) provisions for international commercial RPAS operations.

ICAO Circular#

• ICAO Circular 328 (UAS, 2011) — first ICAO publication setting out the conceptual framework for UAS/RPAS integration and the approach to SARPs development (authoritative source — not in local library).

ICAO RPAS Panel outputs#

• RPASP/5 and RPASP/6 (2018) — Amendment 175 to Annex 1 (remote pilot licence framework) and Amendment 43 to Annex 2 (RPAS provisions) (authoritative source — not in local library; amendments incorporated in local Annex files).
• RPASP/11 and RPASP/13 (2021) — Amendment 47 to Annex 2 (RPAS certificates, C2 Link definitions) and Amendment 108 to Annex 8 (RPAS airworthiness provisions) (authoritative source — not in local library).
• RPASP/18 (2024) — Amendment 179 to Annex 1 and Amendment 110 to Annex 8; new Annex 6, Part IV; full RPAS integration SARPs applicable 26 November 2026 (authoritative source — not in local library).

Industry standards (not in local library)#

• RTCA DO-365 (Minimum Operational Performance Standards for Detect and Avoid Systems for Unmanned Aircraft Systems, large UAS, 2020) — primary US certification standard for DAA systems; basis for FAA STC/TC processes (authoritative source — not in local library).
• RTCA DO-362 (Minimum Operational Performance Standards for C2 Link Systems for Unmanned Aircraft Systems, large UAS, 2020) — primary US certification standard for C2 link systems (authoritative source — not in local library).

Regional regulatory references (not in local library)#

• EASA Reg (EU) 2019/947 (Commission Implementing Regulation on the rules and procedures for the operation of unmanned aircraft) — European UAS framework; certified category applicable to RPAS in controlled airspace alongside crewed traffic (authoritative source — not in local library).
• EASA Reg (EU) 2019/945 (Commission Delegated Regulation on unmanned aircraft systems and on third-country operators) — UAS product standards; certified category product requirements (authoritative source — not in local library).