Detailed working notes on Continuous Descent Operations (CDO). This folder expands the summary in topics/cdo.md into per-aspect files so each can be read on its own.

Files in this folder#

• overview.md — what CDO is, environmental and efficiency rationale, ICAO Doc 9931 anchor.
• components.md — design principles, arrival procedure design, vertical-window approach, FMS-VNAV use.
• blocks.md — CDO maturity levels and ASBU-aligned implementation phases.
• threads.md — stakeholder strands (procedure design, ATC, flight ops, environmental authority).
• modules.md — anatomy of a CDO procedure design (objective, procedure, technology, enablers, KPIs).
• enablers.md — PBN, AMAN/extended AMAN, simulation, controller training, FMS performance.
• performance_objectives.md — KPAs (environment, fuel efficiency, noise) and KPIs (CDO penetration rate).
• timeline.md — Doc 9931 publication and regional CDO uptake (PEA, Asia, EUR).
• references.md — consolidated ICAO and external references for everything in this folder.

Reading order#

Start with overview.md, then components.md for the procedure-design mechanics. Move to blocks.md and threads.md to see how a State or ANSP sequences and assigns the work, then drill into modules.md, enablers.md, and performance_objectives.md. Use timeline.md for date context and references.md for citations.

Source basis#

Content is grounded in:

• ICAO Doc 9931, Continuous Descent Operations (CDO) Manual.
• ICAO Doc 8168 (PANS-OPS) Vol I, Part V, Chapter 3 (noise-abatement procedures, CCO/CDO references).
• ICAO Doc 8168 (PANS-OPS) Vol II (procedure design rules for STARs and approach procedures supporting CDO).
• ICAO Doc 4444 (PANS-ATM) — clearance phraseology, level allocation, AMAN practice.
• ICAO Annex 11 — ATS airspace classification and service responsibilities.
• ICAO Doc 9750 (GANP) and the ASBU framework (CDO thread, modules B0-CDO and B1-CDO).
• EUROCONTROL "A guide to implementing Continuous Descent" (web fallback for operational implementation patterns).
• FAA Optimized Profile Descent (OPD) practice (web fallback).

Scope note#

CDO is the arrival counterpart of CCO (Continuous Climb Operations). CDO and CCO share much of their enabler stack (PBN, FMS performance, controller phraseology) but are designed independently because the operational constraints on descent (sequence, separation in the TMA, noise management on approach paths) differ from those on climb-out.

What CDO is#

CDO stands for Continuous Descent Operation. PANS-OPS (Doc 8168, Vol I) defines CDO as an operation, enabled by airspace design, procedure design and ATC, in which an arriving aircraft descends continuously, to the greatest possible extent, by employing minimum engine thrust, ideally in a low-drag configuration, prior to the final approach fix or final approach point.

CDO is not a single procedure. It is the joint outcome of three domains working together:

1. Airspace design — how arrival airspace is structured around a TMA so that descents can be flown without level segments.
2. Instrument procedure design — STARs and approaches with vertical and speed windows that an FMS can fly at idle thrust.
3. ATC tactical handling — clearances that preserve the FMS path (early descent, minimal vectoring, no late step-downs).

The aircraft side is straightforward: the FMS computes a near-idle descent path from top of descent (TOD) to the final approach fix (FAF), and the pilot flies VNAV PATH/PROF with thrust at or near idle until the final stabilization segment.

Why CDO matters — environmental and efficiency rationale#

CDO is one of the most cited operational measures in ICAO and regional environmental strategies because the benefits are measurable per flight and accumulate quickly across a network:

• Fuel and CO2 — order-of-magnitude saving of tens of kilograms of fuel per arrival relative to a stepped-descent profile, scaling with stage length and TMA complexity. ICAO and EUROCONTROL studies put this in the region of ~50 kg per flight on busy European arrivals.
• Noise — measurable reductions of up to ~5 dB over portions of the arrival, driven by lower thrust at altitude and delayed configuration changes. CDO is a core element of the balanced approach to noise management at airports.
• Local air quality — proportional reductions in NOx, particulates, and contrail-precursor emissions because thrust-time at low altitude drops.
• Predictability — PBN-based CDO arrivals fly a more predictable vertical profile, which lets ATC sequence tighter without sacrificing separation margins.
• Crew workload — a continuous vertical path supports stabilized approach criteria and reduces last-minute re-planning.

The cost side is mostly upstream design effort and a careful re-think of TMA sequencing, not new airborne equipment for already-PBN-equipped fleets.

Distinction from CDFA#

CDO is frequently confused with Continuous Descent Final Approach (CDFA). They are different:

• CDO — the entire arrival from TOD to the FAF, enabled by airspace, procedure, and ATC. Concept-level.
• CDFA — a final-segment technique for non-precision approaches, flown as a stabilized constant-angle descent from the FAF to a decision altitude/height, instead of as dive-and-drive.

PANS-OPS notes that an NPA flown with advisory VNAV CDFA is a 3D operation, whereas a manually computed CDFA remains a 2D operation. CDO and CDFA are complementary: a well-designed STAR delivers CDO down to the FAF, and CDFA then keeps the descent continuous through the final segment.

Regional terminology#

The same operational idea appears under several names; these are not strictly synonyms but the differences are operationally narrow.

• CDA — Continuous Descent Arrival. Older European/UK terminology for what ICAO now calls CDO.
• OPD — Optimized Profile Descent. FAA and US industry term. Emphasises the FMS-computed idle-thrust path that flexes with weight, wind, and ATC constraints rather than a fixed altitude profile.
• Tailored Arrival. Used historically for trial/oceanic-feed variations of OPD.

ICAO Doc 9931 harmonises these under the umbrella term CDO.

Where CDO sits in the GANP#

CDO is one of the operational threads in the ICAO ASBU framework (see topics_detailed/asbu/threads.md). It is delivered through two modules in the standard taxonomy:

• B0-CDO — published CDO procedures at major airports, supported by PBN STARs and the ATC procedures needed to preserve a continuous descent in single-FIR operation.
• B1-CDO — extended CDO with cross-border arrival management (E-AMAN / XMAN) so the descent is preserved across FIR boundaries upstream of the destination TMA.

CDO depends on the NAVS thread (PBN), the RSEQ thread (AMAN / DMAN / SMAN), and the AMET thread (accurate winds for FMS path prediction). It pairs with CCO on the departure side.

CDO is delivered through a stack of design choices that interlock. Each component below is necessary; none is sufficient on its own.

1. Design principles (Doc 9931)#

The CDO Manual sets four design principles that recur through every implementation:

• Continuous descent. The vertical profile from TOD to FAF should contain no level segments. Where a level segment is unavoidable (e.g. for separation), it should be short, predictable, and as high as possible.
• Idle (or near-idle) thrust. The descent should be flyable with thrust at or near flight-idle for the majority of the descent. Drag is deployed only in the final stabilization segment.
• Low-drag configuration until late. Flap and gear extension are delayed to the latest practical point consistent with stabilized approach criteria.
• Compatibility with ATC. The procedure must be flyable under realistic ATC sequencing demands; designers consult controllers and flight-ops representatives, not just procedure specialists.

2. Arrival procedure design#

The STAR and the linked instrument approach are the procedural carrier of CDO. Design choices that matter:

• PBN STARs to the FAF. RNAV 1 or RNP 1 STARs that terminate at or immediately before the FAF, removing the need for tactical step-downs in the TMA.
• Multiple transitions. Long and short transitions, point-merge, or trombone arrival design absorb spacing without level-offs.
• Speed schedule. Published speeds at gate fixes harmonise the arrival flow without ATC having to assign speeds tactically.
• Connection to the approach. RNP APCH or RNP-AR linked to the STAR provides a seamless descent into the FAF and through to landing.
• Aircraft mix. Vertical and speed windows are sized so heavy and medium types, FMS-equipped and legacy aircraft, can all fly the same procedure.

3. The vertical-window approach#

The most consequential design pattern in modern CDO design is the vertical window (or "altitude window"): at each gate fix, the procedure publishes a vertical band — for example "between FL120 and FL150" — rather than a single hard altitude.

Why windows work:

• They give the FMS room to fly the optimum idle path for the day's weight and wind, rather than forcing thrust changes to hit a fixed altitude.
• They give ATC tactical room to manage spacing with small early-descent or hold-high instructions that the FMS can re-plan around.
• They accommodate aircraft mix without separate procedures.
• They keep the procedure simple to publish and chart.

Speed windows operate the same way at gate fixes where flow management matters (e.g. "240–260 KIAS at the merge fix").

A complementary design pattern is the point-merge system (PEA/EUR practice), in which arrivals fly along a fixed sequencing arc until ATC issues a "direct to" the merge point. The arc itself is a continuous descent at a known angle; the directs are also at a known angle to the FAF. The result is CDO with sequencing flexibility and very few controller transmissions.

4. FMS-VNAV use#

CDO depends on the FMS flying its computed VNAV path:

• VNAV PATH / VNAV PROF. The FMS targets a 3D path consistent with the published constraints; thrust auto-modulates around idle to hold the path.
• Wind data. FMS path prediction is wind-sensitive. Uplinked wind (where datalink is available), accurate ATIS winds, and crew-entered forecast winds at descent fixes all materially improve path conformance.
• Cost index and weight. Crew-entered cost index and accurate zero-fuel-weight feed the descent prediction.
• Re-planning. When ATC issues a tactical instruction (early descent, direct-to, hold-high), the FMS recomputes a new path; modern FMSs do this fast enough that the CDO is preserved.

The procedure designer must know which FMS generations are in the served fleet and design windows that the lowest-capability FMS can fly without resorting to drag.

5. ATC procedures preserving CDO#

Procedures and phraseology that protect the descent:

• Early descent clearances ahead of TOD, with the published profile.
• Avoidance of long level segments below 10,000 ft.
• Distance-to-go information rather than vectoring where possible, so the FMS keeps managing the path.
• "Descend via" or equivalent phraseology (per regional supplement) that authorises the published vertical and speed schedule in a single clearance.
• Speed control to manage spacing instead of vectoring or step-downs.
• Where vectoring is unavoidable, early descent and speed information to let the FMS re-plan.

6. Monitoring loop#

Component-level design is incomplete without a monitoring loop:

• CDO conformance — % of arrivals that fly the procedure without a level segment below a defined level (e.g. FL100, 7,500 ft, or 6,000 ft AGL).
• Vertical inefficiency — average distance flown level below FL100.
• Fuel and noise indices — derived from radar / ADS-B replays and FDR samples.

The monitoring outputs feed back into procedure redesign: gate-fix altitudes, window widths, and speed constraints are tuned over time.

CDO is normally implemented in phases rather than as a single project. This file maps out the maturity levels a State or ANSP works through, aligned with the ASBU Block structure for the CDO thread.

ASBU framing#

In the ASBU framework, the CDO thread carries two main modules:

• B0-CDO — Continuous Descent Operations (basic). Notional availability: from 2013. Published CDO procedures at major airports using PBN, controlled mostly within a single FIR.
• B1-CDO — CDO with extended arrival management. Notional availability: from 2019. CDO preserved across FIR boundaries via cross-border AMAN (XMAN / E-AMAN), trajectory-aware sequencing, and more refined vertical/speed-window design.

Block 2/3 evolution of CDO is implicit through the TBO thread: the 4D trajectory becomes the primary planning reference and the descent profile is one element of that trajectory.

Maturity model — the four typical phases#

Independent of the ASBU labels, every State or ANSP CDO programme moves through roughly the same four phases.

Phase 1 — Trial and demonstration#

Goal. Prove the concept locally with a small set of cooperating operators.

• One or two procedures published at a major airport, often at night or in low-demand windows.
• A short list of equipped airframes (typically widebody PBN-rich fleets).
• Manual ATC handling: dedicated controllers, pre-briefed crews, plain altitude restrictions in clearances.
• Measurement is event-based (per flight) rather than continuous.

Deliverable: a documented case that fuel and noise benefits are real in the local airspace, and that the TMA can absorb the procedure at low demand.

Phase 2 — Routine off-peak CDO#

Goal. Make CDO the default in low and medium demand.

• Procedures published as standard STAR/approach pairings.
• Trained controller cadre across the watch.
• Phraseology aligned with PANS-ATM ("descend via" or regional supplement equivalent).
• AMAN deployed at the TMA so arrival rate matches runway capacity at off-peak demand without tactical intervention.
• Continuous monitoring of CDO conformance KPIs.

Deliverable: more than half of arrivals flown as full CDO during off-peak periods; quantified per-flight fuel and noise benefit reported to the State environment authority.

Phase 3 — Mixed-mode CDO at peak#

Goal. Preserve CDO benefit at high demand, even if some level segments are unavoidable.

• Multiple-trajectory STAR designs (long/short transitions, point merge) absorb spacing without prolonged level segments.
• AMAN extends its planning horizon upstream (E-AMAN) so spacing is built up before the TMA, leaving the TMA close to free-flow.
• Time-Based Separation on final approach, where deployed, recovers capacity that headwind-day distance-based separation gives away.
• Mixed mode: full CDO when traffic permits; "partial CDO" with one or two managed level segments at peaks.

Deliverable: CDO-penetration KPI improves at peak hours toward the off-peak baseline; predictability of arrival times improves measurably.

Phase 4 — Cross-border / trajectory-aligned CDO#

Goal. Preserve CDO across FIR boundaries and align with TBO.

• E-AMAN reaching into upstream FIRs (XMAN) so the descent profile is planned from cruise.
• Datalink (CPDLC) clearances for descent management; uplinked winds improve FMS path prediction.
• Coordination with neighbouring ANSPs on speed control and level delegation upstream of the destination TMA.
• Full integration into the destination's TBO trajectory negotiation (Block 2 onwards).

Deliverable: predictable, low-fuel, low-noise arrivals at the destination irrespective of the upstream FIR's traffic load.

Reading the phases against the ASBU Blocks#

A State can be in Phase 2 at one airport and Phase 1 at another. The phase model applies per TMA, not per State.

Practical sequencing notes#

• Do not skip Phase 2. A jump from trial to peak-hour CDO without an embedded controller cadre and AMAN tooling fails on the line.
• Window-design for Phase 3 must include realistic peak traffic models; designs that only work in Phase 2 traffic will erode under load.
• Phase 4 depends on neighbours' equipage (datalink, AMAN with shared metering horizon). It is a regional programme, not a State programme.

Where Pakistan / APAC sit#

Indicative regional context (verify against the latest APANPIRG and APAC Seamless ATM Plan reports):

• Pakistan — early Phase 2 at the major hubs, Phase 1 elsewhere; PBN STAR coverage growing, AMAN deployment is the limiting enabler.
• APAC region — wide variation: Singapore, Hong Kong, Tokyo, Sydney, Auckland in Phase 3; many other major hubs in Phase 2; cross-border XMAN trials between selected pairs.
• Europe (EUR) — most major hubs in Phase 3, with E-AMAN / cross-border arrival management in routine use; selected airports in Phase 4.

CDO is the canonical example of an operational improvement that no single organisation can deliver alone. This file maps the stakeholder strands that must work together and what each contributes.

The strands below are operational, not contractual: they describe roles and outputs, irrespective of how they are organised in a particular State's institutional landscape.

1. Procedure design#

Owner. State / ANSP procedure design office, working under PANS-OPS (Doc 8168).

Outputs.

• PBN STAR designs with vertical and speed windows tuned to the local TMA, traffic mix, and obstacle environment.
• Linked RNP APCH or RNP-AR final approach designs.
• Multiple-transition options (long/short, point-merge, trombone) for flow flexibility.
• Vertical and speed windows sized to the served aircraft mix.
• Charting (AIP), procedure validation, periodic review.

Constraints. Doc 8168 Vol II procedure design rules; obstacle clearance; missed-approach criteria; aerodrome operating environment.

Interfaces. Receives operational requirements from the ATS provider and flight-ops community; validates with simulator and ground-test runs; publishes through AIM (PANS-AIM, Doc 10066).

2. Air Traffic Control (ATC)#

Owner. ANSP / ATS provider. ATC is the strand that determines whether the carefully designed procedure delivers benefit on the day.

Outputs.

• Tactical clearances that preserve the descent: early descent, "descend via", minimal vectoring, no late step-downs.
• AMAN-driven sequencing that pushes delay absorption upstream so the TMA stays close to free-flow.
• Speed control rather than vectoring as the first lever for spacing.
• Phraseology compliant with PANS-ATM (Doc 4444) and any regional supplement.
• Letters of agreement with neighbouring units for cross-FIR XMAN / E-AMAN.

Constraints. Separation standards (Doc 4444); airspace classification (Annex 11); local rules-of-the-air; runway and surface demand.

Interfaces. Procedure design (operational input + post-deployment review); flight-ops (briefings, change notifications); environment authority (noise abatement procedures coordination).

3. Flight operations#

Owner. Aircraft operators (airlines / general aviation operators) and their training and standards organisations.

Outputs.

• Equipage decisions (FMS generation, datalink, ADS-B In) tied to authorised operations under Annex 6 and the State's operational authorisation regime.
• Crew procedures for VNAV-managed descents on the published procedure.
• Cost-index, descent-wind, and weight-entry standards that improve FMS path prediction.
• Stabilized approach criteria aligned with the procedure design.
• Flight-data analysis (FDM/FOQA) feeding back into both crew training and procedure review.

Constraints. Annex 6 operating rules; manufacturer FCOMs; operator approvals (PBN, RNP AR, datalink, RVSM as required).

Interfaces. ATC (briefings, anomaly reporting); procedure design (usability feedback); training (recurrent simulator sessions).

4. Environmental authority#

Owner. State environmental regulator, airport noise office, and (where present) the State Action Plan for emissions reduction coordinator.

Outputs.

• Noise abatement requirements informing procedure design (Doc 8168 Vol I, Part V, Chapter 3 framework — "balanced approach").
• Noise-monitoring infrastructure around the airport.
• Reporting on noise contour evolution and complaint statistics.
• Emissions reporting (CO2 per movement, NOx per movement).
• Inputs to the State Action Plan on emissions reduction submitted to ICAO under the global aspirational goals.

Constraints. National environmental law; ICAO balanced approach guidance; community engagement requirements.

Interfaces. Procedure design (noise-abatement flight paths and power/configuration schedules); ATC (preferred runway and routing schemes for noise); operators (operational restrictions, charging).

How the strands interlock#

CDO works when the four strands share a single picture of the descent flow:

Procedure design  -- publishes -->  STAR + approach + windows
                                            |
                                            v
ATC  -- preserves with -->  clearance phraseology + AMAN sequencing
                                            |
                                            v
Flight operations  -- flies with -->  FMS path + stabilized approach
                                            |
                                            v
Environmental authority  -- measures -->  noise + emissions + report
                                            |
                                            v
Feedback loop back into procedure design / ATC training

A CDO programme that has only three of these strands engaged tends to visible failure modes:

• Without procedure design discipline: windows too tight, fleet drops out, controllers force step-downs.
• Without ATC discipline: vectoring and step-downs erode benefit even on a well-designed procedure.
• Without flight ops discipline: crews fly the procedure with bad cost index, stale wind data, or non-VNAV techniques.
• Without environmental authority discipline: no measurement, no evidence of benefit, no political support for keeping the design.

Working forum#

In most States, the four strands meet through a CDO/CCO working group sitting under the State Aeronautical Information Plan or the national ATM master plan. Membership typically includes the CAA, the ANSP, the airport operator, two or three lead operators, and the State noise authority. Observer seats for a regional planning office (APANPIRG, EANPG, MIDANPIRG) help align with regional metrics.

This file treats a published CDO procedure as the unit of planning and walks through the structured elements that any complete procedure design must address. The structure mirrors the ASBU "module anatomy" pattern applied to the procedure level.

Identifier and scope#

A CDO design is identified by:

• Aerodrome (ICAO location indicator, e.g. OPKC, EGLL, RJTT).
• Runway / RWY direction (e.g. RWY 25L).
• Procedure family — STAR identifier and the linked approach identifier.
• Applicability — aircraft category, equipage requirement (e.g. RNP 1, RNP APCH, A-RNP), and any operating-time restrictions.

A CDO programme at a busy airport will have many designs covering runway directions, transitions, and aircraft category combinations.

1. Operational objective#

A plain-language statement of what the design changes operationally. Examples:

• Eliminate the level segment between FL100 and 6,000 ft on arrivals to RWY 25L during off-peak hours.
• Provide a continuous descent and stabilized approach at idle thrust for all PBN-equipped Cat C/D aircraft on the published transition.
• Replace the radar-vectored downwind/base/final pattern with a procedural point-merge feed during the night.

The objective is the basis on which post-deployment monitoring will report success or failure.

2. Performance objective and applicable KPAs#

The "why". Each CDO design is tagged with the GANP Performance Objectives it serves:

• Reduce fuel burn and CO2 per flight.
• Reduce noise impact on populated areas under the arrival path.
• Improve arrival predictability.
• Maintain or improve runway throughput.

Applicable KPAs (from Doc 9854 / Doc 9883): environment, flight efficiency, predictability, capacity (subject to mixed-mode trade-off), cost-effectiveness.

3. Procedure element#

The procedural artefacts the design produces or modifies:

• A new or revised STAR under PANS-OPS (Doc 8168) Vol II.
• A linked instrument approach procedure (RNP APCH, RNP-AR, ILS with RNAV transition).
• Vertical windows at named gate fixes (e.g. between FL120 and FL150 at fix ALPHA).
• Speed windows at named gate fixes.
• Missed approach consistent with the new approach geometry.
• Phraseology updates per PANS-ATM (Doc 4444) and the regional supplement (Doc 7030) — most often the "descend via" form.
• AIP / chart updates.

4. Technology element#

The system support behind the procedure:

• FMS / VNAV — the airborne system that flies the path. Procedure windows are sized to the lowest FMS capability in the served fleet.
• PBN avionics — RNP 1 for the STAR and RNP APCH for the approach.
• Surveillance — radar / Mode S / ADS-B coverage adequate to monitor conformance.
• AMAN — to space the flow at the TMA so that the procedure can be flown without tactical intervention.
• Datalink (CPDLC) — optional but valuable for descent clearance uplinks and wind uplinks where deployed.
• Wind information — high-resolution descent winds delivered via datalink, ATIS, or pre-flight briefing.
• Monitoring tools — radar / ADS-B replay tooling for CDO conformance analytics.

5. Human performance element#

• Controller training. Phraseology, AMAN tooling, mental model of the FMS-managed descent, judgement on when to break CDO for separation. Endorsement on the licence per Annex 1 if local rules require.
• Pilot training. VNAV-managed descent on the new procedure; cost-index and wind-entry discipline; stabilized approach criteria on the linked approach.
• AIM officer. Quality-managed publication of the procedure to PANS-AIM Aeronautical Data Catalogue standards (Doc 10066).
• Operations engineering / standards. Update of operator FCOM guidance, simulator scenarios, and FDM monitoring.

6. Standards basis#

• Annex 11 — ATS airspace and service responsibilities under which the procedure is delivered.
• Annex 14 — aerodrome design and obstacle environment.
• Annex 6 — operator carriage and approval.
• Annex 1 — personnel licensing endorsements.
• Doc 8168 Vol I, Part V, Chapter 3 — noise-abatement aeroplane operating procedures using continuous descent with reduced power / reduced drag.
• Doc 8168 Vol II — procedure design rules for STARs and approach procedures.
• Doc 4444 — PANS-ATM clearance phraseology and AMAN/sequencing practice.
• Doc 9931 — CDO Manual: harmonised guidance integrating the domains above.
• Doc 9613 — PBN Manual: navigation specifications referenced by the STAR and approach.

7. Enablers#

The dependency chain that must be in place; see enablers.md for detail. Headlines:

• PBN environment for the relevant navigation specification.
• AMAN at the TMA, with an extended horizon for Phase 3 / 4.
• Controller and crew training programmes.
• Simulation and validation infrastructure.
• Monitoring infrastructure to evidence benefit.

8. Dependencies on other ASBU modules#

• NAVS-B0/B1 — PBN baseline for the STAR and approach.
• RSEQ-B0/B1 — AMAN, XMAN / E-AMAN for spacing upstream.
• AMET-B1 — IWXXM-based wind information for FMS path prediction.
• COMI-B0/B1 — datalink (CPDLC) for descent clearance and wind uplinks where used.

9. KPI linkage#

A complete CDO design declares the KPIs it expects to move:

• CDO penetration rate — % of arrivals on the procedure that fly a defined "no level segment below X" criterion.
• Vertical inefficiency — average distance flown level below FL100.
• Fuel burn per arrival — derived from FDM or radar replay.
• Noise contour area — measured by the airport noise office.
• Stabilized approach rate — at the gate altitude (e.g. 1,000 ft AAL on IMC arrivals).
• Predictability — variance between planned and actual landing time on the procedure.

10. Region applicability and lifecycle#

CDO designs are local; the underlying enabler stack is regional. A CDO design has a lifecycle:

1. Conceive — operational objective signed off by the working group.
2. Design — PANS-OPS-compliant STAR/approach with vertical/speed windows.
3. Validate — simulator runs, fly-through trials, controller and pilot review.
4. Publish — AIRAC cycle through AIM.
5. Train — controllers, pilots, AMAN operators.
6. Operate — routine use; periodic conformance review.
7. Iterate — windows, transitions, phraseology refined as the monitoring loop reveals frictions.

What an Enabler is#

An Enabler is a supporting element without which a CDO procedure cannot deliver its intended benefit. Enablers are not operational improvements in themselves — they are prerequisites. ICAO Doc 9931 makes the dependency chain explicit so that planners do not publish a CDO procedure whose foundation is missing.

The CDO enabler stack splits into five categories.

1. Performance-Based Navigation (PBN)#

PBN is the most foundational enabler for CDO. Without it, the airborne side cannot fly the published vertical profile.

• STAR navigation specification. RNAV 1 or RNP 1 for the STAR, giving lateral path repeatability tight enough to publish vertical windows that are not over-padded for navigation error.
• Approach navigation specification. RNP APCH (LNAV/VNAV, LPV, LP) or RNP-AR APCH for the linked instrument approach, providing a stabilised final segment that the FMS can fly continuously from the STAR.
• PBN environment. Doc 9613 (PBN Manual) defines the navigation specifications; State implementation requires PBN approvals on the fleet, controller training in PBN handling, and a PBN-aware AIM publication regime.
• GNSS integrity. Multi-constellation, multi-frequency GNSS where available improves availability of LPV and Baro-VNAV minima that CDO procedures terminate on.

A State that has not completed its PBN baseline (ASBU NAVS-B0) will struggle to deliver Phase 2 CDO at scale.

2. AMAN and Extended AMAN (E-AMAN / XMAN)#

Arrival Management is the enabler that makes CDO survive at peak demand.

• AMAN — single-TMA arrival manager. Computes a planned landing sequence and meters traffic into the TMA so that arrival rate matches runway capacity. Reduces tactical step-downs and vectoring that would otherwise destroy the descent profile.
• E-AMAN / XMAN — extended arrival management. AMAN's planning horizon reaches into upstream FIRs (often hundreds of nautical miles out). Spacing is built up by speed control upstream, leaving the TMA closer to free-flow.
• Coordination. Cross-FIR letters of agreement with neighbouring ANSPs; harmonised metering points and "ready time" definitions.
• Integration with point-merge / trombone designs. AMAN's preferred spacing technique (speed control on a sequencing arc, then "direct to" the merge) is itself a CDO-preserving design pattern.

Time-Based Separation (TBS) on final approach, where deployed, recovers capacity that headwind-day distance-based separation surrenders, and so removes a common reason controllers reach for vectoring during CDO operations.

3. Simulation and validation#

A CDO design that has not been simulated rigorously tends to fail on the line.

• Real-time simulation. Controllers fly the procedure in their operational sim against representative traffic mixes, including adverse winds and equipment failures. Reveals where windows are too tight or phraseology is ambiguous.
• Fast-time simulation. Bulk runs across a year of traffic samples to size capacity, vertical inefficiency, and fuel benefit.
• Pilot simulator validation. Operators fly the procedure in full-flight simulators across the fleet types served, including adverse cost-index and wind cases.
• Live trial. Selected operators fly the procedure on revenue flights in a measurement window before full publication.
• Post-deployment monitoring. Continuous radar / ADS-B replay tooling that scores conformance and feeds back into design.

Validation is required by Doc 8168 Vol II for the underlying procedure design and is good practice over and above that for the CDO operational concept.

4. Controller training#

Controllers determine whether CDO works on the day. Training elements:

• Phraseology. "Descend via" or the regional supplement equivalent; speed assignments; explicit altitude assignments only when needed.
• Mental model of FMS-managed descent. Why interrupting a descent forces drag deployment; how an FMS recovers from an early descent versus a late one; what wind data the FMS depends on.
• AMAN tooling. Reading the metering plan; respecting time-to-lose / time-to-gain advisories; understanding the upstream horizon.
• Judgement on breaking CDO. When a level segment is justified for separation; how to keep it short and high; how to recover the descent afterwards.
• Recurrent training. Annual recurrent on procedure changes; periodic refresher on rare events (missed approach during point merge, etc.).

Endorsements may be required on the controller licence under Annex 1, depending on the State's regime.

5. FMS performance and crew procedures#

The aircraft side of the enabler stack.

• FMS generation. Modern FMS generations compute idle-thrust descent paths that flex with weight, wind, and constraints. Older generations may need wider windows or additional crew technique.
• VNAV PATH / VNAV PROF capability. The FMS targets a 3D path with thrust auto-modulation. Procedure designs must be flyable in the weakest VNAV mode of the served fleet.
• Wind data ingestion. Forecast winds entered at descent fixes; uplinked winds via datalink where available; accurate ATIS surface wind. Wind error is the single largest cause of FMS path deviation.
• Cost-index / weight discipline. Operator-mandated cost index and zero-fuel-weight entries that match the day's fuel and payload.
• Configuration schedule. Crew procedures that delay flap and gear to the latest practical point consistent with stabilized approach.
• Stabilized approach criteria. Operator-defined gates (e.g. 1,000 ft AAL IMC, 500 ft AAL VMC) that must be met or the approach is discontinued.
• FDM / FOQA. Flight-data analytics that reveal CDO conformance per fleet, pilot and route, feeding both training and procedure redesign.

How enablers are managed in practice#

A CDO programme tracks each enabler as a deliverable with an owner and a date:

A CDO procedure is considered ready for unrestricted use only when every declared enabler is in place — not only the published procedure itself.

The performance lens of CDO#

CDO is justified, sequenced, and monitored on a performance basis. Like every ASBU operational improvement, it is anchored in the eleven Key Performance Areas (KPAs) defined by ICAO Doc 9854 (Global ATM Operational Concept) and the performance methodology of Doc 9883 (Manual on Global Performance of the Air Navigation System).

The chain is the same as elsewhere in the ASBU framework:

KPA  --(measured by)-->  KPI  <--(targeted by)--  Performance Objective  --(achieved by)-->  CDO procedure

CDO touches several KPAs simultaneously, with environment and flight efficiency as the headline drivers.

KPAs primarily affected by CDO#

Environmental impact (primary)#

The headline KPA. CDO reduces fuel burn, CO2, NOx, and noise per arrival. The State Action Plan on emissions reduction submitted to ICAO under the global aspirational goals normally lists CDO/CCO as a core operational measure.

Flight efficiency (primary)#

Vertical-profile efficiency (cruise altitude vs. optimum, time spent at sub-optimal levels in descent) is a core flight-efficiency dimension. CDO directly improves it.

Predictability (secondary)#

PBN-based CDO produces a more predictable vertical profile and a more predictable arrival time than radar-vectored arrivals. This helps both ATC sequencing and airport ground operations.

Capacity (constraint, not driver)#

CDO does not by itself raise runway throughput. Its capacity story is defensive: AMAN, E-AMAN, point-merge, and TBS allow CDO to be preserved without throughput loss. A CDO programme that ignores capacity will be unwound at peak demand.

Cost-effectiveness (secondary)#

Fuel saving and reduced engine wear are direct operator-side cost benefits. ANSP-side cost is upstream design and monitoring effort, plus the AMAN tooling that is justifiable on capacity and predictability grounds independently.

Access and equity (constraint)#

Vertical/speed window design must accommodate the served aircraft mix without excluding less-equipped or smaller operators from the procedure.

Performance Objectives delivered by CDO#

Illustrative Performance Objectives (consistent with the GANP Portal style) that CDO contributes to:

• PO — Reduce fuel burn and CO2 per flight. Measured by fuel/CO2 per movement and vertical inefficiency. Delivered jointly by B0-CDO, B0-CCO, OPFL-B1, TBO-B2.
• PO — Reduce noise impact at and around airports. Measured by noise contour area, complaint statistics, and the noise model output for the procedure. Delivered by B0-CDO, balanced-approach measures, procedure-route design.
• PO — Improve arrival predictability. Measured by standard deviation of actual vs. planned landing time. Delivered by B0-CDO in combination with RSEQ-B0/B1 (AMAN/XMAN) and ACDM-B0/B1.
• PO — Improve vertical-profile flight efficiency. Measured by vertical inefficiency below FL100 and by % of arrivals achieving CDO from a defined level. Delivered primarily by B0-CDO and B1-CDO.

Key Performance Indicators (KPIs)#

CDO-specific KPIs#

• CDO penetration rate. The headline KPI. % of arrivals that fly the procedure without a level segment longer than a defined threshold (commonly: no level segment below FL100, or below a defined altitude such as 7,500 ft or 6,000 ft AGL).
• Vertical inefficiency. Average level distance flown in the descent below a reference level (usually FL100), expressed in nautical miles per arrival.
• Time at level below FL100. Companion measure to vertical inefficiency, expressed in seconds.
• CDO from TOD. Fraction of arrivals where the entire descent from top of descent contains no level segment beyond a defined tolerance.
• Excess fuel per arrival. Modelled fuel above the idle-thrust reference profile, in kilograms.

Environmental KPIs (secondary, derived)#

• Fuel burn per arrival.
• CO2 per arrival.
• NOx per arrival.
• Noise contour area.
• Noise complaint count per movement.

Predictability KPIs#

• Landing-time variance between planned and actual.
• AMAN-target adherence at the metering point.

Capacity KPIs#

• Arrival rate maintained during CDO operation vs. baseline.
• % of CDO arrivals at peak hour as a defensive indicator.

Reporting cadence and ownership#

• Per-procedure dashboard. ANSP performance unit reports CDO conformance per procedure, monthly, to the CDO/CCO working group.
• Airport-level report. Airport noise office reports contour and complaint statistics to the State environmental authority.
• State-level. State Action Plan on emissions reduction references CDO uptake; cycle aligned with ICAO triennial reporting.
• Regional. APAC Seamless ATM Plan, MID Air Navigation Strategy, EUROCONTROL Performance Review Body / LSSIP cycle aggregate national CDO penetration rates.

Why this matters for planning#

Tying every CDO design to a Performance Objective and a KPI keeps the programme honest. It forces the question "what measurable problem does this procedure fix?" during design and gives the State environmental authority the evidence it needs to support keeping the procedure when runway capacity pressure increases.

A CDO design that publishes a procedure but does not publish the KPI it expects to move is incomplete, even if the procedure itself is PANS-OPS-compliant.

Three timelines to keep distinct#

When discussing CDO "dates", separate three things:

1. ICAO publication timeline — when ICAO published or amended the guidance and the underlying PANS material.
2. Block availability timeline — the notional dates from which the ASBU CDO modules become globally implementable.
3. Regional uptake timeline — when major regions and States moved from trial to routine to peak-hour CDO.

A State's own implementation roadmap is a fourth, national timeline, expressed against the regional plan's milestones.

ICAO publication timeline#

Block availability timeline#

Notional dates for the CDO thread, set in GANP 5th edition:

B0-CDO ........ from 2013
B1-CDO ........ from 2019
TBO-aligned CDO  from 2025 (via TBO-B2 and onwards)

Visualised:

2010 ----- 2013 ----- 2019 ----- 2025 ----- 2031
  |          |          |          |          |
  Doc 9931   B0-CDO     B1-CDO     TBO-B2     TBO-B3
  1st ed     basic      with       initial    full
             single-FIR XMAN /     4D         4D
             CDO        E-AMAN     trajectory trajectory

These dates are not deadlines for States. They are the dates by which the SARPs, PANS, technology, and training material underpinning each module are mature enough that any State can implement them.

Regional CDO uptake#

Indicative regional context (verify against the latest regional plan documents — these change annually).

Europe (EUR)#

• Mid-2000s. UK and Nordic ANSPs publish early CDA procedures at major hubs, supported by EUROCONTROL guidance.
• 2010s. Point-merge becomes the dominant TMA design pattern in much of Europe; CDO becomes routine off-peak at most major hubs.
• 2015 onwards. E-AMAN / XMAN deployed across a growing list of ANSP pairs (e.g. NATS – Maastricht, DSNA – Skyguide, ENAIRE – EUROCONTROL); cross-border arrival management formalised in the European ATM Master Plan.
• 2020 onwards. Phase 3/4 CDO at most major hubs; the LSSIP cycle reports CDO penetration as a standard performance indicator.

Asia / Pacific (APAC)#

• 2007–2012. Tailored arrival / OPD trials between United States west-coast and Pacific destinations; oceanic-to-TMA continuous descent demonstrated.
• 2010s. Singapore, Hong Kong, Tokyo, Sydney, and Auckland publish CDO procedures and report measurable fuel/noise benefit.
• APAC Seamless ATM Plan. Sets CDO/CCO as a regional priority and monitors implementation through APANPIRG. Many APAC States now have CDO at major hubs in routine use.
• Ongoing. Cross-border XMAN trials between selected pairs (e.g. Australia – New Zealand on trans-Tasman flows).

Pakistan / South Asia (PEA / South Asia subset of APAC)#

• 2013 onwards. PBN approach baseline rolled out at major airports per Doc 9613 and the PBN Roadmap, providing the navigation precondition for CDO.
• Late 2010s and into the 2020s. Initial CDO/CCO procedure publication at the major hubs; AMAN deployment is the limiting enabler for moving from Phase 1/2 to Phase 3.
• Current. Programmes are at a Phase 1–2 maturity at the busiest airports; the regional priority is completing the AMAN / E-AMAN enabler stack to support Phase 3.

North America#

• 2007 onwards. FAA OPD trials at major hubs; OPD published as routine RNAV STAR design at most large US airports through the 2010s.
• Block 1 era. Time-Based Flow Management (TBFM) and extended metering align with the E-AMAN concept.
• Current. CDO/OPD is the default arrival design philosophy at major US hubs.

Implementation monitoring cadence#

• Global. ICAO publishes ASBU implementation status as input to the GANP review cycle (3-yearly, aligned with the ICAO Assembly). CDO penetration is reported among the headline performance indicators.
• APAC. APANPIRG reviews CDO implementation against the Seamless ATM Plan annually.
• MID. MIDANPIRG reviews CDO implementation against the MID Air Navigation Strategy annually.
• Europe. LSSIP cycle reports annually against ICAO ASBU and the European ATM Master Plan; the EUROCONTROL Performance Review Body publishes performance reports that include vertical efficiency.
• National. Most States publish a 3–5 year air navigation plan, reviewed annually, in which CDO procedures are tracked at the individual procedure level.

How to read a date in a CDO document#

When a CDO document uses a date, check which kind it is:

• "Doc 9931 (2010)" — ICAO publication date of the CDO Manual.
• "B0-CDO from 2013" — Block availability date (global notional earliest).
• "CDO at hub X by 2026" — national or regional commitment.
• "CDO penetration target 80% by 2030" — regional or national performance ambition.

Mixing these up leads to false claims that a State is "behind" or "ahead" of CDO implementation, when the only meaningful measure is the State's own implementation plan against its declared milestones and the per-procedure CDO penetration KPI.

Primary ICAO documents#

• Doc 9931 — Continuous Descent Operations (CDO) Manual (ICAO). Primary harmonised guidance for airspace, procedure, and ATC design that together enable CDO. Establishes the airspace / procedure / ATC integrated approach and the design principles (continuous descent, idle thrust, low-drag configuration until late, ATC compatibility). (Authoritative source — not in local library.)
• Doc 8168 — PANS-OPS, Vol I, Part I, §1 (Definitions) — formal definitions of CDO and CDFA, distinguishing the airspace/procedure/ ATC-enabled arrival operation from the non-precision final-approach technique.
• Doc 8168 — PANS-OPS, Vol I, Part I, §1 (IAP note on CDFA) — clarifies that NPAs flown with advisory VNAV CDFA are 3D operations, while manually computed CDFA remains a 2D operation.
• Doc 8168 — PANS-OPS, Vol I, Part V, Chapter 3, §3.1.1 — places CCO/CDO within noise-abatement aeroplane operating procedures and cross-references Doc 9931 (CDO Manual) and Doc 9993 (CCO Manual).
• Doc 8168 — PANS-OPS, Vol I, Part V, Chapter 3, §3.4.3 — noise- abatement descent and approach procedures using continuous descent with reduced power / reduced drag, including delayed flap and gear extension.
• Doc 8168 — PANS-OPS, Vol II — design rules for STARs and approach procedures that support CDO (vertical windows, speed constraints, transition design).
• Doc 4444 — PANS-ATM — clearance phraseology, level allocation, and AMAN/sequencing practice that preserve continuous descent in the TMA, including the "descend via" form.
• Doc 9613 — Performance-Based Navigation (PBN) Manual — navigation specifications (RNAV 1, RNP 1, RNP APCH, RNP-AR APCH) referenced by CDO STARs and approaches.
• Doc 9868 — PANS-TRG, Appendix to Chapter — descent-management training competencies (optimum descent point, FMS descent path management, RNAV/RNP arrival compliance).
• Doc 9750 — Global Air Navigation Plan (GANP) — strategic and technical level of ICAO's air navigation modernization, including the ASBU framework with B0-CDO and B1-CDO modules.
• Doc 9854 — Global Air Traffic Management Operational Concept — source of the eleven Key Performance Areas used to justify CDO.
• Doc 9883 — Manual on Global Performance of the Air Navigation System — methodology for KPAs, KPIs, and Performance Objectives applied to CDO modules.
• Doc 9993 — Continuous Climb Operations (CCO) Manual — companion manual on the departure side, sharing much of CDO's enabler stack. (Authoritative source — not in local library.)
• Doc 10066 — PANS-AIM — quality-managed publication of CDO procedures and the Aeronautical Data Catalogue.
• Doc 10157 — PANS-MET — meteorological information procedures underpinning the wind data CDO depends on.
• Doc 7030 — Regional Supplementary Procedures — regional procedures (EUR, MID, ASIA/PAC, AFI, NAT, SAM, CAR) that may carry region-specific CDO phraseology.

ICAO Annexes most touched by CDO#

• Annex 1 — Personnel Licensing. Endorsements (PBN, RNP AR, datalink) for pilots and controllers operating in CDO environments.
• Annex 2 — Rules of the Air. General rules under which CDO is flown.
• Annex 3 — Meteorological Service. Wind information feeding FMS path prediction.
• Annex 4 — Aeronautical Charts. Chart provisions for the STAR and approach procedures supporting CDO.
• Annex 6 — Operation of Aircraft. Operator equipage and approval requirements for PBN, datalink, and approach minima.
• Annex 10 — Aeronautical Telecommunications. CNS standards (GNSS, data link, surveillance) underpinning CDO.
• Annex 11 — Air Traffic Services. ATS airspace classification and service responsibilities under which CDO is delivered (sequencing, vectoring, and clearance authority).
• Annex 14 — Aerodromes. Aerodrome design and obstacle environment governing the published procedure.
• Annex 19 — Safety Management. SMS integration of new CDO procedures.

Live / authoritative sources#

• ICAO GANP Portal — https://ganpportal.icao.int/ — live home of the ASBU framework, including the CDO thread and modules.
• ASBU Threads catalogue — https://ganpportal.icao.int/asbu/thread
• ICAO GANP overview page — https://www.icao.int/global-air-navigation-plan-ganp
• ICAO Environmental Protection portal (CAEP and operational measures) — https://www.icao.int/environmental-protection/Pages/default.aspx

Regional implementation references#

• APAC Seamless ATM Plan (ICAO Asia/Pacific Regional Office) — APAC realisation of the ASBU framework, including CDO/CCO as a regional priority; monitored by APANPIRG.
• MID Air Navigation Strategy (ICAO MID Regional Office) — MID realisation; monitored by MIDANPIRG.
• European ATM Master Plan (SESAR JU) and EUROCONTROL LSSIP cycle — EUR realisation and annual reporting, including CDO vertical efficiency indicators.

External operational guidance (web fallback)#

These are non-ICAO references that provide operationally detailed implementation guidance. Marked as fallback because they sit outside the ICAO authoritative chain.

• EUROCONTROL — "European Joint Industry CDA Action Plan" and successor guidance materials on CDO/CCO, including practical implementation notes on vertical/speed-window design and AMAN integration. https://www.eurocontrol.int/concept/continuous-descent-operations
• EUROCONTROL — "A guide to implementing Continuous Descent." Reference text frequently cited by national CDO programmes.
• FAA — Optimized Profile Descent (OPD) programme materials and Order JO 7110.65 (Air Traffic Control) phraseology references for "descend via" clearances. https://www.faa.gov/air_traffic/publications/atpubs/atc_html/
• SKYbrary — "Continuous Descent" article. https://skybrary.aero/articles/continuous-descent
• ICAO Doc 9931 summary materials as reproduced on ICAO regional office training pages and CAEP working-group documents.

Related topics in this workspace#

• topics_detailed/asbu/ — ASBU framework, including the CDO thread.
• topics_detailed/airspace_design/ — TMA design choices that CDO depends on.
• topics/cco.md and topics/pbn.md — companion topics on the departure side and the PBN baseline.
• topics/aman.md, topics/atfm.md, and topics/tbo.md — sequencing, flow, and trajectory threads that interact with CDO.