Simulated scenario — no real aircraft, no real sensors, no live data. Every number on this page was produced by a seeded simulation in the skytrace source and written to a self-contained HTML file by ./run.sh demo, regenerated locally on 2026-09-02. There is no feed behind it and nothing updates; the playback controls replay a recording that is baked into the file.

skytrace is a passive sensing concept: a mesh of microphones and receivers, time-difference-of-arrival multilateration, and a ranked warning. It does no jamming, spoofing, takeover or engagement, and the package contains no network capability at all. The threat-escalation thresholds are the project's own invented choices, not any national standard. Not an operational system and not an emergency service.
← all four scenarios

skytrace passive RF + acoustic drone detection · scenario: airfield

A commercial quadcopter approaches a protected airfield from the south-west while its pilot stands 1.4 km off the perimeter. The mesh locates both -- the aircraft by multilateration, the pilot twice over: once by multilaterating the controller uplink, and once by simply decoding what the aircraft broadcasts about him.
node (RF+acoustic) node (RF only) confirmed track + 95% ellipse tentative track ground truth protected asset

The shaded background is not a result. It is the Cramér–Rao lower bound on rf position accuracy evaluated on a grid at 120 m altitude — the best any unbiased estimator could do with this geometry and these clocks, computed before any target exists. Green is under about 25 m; red is beyond 250 m. The cliff at the edge of the node footprint is why detection range and localisation range are different numbers. The modality shown is whichever one this scenario actually depends on: drawing an RF bound for a target that emits no RF would describe a capability that will never be used against it.

Scorecard — measured against truth

emitterfixesp50p90in 95% trksdetloc
operator546 m14 m100%13.4 km0.7 km
quad1768 m65 m99%18.3 km3.5 km

Covariance calibration: truth fell inside the stated 95% ellipse 97.0% of the time. An honest system lands near 95%; well below means the error bars are too small and every downstream decision inherits that over-confidence.

Alerts this scan

Live tracks

Timing — the whole accuracy budget

At the speed of light 1 ns of clock disagreement is 30 cm and 1 µs is 300 m. Nothing else in the system matters as much.

Mesh

frames sent2283
delivered to hub2283
relayed (multi-hop)1984
dropped by link loss97
forged / tampered rejected0
replays rejected0
nodes able to reach hub9 / 9
hub key fingerprint7e37bdf90daf1c8b

Every detection above crossed this mesh — X25519 key agreement, ChaCha20-Poly1305 per frame, authenticated routing headers, sliding-window replay rejection — before fusion was allowed to see it. A frame the mesh loses is a detection the picture does not contain.