Skip to Main Content
FlightPushFLIGHTPUSH
Chapter 6

Learn

Dashboard My Courses Mastery Map Practice Flight Bag

Resources

CFR & AIM FAA Orders Handbooks & Guides Certification Standards Pilot/Controller Glossary Advisory Circulars Legal Interpretations
Safety Center
Articles Trust Center
Help Center FAQ Status
  1. Reference Library
  2. FAA Orders
  3. JO 7210.3
  4. Chapter 6
  5. Section 5
Loading
flightpush.co home
JO 7210.3 Facility Operation and Administration
  1. Chapter 1. General

    Section 1. Introduction
  2. Section 2. Order Use
  3. Chapter 2. Administration of Facilities

    Section 1. General
  4. Section 2. Responsibilities
  5. Section 3. Air Traffic Familiarization/Currency Requirements for En Route/Terminal/System Operations Facilities
  6. Section 4. Hours of Duty
  7. Section 5. Watch Coverage-Flight Service Stations
  8. Section 6. Watch Supervision-Terminal/En Route
  9. Section 7. Appearance and Security
  10. Section 8. Medical
  11. Section 9. Weather/Visibility
  12. Section 10. Wind/Altimeter Information
  13. Chapter 3. Facility Equipment

    Section 1. General
  14. Section 2. Use of Communications
  15. Section 3. Communications Procedures
  16. Section 4. Recorders
  17. Section 5. Navigational Aids
  18. Section 6. Surveillance Source Use
  19. Section 7. Video Maps
  20. Section 8. Other Displays
  21. Section 9. Color Displays-Terminal
  22. Chapter 4. Correspondence, Conferences, Records, and Reports

    Section 1. General
  23. Section 2. User Coordination/Conferences/Publicity
  24. Section 3. Letters of Agreement (LOA)
  25. Section 4. Application
  26. Section 5. Other Correspondence
  27. Section 6. Records
  28. Section 7. Reports
  29. Section 8. Freedom of Information Act (FOIA)
  30. Chapter 5. Special Flight Handling

    Section 1. Presidential Aircraft
  31. Section 2. FAA Aircraft
  32. Section 3. DOE and Other Aircraft
  33. Section 4. Other Flight Requests
  34. Section 5. 14 CFR Part 91, UAS Operations
  35. Chapter 6. En Route Operations and Services

    Section 1. General
  36. Section 2. Sector Information Binders
  37. Section 3. Operations
  38. Section 4. Services
  39. Section 5. Air Carrier Computer Interface Program
    1. 6-5-1 GENERAL
    2. 6-5-2 FACILITY RESPONSIBILITIES
    3. 6-5-3 CRITERIA FOR PARTICIPATION
    4. 6-5-4 FORMAT CONVENTIONS
    5. 6-5-5 MESSAGE CONTENT
  40. Section 6. En Route Decision Support Tool (EDST)
  41. Section 7. Advanced Technologies and Oceanic Procedures (ATOP)
  42. Section 8. Reduced Vertical Separation Minimum (RVSM)
  43. Section 9. En Route Information Display System (ERIDS)
  44. Section 10. En Route Data Communications
  45. Chapter 7. En Route Data

    Section 1. Performance Checks
  46. Section 2. Deficiencies
  47. Chapter 8. NAS En Route Automation

    Section 1. General
  48. Section 2. Procedures
  49. Section 3. Displays
  50. Chapter 9. Facility Statistical Data, Reports, and Forms

    Section 1. Operational Count Data
  51. Section 2. Instrument Approach Data
  52. Section 3. Other Reports and Forms
  53. Chapter 10. Terminal Operations, Services, and Equipment

    Section 1. General
  54. Section 2. Position Binders
  55. Section 3. Operations
  56. Section 4. Services
  57. Section 5. Terminal Radar
  58. Section 6. Airport Lighting
  59. Section 7. Airport Arrival Rate (AAR)
  60. Chapter 11. FAA Contract Tower Operation and Administration

    Section 1. Organizational Responsibilities
  61. Section 2. Operations and Staffing
  62. Section 3. Training
  63. Section 4. Documents, Forms, and Charts
  64. Section 5. Operational Documents, Directives, and Regulations
  65. Chapter 12. National Programs

    Section 1. Terminal VFR Radar Services
  66. Section 2. Data Recording and Retention
  67. Section 3. VFR Flyway Planning Chart Program
  68. Section 4. Helicopter Route Chart Program
  69. Section 5. VFR Transition Route Program
  70. Section 6. Standard Terminal Automation Replacement System (STARS)
  71. Section 7. Safety Logic Systems Operations Supervisor/CIC Procedures
  72. Section 8. VFR Waypoint Chart Program
  73. Section 9. Low Altitude Authorization Notification Capability
  74. Section 10. UAS Facility Maps (UASFM)
  75. Section 11. UAS Operations at Towered Airports
  76. Chapter 13. Facility Statistical Data, Reports, and Forms

    Section 1. General Information
  77. Section 2. Itinerant Operations
  78. Section 3. Local Operations
  79. Section 4. Overflight Operations
  80. Section 5. Amending and Reviewing Data
  81. Chapter 14. Flight Service Operations and Services

    Section 1. General
  82. Section 2. Position/Service Information Binders
  83. Section 3. Operations
  84. Section 4. Services
  85. Chapter 15. Aviation Meteorological Services and Equipment

    Section 1. General
  86. Section 2. Pilot Weather Briefing
  87. Section 3. Broadcasts
  88. Chapter 16. Equipment

    Section 1. General
  89. Section 2. Frequencies
  90. Chapter 17. Facility Statistical Data, Reports, and Forms (Alaska Only)

    Section 1. General Information
  91. Section 2. Aircraft Contacted
  92. Section 3. Flight Plan Count
  93. Section 4. Pilot Briefing Count
  94. Section 5. Other Reports and Information
  95. Section 6. FSS Lists, Logs, and Tallies (OASIS)
  96. Chapter 18. Traffic Management National, Center, and Terminal

    Section 1. Organizational Missions
  97. Section 2. Organizational Responsibilities
  98. Section 3. Line of Authority
  99. Section 4. Supplemental Duties
  100. Section 5. Coordination
  101. Section 6. Trajectory‐Based Operations (TBO)
  102. Section 7. Traffic Management Initiatives
  103. Section 8. Flow Evaluation Area (FEA), Flow Constrained Area (FCA), and Integrated Collaborative Rerouting (ICR)
  104. Section 9. Monitor Alert Parameter
  105. Section 10. Ground Delay Programs
  106. Section 11. Airspace Flow Programs (AFP)
  107. Section 12. Collaborative Trajectory Options Program (CTOP)
  108. Section 13. Ground Stop(s)
  109. Section 14. Special Traffic Management Programs
  110. Section 15. Severe Weather Management
  111. Section 16. Severe Weather Avoidance Plan (SWAP)
  112. Section 17. Preferred IFR Routes Program
  113. Section 18. North American Route Program
  114. Section 19. Coded Departure Routes
  115. Section 20. Route Advisories
  116. Section 21. Operations Plan
  117. Section 22. National Playbook
  118. Section 23. Traffic Management (TM) Support of Non‐Reduced Vertical Separation Minima (RVSM) Aircraft
  119. Section 24. Route Test
  120. Section 25. Time‐Based Flow Management (TBFM)
  121. Section 26. Weather Management
  122. Chapter 19. Waivers, Authorizations, and Exemptions

    Section 1. Regulatory Waivers and Authorizations
  123. Section 2. Elimination of Fixed‐Wing Special Visual Flight Rules Operations
  124. Section 3. Current Authorizations and Exemptions from Title 14, Code of Federal Regulations
  125. Section 4. Parachute Jump Operations
  126. Section 5. Moored Balloons, Kites, Parasail, Unmanned Rockets, and Unmanned Free Balloons/Objects
  127. Section 6. 14 CFR Part 107, sUAS Operations
  128. Section 7. Procedural Waivers
  129. Chapter 20. Temporary Flight Restrictions (TFRs)

    Section 1. General Information
  130. Section 2. Temporary Flight Restrictions for Unmanned Aircraft (49 U.S.C. Section 44812)
  131. Section 3. Temporary Flight Restrictions in the Vicinity of Disaster/Hazard Areas (14 CFR Section 91.137)
  132. Section 4. Temporary Flight Restrictions in National Disaster Areas in the State of Hawaii (Section 91.138)
  133. Section 5. Emergency Air Traffic Rules (14 CFR Section 91.139)
  134. Section 6. Flight Restrictions in the Proximity of the Presidential and Other Parties (14 CFR Section 91.141)
  135. Section 7. Flight Limitation in the Proximity of Space Flight Operations (14 CFR Section 91.143)
  136. Section 8. Management of Aircraft Operations in the Vicinity of Aerial Demonstrations and Major Sporting Events (14 CFR Section 91.145)
  137. Chapter 21. Operations Security: Tactical, Special, and Strategic

    Section 1. Organizational Missions
  138. Section 2. Responsibilities
  139. Section 3. Operational Line of Authority
  140. Section 4. Supplemental Duties
  141. Section 5. Coordination
  142. Section 6. Special Security Instruction (SSI) (14 CFR Section 99.7)
  143. Section 7. Security Notice (SECNOT)
  144. Appendices

    Appendix 1. [RESERVED]
  145. Appendix 2. [RESERVED]
  146. Appendix 3. Air Carrier Aircraft for Air Traffic Activity Operations Count
  147. Appendix 4. Glideslope Outage Authorization Request
  148. Appendix 5. Checklist for Reported Headset Tone Incidents
  149. Appendix 6. Space LOA Sample Templates

JO 7210.3 Facility Operation and Administration|JO 7210.3EE · Change 3 · Effective 7/9/2026

Chapter 6 · Section 5

Air Carrier Computer Interface Program

5 Paragraphs|6-5-1–6-5-5

Read Citation (on FlightPush)

6-5-1 GENERAL

Apply the provisions of this section when coordinating and implementing the air carrier computer interface program. The term air carrier used in this section includes scheduled air taxi operators that have the capability to transmit flight plans via the NADIN/Center B interface to ARTCC computer programs.

6-5-2 FACILITY RESPONSIBILITIES

The ARTCC, upon request from an air carrier to participate in this program, must:

a.

Obtain local contacts from the air carrier for coordinating the program.

b.

Provide the air carrier with a contact for the continued coordination of the program.

c.

Ensure that the air carrier is apprised of the criteria in paragraph 6-5-3, Criteria for Participation.

6-5-3 CRITERIA FOR PARTICIPATION

Air carriers participating in the program must be advised of the following criteria:

a.

Departure points and destinations must be contained within the CONUS. However, some users have made previous arrangements with various ICAO States (Puerto Rico, Panama, Canada, etc.) to accept domestic format. These agreements must be honored.

b.

Flight plans must not be filed more than 3 hours in advance of the proposed departure times. Flight plans must be telephoned to the appropriate facility if less than 45 minutes from the proposed departure time. All changes in the flight plan after filing must be telephoned to the appropriate facility.

c.

All flight plans must adhere to the format convention and content specified in paragraph 6-5-4, Format Conventions, and paragraph 6-5-5, Message Content.

6-5-4 FORMAT CONVENTIONS

Flight plans must be filed in the following format:

a.

Data input must adhere to a fixed order and not exceed the stated maximum number of characters or elements allowed for each field in messages addressed to an ARTCC computer.

b.

Each field of data is composed of one or more elements. Discrete elements of information within a field are separated by delimiters; generally, virgules (/) or periods.

c.

Some fields contain the necessary functions to operate the computer adapters and are designated by alpha characters. Do not separate these fields with spaces.

d.

One space character must be entered at the end of each data field, except:

1.

The first data field of a message must not be preceded by a space.

2.

The last data field of message need not be followed by a space.

3.

The Remarks (Field 11) terminate with the last nonspace character transmitted.

6-5-5 MESSAGE CONTENT

The complete message content, the order of data, the number of characters allowed within any data field or element, and any associated operational procedure or restrictions must be as follows: (See FIG 6-5-1).

a.

Start of Message Code (Field A). Appropriate individual company coding to ensure entry into the AFTN system.

b.

Preamble Line (Field B). Consists of priority and addressees in ICAO format.

c.

End of Line Function (Field C). Three characters composed of carriage return, carriage return, line feed.

d.

Computer Adapter Turn‐on Code (Field D). Three characters specifying the facility adapter code plus carriage return, carriage return, line feed.

e.

Source Identification (Field 00). Ten characters followed by a space character in the following order:

1.

Three‐character address of the originating office.

2.

Four‐character (digits) time in UTC.

3.

Three characters (digits) representing the number of the message being transmitted to the specific facility. All facilities will have individual sequence numbers beginning with number 000 at 0000Z.

f.

Message Type (Field 01). The letters “FP” followed by a space character.

g.

Aircraft Identification (Field 02). Consists of two to seven characters followed by a space character. The first character of the identification must be a letter.

h.

Aircraft Data (Field 03). Consists of two to nine characters followed by a space character. Aircraft data within the field may vary from one to three elements consisting of:

1.

Super or heavy aircraft indicator (H/): When aircraft are designated super orheavy, the heavy indicator is mandatory.

2.

Type of Aircraft: This element is mandatory and contains the standard aircraft type designator, in accordance with FAA Order JO 7360.1, Aircraft Type Designators.

3.

Equipment Suffix: This element is optional and consists of a slash followed by one letter which is one of the approved designators identifying transponder and/or navigation equipment.

i.

Airspeed (Field 05): Consists of two to four characters followed by a space character. This field must include the filed true airspeed in knots or Mach speed.

j.

Departure Point (Field 06): The airport of departure must be two to a maximum of five characters using the authorized identifier accessible through FAA Order JO 7350.9, Location Identifiers, and must duplicate the first element of the route of flight (Field 10).

k.

Proposed Departure Time (Field 07): Consists of five characters followed by a space character. This field contains the letter “P” followed by a four‐digit time group (in UTC).

l.

Requested Altitude (Field 09): Consists of two to three characters followed by a space character. Altitudes or flight levels, as appropriate, must be expressed in hundreds of feet.

m.

Route of Flight (Field 10): The route of flight consists of the departure point, the route of flight, and a destination:

1.

Field 10 is fixed sequence field and must begin with a fix; e.g., fix.route.fix.route., etc. An element is separated from another element by a period character.

2.

When consecutive fix elements or route elements are filed, the fixed sequence format is maintained by inserting two period characters between the filed Field 10 elements; e.g., fix..fix or route..route.

3.

The maximum number of filed field elements for computer‐addressed flight plans is 40. Double period insertions do not count against the 40‐element limitation.

(a)

Fix Descriptions: A fix identifies a geographic point and must be one of either domestic, Canadian, or international identifiers, which are two to twelve alphanumeric characters.

(b)

Route Descriptions: A route element must be one of the following:

(1)

Airway: The official airway designator must be filed.

(2)

Standard Instrument Departures (SID): SIDs, if used, must be filed by the computer-code designator as the second element of Field 10 and followed by the transition fix.

(3)

Standard Terminal Arrivals (STAR): STARs, if used, must be filed by the computer-code designator as the next to last element of Field 10 and be immediately preceded by the entry or transition fix.

(4)

Published Radials: Published radials; e.g., within a preferred route, are considered airways. Do not file unpublished radials.

EXAMPLE

“.RBV020” “.JFK053” “DPK017”

(5)

North American Routes (NAR): Numerically coded routes preplanned over existing airways and route system to and from specific coastal fixes serving the North Atlantic.

EXAMPLE

“.NA50” “.NA9”

(c)

Estimated Time En Route Suffix: Consists of an element separator (/) and four digits appended to the destination. Leading zeros are required, and the time en route is expressed in hours and minutes.

EXAMPLE

“.STL/0105”

n.

Remarks (Field 11): Consists of the remarks code character--a clear sky symbol or an overcast sky symbol, and the remarks.

NOTE

If remarks (Field 11) are present, a space is required after the last element of Field 10. If remarks are not present, no space is required, and Field E (End of Text) should be the next entry.

1.

The overcast sky symbol limits the transmittal of the remarks to the center controlling a point of departure. This should be used when the only remarks are a request for a full route clearance (FRC). It may also be used when it is known that the remarks are only pertinent to the center controlling the departure airport.

2.

Remarks are not interpreted by the NAS En Route Program and are optional. When used, they must be limited to flight information pertinent to ATC.

o.

End of Text Signal/End of Message Function (Field E).

NOTE

Fields 04 and 08 are not applicable to proposed flight plans and have been intentionally omitted. (See FIG 6-5-1.)

(A)(B)(C)(D)(00)
Individual company codingFF KZFWZDZXDTG KDALAALXAAL1630001
(01)(02)(03)(05)(06)(07)(09)
FPAAL123B727/A0350OKCP1830160
(10)(11)(E)
OKC..GAG.V280.AMA/0139-> Pressurization inoperativeEnter Key
Computer Flight Data Input Chart
FieldElementExampleRequirements
AStart of Message (SOM code)/BRequired for SOM recognition
BPriority/Address LineFF KZFWZQZXProvides priority and addressee
CDTG/OriginatorDTG KDALAALXIdentifies time of transmission and originator
DEnd of Line (EOL) FunctionNew Line KeyRequired to end all lines except line of text
EEOT/EOMEnter KeyTerminates message
Previous Section6-4 ServicesNext Section 6-6 En Route Decision Support Tool (EDST)

You Are Reading

6-5-1 GENERAL

Read Citation (on FlightPush)