Radar Vectors
FAA OrderText changedNov 21, 2026

Order JO 1320.1A AIR TRAFFIC ORGANIZATION PREFIXES FOR DIRECTIVES

Text re-read from the scan: 8 of 8 passages.

Date
Nov 21, 2026
Recorded
Nov 21, 2026
Passages
8 of 8 changed (was 9)
Paragraphs
30 added or rewritten, 51 removed or rewritten

Read the current text Official source ↗

What changed in the text

Key: [removed: removed words] are struck through; [added: added words] are underlined. Each changed paragraph is labelled in the margin.

  1. Changed

    U.S. DEPARTMENT OF TRANSPORTATION[added: FEDERAL AVIATION ADMINISTRATION ORDER]

  2. Removed

    [removed: FEDERAL AVIATION ADMINISTRATION]

  3. Added

    [added: Air Traffic Organization Policy JO 1320.1A]

  4. Removed

    [removed: Air Traffic Organization Policy]

  5. Added

    [added: Effective Date: DECEMBER 15, 2006 SUBJ: Air Traffic Organization Prefixes for Directives]

  6. Removed

    [removed: SUBJ: Air Traffic Organization Prefmes for Directives]

  7. Added

    [added: 1. Purpose of This Order. To establish prefixes to identify and index directives issued by the Air Traffic Organization (ATO).]

  8. Removed

    [removed: ORDER]

  9. Added

    [added: 2. Who This Order Affects. This order affects all ATO personnel and anyone using ATO directives.]

  10. Removed

    [removed: JO 1320.1A]

  11. Added

    [added: 3. What This Order Cancels. This order cancels the JO 1320.1 Air Traffic Organization Prefixes for Directives, dated March 27, 2006.]

  12. Removed

    [removed: Effective Date: DECEMBER 15,2006]

  13. Removed

    [removed: 1. Purpose of This Order. To establish prefixes to identi@ and index directives issued by the Air Traffic Organization (ATO).]

  14. Removed

    [removed: 2. Who This Order Affects. This order affects all AT0 personnel and anyone using AT0 directives.]

  15. Removed

    [removed: 3. What This Order Cancels. This order cancels the JO 1320.1 Air Trafic Organization Prefixes for Directives, dated March 27,2006.]

  16. 4. Explanation of Changes. This reissues the same information that was originally contained in Order JO 1320.1, Air Traffic Organization Prefixes for Directives, and provides the following clarifications which are shown in the text in bold:

  17. a. Clarifies notice numbering (see paragraph 8).

  18. b. Clarifies that action item in paragraph 10 does not apply to the field.

  19. c. Specifies due date for action item in paragraph 10.

  20. 5. Background. Federal Aviation Administration Order 1320.1, FAA Directives System, uses prefix identifiers to denote that the directive applies to a specific line of business or geographic area. National directives, which apply to an agency-wide audience, do not have prefixes.

  21. Changed

    6. Format for Prefixes. Prefixes are assigned to the front of a directive's subject classification code or in front of the [removed: "SUP][added: “SUP”] when supplementing orders.

  22. Changed

    a. When there is no prefix, the directive applies to more than one line of business within the FAA. Example: FAA Order [removed: 1320. ID,][added: 1320.1D,] FAA Directives System, applies to all FAA employees.

  23. Changed

    Distribution: A-WXYZ [removed: (AT0)-2;][added: (ATO)-2;] [removed: A-FAFEAT-0][added: Initiated By: AJA-0 A-FAF/FAT-0] (STD)

  24. Removed

    [removed: Initiated By: AJA-0]

  25. Added

    [added: b. When the directive applies to only organizations within ATO, an ATO prefix is used. The ATO prefix is based on a three-character system that includes: geographical location, ATO specific letter identifier (i.e., "J") and the service unit's specific letter identifier. Note: The example below would be for a directive that applies to Headquarters Terminal Services only.]

  26. Removed

    [removed: b. When the directive applies to only organizations within ATO, an AT0 prefix is used. The AT0 prefix is based on a three-character system that includes: geographical location, AT0 specific letter identifier (i.e., "J") and the service unit's specific letter identifier. Note: The example below would be for a directive that applies to Headquarters Terminal Services only.]

  27. Added

    [added: JTH1320.1A Revision ▶ Sequence number ▶Subject classification Geographical location Chief Operations Officer (COO) or Vice President]

  28. Removed

    [removed: JTH1320.1 A]

  29. Added

    [added: Standard character assigned to ATO]

  30. Removed

    [removed: ---P Revision]

  31. Added

    [added: 7. Characters Assigned. The following is a list of characters used in ATO prefixes and what they represent.]

  32. Removed

    [removed: Sequence number]

  33. Added

    [added: a. The character in the first position represents the ATO and is always a "J."]

  34. Removed

    [removed: Subject classification]

  35. Added

    [added: b. The character in the second position represents the ATO service unit affected by the directive. If more than one service unit is affected, the character in the second position is "O." Other characters that may be used in the second position are:]

  36. Removed

    [removed: Geographical location]

  37. Added

    [added: O = All Air Traffic Organizations P = Operations Planning Services A = Acquisition and Business Services R = System Operations Services C = Communications Services S = Safety Services D = Flight Services T = Terminal Services E = En Route and Oceanic Services W= Technical Operations Services F = Finance Services c. The character in the third position represents the geographical location affected by the directive. If no character appears in the third position, the directive applies to all geographic locations. The characters that may be designated in the third position are:]

  38. Removed

    [removed: Chief Operations Officer (COO) or Vice President]

  39. Added

    [added: C = Central Service Area H = Headquarters E = Eastern Service Area A= Alaska Flight Services Information Office W = Western Service Area S = CONUS Flight Services Information Office]

  40. Removed

    [removed: 1 - Standard character assigned to AT0]

  41. Added

    [added: 8. Header Blocks. When initiating an order, notice, change or supplement, complete the first page-numbering block by selecting the appropriate formatted example used below. Thereafter, prefix the order number in the header for each additional page.]

  42. Removed

    [removed: 7. Characters Assigned. The following is a list of characters used in AT0 prefixes and what they represent.]

  43. Removed

    [removed: a. The character in the first position represents the AT0 and is always a "J."]

  44. Removed

    [removed: b. The character in the second position represents the AT0 service unit affected by the directive. If more than one service unit is affected, the character in the second position is "0." Other characters that may be used in the second position are:]

  45. Removed

    [removed: 0 = All Air Traffic Organizations P = Operations Planning Services A = Acquisition and Business Services R = System Operations Services C = Communications Services S = Safety Services D = Flight Services T = Terminal Services E = En Route and Oceanic Services W= Technical Operations Services F = Finance Services c. The character in the third position represents the geographical location affected by the directive. If no character appears in the third position, the directive applies to all geographic locations. The characters that may be designated in the third position are:]

  46. Removed

    [removed: C = Central Service Area E = Eastern Service Area W = Western Service Area]

  47. Removed

    [removed: H = Headquarters A= Alaska Flight S e ~ c e s Information Office S = CONUS Flight Services Information Office]

  48. Removed

    [removed: 8. Header Blocks. When initiating an order, notice, change or supplement, complete the first page-numbering block by selecting the appropriate formatted example used below. ThereaRer, prefix the order number in the header for each additional page.]

  49. Examples of page numbering blocks:

  50. Removed

    [removed: ORDER]

  51. Added

    [added: ORDER NOTICE CHANGE 2]

  52. Removed

    [removed: JO 1320.1]

  53. Added

    [added: JO 1320.1 N JO 1320.1 JO 1320.1]

  54. Removed

    [removed: NOTICE N J 0 1320.1]

  55. Added

    [added: Examples of Prefix Numbering in Text: JO 1320.5A – An Order that applies to multiple ATO service units (no specific geographic area). N JO 1320.1 - A Notice that applies to multiple ATO service units (no specific geographic area). JE 1800.2 - An Order that applies to only the En Route/Oceanic Service Unit (no specific geographic area). JT 7000.16 - An Order applies to only the Terminal Service Unit (no specific geographic area). JWH 6000.19 – An Order that applies to the headquarters Technical Operations Service Unit (Tech Ops). Example of page numbering block below:]

  56. Removed

    [removed: CHANGE 2]

  57. Added

    [added: ORDER JWH 6000.19]

  58. Removed

    [removed: JO 1320.1 I]

  59. Added

    [added: JOH 4650.25 – An Order that applies to multiple ATO service units (headquarters only). JW 6000.15 - An Order that applies to only Tech Ops (no specific geographic area). 1320.1 JO SUP1 - First ATO supplement to FAA Order 1320.1 - applies to multiple ATO service units (no specific geographic area). Example of page numbering block below:]

  60. Removed

    [removed: Examples of Prefm Numbering in Text:]

  61. Added

    [added: 1320.1 JO SUP 1]

  62. Removed

    [removed: JO 1320.5A - An Order that applies to multiple AT0 service units (no specific geographic area).]

  63. Added

    [added: 9. Field Facilities. Facilities under the ATO will identify their local orders through the same process using the following example:]

  64. Removed

    [removed: N JO 1320.1 -A Notice that applies to multiple AT0 service units (no specific geographic area). JE 1800.2 - An Order that applies to only the En Route/Oceanic Service Unit (no specific geographic area). JT 7000.16 - An Order applies to only the Terminal Service Unit (no specific geographic area).]

  65. Removed

    [removed: JWH 6000.19 - An Order that applies to the headquarters Technical Operations]

  66. Removed

    [removed: Service Unit (Tech Ops). Example of page numbering block below:]

  67. Removed

    [removed: JOH 4650.25 - An Order that applies to multiple AT0 service units (headquarters only). JW 6000.15 - An Order that applies to only Tech Ops (no specific geographic area).]

  68. Removed

    [removed: 1320.1 JO SUP1 - First AT0 supplement to FAA Order 1320.1 - applies to multiple AT0 service units (no specific geographic area). Example of page numbering block below:]

  69. Removed

    [removed: 1320.1]

  70. Removed

    [removed: JOSUP 1 I]

  71. Removed

    [removed: 9, Field Facilities. Facilities under the AT0 will identifjr their local orders through the same process using the following example:]

  72. Denver Terminal Radar Control Facility Order 1320.1

  73. Changed

    ORDER DEN TRACON[added: 1320.1]

  74. Removed

    [removed: 1320.1 I]

  75. Phoenix Airport Traffic Control Tower Notice 1320.1

  76. Changed

    NOTICE N PHX ATCT[added: 1320.1]

  77. Removed

    [removed: 1320.1 I]

  78. Cleveland Air Route Traffic Control Center Notice 1320.1

  79. NOTICE

  80. N ZOB 1320.1

  81. Removed

    [removed: 10. Update of Existing Orders to Comply with AT0 Prefixes. All existing AT0 orders must be reviewed to determine whether they apply to only AT0 organizations. Orders that apply]

  82. Added

    [added: 10. Update of Existing Orders to Comply with ATO Prefixes. All existing ATO orders must be reviewed to determine whether they apply to only ATO organizations. Orders that apply to only ATO organizations must be renumbered to comply with the new prefixes by September 30, 2007. Orders that have content that is not current will also be updated as part of this effort. Consult with your Directives Management Officer (DMO) for specific requirements. This action item does not apply to field level directives. New field level directives should be numbered according to this order but existing field level directives do not have to be renumbered.]

  83. Removed

    [removed: to only AT0 organizations must be renumbered to comply with the new prefixes by September 30,2007. Orders that have content that is not current will also be updated as part of this effort. Consult with your Directives Management mcer (DMO) for specific requirements. This action item does not apply to field level directives. New field level directives should be numbered according to this order but existing field level directives do not have to be renumbered.]

  84. 11. Waivers. A waiver may be obtained from the Vice President, Acquisition and Business Services, for relief from the due date of the action item where extenuating circumstances are demonstrated. The authority to issue this waiver may not be redelegated.

  85. Removed

    [removed: fPmes H. Washington Vice President, Acquisition and Business Services]

  86. Added

    [added: Gmes Waal]

  87. Added

    [added: tames H. Washington Vice President, Acquisition and Business Services]

Whole text before this change

U.S. DEPARTMENT OF TRANSPORTATION

FEDERAL AVIATION ADMINISTRATION

Air Traffic Organization Policy

SUBJ: Air Traffic Organization Prefmes for Directives

ORDER

JO 1320.1A

Effective Date: DECEMBER 15,2006

1. Purpose of This Order. To establish prefixes to identi@ and index directives issued by the Air Traffic Organization (ATO).

2. Who This Order Affects. This order affects all AT0 personnel and anyone using AT0 directives.

3. What This Order Cancels. This order cancels the JO 1320.1 Air Trafic Organization Prefixes for Directives, dated March 27,2006.

4. Explanation of Changes. This reissues the same information that was originally contained in Order JO 1320.1, Air Traffic Organization Prefixes for Directives, and provides the following clarifications which are shown in the text in bold:

a. Clarifies notice numbering (see paragraph 8).

b. Clarifies that action item in paragraph 10 does not apply to the field.

c. Specifies due date for action item in paragraph 10.

5. Background. Federal Aviation Administration Order 1320.1, FAA Directives System, uses prefix identifiers to denote that the directive applies to a specific line of business or geographic area. National directives, which apply to an agency-wide audience, do not have prefixes.

6. Format for Prefixes. Prefixes are assigned to the front of a directive's subject classification code or in front of the "SUP when supplementing orders.

a. When there is no prefix, the directive applies to more than one line of business within the FAA. Example: FAA Order 1320. ID, FAA Directives System, applies to all FAA employees.

Distribution: A-WXYZ (AT0)-2; A-FAFEAT-0 (STD)

Initiated By: AJA-0

b. When the directive applies to only organizations within ATO, an AT0 prefix is used. The AT0 prefix is based on a three-character system that includes: geographical location, AT0 specific letter identifier (i.e., "J") and the service unit's specific letter identifier. Note: The example below would be for a directive that applies to Headquarters Terminal Services only.

JTH1320.1 A

---P Revision

Sequence number

Subject classification

Geographical location

Chief Operations Officer (COO) or Vice President

1 - Standard character assigned to AT0

7. Characters Assigned. The following is a list of characters used in AT0 prefixes and what they represent.

a. The character in the first position represents the AT0 and is always a "J."

b. The character in the second position represents the AT0 service unit affected by the directive. If more than one service unit is affected, the character in the second position is "0." Other characters that may be used in the second position are:

0 = All Air Traffic Organizations P = Operations Planning Services A = Acquisition and Business Services R = System Operations Services C = Communications Services S = Safety Services D = Flight Services T = Terminal Services E = En Route and Oceanic Services W= Technical Operations Services F = Finance Services c. The character in the third position represents the geographical location affected by the directive. If no character appears in the third position, the directive applies to all geographic locations. The characters that may be designated in the third position are:

C = Central Service Area E = Eastern Service Area W = Western Service Area

H = Headquarters A= Alaska Flight S e ~ c e s Information Office S = CONUS Flight Services Information Office

8. Header Blocks. When initiating an order, notice, change or supplement, complete the first page-numbering block by selecting the appropriate formatted example used below. ThereaRer, prefix the order number in the header for each additional page.

Examples of page numbering blocks:

ORDER

JO 1320.1

NOTICE N J 0 1320.1

CHANGE 2

JO 1320.1 I

Examples of Prefm Numbering in Text:

JO 1320.5A - An Order that applies to multiple AT0 service units (no specific geographic area).

N JO 1320.1 -A Notice that applies to multiple AT0 service units (no specific geographic area). JE 1800.2 - An Order that applies to only the En Route/Oceanic Service Unit (no specific geographic area). JT 7000.16 - An Order applies to only the Terminal Service Unit (no specific geographic area).

JWH 6000.19 - An Order that applies to the headquarters Technical Operations

Service Unit (Tech Ops). Example of page numbering block below:

JOH 4650.25 - An Order that applies to multiple AT0 service units (headquarters only). JW 6000.15 - An Order that applies to only Tech Ops (no specific geographic area).

1320.1 JO SUP1 - First AT0 supplement to FAA Order 1320.1 - applies to multiple AT0 service units (no specific geographic area). Example of page numbering block below:

1320.1

JOSUP 1 I

9, Field Facilities. Facilities under the AT0 will identifjr their local orders through the same process using the following example:

Denver Terminal Radar Control Facility Order 1320.1

ORDER DEN TRACON

1320.1 I

Phoenix Airport Traffic Control Tower Notice 1320.1

NOTICE N PHX ATCT

1320.1 I

Cleveland Air Route Traffic Control Center Notice 1320.1

NOTICE

N ZOB 1320.1

10. Update of Existing Orders to Comply with AT0 Prefixes. All existing AT0 orders must be reviewed to determine whether they apply to only AT0 organizations. Orders that apply

to only AT0 organizations must be renumbered to comply with the new prefixes by September 30,2007. Orders that have content that is not current will also be updated as part of this effort. Consult with your Directives Management mcer (DMO) for specific requirements. This action item does not apply to field level directives. New field level directives should be numbered according to this order but existing field level directives do not have to be renumbered.

11. Waivers. A waiver may be obtained from the Vice President, Acquisition and Business Services, for relief from the due date of the action item where extenuating circumstances are demonstrated. The authority to issue this waiver may not be redelegated.

fPmes H. Washington Vice President, Acquisition and Business Services

Whole text after this change

U.S. DEPARTMENT OF TRANSPORTATION FEDERAL AVIATION ADMINISTRATION ORDER

Air Traffic Organization Policy JO 1320.1A

Effective Date: DECEMBER 15, 2006 SUBJ: Air Traffic Organization Prefixes for Directives

1. Purpose of This Order. To establish prefixes to identify and index directives issued by the Air Traffic Organization (ATO).

2. Who This Order Affects. This order affects all ATO personnel and anyone using ATO directives.

3. What This Order Cancels. This order cancels the JO 1320.1 Air Traffic Organization Prefixes for Directives, dated March 27, 2006.

4. Explanation of Changes. This reissues the same information that was originally contained in Order JO 1320.1, Air Traffic Organization Prefixes for Directives, and provides the following clarifications which are shown in the text in bold:

a. Clarifies notice numbering (see paragraph 8).

b. Clarifies that action item in paragraph 10 does not apply to the field.

c. Specifies due date for action item in paragraph 10.

5. Background. Federal Aviation Administration Order 1320.1, FAA Directives System, uses prefix identifiers to denote that the directive applies to a specific line of business or geographic area. National directives, which apply to an agency-wide audience, do not have prefixes.

6. Format for Prefixes. Prefixes are assigned to the front of a directive's subject classification code or in front of the “SUP” when supplementing orders.

a. When there is no prefix, the directive applies to more than one line of business within the FAA. Example: FAA Order 1320.1D, FAA Directives System, applies to all FAA employees.

Distribution: A-WXYZ (ATO)-2; Initiated By: AJA-0 A-FAF/FAT-0 (STD)

b. When the directive applies to only organizations within ATO, an ATO prefix is used. The ATO prefix is based on a three-character system that includes: geographical location, ATO specific letter identifier (i.e., "J") and the service unit's specific letter identifier. Note: The example below would be for a directive that applies to Headquarters Terminal Services only.

JTH1320.1A Revision ▶ Sequence number ▶Subject classification Geographical location Chief Operations Officer (COO) or Vice President

Standard character assigned to ATO

7. Characters Assigned. The following is a list of characters used in ATO prefixes and what they represent.

a. The character in the first position represents the ATO and is always a "J."

b. The character in the second position represents the ATO service unit affected by the directive. If more than one service unit is affected, the character in the second position is "O." Other characters that may be used in the second position are:

O = All Air Traffic Organizations P = Operations Planning Services A = Acquisition and Business Services R = System Operations Services C = Communications Services S = Safety Services D = Flight Services T = Terminal Services E = En Route and Oceanic Services W= Technical Operations Services F = Finance Services c. The character in the third position represents the geographical location affected by the directive. If no character appears in the third position, the directive applies to all geographic locations. The characters that may be designated in the third position are:

C = Central Service Area H = Headquarters E = Eastern Service Area A= Alaska Flight Services Information Office W = Western Service Area S = CONUS Flight Services Information Office

8. Header Blocks. When initiating an order, notice, change or supplement, complete the first page-numbering block by selecting the appropriate formatted example used below. Thereafter, prefix the order number in the header for each additional page.

Examples of page numbering blocks:

ORDER NOTICE CHANGE 2

JO 1320.1 N JO 1320.1 JO 1320.1

Examples of Prefix Numbering in Text: JO 1320.5A – An Order that applies to multiple ATO service units (no specific geographic area). N JO 1320.1 - A Notice that applies to multiple ATO service units (no specific geographic area). JE 1800.2 - An Order that applies to only the En Route/Oceanic Service Unit (no specific geographic area). JT 7000.16 - An Order applies to only the Terminal Service Unit (no specific geographic area). JWH 6000.19 – An Order that applies to the headquarters Technical Operations Service Unit (Tech Ops). Example of page numbering block below:

ORDER JWH 6000.19

JOH 4650.25 – An Order that applies to multiple ATO service units (headquarters only). JW 6000.15 - An Order that applies to only Tech Ops (no specific geographic area). 1320.1 JO SUP1 - First ATO supplement to FAA Order 1320.1 - applies to multiple ATO service units (no specific geographic area). Example of page numbering block below:

1320.1 JO SUP 1

9. Field Facilities. Facilities under the ATO will identify their local orders through the same process using the following example:

Denver Terminal Radar Control Facility Order 1320.1

ORDER DEN TRACON 1320.1

Phoenix Airport Traffic Control Tower Notice 1320.1

NOTICE N PHX ATCT 1320.1

Cleveland Air Route Traffic Control Center Notice 1320.1

NOTICE

N ZOB 1320.1

10. Update of Existing Orders to Comply with ATO Prefixes. All existing ATO orders must be reviewed to determine whether they apply to only ATO organizations. Orders that apply to only ATO organizations must be renumbered to comply with the new prefixes by September 30, 2007. Orders that have content that is not current will also be updated as part of this effort. Consult with your Directives Management Officer (DMO) for specific requirements. This action item does not apply to field level directives. New field level directives should be numbered according to this order but existing field level directives do not have to be renumbered.

11. Waivers. A waiver may be obtained from the Vice President, Acquisition and Business Services, for relief from the due date of the action item where extenuating circumstances are demonstrated. The authority to issue this waiver may not be redelegated.

Gmes Waal

tames H. Washington Vice President, Acquisition and Business Services