Traffic Monitoring
DEMO DATA

DEMO WORKSPACEIllustrative traffic only. No authorised PTFS feed is connected.

Feed setup

EVIDENCE-BASED ADVISORIES

Traffic Monitoring

Deterministic checks against ATC-assigned values and verified geometry. Advisories never issue clearances or replace ATC judgment.

Operational limits

No production alerts are generated without an authorised feed. Routes require matching, source-verified chart coordinates. Geographic crossing-track checks require fresh latitude/longitude, altitude and compatible observation times; heading and groundspeed enable constant-velocity prediction. Pair checks are capped at 250 geographic and 100 runway-associated aircraft per evaluation. At most 15 new alert records are opened per evaluation to bound notification work; additional conditions are processed in later evaluations. There is no guarantee of separation or collision avoidance.

Runway/approach advisories require explicitly evidenced provider phases and ATC source-verified runway records at the same airport. They do not independently verify runway occupancy. Missing fields disable the corresponding check.

Departure queue · 0

    No verified flights awaiting pilot-reported departure.

    Controller workload

    0 active/scheduled filings · 0 unresolved advisories

    Demo data is not evaluated or presented as production alerts.

    Configurable tolerances

    Supervisor / Owner changes are audited. Thresholds are advisory settings, not a certified separation standard. Feed freshness indicators retain their provider's separate 45-second rule.

    ⚡Make an app like this, free