ADS-B · a home-made project

ZenithBoard: what flies above me

An old tablet on the wall, a Raspberry Pi and a USB radio dongle with an antenna. Together they show, like an airport departure board, every aircraft flying within a few kilometres of home, share what the antenna hears with the big flight-tracking networks, and can tell Bluesky what went over, and send me a private message when an aircraft squawks an emergency. Everything is received and decoded at home, by my own ADS-B station.

The wall in its demo mode, which runs without an antenna: invented airlines, illustrated photos.

Why I built it

Ever since Shannon, I look up when a plane goes over. A flight-tracking app answers the question, but it means taking a phone out, opening a map and searching. I wanted the answer to simply be there, on the wall, the way a departure board is just there in a terminal.

Ready-made displays exist, and I like them. But I already ran my own receiver, and an old tablet was sitting in a drawer. So the idea became: recycle the tablet, use my own station’s data, and make the whole thing free and open for anyone with the same parts. That is ZenithBoard, the board that shows what is at your zenith. Its front door is zenithboard.app; this page tells the story behind it.

What it does, in one picture

One small computer, five jobs, each one optional except the first:

  1. A receiver that feeds the networks. The antenna hears the aircraft; the Pi decodes them and shares them with ADSB Exchange and, if you wish, FlightAware, Flightradar24, Plane Finder and AirNav Radar.
  2. The wall. Any tablet or screen with a browser shows the aircraft overhead, as glowing dots or as an airport split-flap board.
  3. The posts. The aircraft worth a post go to Bluesky, as a picture of the wall, with weekly summaries.
  4. Private messages. The same crossings, and the emergency squawks heard anywhere in range, as text messages to my own Telegram chat.
  5. The statistics and the console. Pages served at home show what the antenna heard and let you change every setting from a phone, and Tailscale makes them reachable from anywhere without opening a port.

All you need is a Raspberry Pi (a 1 GB Pi 3B runs everything, measured: on mine, with the five networks, the wall, the posts, the Telegram messages, the statistics and Tailscale, 436 MB of its 905 are still free), an RTL-SDR USB dongle with a 1090 MHz antenna, and any old tablet, phone or screen with a web browser. Nothing is installed on the tablet: it just opens a page served by the Pi.

Installation: a guided wizard

The installer is written for someone who has never opened a terminal. Write Raspberry Pi OS to the card, connect to the Pi, download ZenithBoard and start it: four questions (the region, the units, the antenna’s position, how close an aircraft must be to appear), then Start here takes you through the first installation in order, skipping what is already done.

Start here: the first installation in five steps. Each can be done again later from its own menu.

The wizard ends in the browser, in the web console. Afterwards, each subject has its own menu of seven entries at most: ADS-B, the wall, connectivity, troubleshooting, updates, backup and options. Everything in the menus also exists as a command. A few habits from my day job are built in:

  • Everything optional is off by default, and every switch can be turned off again, putting back what it found.
  • Irreversible steps ask for a typed word, such as uninstall, rather than one Enter too many.
  • One backup file moves a whole ZenithBoard to a new card: settings, statistics, logs and the networks’ identities.
  • Updates are checked before they run: the new code must carry a valid signature, and a setting you chose is never changed behind your back.

Sharing the feed

A cheap dongle hears more than one person needs, so the antenna works for everyone. ADSB Exchange, the open network that does not filter what it receives, is always on. FlightAware, Flightradar24, Plane Finder and, since 30 October 2026, AirNav Radar (once RadarBox) are ticks in a list, and each one’s own installer runs with the screen telling you what to answer. AirNav Radar makes its own sharing key on the Pi; the terminal prints it with the three steps to link the station to an account on their site. Unticking a network removes it.

One rule came from measurement, not taste: only one MLAT client runs. MLAT works out the position of aircraft that do not broadcast one, from the timing of their signals at several receivers; several MLAT clients on one small Pi overload it, so ADSB Exchange keeps the only one and the installer switches it off in the others. An optional switch also fills in ADSB Exchange’s own statistics for your feed, with a map of what your antenna hears.

The wall

The wall shows the aircraft inside the radius you choose, nearest first, fourteen seconds each: the flight and the registration, the airline, the model, altitude and speed, where the flight comes from and where it goes, then the distance and direction from the antenna. Top right, a silhouette that matches the aircraft: an A380 is drawn as a four-engine airliner, a Cessna as a light aircraft, an F-16 as a fighter. Bottom right, a real photo of that very aircraft from Planespotters, credited to its photographer and loaded by the tablet itself, as their terms ask; without one, an animated sky that follows the time of day.

There are no logos, by rule: airline and maker logos are trademarks. Two small flags stand in for them, where the aircraft is registered and where it was built, read from the registration itself without asking the internet.

The same data has a second look, chosen per tablet or for the whole house: the split-flap board of an old airport hall, whose letters roll one by one until they land on the next aircraft.

The split-flap look: same data, letters on flaps.

Five colours, amber by default. A faint gear in the corner changes the look, the units, the radius or the colour for one screen, and named presets give each tablet its own address. The wall answers the home network only.

Posts on Bluesky, and the week in figures

Off by default. Switched on, the Pi posts the aircraft worth a post, by rules you choose (military, helicopters, heavy aircraft, rare types, the farthest of the month, or every crossing), as a picture of the wall beside a map of the aircraft’s track. The account’s bio says it is automated, and that its texts come from templates, not AI.

A post's picture with the map switched off: the track drawn in dots. Demo data, invented flight.

The map is centred on the aircraft, and posts carry no photo, only a link to its photo page if you switch that on. The words come in several styles, or your own templates, in the language you choose. Summaries of the day, the week and the month go out at the time you pick, from the statistics below: the aircraft heard, the busiest day and hour, the airlines and models most seen, then the cargo airlines and business jets, the military aircraft by country, and general aviation.

A weekly summary picture, its title and dates left out.

Statistics at home

Also off by default, and cheap: one sample every fifteen minutes, about 30 KB a day on the card. The statistics page, served by the Pi in the wall’s look, shows the last 24 hours, 7 days or 30 days: the aircraft heard, the messages, the farthest aircraft with its route, the sky hour by hour, the airlines with their flags and the models most seen, cargo and business jets, military aircraft by country, and how high they fly. For years of the decoder’s own graphs, graphs1090 can be added in the same look.

Part of the statistics page from my own Pi, over seven days.

The same counters decide what to build next: they note the airlines the wall cannot name and the aircraft it can only draw with a generic shape, so the next features are chosen on figures, not guesses.

The web console, in your language

Every setting is also in a web console served by the Pi: an overview of the machine and each service, then the wall, the receiver, the posts, the watchdogs and the updates. A side bar on a computer, tabs at the bottom of a phone, in twenty-two languages. A phone signs in once with a QR code. It is off by default, answers the home network only, and each change it makes runs the same command as the menu, through a small helper that accepts only a fixed list of actions.

The console's overview, from my own Pi. The Wi-Fi name is hidden.

Telegram, for me alone

Bluesky is public. Some things I want to know are not for a public feed, and since 30 October 2026 the Pi can also write to my own Telegram chat: plain text, sent by a bot I made in two minutes with Telegram’s @BotFather, to a chat or a group of mine and nobody else’s. Off by default, like everything else.

Two kinds of message. The crossings, one per aircraft, under the same rules as the posts or narrower (military, helicopters, heavies): the flight and the airline, the model with its registration and flag, the route, the altitude and speed and whether it climbs or descends, the time, and a link to the aircraft on ADSB Exchange. And the emergency squawks, 7500, 7600 and 7700, heard anywhere the antenna reaches rather than only overhead: once per flight and code, believed only when heard twice in a row or confirmed by the aircraft’s own emergency status, with the meaning of the code and the nearest town. Those are never posted to Bluesky: an emergency is not a fact to broadcast.

The first evening of messages, 30 October 2026, in French. The place name is hidden here.

The bot’s token is typed once in the terminal and stays on the Pi, readable by the service alone; it is never in the settings, a log, a backup or the web console. The chat is picked from those that wrote to the bot, never typed. Everything else is in the console: which crossings, the squawks, the language, the units, and my own words for each kind of message.

The Telegram card in the web console. The chat's name is hidden.

From anywhere, with Tailscale

The wall, the statistics and the console are made for the home network, and nothing on the Pi has to be opened to the internet. To see them away from home, the menu installs Tailscale: a free account, an app on your phone, a sign-in link and its QR code, and the Pi joins your own private network. It works behind the shared addresses some providers use, where no port could be opened anyway. Disconnecting is one entry; removing it completely asks for a typed word.

The Tailscale menu. Read first, then install and connect.

Built with an agent, proven on a real Pi

I did not write the code: an AI coding agent did, under rules I wrote, and every change was accepted by me after seeing it on the real wall or the real Pi. The rules are short: no logos; never switch off a signature check; features off by default; every change reversible; nothing ships that nobody has seen; figures checked on the real service or the real Pi, never guessed. Every ZenithBoard service runs in a sandbox that keeps only what its job needs, and zenithboard security checks the running Pi and says how to close whatever is open.

The project’s status page keeps two columns, what has been proven on a real Pi and what is only written and unit-tested. Version 1.0 will mean the second column is empty: a fresh install on a blank card finished from the web console, a month hands-off, and an update from an old release with nothing done by hand.

The features were frozen on 25 October 2026: the 0.99 releases are the release candidate, fixes only. I broke my own freeze once, on 30 October, to let AirNav Radar and the Telegram messages in, and the price is written in the roadmap: the month hands-off starts again from that update, so 1.0 comes on 29 November 2026 at the earliest, if nothing is left open. Anything else asked meanwhile waits for 1.1.

Watch it

ZenithBoard in one minute: the wall, the five networks, the posts, the Telegram messages, the statistics and the console.

YouTube videoWatch on YouTube

ZenithBoard has its own YouTube channel, @ZenithBoard-ADSB: the wall, dot matrix or split-flap, the Bluesky posts, Telegram messages and statistics, and the 30-second Short. A new Short comes every week.

Read more

ZenithBoard is free and open source (GPL-3.0). Its home is zenithboard.app; the installation guide, every command and a demo that runs without any antenna are on GitHub.

Published , updated .