EDCT Support Tool
Controller guide for cross-facility support event operations
Overview
The EDCT (Expect Departure Clearance Time) tool manages departure flow during cross-facility support events. When ZNY supports events at neighboring facilities (ZDC, ZBW, ZOB, etc.), departures from NY metro airports must be spaced to prevent congestion at the sequencing fix.
The destination facility specifies the required spacing (e.g., "20 miles in trail over COPES"). The tool calculates when each aircraft needs to depart from its airport to maintain that spacing at the fix, accounting for transit time differences between airports and current wind conditions.
Each departure receives a specific EDCT. Controllers release aircraft according to their assigned times.
Accessing the Tool
Navigate to vzny.org/tmu/edct and sign in with your VATSIM account. The tool detects your active position from the VATSIM datafeed and sets your access level automatically.
A pop-out option is available for use alongside other tools. The pop-out window opens at 1400x900, suitable for a secondary monitor or side panel.
Access Tiers
Your access tier is displayed as a badge in the top-right corner. Tier assignment is automatic based on your VATSIM callsign.
Read-only access. Full visibility into the flow, queue, and assigned EDCTs. No modification capability.
Departure queue filtered to your facility's event traffic. JFK_TWR sees JFK departures, EWR_GND sees EWR departures, etc. NY_APP controllers see departures matching their facility certifications. Center controllers see all departure airports.
Full access to assign and modify EDCTs across all airports, adjust MIT spacing, and manage programs. Automatically granted to NY_T_CTR positions and controllers with explicit EDCT authority from the event coordinator.
Interface Layout
During a live event, a green LIVE banner displays at the top with the event name and pilot/program counts. Below the banner, a program selector bar shows each active CFR program (e.g., DCA COPES | BWI COPES | IAD LRP). Select a program to filter the view to that flow.
⚙️ Configuration
Current program settings: MIT spacing, departure runways, and transit times per airport. Primarily a TMU reference tab. Facility controllers generally do not need to interact with this tab.
✈️ EDCT Request
Primary tab for facility controllers. Displays pilots on the ground at your airport filed to the event destination. Queue auto-updates every 5 seconds from the VATSIM datafeed. Each aircraft shows callsign, type, destination, and filed route.
📡 Sequencing
Full flow view showing all aircraft approaching the sequencing fix, sorted by ETA. Displays overflights (airborne traffic), gaps where departures can be inserted, and current MIT/MINIT spacing. TMU uses this tab to assign EDCTs.
📋 Release Board
All assigned EDCTs with real-time countdown timers, sorted by urgency (soonest first). When a timer reaches zero, that aircraft is cleared for release.
Facility Controller Workflow
Open the EDCT Request tab
Select the program for the destination you are working (e.g., "DCA COPES"). The queue displays pilots on the ground at your airport filed to that destination.
Check for assigned EDCTs
If TMU has assigned an EDCT to one of your departures, a countdown timer will appear next to the aircraft. This is the time the pilot needs to be wheels-up.
Release on time
Taxi the pilot into position as the countdown approaches. Target wheels-up within approximately 90 seconds of the assigned EDCT. Do not release early; the spacing depends on adherence to the assigned times.
Monitor the Release Board
The Release Board tab provides a consolidated view of all assigned EDCTs with color-coded countdowns. Monitor it for upcoming departures at your facility.
Release Board Countdown States
Countdown timers change color as the EDCT approaches:
Audio alerts: single tone at 2 minutes, double tone at EDCT time. Use the speaker icon in the header to toggle audio.
MIT and MINIT Spacing
The destination facility requests spacing as MIT (Miles-in-Trail), for example, "20 miles in trail over COPES." The tool converts MIT to MINIT (Minutes-in-Trail) using live groundspeeds sampled from aircraft near the sequencing fix.
Example: 20nm MIT with an average groundspeed of 360 knots near the fix yields approximately 3.3 minutes between each aircraft at the fix. The tool uses this value along with each airport's transit time to the fix to calculate departure times.
Transit times differ by airport and runway configuration (e.g., JFK may be 12 minutes to a fix while EWR is 14). The tool accounts for these differences automatically. Wind shifts that affect groundspeed will adjust the MINIT calculation in real time.
Pilot Not in Queue
The departure queue is populated from the VATSIM datafeed. A pilot will not appear if:
- No flight plan has been filed
- The filed arrival airport does not match the event destination
- The pilot is not connected to VATSIM at your airport
- The pilot just connected (allow up to 15 seconds for the next datafeed cycle)
Resolution: Verify the pilot's flight plan, specifically that the arrival airport matches the event destination (e.g., KDCA, KIAD, KBWI).
Demo Mode
When no support event is active, the tool loads in demo mode with simulated traffic. A yellow DEMO banner will display in place of the green LIVE banner.
Navigate to vzny.org/tmu/edct while signed in to access demo mode. The demo includes simulated overflights, ground departures, and sample CFR programs across all four tabs. Demo data is entirely simulated and does not affect live operations.
Technical Details
- •Data source: Pilot positions are sourced from the VATSIM datafeed (updated approximately every 15 seconds). The tool polls every 5 seconds.
- •Transit times: Pre-calculated for each airport, runway, and fix combination using FAA STAR route geometry. TMU may adjust these values based on current conditions.
- •Groundspeed sampling: Live groundspeeds from aircraft near the sequencing fix are used to compute MINIT from MIT. Changes in wind conditions are reflected automatically.
- •Multiple programs: Events with multiple destinations (e.g., DCA + BWI + IAD) run independent programs, each with its own fix, MIT value, and timing calculations.
- •Program pausing: TMU may pause individual programs during an event (indicated by ⏸ with strikethrough). Paused programs stop generating new EDCTs and resume immediately when unpaused.
Reporting Issues
This tool is under active development. If you encounter unexpected behavior, please report it so the issue can be addressed.
When submitting a report, include:
- Expected behavior vs. observed behavior
- Your VATSIM callsign at the time of the issue
- The event and program you were viewing
- A screenshot, if available
Submit reports via the feedback page or in the ZNY Discord.