JO 7110.65 5-4-10

The fourth line of the data block must be displayed. When using the fourth line for forwarding control information, only messages specified in this section, a facility directive or LOA are authorized. 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).

The en route fourth line data block area must be used for coordination purposes only in association with radar identified aircraft.

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-10, Automated Information Transfer (AIT).

Coordination format for assigned headings must use the designation character “H” preceding a three-digit number. EXAMPLE-

H080, H270

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. NOTE-

The notation “PH” may be used to denote present heading.

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.

EXAMPLE-

H080/ALB, 080/J121, PH/ALB

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 in the flight plan

D(heading)-(heading)–deviate between two specified headings. NOTE-

Two digits specify turns in degrees and must include direction character(s). Three digits specify heading(s).

The inclusion of /(NAVAID) or /(waypoint), when preceded by the designated characters for weather deviations, indicates that a pilot has been authorized to deviate for weather and rejoin the route at the specified NAVAID or waypoint. The use of /F, following the designated weather deviation characters, indicates that a pilot has been authorized to deviate and rejoin the route of flight at the next fix in the route in accordance with paragraph 2-6-4 .

EXAMPLE-

D90L/ATL, DL/KD75U, D090/F

NOTE-

EXAMPLE-

DN, D20L, D30R, D180-210

Coordination format for specific assigned airspeeds must use the designation character “S” preceding a three‐digit number. A three-digit number followed by a “+” must be used to denote an assigned speed at or greater than the displayed value, or followed by a “-” to denote an assigned speed at or less than the displayed value. EXAMPLE-

S210, 250+, 280-

Aircraft assigned a Mach number must use the designation “M”, “M.”, or “.” preceding the two‐digit assigned value. The displayed Mach number must also be followed by a “+” to denote an assigned speed at or greater than the displayed value, or a “-” to denote an assigned speed at or less than the displayed value. EXAMPLE-

M80, M80+, M80-, M.80, .80, .80-

Coordination format for aircraft authorized to conduct celestial navigation training within 30 NM of the route centerline specified within the en route clearance must use “CELNAV.”

Coordination format for aircraft requesting an altitude change must use the designation characters “RQ” preceding a three‐digit number. EXAMPLE-

RQ170, RQ410

Coordination format for aircraft requesting a route change must use the designation “RQ/” preceding a specific fix identifier. EXAMPLE-

RQ/LAX, RQ/NEUTO

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.

All other control information must be coordinated via other methods.

Previous | Top | Next 7110.65 |

ATPUBS |

FAA |

Send your comments regarding this website.

Chapter 5. Radar 7110.65BB

7110.65 by Chapter Number Chapter 0. General Information Chapter 1. General Chapter 2. General Control Chapter 3. Airport Traffic Control - Terminal Chapter 4. IFR Chapter 5. Radar Chapter 6. Nonradar Chapter 7. Visual Chapter 8. Offshore/Oceanic Procedures Chapter 9. Special Flights Chapter 10. Emergencies Chapter 11. Traffic Management Procedures Chapter 12. Canadian Airspace Procedures Chapter 13. Decision Support Tools Chapter 14. Data Link Communications Appendix A Appendix B

ATPUBS

JO 7110.65BB by Topic

General Information Explanation of Changes

General Introduction

Terms of Reference

General Control General

Flight Plans and Control Information

Flight Progress Strips

Radio and Interphone Communications

Route and NAVAID Description

Weather Information

Altimeter Settings

Runway Visibility Reporting- Terminal

Automatic Terminal Information Service Procedures

Team Position Responsibilities

Airport Traffic Control - Terminal General

Visual Signals

Airport Conditions

Airport Lighting

Runway Selection

Airport Surface Detection Procedures

Taxi and Ground Movement Procedures

Spacing and Sequencing

Departure Procedures and Separation

Arrival Procedures and Separation

Helicopter Operations

Sea Lane Operations

IFR NAVAID Use Limitations

Clearances

Departure Procedures

Route Assignment

Altitude Assignment and Verification

Holding Aircraft

Arrival Procedures

Approach Clearance Procedures

Radar General

Beacon/ADS-B Systems

Radar Identification

Transfer of Radar Identification

Radar Separation

Vectoring

Speed Adjustment

Radar Departures

Radar Arrivals

Radar Approaches- Terminal

Surveillance Approaches- Terminal

PAR Approaches- Terminal

Automation- En Route

Standard Terminal Automation Replacement System (STARS)-Terminal

Nonradar General

Initial Separation of Successive Departing Aircraft

Initial Separation of Departing and Arriving Aircraft

Longitudinal Separation

Lateral Separation

Vertical Separation

Timed Approaches

Visual General

Visual Separation

VFR‐On‐Top

Approaches

Special VFR (SVFR)

Basic Radar Service to VFR Aircraft- Terminal

Terminal Radar Service Area (TRSA)-Terminal

Class C Service- Terminal

Class B Service Area- Terminal

Offshore/Oceanic Procedures General

Coordination

Longitudinal Separation

Lateral Separation

Offshore/Oceanic Transition Procedures

Separation from Airspace Reservations

North Atlantic ICAO Region

Caribbean ICAO Region

Pacific ICAO Region

North American ICAO Region

Special Flights General

Special Operations

Special Use, ATC-Assigned Airspace, and Stationary ALTRVs

Fuel Dumping

Jettisoning of External Stores

Unmanned Free Balloons

Parachute Operations

Unidentified Anomalous Phenomena (UAP) Reports

Emergencies General

Emergency Assistance

Overdue Aircraft

Control Actions

Miscellaneous Operations

Oceanic Emergency Procedures

Ground Missile Emergencies

Traffic Management Procedures General

Canadian Airspace Procedures General Control

Decision Support Tools ERAM - En Route

ATOP - Oceanic

Data Link Communications Terminal Procedures for Issuing Automated Clearances

En Route Controller Pilot Data Link Communications (CPDLC) - Domestic

Advanced Technologies and Oceanic Procedures (ATOP) - Oceanic Controller Pilot Data Link Communications (CPDLC)

Appendix A

Appendix B

Radar

Radar Separation

Chapter 5. Radar

Section 5. Radar Separation