Helicopter line patrols, drone inspection sorties, and post-storm air operations all share the sky with everyone else. Point an ASTERIX CAT-048 UDP multicast feed at VoltGrid and every active radar track lands on the map and in a live Track Table — with velocity vectors, trails, automatic emergency-squawk alerting, and a closest-point-of-approach calculator between any two tracks. The same overlay pattern then serves ADS-B, AIS, and APRS: one platform, every track source.
Open the Track Table and you see every active radar track in a sortable, filterable grid — callsign, squawk, flight level, speed, heading, type, ICAO24. Select any two tracks and click CPA to compute their Closest Point of Approach: time, distance, and bearing. When a patrol helicopter and an inspection drone are working the same corridor, that's the calculation your flight coordinator needs — in the same window as the map.
// live track table — sortable, filterable CALLSIGN SQUAWK FL SPD HDG ICAO24 BAW192 2044 350 462kt 094° 400ABC DLH4TX 1362 280 431kt 187° 3C66B1 N481TC 7700 085 164kt 221° A5D2E8 ⚠ EMERGENCY cpa(BAW192, DLH4TX) → time · distance · bearing ● ingesting cat-048 · vectors +3 min · trails ×30
Each track renders with the display elements a radar operator expects — and the alerts a flight-operations supervisor can't afford to miss.
A heading-by-speed projection drawn 3 minutes ahead of each track — the standard ATC display element — so closure develops on the screen before it develops in the air over your corridor.
7500 (hijack), 7600 (radio failure), and 7700 (emergency) are auto-detected the moment the squawk changes: pulsing red marker on the map, toast notification, and a StatusBar alert.
The last 30 positions per track render as fading dashed polylines — history and intent at a glance, without a replay tool.
Callsign, squawk, flight level, speed, heading, type, ICAO24 — every active track in one sortable, filterable grid beside the map.
Closest Point of Approach between any two tracks: time, distance, and bearing. Deconfliction as a click, not a mental math problem.
Temporal, movement, and pattern-of-life analytics run against tracks through the DuckDB TrackSourceRegistry — the same hub that serves every other layer.
The Track Table, trails, vectors, and analytics aren't a radar-only feature — they're the platform's track pattern. ADS-B, AIS, and APRS feed the same DuckDB hub and inherit the same tooling.
Aircraft and RemoteID drone tracking from software-defined radio via readsb / dump978 — a cooperative air picture over your service territory alongside the primary radar feed.
Vessel tracking through rtl_ais with an NMEA VDM/VDO decoder — surface awareness where lines cross navigable water, on the same map and hub.
Amateur-radio stations, weather reports, objects, and messages from both RF and APRS-IS — the volunteer and emergency nets that light up during storm response, on the same overlay pattern.
Track rows, callsigns, and values shown in the terminal graphic are illustrative sample data, not recorded traffic. CAT-048 ingestion requires a radar feed reachable on your network as UDP multicast.
CAT-048 in, decision-quality air picture out — Track Table, CPA, squawk alerts, trails, and analytics running today on a laptop in the EOC or a storm-room trailer, connected to nothing but your feeds.
