EDST 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. Under ERAM, the EDST capabilities constitute the initial En Route decision support tools.
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).
NOTE: The requirement in paragraph 13-1-2e does not apply to aircraft entering a non EDST facility.
When EDST is operational at the sector and when sector priorities permit, use the trial plan capability to evaluate:
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.
For flights in hold, use the ERAM Hold Data Menu/Hold View, the EDST Hold Annotations Menu, a flight progress strip, or a facility approved worksheet, to annotate holding instructions, in accordance with facility directives.
|A||Cleared to airport (point of intended landing)|
|B||Center clearance delivered|
|C||ATC clears (when clearance relayed through non-ATC facility)|
|CAF||Cleared as filed|
|D||Cleared to depart from the fix|
|F||Cleared to the fix|
|H||Cleared to hold and instructions issued|
|N||Clearance not delivered|
|O||Cleared to the outer marker|
|PD||Cleared to climb/descend at pilot’s discretion|
|Q||Cleared to fly specified sectors of a NAVAID defined in terms of courses, bearings, radials, or quadrants within a designated radius|
|T||Cleared through (for landing and takeoff through intermediate point)|
|V||Cleared over the fix|
|X||Cleared to cross (airway, route, radial) at (point)|
NOTE: Information entered into the Free Text Area does not pass on handoff and, if necessary, must be coordinated.
|BC||Back course approach|
|FMS||Flight management system approach|
|NDB||Nondirectional radio beacon approach|
|RA||Resolution advisory (Pilot-reported TCAS event)|
|RNAV||Area navigation approach|
|RP||Report immediately upon passing (fix/altitude)|
|T dir||Depart (direction if specified)|
|↑||Climb and maintain|
|↓||Descend and maintain|
|/ airway||Join or intercept (airway, jet route, track, or course)|
|=||While in controlled airspace|
|WICA||While in control area|
|dir ECA||Enter control area|
|dir OOCA||Out of control area|
|dir ESA||Cleared to enter surface area. Indicated direction of flight by appropriate compass letter(s)|
|TSA alt||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|
|250 K||Aircraft requested to adjust speed to 250 knots|
|-20 K||Aircraft requested to reduce speed 20 knots|
|+30 kt||Aircraft requested to increase speed 30 knots|
|SVFR||Local Special VFR operations in the vicinity of (name) airport are authorized until (time). Maintain special VFR conditions (altitude if appropriate)|
|AF||After or Past|
|AOB||At or Below|
|AOA||At or Above|
|-||From-to (route, time, etc.)|
|(alt)B(alt)||Indicates a block altitude assignment. Altitudes are inclusive, and the first altitude must be lower than the second (Example 310B370)|
|V time||Clearance void if aircraft not off ground by time|
|CL||Pilot canceled flight plan|
|+info+||Information or revised information forwarded|
|**alt**||Other than assigned altitude reported. Example: **50**|
|ARC mi. dir.||DME arc of VORTAC or TACAN|
|C freq.||Contact (facility) or (freq.), (time, fix, or altitude if appropriate). Insert frequency only when it is other than standard|
|R alt||Requested altitude|
|R/||Radar service terminated|
|RX||Radar Contact Lost|
|RVX||Pilot resumed own navigation|
|P||Point out initiated. Indicate the appropriate facility, sector, or position.|
|EFC time||Expect further clearance at (time)|
|- fix||Direct to fix|
|FRC||Full route clearance|
|IAF||Initial approach fix|
NOTE: Conflict probe accuracy in assigning alert notification is dependent upon entry/update of a flight’s interim altitude.
NOTE: When using EDST hold annotations, delay information cannot be accurately recorded unless the annotations are deleted when the aircraft is cleared from holding. When using the ERAM Hold Data Menu or Hold View, delays are automatically recorded when the aircraft is cleared out of hold.
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.
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.
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.
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.
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.