Loading report…
Live operations
Watch
Live feed health, inbound traffic, and the tracks currently in view. Select any track for its full detail.
Feed status
Waiting for the first snapshot…
Active weather alerts
Waiting for weather data…
Inbound
Nothing inbound in current data.
Track list
No tracks in current data.
Track detail
Select a track card or a map marker to see its detail.
Operator summary
Brief
Briefs are built from real stored data only. A degraded feed produces a coverage caveat, never an unqualified “all clear.”
Record and review
History
Review alerts, label what was useful or noise, manage mutes, and open the incident reports generated from this site’s record.
Labeling queue
Labeling coverage is loading…
Loading labeling queue…
Alert history
Labeling coverage is loading…
Loading alert history…
Active mutes
Loading mutes…
Reports
Loading incident reports…
Model Health
Loading model health…
FAA airspace and drones
Airspace
Airspace information is for planning and awareness only. It is not an authorization to fly, and the official NOTAM always prevails.
LAANC grid
Waiting for airspace data…
LAANC legend
Temporary flight restrictions
Waiting for TFR data…
Drones and Remote ID
No receiver connected.
Receiver token management
Pilot location is generalized and never stored.
Site and product controls
Settings
Watch site
Airport Finder
Advanced custom site
Alert rules
These settings persist on the server and the evaluator honors them from its next cycle. When nothing has been saved yet, the built-in defaults shown here are in effect.
Phone alerts
A push-service acceptance proves the send path, not that a person saw the notification. On iPhone, install the site to the Home Screen before enabling push.
AIS key status
Owner access
Trust & Data
Definitions & limits
- LIVE
- Connected and receiving current data.
- LIVE-EMPTY
- Connected and healthy — nothing to report right now (for example, no aircraft inside the ring). Empty is a finding, not a failure.
- SAMPLED
- Intentionally intermittent — the vessel feed. The source is heard in windows with gaps between them, by design: a lighthouse sweep, not a continuous stare.
- STALE
- The feed was reporting and stopped. The age shown is the time since its last successful report.
- ERROR
- The last attempt failed; the provider’s reason is shown with it. Nothing is ever drawn from invented data while a feed is in ERROR.
- FAA rate limit
- The LAANC airspace grid comes from the FAA’s public UAS Facility Maps service, which limits how often it will answer. Asked too quickly it temporarily refuses (“Too many requests”) and clears on its own schedule. Only the grid layer is affected; the grid is reference context, not an authorization.
- Vessel departures
- “No vessel shown” never establishes that no vessel is present. A vessel is recorded as departed only after it has been absent for more than 30 minutes while the feed was receiving.
- Retention
- Observations are kept 7 days and alerts 30 days, then deleted automatically. Incident reports are the permanent record and are never edited after generation.
- Incident report integrity
- At generation, each report is fingerprinted with SHA-256 over its exact contents. The fingerprint is printed on the report and stored twice: in the report record and in a separate audit record. Any later change to the stored report — even one character — breaks the fingerprint match. Anyone holding a report can check it at app.laufey.si/verify.html; the check reveals nothing about the contents. Reports generated before fingerprinting carry a fingerprint recorded later, labeled with its recording time; it covers the contents exactly as stored at that time.