Audience Fit
Built for analysts, operations centers, security monitoring teams, and aviation research workflows.
← Knowledge Base
Data Transparency
Data Sources & Evidence Model
This article explains where SkyGrid data comes from, how detections are classified, and how to integrate outputs into review, triage, and delivery workflows.
Detection Model
Eight anomaly detection classes — loiter, ghost, squawk, rapid-descent, ICAO spoof, formation flight, callsign duplicate, and GPS jamming — are persisted with time and location context.
Boundaries
Event classes are advisory indicators. Human review is expected before operational action.
How detections are generated
- Loiter: aircraft remains in the same H3 cell beyond configured dwell threshold.
- Ghost: missing callsign with valid position and airborne-enough altitude profile.
- Squawk: emergency transponder codes 7500, 7600, and 7700.
- Rapid-descent: altitude loss rate exceeds safe-descent threshold over a rolling window.
- ICAO-spoof: ICAO24 address appears in conflicting geographic locations simultaneously.
- Formation-flight: multiple aircraft maintain correlated heading, speed, and proximity beyond chance.
- Callsign-duplicate: identical callsign observed on distinct ICAO24 addresses within overlapping time windows.
- GPS-jamming: position jitter, impossible ground-speed, or sudden position jumps consistent with GNSS interference.
SkyGrid stores event metadata for workflow and auditing. It does not assert legal intent from a single event.
Reference endpoint surface
Key endpoints for integration. See the interactive API docs for full schemas.
GET /api/v1/network/mission-summaryGET /api/v1/network/anomaly-leaderboard?window=24h&type=allGET /api/v1/watch-gridsGET /api/v1/watch-grids/{watchGridId}/historyPOST /api/v1/webhooksGET /api/v1/network/liveGET /api/v1/network/aircraft-snapshotGET /api/v1/network/recent-anomaliesSample anomaly payload
Representative structure used in review and webhook delivery flows.
{
"anomalyType": "squawk",
"aircraftIcao24": "4ca812",
"callsign": "UNKNOWN",
"squawk": "7700",
"latitude": 51.88026,
"longitude": -0.37831,
"observedAt": "2026-04-09T20:15:17Z"
}