A consistent record
Incoming observations are checked and duplicate deliveries are filtered out. Reception time and arrival time are kept separately, preserving the context of each report.
Connected Airfield Intelligence
Better airfield insight starts with what’s happening around you.
CAVOK Nodes receive ADS-B, FLARM and UAT signals locally. Pulse Server brings the observations together, with live traffic and receiver health available through the Console, airfield dashboards and connected screens.
01 / The network
One receiver brings a local perspective. A network of receivers can build a richer picture of aircraft activity.
Live traffic and receiver health in the Console, your airfield dashboard and connected displays.
01 Receive aviation signals locally
02 Connect securely to the platform
03 Build insight across locations
02 / Meet the hardware
A dedicated aviation receiver, positioned where the activity happens.
Prototype V2 combines Raspberry Pi computing, three radio receivers and Power over Ethernet in a custom enclosure with three antenna positions on top. Its software decodes locally, buffers observations and sends them securely to Pulse Server.
ADS-B, FLARM and 978 MHz UAT reception are all built in. Bring reports from equipped aircraft into one live view, or inspect each receiver’s traffic separately.
A bounded local queue holds observations during internet outages and sends them when the connection returns. Capacity is finite; extended outages can exceed it.
Receiver status, temperature, resource use and queue health are reported to the platform, helping operators spot problems without visiting the site.
Prototype V2 is under development, with field testing at Deanland. Reception depends on compatible transmissions, antenna placement, terrain and local conditions.
Discuss a deployment03 / Pulse Server
The platform behind the network.
Pulse Server receives observations from Nodes and maintains a current traffic view. The platform is running with the Deanland field deployment, supporting live monitoring, receiver checks and continued evaluation.
Incoming observations are checked and duplicate deliveries are filtered out. Reception time and arrival time are kept separately, preserving the context of each report.
Current aircraft reports include their contributing receivers and data age. Delayed observations are stored in history and kept out of the live picture; ageing positions are marked stale.
Operators can monitor Nodes, receiver performance and system health, with alerts for offline equipment, high temperatures and queue problems.
The Node is receiving at Deanland, with live traffic, receiver monitoring, airfield dashboards and Android-connected screens implemented. Field observations are helping us evaluate coverage and reliability. Automatic flight, arrival and departure detection remains planned.
04 / Ways to connect
From an operator’s browser to your airfield dashboard and clubhouse screen, put local aviation data where it is useful.
Implemented / Operator access
The web Console brings fleet status, individual Node history and live traffic together. A range-and-bearing view and aircraft table show position, altitude, speed and data age, alongside the receivers contributing each report.
Authenticated access, with accounts managed by the operator.
Implemented / Web app
Each airfield has its own dashboard for local traffic, receiver health, users and displays. Install it to the home screen in supported browsers for convenient access on compatible phones, tablets and computers.
Live information needs a connection. Only the app shell is cached; aircraft positions are never presented from an offline cache.
Implemented / Android display app
Pair a compatible Android TV device with your airfield to show Live traffic or Receiver status. Use the remote to switch between the screens your airfield makes available.
Manage connected displays and enable screens through the airfield dashboard, with central oversight in the Console.
Implemented / Integration foundation
Authenticated REST endpoints and a live WebSocket feed underpin the Console, providing a foundation for connections to other applications and airfield tools.
External access and permissions need to be agreed for each integration. Public self-service feeds are not currently offered.
Planned / Display
A dedicated board will turn detected aircraft movements into an arrivals and departures view for clubhouse and briefing-room screens.
Movement detection and the board layout still need to be built and validated. They will build on the existing display app and pairing system.
Have a display, app or data-feed use in mind?
Tell us what you need06 / Be part of it
We’re interested in speaking with airfields, flying clubs and aviation organisations about early participation.
Explore a dedicated source of aviation data at your own location.
Help connect more locations and contribute to wider coverage.
Discuss how the developing network could support your airfield.
07 / Let’s talk
Interested in a Node, display or integration? Tell us what you have in mind.
Whether you’re exploring a receiver location, a clubhouse board or data for your own application, use the message field to describe your plans.
This form registers your interest. It does not place an order or take a payment.
Network and product in development