Skip to content
Wyvern Watch mark

EAA AirVenture Oshkosh · KOSH

One window on the whole airshow.

Airshow Traffic Monitor brings live ATC audio, a wall of airfield video, and flight tracking together in one desktop command center — built first for AirVenture Oshkosh.

Download View on GitHub

Free & open source · macOS · Windows · Linux

The Airshow Traffic Monitor dashboard: a FlightRadar24 map beside a grid of live airfield webcams and a column of ATC audio channels

What it does

Three feeds, one window.

ATC Audio

Every tower, approach, and ground frequency at once — with priority ducking, one-click solo, activity lights, and stereo placement so you can tell who's talking without looking.

GUARD · FISK · TOWER · DEPARTURE

Live Video

A grid of EAA live webcams and YouTube feeds. Pop any tile out to its own window, fit or fill the frame, and maximize the panel that matters most right now.

EAA LIVE · YOUTUBE

Flight Tracking

A full FlightRadar24 view embedded right in the dashboard — the airfield, the patterns, and every contact overhead, live and interactive.

FLIGHTRADAR24 · KOSH

Multi-monitor

Spread it across the ramp.

Pop any camera into its own window and stack a wall of feeds on a vertical monitor, while the main dashboard keeps the map and the audio front and center. Close a pop-out and its feed docks right back where it belongs — your layout is restored every launch.

A vertical monitor stacking three live airfield webcam feeds — warbirds, vintage aircraft, and the flight line

Ready when you are.

Free and open source. Grab the latest release for macOS, Windows, or Linux — no account, no sign-up.

Download the latest release Browse the source

macOS (Apple Silicon) · Windows · Linux (AppImage)

Project documentation

Documentation index

Status: living | Audience: everyone — start here | See also: the product README (product requirements), Implementation-Plan.md

Airshow Traffic Monitor is a cross-platform desktop dashboard for watching air traffic in and out of an airshow — built first for EAA AirVenture Oshkosh. It unifies three feeds in one window: simultaneous ATC audio streams, a live YouTube video grid, and an embedded FlightRadar24 panel. This page is the documentation home; the map below is the split design-and-development tree behind it.

This tree is split by the question each half answers. design/ answers what and why in the vocabulary of the problem — it stays implementation-agnostic so the design survives any re-platform. development/ answers how and is free to name tools. If a sentence in design/ names a language, library, or tool beyond a brief parenthetical, it belongs in development/ instead.

What goes where

Location Holds Authoritative for
design/Personas.md Guiding principle, persona index + summary matrix Who this is for
design/Stakeholders/ One contract file per persona What each persona gives and gets
design/Audio.md All sound sources: ATC streams, video audio, tracker audio Audio behavior and its boundaries
design/Video.md Live webcam grid, layouts, pop-outs Video behavior
design/Tracking.md Embedded flight-tracking panel Tracking behavior
design/Weather.md Field-weather card: current conditions, forecast, flight category Weather behavior
design/Layout.md Panel tiling, splits, drag docking, maximize, snap templates + named layouts Main-window layout behavior
design/assets/ Prototype screenshots (the baseline this app replaces) —
development/TechStack.md Stack, rationale, limitations, alternatives Tool choices
Implementation-Plan.md Forward work only: phases, dependency graph, backlog, progress log What happens next
decisions/README.md Index of inline decision stamps Where each decision is recorded
archive/ (created on first use) Completed one-time plans — nothing here describes current state —
development/Pages-deployment-runbook.md Manual Pages source-flip steps and the deploy pipeline Publishing this site

Reading orders

For product understanding: design/Personas.md → the three Stakeholders files → design/Audio.md, design/Video.md, design/Tracking.md → Implementation-Plan.md

For engineering understanding: development/TechStack.md → Implementation-Plan.md → root CLAUDE.md (agent context; rewritten in Phase 0)

Also under development/: Getting-Started.md (zero-knowledge clone-and-run walkthrough) and Testing.md (test tiers and guardian rules), both landed with the Phase 0 scaffold.

Conventions

  • Every doc opens with a > Status: … | Audience: … | See also: … line and defers to its sources of truth rather than duplicating them.
  • Decisions are recorded inline where they're made, stamped (decision YYYY-MM-DD), with a one-line row added to decisions/README.md in the same commit.
  • Aspirations are marked "planned, not built" at the point of relevance.