En Route Decision Support Tool (EDST) is an integrated function of ERAM that is used by the sector team in performing its strategic planning responsibilities. EDST uses flight plan data, forecast winds, aircraft performance characteristics, and track data to derive expected aircraft trajectories, and to predict conflicts between aircraft and between aircraft and special use or designated airspace. It also provides trial planning and enhanced flight data management capabilities.
13-1-2. CONFLICT DETECTION AND RESOLUTION
Actively scan EDST information for predicted aircraft-to-aircraft and aircraft-to-airspace alerts.
When a conflict probe alert is displayed, evaluate the alert and take appropriate action as early as practical, in
accordance with duty priorities.
Prioritize the evaluation and resolution of conflict probe alerts to ensure the safe, expeditious, and efficient
flow of air traffic.
NOTE: Conflict probe alerts are based on standard radar separation. Conflict probe does not account for
instances in which greater separation may be needed (e.g., non-standard formations, A380) or where reduced
separation is permitted (e.g., 3mile airspace).
When a conflict probe alert is displayed and when sector priorities permit, give consideration to the following in
determining a solution:
Solutions that involve direct routing, altitude changes, removal of a flight direction constraint (i.e.,
inappropriate altitude for direction of flight), and/or removal of a static restriction for one or more
Impact on surrounding sector traffic and complexity levels, flight efficiencies, and user preferences.
When the Stop Probe feature is activated for an aircraft, conflict probe for that aircraft shall be restarted
before transfer of control, unless otherwise coordinated.
NOTE: The requirement in subparagraph 13-1-2e does not apply to aircraft entering a non EDST facility.
13-1-3. TRIAL PLANNING
When EDST is operational at the sector and when sector priorities permit, use the trial plan capability to evaluate:
Solutions to predicted conflicts.
The feasibility of granting user requests.
The feasibility of removing a flight direction constraint (i.e., inappropriate altitude for direction of flight) for an aircraft.
The feasibility of removing a static restriction for an aircraft.
13-1-4. CONFLICT PROBE-BASED CLEARANCES
When the results of a trial plan based upon a user request indicate the absence of alerts, every effort should be made to grant the user request, unless the change is likely to adversely affect operations at another sector.
13-1-5. THE AIRCRAFT LIST (ACL), DEPARTURE LIST (DL) AND FLIGHT DATA MANAGEMENT
The ACL must be used as the sector team's primary source of flight data.
Actively scan EDST to identify automated notifications that require sector team action.
When an ACL or DL entry has a Remarks indication, the Remarks field of the flight plan must be reviewed. Changes to the Remarks field must also be reviewed.
Highlighting an entry on the ACL or DL must be used to indicate the flight requires an action or special attention.
The Special Posting Area (SPA) should be used to group aircraft that have special significance (e.g., aircraft to be sequenced, air refueling missions, formations).
Sector teams shall post flight progress strips for any non-radar flights.
A flight progress strip shall be posted for any flight plan not contained in the EAS.
Sector teams shall post any flight progress strip(s) that are deemed necessary for safe or efficient operations. The sector team shall comply with all applicable facility directives to maintain posted flight progress strips.
The Drop Track Delete option shall be used in accordance with facility directives.
13-1-6. MANUAL COORDINATION AND THE COORDINATION MENU
Where automated coordination with a facility is not available (e.g., an international facility, a VFR tower), use the Coordination Menu or a flight progress strip to annotate manual coordination status, in accordance with facility directives.
When the Coordination Menu is used and the flight plan is subsequently changed, remove the yellow coding from the Coordination Indicator after any appropriate action has been taken.
For flights in hold, use the Hold View, Hold Data Menu, hold message, a flight progress strip, or a facility
approved worksheet, to annotate holding instructions, in accordance with facility directives.
13-1-8. RECORDING OF CONTROL DATA
All control information not otherwise recorded via automation recordings or voice recordings must be manually recorded using approved methods.
When a verbal point out has been approved, remove the yellow color coding on the ACL.
When the ACL or DL Free Text Area is used to enter control information, authorized abbreviations must be used. You may use:
The clearance abbreviations authorized in TBL 13-1-1.
TBL 13-1-1 Clearance Abbreviations
Cleared to airport (point of intended landing)
Center clearance delivered
ATC clears (when clearance relayed through non-ATC facility)
Cleared as filed
Cleared to depart from the fix
Cleared to the fix
Cleared to hold and instructions issued
Clearance not delivered
Cleared to the outer marker
Cleared to climb/descend at pilot's discretion
Cleared to fly specified sectors of a NAVAID defined in terms of courses, bearings, radials, or quadrants within a designated radius
Cleared through (for landing and takeoff through intermediate point)
Cleared over the fix
Cleared to cross (airway, route, radial) at (point)
The miscellaneous abbreviations authorized in TBL 13-1-2.
The EDST equivalents for control information symbols authorized in TBL 13-1-3.
Plain language markings when it will aid in understanding information.
Locally approved abbreviations.
When the ACL or DL Free Text Area is used to enter control information, the Free Text Area must remain open and visible. When no longer relevant, the information entered into the Free Text Area must be updated or deleted.
Control information entered in the Free Text Area must be used for reference purposes only.
NOTE: Information entered into the Free Text Area does not pass on handoff and, if necessary, must be coordinated.
TBL 13-1-2 Miscellaneous Abbreviations
Back course approach
Flight management system approach
Nondirectional radio beacon approach
Resolution advisory (Pilot-reported TCAS event)
Area navigation approach
Report immediately upon passing (fix/altitude)
TBL 13-1-3 EDST Equivalents for Control Information Symbols
Depart (direction if specified)
Climb and maintain
Descend and maintain
Join or intercept (airway, jet route, track, or course)
While in controlled airspace
While in control area
Enter control area
Out of control area
Cleared to enter surface area. Indicated direction of flight by appropriate compass letter(s)
Through surface area and altitude indicated direction of flight by appropriate compass letter(s). Maintain special VFR conditions (altitude if appropriate) while in surface area
Aircraft requested to adjust speed to 250 knots
Aircraft requested to reduce speed 20 knots
Aircraft requested to increase speed 30 knots
Local Special VFR operations in the vicinity of (name) airport are authorized until (time). Maintain special VFR conditions (altitude if appropriate)
After or Past
At or Below
At or Above
From-to (route, time, etc.)
Indicates a block altitude assignment. Altitudes are inclusive, and the first altitude must be lower than the second (Example 310B370)
Clearance void if aircraft not off ground by time
Pilot canceled flight plan
Information or revised information forwarded
Other than assigned altitude reported. Example: **50**
ARC mi. dir.
DME arc of VORTAC or TACAN
Contact (facility) or (freq.), (time, fix, or altitude if appropriate). Insert frequency only when it is other than standard
Radar service terminated
Radar Contact Lost
Pilot resumed own navigation
Point out initiated. Indicate the appropriate facility, sector, or position.
Expect further clearance at (time)
Direct to fix
Full route clearance
Initial approach fix
13-1-9. ACKNOWLEDGEMENT OF AUTOMATED NOTIFICATION
The EDST Inappropriate Altitude for Direction of Flight (IAFDOF) feature must be used in the automatic mode (i.e., IAFDOF Manual must remain deselected) unless otherwise authorized in a facility directive.
Completion of any required coordination for IAFDOF must be acknowledged on the ACL by removing the IAFDOF coding.
Completion of appropriate coordination for an Unsuccessful Transmission Message (UTM) must be acknowledged on the ACL by removing the UTM coding.
Issuance of the Expect Departure Clearance Time (EDCT) to the pilot or other control facility must be acknowledged on the DL by removing the EDCT coding.
IAFDOF, UTM, or EDCT coding must be acknowledged only after the appropriate action has been completed.
The first sector which displays Embedded Route Text (ERT) coding must issue and send/acknowledge the route prior to initiating a hand-off unless verbally coordinated or as specified in appropriate facility directives. Do not send/acknowledge ERT coding unless the sector has track control for the flight or it has been otherwise coordinated.
Route Action Notifications (RAN) such as ATC preferred routes or route processing errors must be amended at the first control position that displays the RAN unless verbally coordinated or as specified in appropriate facility directives. Do not remove RAN coding unless the sector has track control or it has been otherwise coordinated.
13-1-10. CURRENCY OF TRAJECTORY INFORMATION
The sector team shall perform automation entries in a timely manner.
1. Conflict probe accuracy requires timely updates of data used to model each flight's trajectory. If this data is not current, the aircraft entries and notification of probe results for surrounding sectors and facilities, as well as the subject sector, may be misleading.
2. Data used to model an individual aircraft's trajectory includes route of flight, assigned and interim altitudes, application/removal of an adapted restriction for that flight, and aircraft type.
An exception to the requirement to enter or update interim altitudes may be authorized for certain ARTCC sectors if explicitly defined in an appropriate facility directive.
NOTE: Conflict probe accuracy in assigning alert notification is dependent upon entry/update of a flight's interim altitude.
13-1-11. DELAY REPORTING
Adhere to all applicable delay reporting directives.
Delay information must be recorded. Delay information may be automatically recorded via use of the ERAM Hold Data
Menu, ERAM Hold View, a hold message, or manually on flight progress strips or facility-approved worksheets, in
accordance with the facility-defined standard.
NOTE: When using the ERAM Hold Data Menu or Hold View, delays are automatically recorded when the aircraft is
cleared out of hold.
13-1-12. OVERDUE AIRCRAFT
Upon receipt of the overdue aircraft notification take appropriate actions set forth in Chapter 10, Section 3, Overdue aircraft.
NOTE: ESDT overdue aircraft notification is based on radar track data. Updating an aircraft's route of fight will remove the overdue aircraft notification.
13-1-13. USE OF GRAPHICS PLAN DISPLAY (GPD)
Graphic depictions of flight trajectories may be used only to aid in situational awareness and strategic planning.
Do not use trajectory-based positions as a substitute for radar track position.
Do not use trajectory-based altitude in lieu of Mode C for altitude confirmation.
Do not use the GPD for radar identification, position information, transfer of radar identification, radar separation, correlation, or pointouts.
13-1-14. FORECAST WINDS
In the event that current forecast wind data are not available, continue use of conflict probe and trial planning with appropriate recognition that alert and trajectory data may be affected.
13-1-15. INTERFACILITY CONNECTIVITY
In the event of a loss of connectivity to an adjacent ERAM facility, continue use of EDST with appropriate recognition that alert data may be affected.
13-1-16. SURVEILLANCE AND FLIGHT DATA OUTAGES
In the event of a surveillance or flight data outage, electronic flight data may be used to support situational awareness while the facility transitions to alternate automation capabilities or non radar procedures.
13-1-17. AIRSPACE CONFIGURATION ELEMENTS
Airspace Configuration Elements are:
Special Activity Airspace (SAA).
Airport Stream Filters (ASF).
Where assigned as a sector responsibility by facility directive, the sector team shall update Airspace Configuration Elements to reflect current status.
NOTE: Unless otherwise covered in an LOA or facility directive, activating or scheduling the SAA in the Airspace Status View does NOT constitute coordination for activation of airspace.
For Airspace Configuration Elements designated as a sector responsibility, notify the operational supervisor when the status of an Airspace Configuration Element has been modified.