This section prescribes policies and guidelines for Coded Departure Route(s) (CDR).
The CDR program is a combination of coded air traffic routings and refined coordination procedures designed to mitigate the potential adverse impact to the FAA and users during periods of severe weather or other events that impact the .
Abbreviated clearances must only be used with CDRs at locations covered by a Memorandum of Agreement () between the customers and the FAA that specifies detailed procedures, or with general aviation customers who include in the remarks section of their flight plan, “CDR Capable”.
Air Traffic Control Facilities will determine which city pairs will be included in the database.
- Manage the national CDR program.
- Operate as Office of Primary Interest (OPI) at the national level.
- Conduct a review of the submitted CDRs and facilitate necessary corrections.
- Issue an advisory when facilities implement or terminate use of CDRs.
- Forward to the POC any changes to the published navigational data base (i.e., s/s, NAVAIDs, Fixes, Waypoints, etc.) contained in the (s) that are effective for the subsequent chart date. This data must be provided at least 45 days prior to the chart date.
- Error check all submitted route elements and forward errors noted during the validation to the for resolution.
- Identify, develop, coordinate, and establish CDRs, as needed, in accordance with this section.
- Supply a POC for the to contact regarding CDRs.
- Ensure that all affected facilities have approved newly created CDRs, or CDR route amendments, prior to inclusion in the operational database.
- Notify the originating Center when a CDR must be modified to accommodate changes within their airspace, such as traffic flow changes, airway realignments, and/or navigational aid designator changes. Exceptions: Revisions to // numbers will be entered into the CDR database by the via Global Modification.
- Ensure ERAM CDR data is identical to data published in the CDR operational database.
- Report unusable, inaccurate, or unsatisfactory CDRs to the POC. Reports must include the CDR Route Code, specific description of the impact and if appropriate, suggestion for modification.
- When requested, facilitate the coordination necessary for the use of abbreviated clearances.
- Notify the when implementing and terminating use of CDRs.
- Utilize the eight character naming convention as follows:
- Characters one through three are the three-letter ID of the origination airport.
- Characters four through six are the three-letter ID for the destination airport.
- Characters seven and eight are reserved for local adaptation and may be any two alphanumeric characters other than O or I.
O and I must not be used to preclude confusion with the numbers zero and one.
- Although the use of procedures is preferred when developing or amending CDRs, s may also include conventional CDRs in their CDR database.
- All CDR route strings must tie into normal arrival routings into the destination airport.
- CDRs must be developed and/or amended in accordance with the following:
- Routes and route segments must be defined by any combination of the following:
- s/s/s if applicable.
- NAVAID identifier, intersection name, fix name, Waypoint or Waypoint (e.g., FUZ, ZEMMA, KK45G).
- Type and number of the airway (e.g., J87 M201 Q40 T295 V16).
- When establishing or amending CDRs the following rules must be applied:
- When including a // use a published transition fix or the common fix for the procedure.
- When describing an airway include a published entry and exit point (e.g., CVE J87 BILEE).
- When connecting two airways, a published fix common to both airways and that is depicted on en route charts must be included (e.g., ADM J21 ACT J50). If there is not a fix common to both airways, include a published exit point for the first airway and a published entrance point for the second airway (e.g., OCS J206 NLSEN CYS J148).
- The first route element following the origin must not be an airway (e.g., KDFW J4).
- The last route element prior to the destination must not be an airway (e.g., J35 KMSY).
- CDRs for each location must be published via the Route Management Tool (RMT) CDR database. Updates to the database will coincide with the normal 56-day chart updates. There are two components of the CDR database. The operational database is a read-only record of all the current CDRs. The staging database is amendable by ARTCC POCs. The staging database replaces the operational database on each chart date.
- CDR changes must be entered into the staging database at least 36 days prior to the chart date. The staging database is closed to changes 35 days prior to the chart date.
The timeline for the CDR staging database is available in RMT under the Help tab, Show Chart Dates. The status of the staging database is provided at each login to the CDR database.
- 30-35 days prior to the Chart Date. During this period, the staging database is checked for errors. Any errors are forwarded to the POC designated at each facility for correction. If the error cannot be corrected immediately, the route involved will be deleted from the database for that cycle. Once the error is corrected, the route may be reentered for a future date.
30 days prior to the Chart Date the staging database is available to FAA and users for downloading or updating of their files.
- On each chart date, the staging database replaces the operational database and a mirror copy becomes the new staging database. The staging database is available for changes until it is locked 35 days prior to the next chart date, and the cycle starts over.