Section 2. Procedures

  1. THREE MILE OPERATIONS

Facilities may adapt airspace to permit the use of 3 NM separation as defined in FAA Order JO 7110.65, Air Traffic Control, subparagraph 5-5-4c, subparagraph 5-5-4d, or subparagraph 5-5-4e, provided all of the following are met:

  1. An operational advantage will be obtained. Consideration must be given to such aspects as terminal interface, radar reliability, etc.
  2. Facility directives are issued to:
  1. Define the 3 NM separation area.
  2. Permit 3 NM separation in the defined area.
  3. Accommodate local procedural changes.
  1. ERAM:
  1. The 3 NM separation area is displayable on the video map.
  2. The aircraft alert volume is adapted for 3 NM separation.
  3. Within 40 NM of the preferred radar; or
  4. Within 60 NM of the preferred radar when using an MSSR; or
  5. When the facility is operating in track-based display mode.

NOTE-

  1. ADS-B allows the expanded use of 3 NM separation in approved areas. It is not required for and does not affect the use of radar for 3 NM separation.
  2. The Surveillance Services Directorate provides maps to facilities depicting the geographic areas and altitudes where ADS-B has been validated for 3 NM separation.
  1. MEARTS: All sort boxes within 40 NM of the sensor or within 60 NM of the sensor when using an MSSR and with the single site indicator set to permit the use of 3 NM radar separation.
  1. ADAPTED ALTIMETER SETTINGS

Ensure a current altimeter setting from the adapted reporting station for each radar sort box/surveillance sort cell or geographic area is input into the center's computer. When an altimeter setting for an adapted reporting station cannot be obtained, enter the altimeter setting from the appropriate alternate reporting station.

  1. ADAPTATION OF EXTERNAL ALTIMETER SETTINGS

Adaptation of altimeter settings for reporting stations outside a facility's area is optional up to the maximum number listed in the NAS adaptation specifications.

  1. CONFLICT ALERT FUNCTION PARAMETERS
  1. Use the approved CA preset values as defined in the ERAM Site Adaptation Manual (SAM) unless otherwise approved by the En Route and Oceanic Safety and Operation Support Office.
  2. Facility air traffic managers are authorized to inhibit the display of CA at specified sectors and within ERAM Aircraft Alert Volumes (AAVs).
  1. MODE C INTRUDER (MCI) ALERT PARAMETERS
  1. Use the approved MCI CA preset values as defined in the ERAM Site Adaptation Manual (SAM) unless otherwise approved by the En Route and Oceanic Safety and Operations Support Office.
  2. MCI Alert base altitude must be set at any value between ground level and 5,000 feet MSL at the discretion of the facility air traffic manager. When a facility's or sector's ground level is above 5,000 feet MSL, base altitudes may be set to 1,500 AGL. Any instance of base altitudes above 5,000 feet MSL must be documented and forwarded to the En Route and Oceanic Safety and Operations Support Office through the respective Service Area Operations Directorate.
  3. Facility air traffic managers are authorized to temporarily adjust the Mode C Intruder Alert base altitude at a sector(s) when excessive MCI alerts derogate the separation of IFR traffic. For the purpose of this section, temporary is considered to be of less than 4 hours duration, not necessarily continuous, during any calendar day. The following is required when MCI base altitude is adjusted:
  1. Log each occurrence when this procedure is used on FAA Form 7230-4, including the sector and temporary altitude.
  2. Documentation must be forwarded according to subparagraph b above, if it is determined that a temporary adjustment of the MCI base altitude does not meet the needs of the sector.
  3. Facility air traffic managers are authorized to inhibit the situation display of MCI Alert at specified sectors.
  1. E-MSAW ADAPTATION

Ensure that all internal airspace is adapted for E-MSAW processing. Ensure that the internal altitude information adapted in the polygons agrees with the MIA sector charts and is in accordance with the ERAM Site Adaptation Manual.

  1. INTERIM ALTITUDE FACILITY DIRECTIVE REQUIREMENTS

Where sector conditions (e.g., heavy traffic or sector complexity) preclude meeting the requirements of FAA Order JO 7110.65, Air Traffic Control, paragraph 5-13-3, Computer Entry of Flight Plan Information, ARTCC air traffic managers may authorize exceptions to the requirement to update the data block with a temporary altitude if an operational advantage is gained. A facility directive must be issued with instructions governing permissible procedures. It must contain:

  1. Procedures/sectors where the directive applies.
  2. Coordination procedures if required.
  3. Specific instructions to input a reported altitude for non-Mode C-equipped aircraft when it will operate at an altitude before proceeding to the assigned altitude.
  1. REQUIREMENTS FOR ERAM DATA BLOCK CHANGES WITHOUT COORDINATION

Where sector conditions offer a significant operational advantage, air traffic managers may authorize exceptions to data block change coordination required by FAA Order JO 7110.65, Air Traffic Control, paragraph 5-4-5, Transferring Controller Handoff, and FAA Order JO 7110.65, Air Traffic Control, paragraph 5-4-6, Receiving Controller Handoff. The facility directive or LOA must contain, at a minimum:

  1. Sectors where the directive or LOA applies.
  2. Specific situations where omission of coordination is permitted.

EXAMPLE-

LOA specifies the aircraft will be descending to FL290 and changes in interim altitude are authorized after handoff to get to FL 290.

NOTE-

Consideration needs to be given to the ability of all sector team members to readily discriminate the indicator in the B4 field under varied conditions, such as font size and brightness, situation display orientation, and lighting. There is a significant operational difference between accepting a handoff with:

a. An “up arrow" in which aircraft will not climb beyond displayed assigned altitude, and

b. A “T" (interim) altitude where the aircraft may climb beyond the currently displayed interim altitude.

  1. ERAM HOLD INFORMATION FACILITY DIRECTIVE REQUIREMENTS

Where sector conditions offer a significant operational advantage, air traffic managers may authorize exceptions to FAA Order JO 7110.65, Air Traffic Control, paragraph 5-14-9, ERAM Computer Entry Hold Information. The facility directive must contain, at a minimum:

  1. Sectors where the directive applies.
  2. Required coordination procedures.
  3. Specific instructions for reporting delays.
  1. ERAM SPECIAL ACTIVITY AIRSPACE (SAA) ADAPTATION

Facilities must ensure that every SAA within their Aircraft Problem Detection (APD) Area is adapted for SAA scheduling and alert processing.

  1. ERAM HOLDING PATTERN ADAPTATION

Ensure published holding patterns on Standard Terminal Arrival Routes (STARs) are adapted to automatically populate the Hold Data Menu.

NOTE-

Adapting holding patterns will reduce controller workload by automatically populating the Hold Data Menu. Therefore, facilities should consider adapting all frequently used holding patterns.

  1. ERAM MASTER TOOLBAR MAP BUTTON LABEL

Ensure the adapted label of the GEOMAP button matches the name of the GEOMAP selected at the sector. The map button label may be displayed on two lines and may include spaces to improve label readability.

NOTE-

Since the GEOMAP is saved with the preference set, displaying the map name on the GEOMAP button label provides a visual indication to the controller when a GEOMAP changes as a result of invoking a preference set.

  1. LOCAL INTERIM ALTITUDE

Ensure that the ERAM Local Interim Altitude function is turned on.