5-4-10. EN ROUTE FOURTH LINE DATA BLOCK USAGE

5-4-10. ENROUTE FOURTH LINE DATA BLOCK USAGE

1. The fourth line of the data block must be displayed. When used for forwarding control information, only the specified messages listed in this section may be used. Any additional control information must be forwarded via other communications methods. Free text may be used by individual sector teams for recording information the team deems appropriate for managing the sector, but must be removed prior to initiation of identification transfer.
   • REFERENCE
   • FAA Order JO 7110.65, Para 5-4-5, Transferring Controller Handoff, subpara b.
   • FAA Order JO 7110.65, Para 5-4-8, Automated Information Transfer (AIT).
2. The enroute fourth line data block area must be used for coordination purposes only in association with radar identified aircraft.
3. When automated information transfer (AIT) procedures are applied, en route fourth line usage for transfer of control information must be specifically defined within facility AIT directive.
   • REFERENCE
   • FAA Order JO 7110.65, Para 5-4-8, Automated Information Transfer (AIT).
   • FAA Order JO 7210.3, Para 4-3-8, Automated Information Transfer (AIT).
4. Coordination format for assigned headings must use the designation character “H” preceding a three-digit number.
   • EXAMPLE
   • H080, H270
5. Aircraft assigned a heading until receiving a fix or joining a published route must be designated with assigned heading format followed by the fix or route.
   • EXAMPLE
   • H080/ALB, 080/J121, PH/ALB
   • NOTE:
   • 1. The notation “PH” may be used to denote present heading.
   • 2. The character “H” may be omitted as a prefix to the heading assignment only if necessary due to character field limitations, and it does not impede understanding.
6. Coordination format for weather deviations must use the designated characters:
   • D - deviation
   • L - left
   • R - right
   • N - north
   • E - east
   • S - south
   • W - west
   • /F - direct next NAVAID/waypoint
   • D+2 headings - deviate between.
   • NOTE:
   • 1. Two digits specify turns in degrees and must include direction character(s). Three digits specify heading(s).
   • 2. The inclusion of a /NAVAID, /waypoint, or /F indicates that the pilot has been authorized to deviate for weather and must rejoin the route at the next NAVAID, waypoint, or fix in the route of flight in accordance with the phraseology in paragraph 2-6-4.
     • EXAMPLE
     • D90/ATL, DL/KD75U, D090/F
   • 3. The absence of a NAVAID, waypoint, or /F indicates that the pilot has been authorized to deviate for weather only, and the receiving controller must provide a clearance to rejoin the route in accordance with paragraph 2-1-15c.
     • EXAMPLE
     • DN, D20L, D30R, D080+120
7. Coordination format for assigned airspeeds must use the designation character “S” preceding a three-digit number.

   NOTE: A “+” notation may be added to denote an assigned speed at or greater than the displayed value. A “-” notation may be added to denote an assigned speed at or less than the displayed value.

   • EXAMPLE
   • S210, S250, S250+, S280-
8. Aircraft assigned a Mach number must use the designation “M” preceding the two-digit assigned value.
   • EXAMPLE
   • M80, M80+, M80-
   • REFERENCE
   • FAA Order JO 7110.65, Para 5-4-10, En Route Fourth Line Data Block Usage, subpara g NOTE.
9. Aircraft authorized to conduct celestial navigation training within 30 NM of the route centerline specified within the en route clearance.
   • EXAMPLE
   • CELNAV
10. Coordination format for aircraft requesting an altitude change must use the designation characters “RQ” preceding a three-digit number.
    • EXAMPLE
    • RQ170, RQ410
11. Coordination format for aircraft requesting a route change must use the designation “RQ/” preceding a specific fix identifier.
    • EXAMPLE
    • RQ/LAX, RQ/NEUTO
12. The acceptance of a handoff by the receiving controller must constitute receipt of the information contained within the en route fourth line data block. This information must not be modified outside of the controller's area of jurisdiction unless verbally coordinated or specified in a Letter of Agreement or Facility Directive. It is the responsibility of the receiving controller to advise the transferring controller if any information is not understood, or needs to be revised.

    NOTE: Due to system and character limitations the usage of these standardized entries may require additional support via facility directive in order to provide complete coordination.

13. All other control information must be coordinated via other methods.