Search callsigns only. Search and order change this list; traffic keeps its course.
0 of 0 flights shown
No callsigns match this search. Clear the search to see all flights.
DECISION SUPPORT / RESEARCH SIMULATION
Two flights are on a collision course. Ask the planner for a fix, approve it, and watch the gap reopen. Every step is checked against a fixed separation rule.
ONE PROPOSAL AT A TIME
Compare setpoints in the planner's original order. Reviewing leaves the live world and current approval intact. Choosing a different proposal requires a new approval and readback.
Options are alternatives, never a simultaneous batch. The original gate checks the selected proposal again before simulated application. Other conflict pairs may need another planning pass.
GO DEEPER
Minutes ahead · dashed line: configured minimum · orange band: simultaneous intrusion interval
Intervals use the continuous policy calculation. The 81 plotted samples are a visual guide; they do not decide conflicts. Equality meets a minimum. Times and distances shown here are rounded.
0° = north; 90° = east. Select a flight in the traffic register to edit it, or inject a new track.
These values feed the planner and safety gate.
Every marker advances from its velocity vector. Add, edit or perturb traffic; the solver recomputes the live world.
Save the traffic and complete separation policy in a local JSON file. Choose a file to review it before loading.
Loading replaces the traffic, policy, clock and selected flight. It clears pending proposals, approvals and the decision trace. The imported traffic starts paused.
No scenario file selected.
Paste a TowerOps state to run the same conflict detector and bounded planner on your own traffic. Export any live state to keep iterating.
One to 60 aircraft; finite numeric fields and unique callsigns required.
Search callsigns only. Search and order change this list; traffic keeps its course.
0 of 0 flights shown
No callsigns match this search. Clear the search to see all flights.
Check the recorded screening, approval, readback and actuation sequence. Pause traffic before a review. Opening a trace reads its history without loading aircraft or applying decisions.
No trace file opened.
Review up to 2 MiB of JSON and 5,000 events. Downloads preserve the original native trace.
Reviews the recorded gate sequence and world links. It does not rerun the safety policy, recreate aircraft movement or authenticate an approval.
Tune the active separation envelope. The Python policy solves unsafe time intervals analytically; it does not sample a decorative path.