Nine inbound flights, watched without refreshing a page.

The program's air manifest, parsed once and watched continuously. Delays, gates, diversions and cancellations arrive on their own, and because the manifest lives in the system of record, a flight that moves takes its pickup, its day-sheet row and its cockpit tile with it.

A manifest becomes watched flights. When one moves, everything downstream is told.

From uploaded manifest to the arrivals hall

  1. Upload & parse

    The manifest as it arrived. AI extracts passengers, flights and codes; you confirm. Card and table views from there.

  2. Watch live

    Webhook push for status changes, polling fallback for belt and braces, and a trackability check that's honest about what can be watched.

  3. Check off at the belt

    The airport team gets a realtime token page: search, tick, done. Progress streams to the home board and the client's window.

The manifest is the program's nervous system.

Everything on an arrival day keys off flights: pickups, staffing, the first dinner's headcount, the client's anxiety. A standalone tracker can tell you a flight moved; only a tracker inside the system of record can move the pickup, re-time the day sheet row and update the cockpit in the same breath.

  • Delays, gate/terminal changes, diversions, cancellations
  • Passenger list download for the people who want paper
  • Feeds Arrival-to-Ground clustering directly
  • Included on every plan

Flight tracking questions

How does the manifest get in?

Upload it in the shape it arrived: spreadsheets and the formats group desks actually send. AI parses passengers, flights and codes into records you confirm, and the same manifest then powers tracking, check-off, transfers and the cockpit.

How live is “live”?

Status changes arrive by webhook push from the flight data provider, with a scheduled polling fallback underneath so a missed webhook never means a missed delay. Delays, gate and terminal changes, diversions and cancellations all land on the flight record, and ripple to whatever depends on it.

What is the airport check-off page?

A token link for the airport team: no login. Search by name or group, tick guests off as they clear arrivals, and watch it sync in real time across every device holding the link. The count feeds the home board and the Client Cockpit's “612 of 840 landed”.

Which providers are supported?

FlightAware AeroAPI and AviationStack, both implemented behind one provider interface, so the product doesn't care which is live, and neither do you.

See it on your own programs.

A 30-minute walkthrough with the team, on data that looks like yours. Sales-led onboarding: we load your catalog, your vendors and your first programs with you.