EVALUATION — simulated traffic. Public demo: changes are shared. Not for operational use.

HCF DEPARTURES

ALL SECTORS DEMO · MADE-UP FLIGHTS ATIS —
0000:00Z
Waiting for the next departure.
ROLLING
DEPARTEDLAST 30 MIN
CLEARANCE
TAXIING
DEPARTURE SECTORS

Each departure is tagged with the sector it goes to. The STARS exit fix decides first, then a route through one of a sector's fixes or warning areas, then the destination. In Destinations, MAINLAND means every airport in the 48 states, Alaska, Canada and Mexico, and a pattern like R* means every ICAO code starting with R (Japan, Korea and so on). Anything not listed shows SECTOR ? and appears on both the H and L screens, so nothing is missed. Separate entries with spaces or commas. Saved in this browser only: set the same lists on each position.

MILITARY DEPARTURES

Fighters roll with the transponder off, so ASDE-X shows them with no callsign, and their flight plans are not in the TFMS or STDDS feeds. Type in the day's military departures here (from the mission board or DCAST). Each goes on the board as a proposed strip, and the fighter flight that rolls near its P-time takes its callsign and flight plan: one strip with the number of aircraft, and on the map the lead shows the callsign and the others #2, #3 and so on. Times are Zulu.

EVENT LOG

Strips move only when an event arrives: Clearance holds the proposed time (TFMS) and the clearance delivered (STDDS); Taxiing starts when ASDE-X shows the aircraft moving, through lining up; Rolling when ASDE-X shows it accelerating on the runway; Departed at the wheels-up time from the STDDS surface events, or the TFMS departure message as a backup. Demo and replay are not connected to any FAA system. Live mode reads the HCF Flow Board relay (departures.js), on this computer or by a position link. Awareness only: not a substitute for the rolling call or required coordination.