24/7 fleet visibility.
ADS-B live. SSE auto-refresh. No tab-switching.
Charter flight following has historically meant subscribing to a separate ADS-B tracker, alt-tabbing to a third-party map, and praying your dispatcher remembers to check on it. AeroCopilot Ops folds it into the dispatch board.
ADS-B Live Feed
Direct ADS-B integration via our beta API. Position, altitude, ground speed, and squawk update every few seconds. No 3rd-party tracker subscription required.
MapLibre Live Map
Vector-tile aviation map (FAA sectionals, IFR low/high, weather radar overlays) with every active flight from your fleet pinned in real time. Click a flight to see release, crew, and live tail-side data.
ETA-Aware Overdue Alerts
Overdue logic that knows the difference between weather hold and a missed checkpoint. Alerts route to the dispatcher on duty with FAR §135 incident-reporting templates pre-filled.
SSE Auto-Refresh
Server-Sent Events stream updates to the dispatch board without polling. The board stays current while you work in another tab — no manual refresh, no stale data.
Flight following, properly integrated
The standard charter flight-following stack is two or three separate tools: a dispatch system, a dedicated ADS-B tracker, and an SMS notification service for overdue flights. Each tool has its own login, its own data model, and its own gap where information falls through.
AeroCopilot Ops merges them. The release that the dispatcher built is the same release the live map is tracking. The tail number on the dispatch board is the same tail number on the ADS-B feed. When the flight is overdue, the alert references the release ID and the last-known position — not a generic "tail N123AB late" ping.
ETA-aware overdue logic
A flight that's 10 minutes late because of a wind shift is not the same as a flight that's 10 minutes late because the dispatcher hasn't heard from the captain in 90 minutes. AeroCopilot Ops uses the filed ETA, the in-flight ground speed, and the last ADS-B position to compute a real overdue threshold per flight — not a static 15-minute timer.
When the threshold is crossed, the alert escalates: dispatcher first, then chief pilot, then DOM. Every step is logged. If the flight turns into a §135 incident, the report template is pre-filled with the timeline, the last-known position, and the contact attempts made.
Built on MapLibre, not Mapbox
We use MapLibre GL JS (MIT license, no per-MAU billing) with custom vector tile sources for FAA sectionals, IFR low/high charts, and weather radar overlays. That keeps the cost flat as your fleet grows — and lets us ship layers your incumbent never will.
Example overdue alert
N123AB · KSNA → KAPA · ETA +12 min · last ADS-B 42 nm SE KAPA at FL230 · radio check requested · escalating to chief pilot in 5 min
Watch your fleet move in real time.
We'll demo the live map with sample tail numbers from your fleet — or ours, if you prefer.